First of all, new contributors are always welcome in Glimpse Framework.
Programming is a social activity. ― Robert C. Martin
Please do not use labels other than:
- android—for issues related to Android implementation
- bug
- feature
- refactoring
If you have found a bug, don't hesitate to report it—even if you're not sure if it's a real bug. False alarms are better than hidden bugs.
Label the issue as a bug.
If you'd like to see a new feature in Glimpse Framework, just create a new issue. Each request will be taken under consideration.
Label the issue as a feature.
- Indentation with tabs, and tabs only.
- Lines no longer than 160 characters—a maximum line length visible in a typical IDE without scrolling. A tab counts as 4 characters.
The following rules are direct quotes from Uncle Bob's Clean Code: A Handbook of Agile Software Craftsmanship:
- It is not enough for code to work.
- Leave the campground cleaner than you found it.
- A long descriptive name is better than a short enigmatic name. A long descriptive name is better than a long descriptive comment.
- When you see commented-out code, delete it!
- Building a project should be a single trivial operation.
If you haven't read Uncle Bob Martin yet, you probably should.
Whenever you submit a pull request, make sure your changes are tested.
Typically, CodeCov will approve pull requests with:
- at least 85% overall coverage,
- at least 75% coverage of your changes.
However, these are only suggestions, and every change will treated individually. Your pull request might be accepted even when the coverage is 0%, if you can justify it.