CMS-Android fork (see also:
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Fynn Godau 806fa38fd6 Benefit from TypedRecyclerViewAdapter 2.0 5 months ago
app Benefit from TypedRecyclerViewAdapter 2.0 5 months ago
gradle/wrapper Bump versions of Gradle and Android Gradle tools 11 months ago
.gitignore Update CHANGELOG and gitignore 2 years ago
.travis.yml Upgrade Android SDK Build Tools from 28.0.2 to 28.0.3 1 year ago AlertDialog to view File properties 1 year ago
LICENSE Create LICENSE 3 years ago Update README (WIP) 11 months ago
build.gradle Add AboutLibrary screen 11 months ago Refactor from appcompat to AndroidX 1 year ago
gradlew Fixes #54: Adds Travis CI and updates build tools 2 years ago
gradlew.bat Fixes #54: Adds Travis CI and updates build tools 2 years ago
settings.gradle Initial commit 4 years ago

moodleDirect – WIP

License: MIT

This is a fork of the Android version of the CMS BPHC app. The app plans to allow users to configure their own Moodle server.


Changelogs are necessary so that the end user knows what changes were brought in each new release. This project maintains changelogs using the Keep a Changelog guidelines.

Version numbers are important in helping to differentiate releases of a product. This project follows Semantic Versioning to keep track of versions.

Android uses a unique integer for each release to the Google Version Code. To ensure proper version code semantics and proper correlation with semantic versioning, the following standard is used:

  1. The Major version will be multipled by 1,000,000.
  2. The Minor version will be multiplied by 10,000.
  3. The Patch version will be multipled by 100.
  4. The above values will be added together to get the version code a release.
  5. Pre-releases, alpha releases etc shoud be signified by appropriate values in the least two significant digits.
  6. The changelog should state the semantic version number as well as version code (if a Playstore rollout has been done) with each release.


You can contribute by submitting an issue, or by picking an existing one from the list and sending a PR. Ensure that the branch underlying the PR is up-to-date with latest changes. Contributors must ensure they add any significant changes to the changelog in the same PR itself.

All changes must be made on top of a new branch forked off the development branch. The master branch is only updated when a new release is made.

Commit messages should follow common guidelines, such as the ones mentioned here, whenever possible.

Mention keywords such as "Fixes" or "Closes" in commit messages, followed by the issue number, to automatically close corresponding issues. (List of keywords)

The Moodle endpoints used by this app have been collected in a Postman Here. You may import this collection into Postman directly using the link.