Skip to content

How to help

Raphael Mack edited this page Mar 4, 2018 · 7 revisions

These days are awesome, because this app attracted a few users, some even willing to help. So let me try to do something for them. In all cases please consider the Code of Conduct and the notes on licensing and contribution

Translation

Translating is not very complicated but very important. ActivityDiary uses crowdin for text translations. To start with a new language go on like that:

  • register a free-of-charge account on Crowdin
  • open the project site and click "Join Translation Project"
  • validate existing translations and add translate the missing strings
  • fork the repository on github and clone that one to your disk
  • add screenshots or links to videos in your langauge in app/src/main/play//listing/; commit and push them, afterwards create a pull request on github.
  • Note, that by the act of suggestion translations on crowdin to this project or sending a PR you release your work under the terms of the General Public License v3 or later.

Testing

So far I have not really distributed versions for testing. Even though I am not a play store fan I could use the beta track there to easily distribute testing version. Please get in contact with me, whether this would help. In that case you would be able to get early versions with the same APP ID, and therefore also acting on your real data. It is what I personally also do, but there is the risk that the data gets corrupted - even though I do my best to prevent that.

An alternative would be to distribute apks with a debug version, which you can install in parallel to the live version of the app, so you can use the stable version in daily life and still try pre-releases.

Please let me know what you prefer, that I can setup this.

In all cases you can export your data from the settings menu and also import this, after you reinstalled the app or to move data between debug and release apks back and forth.

Contributing Code

The level for the advances users is for sure code contribution. You can always send pull request, and I am happy about those. Nevertheless, I would suggest, that you first discuss in a ticket the feature you want to add or the bug you wanna fix. You can select one of the issues tagged with "help wanted" but finally the best would be to start with something you personally are interested in.

Clone this wiki locally