This is an individual assignment.
The purpose of this assignment is to further deal with collaboration on bigger projects.
- Open at least three issues against the repo that you worked with this past week. These can be anything from bug fixes to feature requests, but do not open issues that have already been opened.
- Open at least one issue against the repo that you worked with in Week 0. Make sure to look at the other issues that have been open. Do not duplicate issues.
- With your team from week 0, review all pull requests and respond to all issues on your group project repo. Responses could be about project scope, or simply discussion on how the issue fits in with the app. The point is to address the concern raised in the issue. Not everyone has to respond to everything - divide up the work amongst yourselves. You do not have to merge anything or implement anything new.
Take a look at the issues for The Github Android App. Choose an issue to tackle. Open that issue against the Access Code fork of this project. Do not open a new issue if your issue is already there.
Write some code to fix the issue. Create a PR against the Access Code fork of this project.
Contribute to an open source Java or Android project. If you do this, please send us a link to the PR.
If you want to contribute to any of these, let us know! They're excited to help AccessCoders get their PRs through:
- Alessandro's repos
- Some repos managed by Ben Romano: CacheManager, Android Typeface Views, Recycler Core, Shortcake, Cream, Swap, Unitizer
Here are a few others you can look at:
- Github's Android App
- Jake Wharton's Repos
- The Android Open Source Project
- Github's List of Android Projects Sorted by # of Forks
- Branch names should be descriptive.
- Pull requests should be descriptive.
- Discussion is healthy!
- Open source projects are communities as much as software.