forked from wikimedia/wikipedia-ios
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
7 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,46 +1,34 @@ | ||
| # Contributing | ||
|
|
||
| We welcome volunteers to contribute to the Wikipedia iOS app codebase. | ||
|
|
||
|
|
||
| ##Development instructions | ||
|
|
||
| ## Development instructions | ||
| Before developing, please read the [setup instructions](README.md). | ||
|
|
||
| We do all of our active development on the [develop](https://github.com/wikimedia/wikipedia-ios) branch. Your pull requests will automatically be targeted at that branch by Github. To make merging easier, be sure you create your branches based on the develop branch. | ||
|
|
||
| Once your contributions are ready for review, add yourself in alphabetical order under contributors in `Code/AboutViewController.plist` and post a pull request on GitHub. One of the maintainers will review the PR. Thanks for contributing! 🎉 | ||
|
|
||
|
|
||
| ##What can I work on? | ||
|
|
||
| ## What can I work on? | ||
| If you're looking for easy work, look at the tasks marked with the "Easy" tag. This link will show you all the "Easy" tasks in the iOS backlog. | ||
|
|
||
| If you're ready to pick up more difficult work, look at the iOS backlog and pick something from the Bug Backlog column. This link will show you all the tasks in the iOS backlog. If the status of the task is unclear or you need more information, feel free to leave a comment and we'll try to respond as soon as possible. | ||
|
|
||
|
|
||
| ##I found my task. What next? | ||
|
|
||
| ## I found my task. What next? | ||
| Now you want to let the team know what you're working on. | ||
|
|
||
| 1. In Phabricator, assign the task to yourself. | ||
| 2. Add the tag representing the current release to the task. This link will take you to currently open releases. Tagging your task with the name of the release will add it to the release board. | ||
| 3. On the release board, move the task to the "Doing" column. | ||
| 4. When you're done developing, move the task to the "Needs Code Review" column. | ||
|
|
||
|
|
||
| ##I don't want to work on my task any more. | ||
|
|
||
| ## I don't want to work on my task any more. | ||
| You can let us know by unassigning the task and moving it back to the "Tasks from Product Backlog" column. | ||
|
|
||
|
|
||
| ##How will I know that my contribution was accepted? | ||
|
|
||
| ## How will I know that my contribution was accepted? | ||
| Your PR will be merged and your task will get moved to the "Ready for PM Signoff" column. This means that your contribution will be included in the upcoming release. | ||
|
|
||
|
|
||
| ##Tips | ||
|
|
||
| ## Tips | ||
| [Wiki on how to use Phabricator](https://www.mediawiki.org/wiki/Phabricator/Project_management) | ||
|
|
||
|
|
||
|
|