Thanks for throwing some effort into helping us improve our project! This is a set of guidelines to contributing to the UserLAnd Android application. These are intended as just that: guidelines, so use your best judgement when submitting contributions.
All contributions must follow the UserLAnd Code of Conduct.
Please talk with us here in the form of a PR or an issue.
We follow the MVVM-C architecture in UserLAnd. UI updates should exist exclusively within XML and be inflated exclusively from
view-controllers like activies and fragments. Business logic should be decoupled from the Android framework as extensively
as possible, and live somewhere with the model
or utils
package. Application layer logic should exist within the
viewmodel as much as possible.
- Submit an issue describing the problem you will be solving with your contribution if one doesn't exist. Assign yourself to the ticket.
- Fork from master.
- Write your code.
- Write tests your code.
- Run the test suite to ensure
./gradlew testAll
. - Ensure that your code follows our styling by running
./gradlew ktlint
at the root of the project. - Submit a pull request to master!
Commit Messages
- Use present tense.
- Keep the first line short, but feel free to reference issues etc. in lines after.
Branch Names
- Reference issue number in branch name.
- Describe issue solved in branch name as briefly as possible.