Self explanatory. A good readme should probably answer some or all of these questions:
- What is this project all about?
- Who made it?
- How do I use it?
- How do I contribute?
- Can I copy this and use it in my own project (eg: license, fork & deploy instructions)?
- Are there coding/style standards for contribution?
- What help does this project need?
Working on this as your first Open Data DE issue?
This is a great first issue for all skill levels because it mostly involves asking people questions and creating a single text file (Readme.md) with the answers. It's also a great way to get to know more about this project and other ideas that Open Data DE contributors have for future projects.
Self explanatory. A good readme should probably answer some or all of these questions:
Working on this as your first Open Data DE issue?
This is a great first issue for all skill levels because it mostly involves asking people questions and creating a single text file (
Readme.md) with the answers. It's also a great way to get to know more about this project and other ideas that Open Data DE contributors have for future projects.