Joining
|
Size: 1407
Comment:
|
Size: 2568
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Joining the Beginners Development Group = | ## We are Development. You will be assimilated. ## Your individual technical abilities will be added ## to our own. Resistance is futile. #title Joining the Development Focus Group #pragma section-numbers on #format wiki #language en ||<tablestyle="float: right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents(2)>>|| |
| Line 3: | Line 10: |
| == Mentor System == New prospects are up for the adoption of a Mentor. The Collective is based on a tight ring of trust, joining the group requires hard work and dedication. The Mentor will server as the team's eyes and ears with regards to the new member's status with the team, and ability level. New members will be expected to preform simple tasks regarding application design, programming concepts, and an aptitude with Subversion. Mentors will be required to take accountability for their young'en, until such a time as the young'en proves credibility with the team. All work done by the Young'en will be buffered through the mentor, ensuring high quality code, and no "oppsies". |
= Mentor System = New drone prospects will be adopted by a Tertiary Adjunct. The Collective is based on a tight ring of trust. As such, joining requires hard work and dedication. The Tertiary Adjunct will serve as the Collective's eyes and ears with regards to the new drone's status with the team and their ability level during the assimilation process. New drones will be expected to preform simple tasks regarding application design, programming concepts, and must demonstrate an aptitude with Subversion. Tertiary Adjuncts will be required to take accountability for their newly-assimilated drone, until such a time as they prove their credibility to the Collective. All work done by the new drone will be buffered through the Tertiary Adjunct, meaning the Tertiary Adjunct will be responsible for doing code reviews. This is necessary to ensure high quality code, and to avoid "whoopsies". |
| Line 6: | Line 13: |
| == Accepting New Members == When a new members have shown their dedication to the team, a second member of the Collective will be asked to step forward and vouch for the new member. After a team vote, any member has a chance to speak out in both support or descent about the new member. After a discussion ( without the new member present ) a vote takes place. With a 3/4 vote positive, the new member is inducted, barring any lead opposing the new member. |
= Accepting New Drones = When a new drone has shown their dedication to the Collective, a second member will be asked to step forward and vouch for the new drone. After a team vote, any Collective member will have a chance to speak out in both support of or opposition to about the new drone. After a discussion (without the prospective drone present) a vote takes place. With a 3/4 vote in favour, barring any lead opposing assimilation, the new drone will be fully assimilated. |
| Line 9: | Line 16: |
| == The "Quiz" == * Stuff * Things |
= The "Quiz" = A demonstration of basic development knowledge will be required of all new drones. These skills include, but are not necessarily limited to, the following: * Compiling code from source * Competence with Subversion * Basic version control knowledge |
| Line 14: | Line 23: |
| * Stuff * Things |
* Basic version control skills, applied with Subversion * Check out code, commit changes, merge conflicts * What files should and should not be placed under version control * Creating and applying patches * Finding differences between two arbitrary checkouts * Able to avoid the most common programming pitfalls, especially ones creating security problems |
1. Mentor System
New drone prospects will be adopted by a Tertiary Adjunct. The Collective is based on a tight ring of trust. As such, joining requires hard work and dedication. The Tertiary Adjunct will serve as the Collective's eyes and ears with regards to the new drone's status with the team and their ability level during the assimilation process. New drones will be expected to preform simple tasks regarding application design, programming concepts, and must demonstrate an aptitude with Subversion. Tertiary Adjuncts will be required to take accountability for their newly-assimilated drone, until such a time as they prove their credibility to the Collective. All work done by the new drone will be buffered through the Tertiary Adjunct, meaning the Tertiary Adjunct will be responsible for doing code reviews. This is necessary to ensure high quality code, and to avoid "whoopsies".
2. Accepting New Drones
When a new drone has shown their dedication to the Collective, a second member will be asked to step forward and vouch for the new drone. After a team vote, any Collective member will have a chance to speak out in both support of or opposition to about the new drone. After a discussion (without the prospective drone present) a vote takes place. With a 3/4 vote in favour, barring any lead opposing assimilation, the new drone will be fully assimilated.
3. The "Quiz"
A demonstration of basic development knowledge will be required of all new drones. These skills include, but are not necessarily limited to, the following:
- Compiling code from source
- Competence with Subversion
- Basic version control knowledge
3.1. Skills We Look For
- Basic version control skills, applied with Subversion
- Check out code, commit changes, merge conflicts
- What files should and should not be placed under version control
- Creating and applying patches
- Finding differences between two arbitrary checkouts
- Able to avoid the most common programming pitfalls, especially ones creating security problems
BeginnersTeam/FocusGroups/Development/Joining (last edited 2010-01-15 09:24:47 by adsl-76-241-121-249)