Veripeditus is a project in a very early stage. While we are planning to release a first preview in November 2016, things may be changing a lot and we do not have a real roadmap yet. However, there are quite a few things that are well-defined and the scope is clearly known. So if you want to contribute, feel free to do so!
- FInd something you want to do in the issue tracker.
- Read the issue description and any comments carefully.
- Try looking at the relevant sources.
- Ask any questions that may arise.
- Take feedback into account and start hacking!
Please mind the following:
- Fork the project, then create a new branch.
- In this branch, only work on a specific issue. Do not mix issues!
- Do micro-commits. Each logical step in your development should be one commit.
- Write clear commit messages (look at the log for ideas).
As strange as this may sound, technical debt is planned into the Veripeditus development at this stage. We want to explore what can be done and produce something that works and can be shown. After the first preview release, we will tidy up (yes, we will - no further development will take place until we really did!).
That means that you do not have to worry too much about the code you contribute, as long as it is cool.
Please try to avoid adding dependncies if possible. If you really need to add a dependency, please try to use something that is available as a Debian package. If you can't, please discuss the problem in the issue you are working on!