# PCGen Bylaws

Initially adopted: November 2, 2003
Last Ammended: November 2, 2003
Version: 1

### Article I (Name)

> The name of this organization is to be PCGen.

### Article II (Purpose)

> The purpose of PCGen is to create a character generator for all role-playing games.

### Article III (Membership)

> Section 1

> > Membership to PCGen is open to anyone. Members of PCGen are all volunteers.

> Section 2: PCGen sub-teams

> > PCGen is composed of numerous sub-teams that make up the whole. These teams are:

> > 1. Code
> > 2. Data
> > 3. Documentation
> > 4. Output Sheets
> > 5. Trackers
> > 6. Licenses
> > 7. Publisher Liaison
> > 8. GMGen
> > 9. Special Projects
> > 10. Moderator

> Section 3: Ranking

> > Each team is composed of one or more people. Each team will have at least one Silverback. The
> > duties of the Silverback(s) are:

> > 1. Help recruit and train new members
> > 2. If requested, help mediate any team-member related tensions
> > 3. Remove inactive members from their group

> > Below the Silverbacks, in decreasing status, are the following ranks:

> > - Chimp
> > - Gibbon
> > - Tamarin
> > - Lemur
> > - Ooze

> Section 4: Code

> > Duties of the Code sub-team include, but are not limited to:

> > > 1. If requested, help a new team member spec out how they will implement the assigned task. This may entail helping them come up with proposed data syntax additions or modifications.

> > > 2. Can grant approval to a coder to check in during a code-freeze, though this approval, and subsequent confirmation that the check in is complete, must be sent to the person performing the release so the release isn’t done before the check in is complete.

> Section 5: Data

> > Duties of the Data sub-team include, but are not limited to:

> > > 1. If requested, help new team members design data syntax for trackers

> > > 2. Generally speaking, a silverback should be in charge of any books being actively developed for a publisher (each book could be taken by a different silverback). This silverback would be responsible for making sure that it works properly before letting the Data BoD member know to report to the BoD that the book is ready to be sent to the publisher.

> Section 6: Documentation

> > Duties of the Documentation sub-team include, but are not limited to:

> > > 1. Making sure that the documentation is comprehensive (covering GUI, FAQ and lst syntax)

> Section 7: Output Sheets

> > Duties of the Output Sheet sub-team include, but are not limited to:

> > > 1. Help design Output Sheet Token syntax for new tokens (with the goal of keeping things as simple and consistent as possible).

> > > 2. Respond to Bug and Freq trackers in as timely a manner as possible

> > > 3. Create new output sheets and improve older ones as better methods develop

> > > 4. Coordinate/communicate with Data and Code teams as necessary for the best resolution to any Bug/Freq that might involve more than just the output sheet team.

> Section 8: Trackers

> > Duties of the Tracker sub-team include, but are not limited to:

> > > 1. Prioritize trackers according to the agreed upon policy from the BoD

> > > 2. Help administer trackers to make sure important ones are being actively worked on

> > > 3. Delete duplicate trackers

> > > 4. Confirm bugs

> > > 5. Gather freqs and bugs as reported from the various forums

> > > 6. Seek clarification on any trackers that require more information

> > > 7. Periodically sweep through code, data and doc groups to see if any one has been inactive for more than 3 months - contact them and ask if they intend to become active soon (if they won't become active, send the appropriate silverback a note indicating
> > > they can be removed)

> Section 9: Licenses

> > Duties of the Licenses sub-team include, but are not limited to:

> > > 1. Review existing data from time to time to make sure it's compliant with applicable licenses

> > > 2. Review any data submissions to publishers to make sure they comply with licenses

> > > 3. Handle any license related questions requested by the Board or silverbacks

> Section 10: Publisher Liaison

> > Duties of the Publisher Liaison sub-team include, but are not limited to:

> > > 1. Contact and maintain relationship with as many publishers as possible

> > > 2. Seek permission to include data in PCGen (though we don't want to get permission for too much more than we can handle in the next month or so, otherwise we get permission for a book but can't actually get to it for a year!)

> Section 11: GMGen

> > Duties of the GMGen sub-team include, but are not limited to:

> > > 1. If requested, help a new team member spec out how they will implement the assigned task.

> > > 2. Can grant approval to a coder to check in during a code-freeze, though this approval, and subsequent confirmation that the check in is complete, must be sent to the person performing the release so the release isn’t done before the check in is complete.

> > > 3. Assist team members in their understanding of the plugin architecture, and in the design and specification of new plugins.

> > > 4. Interface with code and data teams to solve GMGen specific problems.

> Section 12: Special Projects

> > Duties of the Special Projects sub-team include, but are not limited to:

> > > 1. If a project requires a coder, work with that coder to fully specify the design.

> > > 2. If the project requires a data monkey, work with the data monkey to full specify the syntax.

> > > 3. Help coordinate the efforts of the code and data workers if both are required on the task.

> Section 13: Moderators

> > Duties of the Moderators sub-team include, but are not limited to:

> > > 1. Review posts on all PCGen message boards to insure that posters are following the terms of the list properly.

> > > 2. Helping diffuse problems between various other sub-teams if the sub-teams can not work the problem out on their own.

### Article IV: Board of Directors

> PCGen shall be run by a Board of Directors. This board shall be constituted by at least one Silverback from each of the sub-teams and be chaired by the Benevolent Dictator. One person can represent more than one team if needed. The size of the Board may vary with time. Duties of the board shall include, but not be limited to:

> > 1. A tracker needs clarification/prioritization or syntax can't be agreed upon

> > 2. Finding a resource to address an important issue is proving to be difficult

> > 3. There's some tension on or between team members that requires attention

> > 4. Someone has done work above and beyond the call of duty, and the BoD needs to be aware of it and acknowledge it

> > 5. Ability to observe any other sub-team in PCGen. If a board member wishes to actively participate in that sub-team, they will need to follow the lead of that team’s Silverback(s). A list of the current members of the Board shall be available for anyone to see. This list will include what sub-team(s) they are from and a preferred method of contacting them.

### Article V: Meetings

> Section 1

> > The Board of Directors shall meet at least once a month. The Benevolent Dictator shall announce these meetings, and how they are to be carried out, to the Board at least one week in advance. If any items before the Board are to be voted on, a quorum (50% + 1) of the Board shall be present at the meeting. If a quorum does not prevail, then no voting can take place. A log of the Board meetings shall be kept for posterity. Minutes of the Board meeting shall be provided to the PCGen volunteers so that they may see what is going with the group.

> Section 2

> > The sub-teams shall meet in a manner most conducive for their work, as guided by the subteam’s Silverback(s).

### Article VI: Voting

> Most items brought before the Board to be voted on will only require a simple (50% + 1) majority to pass. Amending these Bylaws, increasing/decreasing the size of the board and disciplining a volunteer in PCGen shall require a major (2/3) majority.