A Beginner’s Guide for Contributing to DEM V2

Being part of an open source project means more than just writing code — there are many ways that you can contribute.

Since all the source code for the DEM V2 is open, it's possible to get deeply involved, both in tracking down issues and making significant product changes.

What Contributions Will We Accept

In short, we’ll entertain anything that makes the DEM V2 product better in terms of stability, quality, and capability. This may take the shape of:

  1. Report issue or open the proposal
  2. Bug fixes
  3. Feature implementations
  4. Write UI Tests
  5. Improve documentation
  6. Add new amazing Styles and Themes
  7. Update translations or add new languages
  8. DevOps (Release, Deployment, Publish ...)
  9. Create short explainer videos or/and technical blogs
  10. Invite others to participate

Before you even start writing code, unless its a small bug fix, it is best to subscribe to mailing list and discuss your changes.

Community

The DEM V2 open source community includes developers from around the SEE region. For the latest information and discussions on the topics you’re interested in, join our official communication channels.

Although a lot of discussion happens on the public mailing lists, the community also engages in interactive discussion on Microsoft Teams DEM general channel.

Bug reporting

We encourage developers to use our software and help us make it a stable, feature complete and reliable system. In order to achieve that goal, we ask you to report bugs as you find them.

How to contribute a great bug report

Writing a good bug report helps our developers (and other contributors!) figure out where a problem exists and improves the likelihood your bug will get fixed quickly.

Great bug reports:

  • Describe the problem as clearly and concisely as possible, including a description of what happened and was expected to happen.
  • Include any stack traces, error message text, or crash logs.
  • Describe the environment and device where the bug was encountered.

If any dependencies are required to reproduce your bug, please include information about where to download the correct versions of required dependencies.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact us with any additional questions or comments.