The simple and fun number combination game #-ludus goes 2.0 and open source.
#-ludus ia a android game with the goal to eliminate all the numbers on the game field by combining those numbers that are same or sum up to 10.
The player starts of with three rows, filled with the numbers from 1 to 19, without the number 10, as discrete digits.
He then has to eliminate all numbers by combining those above or next to each other (over empty fields and over new rows are also allowed).
If the point of no further combinations is reached, the remaining numbers get added to the end of the game field again, without the empty spaces.
This game flow continues until the player eliminates all the numbers on the game field.
Everybody is welcomed and pleased to contribute to this project.
If you are interested, there are several ways you can contribute:
- Distribute #-ludus to the world by telling your friends, posting on your social networks or writing in your blog about it
- Joining the google group to get beta access, download the app, test it and report bugs or submit enhancement ideas to the issue tracker
- Fork the repository, contribute to the code by fixing bugs, implementing features or translating the app
No matter in which way you contribute to this project, the community and users are thankful.
To contribute by fixing bugs or implementing features try to follow these steps, so that the community can track your work:
- (For features, not mandatory) Discuss the new feature idea in the google group to find out what the community thinks and for help in finalizing the idea.
- If not already present state a new issue explaining the bug or feature and write a comment saying that you are working on this bug/feature.
- Keep the issue up to date by reporting the state of your work (mainly for time taking fixes or implementations).
- Create a pull request with a link to the issue this PR is going to fix/implement (see "Creating a pull request" section bellow for detailed description).
The project contains two places where it contains locale files, one in the source code under app/main/res/values, which are for the app it self, and one under resources/strings, which are for external strings like the play store. To translate the locale files in the source code just follow the android way of working with locale string files. The files in the resources folder follow a similar structure, just create a new file .xml, copy the en.xml content into it and start translating the texts between the xml tags (!!!DON'T CHANGE THE TAGS!!! ONLY THE TEXT!!!)
To keep the code and the history as clean as possible only PRs with the following structure are accepted:
- The code is constantly checked by travis-ci. There for the code must always be able to pass the
./gradlew buildcommand. This command builds the project and checks for linting errors. For the contribution to pass this build it may not contain code that fires a lint error or warning. If for some reason a rule has to be added to the ignore list in the lintOptions section of the gradle build file, this has to be stated and explained in the PR, in order to discuss if a exception is made. - A PR must consist of only one single commit. This doesn't mean that one may not commit any changes during work in progress, but has to squash his commits before the PR is merged. For help on squashing commits, read this post.
- Branching model describing the desired work flow.
- Github contribution guidelines for contributing to an open source project.
- Github fork guidelines for forking to an open source project.
- Android way of handling locale files.
- Squashing multiple commits into one.
Feel free to ask any question that comes to your mind in our google group, not because it would bother me if you write me an e-mail, but because I there is no such thing as a dumb, stupid or useless question and therefore it might also be of value for somebody else.
| Translater | Language |
|---|---|
| Şafak Eşberk | Turkish |