Difference between revisions of "Joining the Code Team"
(Revamp to reflect the new recruitment process) |
(Github update) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 16: | Line 16: | ||
# Also join the IRC channel #pcgen on ~DALnet & ~Freenode, we have our meetings and group discussions there in real time. | # Also join the IRC channel #pcgen on ~DALnet & ~Freenode, we have our meetings and group discussions there in real time. | ||
# Get the latest official version of PCGen from SF and run it. | # Get the latest official version of PCGen from SF and run it. | ||
| − | # Get an id at [ | + | # Get an id at [https://github.com/ GitHub]. |
| − | # Find the [ | + | # Find the [https://github.com/PCGen/pcgen/ pcgen] repository and [https://help.github.com/articles/fork-a-repo/ fork] it. |
=Your first change= | =Your first change= | ||
| − | # Select an issue that interests you, either from our issues flagged as | + | # Get your [[Basic Developer Setup|development environment set up]] |
| + | # Select an issue that interests you, either from our issues flagged as bitsize in the [http://jira.pcgen.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=component+%3D+Bitesize+AND+project+%3D+CODE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Code] and [http://jira.pcgen.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=component+%3D+Bitesize+AND+project+%3D+NEWTAG+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC New Tag] projects, or one you have encountered. | ||
# Build a fix that fixes the bug or implements the new feature | # Build a fix that fixes the bug or implements the new feature | ||
# Test the fix, preferably by writing a unit test | # Test the fix, preferably by writing a unit test | ||
| − | # | + | # Submit the fix as a [https://help.github.com/articles/using-pull-requests/ pull request] to the pcgen repository. |
| − | # Your | + | # Your pull request will be reviewed and friendly feedback provided by one of the team. |
=Joining the team= | =Joining the team= | ||
| − | # Once | + | # Once your pull request (PR) is accepted and merged, you're part of the code team. |
| − | + | # Your second PR should be adding your name to the team listing! | |
| − | # Your second should be adding your name to the team listing! | ||
# Put your details in this wiki under the [[Code]] team! | # Put your details in this wiki under the [[Code]] team! | ||
Any questions, don't hesitate to ask! | Any questions, don't hesitate to ask! | ||
Latest revision as of 13:10, 3 June 2015
Introduction
A list of what to do to join the code team
General steps
- Get a Yahoo Groups id.
- Be sure to subscribe to the Developer's mailing list
- Introduce yourself on the list
- Find the pcgen project on Yahoo! Groups and join.
- Get as many IM IDs as possible (most people use Pidgin, Meebo or Gaim) and get online with them.
- Also join the IRC channel #pcgen on ~DALnet & ~Freenode, we have our meetings and group discussions there in real time.
- Get the latest official version of PCGen from SF and run it.
- Get an id at GitHub.
- Find the pcgen repository and fork it.
Your first change
- Get your development environment set up
- Select an issue that interests you, either from our issues flagged as bitsize in the Code and New Tag projects, or one you have encountered.
- Build a fix that fixes the bug or implements the new feature
- Test the fix, preferably by writing a unit test
- Submit the fix as a pull request to the pcgen repository.
- Your pull request will be reviewed and friendly feedback provided by one of the team.
Joining the team
- Once your pull request (PR) is accepted and merged, you're part of the code team.
- Your second PR should be adding your name to the team listing!
- Put your details in this wiki under the Code team!
Any questions, don't hesitate to ask!
