Skip to content
Dutch Matous edited this page Aug 10, 2013 · 3 revisions

Ownership and Design

Anyone that wants to own a piece of functionality should put their name by a task on the Project Tasks page. Initially there will be one primary to a project task (first come basis).

Then a design page should be filled out using the Design Template

Builds and Releases

There will be a bi-monthly integration release. Anyone working on branches must pull in their code to the integration (master) branch. Two people, the primary and secondary integrators, will be responsible for merging code if necessary, doing a build, testing and logging issues.

Feature owners must identify whether their feature(s) will be ready for that release point. Otherwise they should not merge their code in yet.

Design Reviews

If an owner wants their design reviewed by anyone for any reason, they can create an issue and assign it to that person.

Pull Requests

The project is using the shared repository model. Pull requests can be used to integrate code and also review code. Additionally, code can be reviewed by opening an issue.

Issue Tracker

Issue tracking will be used to move items forward and resolve defects

General Discussions

The Android Meetup discussion board will be used for general project discussions and Q/A. Be sure to track the forum to get email updates.

Initial Setup Tasks

  • Checkout the project from github
  • Build and deploy the app
  • Make a change and redeploy
  • Make a small change (add a comment) and check in to github
  • Select a task on the Project Task page and edit to add name
  • Create a design wiki page
  • Request a design review if desired
  • Branch project (on your local repository)
  • Make a small code change on the branch
  • Commit the change and push the branch to remote
  • Switch to the master branch and merge in changes from your feature branch
  • delete your feature branch