PCGen Wiki - User contributions [en]

Paul Shipley (elro the onk)

2015-05-31T08:50:25Z

Elro the onk:

{| align="right"
| __TOC__
|}

=Introduction=

Paul Shipley (aka elro the onk) volunteered for Data entry way back in 2010.

=Teams I belong to=
{| border=1
|-
! Team !! Rank
|-
| [[Data]] || [[Explanation_of_Teams#Tamarin|Tamarin]]
|}

=Previous Work=
''Advanced Options: Inquisitors' Judgments'' by Super Genius Games (Pathfinder)

''Book of the Damned 2: Lords of Chaos'' by Paizo (Pathfinder)

Spells in ''Ultimate Psionics'' by Dreamscarred Press (Pathfinder) - [[Doug Limmer]] did most of the work on the source

''Rise of the Runelords Anniversary Edition Players Guide'' by Paizo (Pathfinder)

''The Genius Guide to Air Magic'' by Super Genius Games (Pathfinder)

''Krazy Kragnar's Alchemical Surplus Shop'' by Super Genius Games (Pathfinder)

''Adventurer's Handbook'' by Super Genius Games (Pathfinder)

Much of ''Seekers of Secrets'' by Paizo (Pathfinder) - Terry Milnes did the early work

Bestiary & completion of ''Inner Sea World Guide'' by Paizo (Pathfinder) - [[Stefan Radermacher]] did most of the work on the source

Completion of ''Dragon Empires Primer'' by Paizo (Pathfinder) - [[Stefan Radermacher]] and swiftbrook also did much on this

SourceTree Helpful Tips

2015-01-08T13:16:51Z

Elro the onk: /* How to set up and update a forked repo */

== How to set up and update a forked repo ==
First, set up the parent repo:

1. Open your forked repo in SourceTree.

2. Select Settings in the toolbar.

3. In the "Remotes" pane, press "Add".

4. Enter any name you like, and the URL / path to the parent repo.

5. Press OK, then OK.

Now, to update:

1. Select Pull in the toolbar.

2. In the "Pull from repository" dropdown, switch from your fork to the repo you just added.

3. Press OK.

4. (Optional) Once you pull, you may want to Push, to push the new content up to the server.

SourceTree Helpful Tips

2015-01-08T13:16:02Z

Elro the onk: Created page with "== How to set up and update a forked repo == First, set up the parent repo: 1. Open your forked repo in SourceTree. 2. Select Settings in the toolbar. 3. In the "Remotes" pan..."

== How to set up and update a forked repo ==
First, set up the parent repo:

1. Open your forked repo in SourceTree.
2. Select Settings in the toolbar.
3. In the "Remotes" pane, press "Add".
4. Enter any name you like, and the URL / path to the parent repo.
5. Press OK, then OK.

Now, to update:

1. Select Pull in the toolbar.
2. In the "Pull from repository" dropdown, switch from your fork to the repo you just added.
3. Press OK.
4. (Optional) Once you pull, you may want to Push, to push the new content up to the server.

GITHUB and proper procedures

2015-01-08T13:15:45Z

Elro the onk: /* Windows */

==Intro==
GITHUB is a wonderful collaboration tool for developers. We at PCGen are migrating from the SVN repository we host of SF to the free hosting at GITHUB. Most people should be familiar with GIT and GITHUB, but we'll go over what our procedures are:

===Contributor Setup===
If you plan on being a developer and contributing follow these steps:

* 1) Sign in to github with your account. (You should have a SSH key)
* 2) Navigate to the pcgen project you wish to contribute too and click the FORK button. (See below for link)
* 3) Navigate to your FORK of the pcgen project and use the SHH link for cloning a local copy
* 4) Choose a local folder to house your local copy and clone the copy there.
* 5) Add a remote repository and link it to the main pcgen project (or upstream) -- OPTIONAL STEP: This allows fast update to your local copy from the main project, see https://help.github.com/articles/syncing-a-fork/.
* 6) Once your local copy is downloaded, do a git checkout and name your branch* (See Branch Naming practices below)
* 7) Once you have finished working on your feature/bug branch, do the git equivalent of 'add', 'commit', and then 'push' those changes to your remote repository. (See GIT Commit Summary Practices)
* 8) Do a PR (Pull Request) from your repository to the main pcgen repository, using the branch you pushed in - make an explanation summary or JIRA ID

===Just want a Copy of a project===
If you want to maintain an up-to-date copy of the pcgen project repository, but do not have plans to contribute in the near future, you may easily do the following:
* 1) Navigate to the pcgen project repository (See below for link)
* 2) Click the "Link" of your choice for cloning a local copy - SSH is superior, but you may opt for https.
* 3) Choose a local folder to house your local copy and clone the copy there.
* NOTE: This will allow you to grab updates from the project, but not push any changes.

Of course, you are always able to use the download, to get a snapshot of the project. This is the least recommended method of having access to the project.

===Feature/Bug Branch Naming Practices:===
* All Features or Bugs should have a corresponding JIRA ID, example: CODE-1234, or DATA-4321. Your Branch should be JIRA-ID_Title, example: DATA-1234_Fix_Bard_Skills

SSH Keys are useful and should be used whenever possible. For Windows, PuttyGen will allow you to create your own SSH Key.

===Git Commit Summary Practices===
* Each Commit you make should include the JIRA-ID for point of reference and JIRA integration tracking
* Each Commit you make should include enough detail to understand what you were working on

* Before PUSHING, you may do any number of things to clean up before you PUSH to the remote. Please review the options from reputable GIT information sites for proper usage.
* Ideally, you should squash your commits into one commit before pushing into your remote.

There is a useful aide-memoire on GitHub, https://github.com/PCGen/pcgen-newsources/wiki/Contributing-to-NewSources.

===PCGen Projects===
All Active PCGen Repositories are held under the Username "PCGen" which is our organization on github.com. You can find the repositories we host here: https://github.com/PCGen

* Our Main Development Program is "PCGen" - git@github.com:PCGen/pcgen.git
* Our New Source Development is NewSources (Active Now) - git@github.com:PCGen/pcgen-newsources.git

===GIT TOOLS===
* Command line for GIT is by far the superior method. However, we have found tools that our developers like to use and recommend them as easier alternatives to the command line if you choose to do so.

====Windows====
* Atlassian's free SourceTree GUI program ([[SourceTree Helpful Tips]])
* TortoiseGIT (Shell integration)

====Mac====
* ...Pending...

====Linux====
* RabbitVCS (Gnome only, integrates with Nautilus)

GITHUB and proper procedures

2015-01-08T13:13:55Z

Elro the onk: /* Windows */

==Intro==
GITHUB is a wonderful collaboration tool for developers. We at PCGen are migrating from the SVN repository we host of SF to the free hosting at GITHUB. Most people should be familiar with GIT and GITHUB, but we'll go over what our procedures are:

===Contributor Setup===
If you plan on being a developer and contributing follow these steps:

* 1) Sign in to github with your account. (You should have a SSH key)
* 2) Navigate to the pcgen project you wish to contribute too and click the FORK button. (See below for link)
* 3) Navigate to your FORK of the pcgen project and use the SHH link for cloning a local copy
* 4) Choose a local folder to house your local copy and clone the copy there.
* 5) Add a remote repository and link it to the main pcgen project (or upstream) -- OPTIONAL STEP: This allows fast update to your local copy from the main project, see https://help.github.com/articles/syncing-a-fork/.
* 6) Once your local copy is downloaded, do a git checkout and name your branch* (See Branch Naming practices below)
* 7) Once you have finished working on your feature/bug branch, do the git equivalent of 'add', 'commit', and then 'push' those changes to your remote repository. (See GIT Commit Summary Practices)
* 8) Do a PR (Pull Request) from your repository to the main pcgen repository, using the branch you pushed in - make an explanation summary or JIRA ID

===Just want a Copy of a project===
If you want to maintain an up-to-date copy of the pcgen project repository, but do not have plans to contribute in the near future, you may easily do the following:
* 1) Navigate to the pcgen project repository (See below for link)
* 2) Click the "Link" of your choice for cloning a local copy - SSH is superior, but you may opt for https.
* 3) Choose a local folder to house your local copy and clone the copy there.
* NOTE: This will allow you to grab updates from the project, but not push any changes.

Of course, you are always able to use the download, to get a snapshot of the project. This is the least recommended method of having access to the project.

===Feature/Bug Branch Naming Practices:===
* All Features or Bugs should have a corresponding JIRA ID, example: CODE-1234, or DATA-4321. Your Branch should be JIRA-ID_Title, example: DATA-1234_Fix_Bard_Skills

SSH Keys are useful and should be used whenever possible. For Windows, PuttyGen will allow you to create your own SSH Key.

===Git Commit Summary Practices===
* Each Commit you make should include the JIRA-ID for point of reference and JIRA integration tracking
* Each Commit you make should include enough detail to understand what you were working on

* Before PUSHING, you may do any number of things to clean up before you PUSH to the remote. Please review the options from reputable GIT information sites for proper usage.
* Ideally, you should squash your commits into one commit before pushing into your remote.

There is a useful aide-memoire on GitHub, https://github.com/PCGen/pcgen-newsources/wiki/Contributing-to-NewSources.

===PCGen Projects===
All Active PCGen Repositories are held under the Username "PCGen" which is our organization on github.com. You can find the repositories we host here: https://github.com/PCGen

* Our Main Development Program is "PCGen" - git@github.com:PCGen/pcgen.git
* Our New Source Development is NewSources (Active Now) - git@github.com:PCGen/pcgen-newsources.git

===GIT TOOLS===
* Command line for GIT is by far the superior method. However, we have found tools that our developers like to use and recommend them as easier alternatives to the command line if you choose to do so.

====Windows====
* Atlassian's free SourceTree GUI program ([[Helpful Tips]])
* TortoiseGIT (Shell integration)

====Mac====
* ...Pending...

====Linux====
* RabbitVCS (Gnome only, integrates with Nautilus)

Paul Shipley (elro the onk)

2015-01-08T13:12:55Z

Elro the onk:

{| align="right"
| __TOC__
|}

=Introduction=

Paul Shipley (aka elro the onk) volunteered for Data entry way back in 2010.

=Teams I belong to=
{| border=1
|-
! Team !! Rank
|-
| [[Data]] || [[Explanation_of_Teams#Tamarin|Tamarin]]
|}

=Previous Work=
''Book of the Damned 2: Lords of Chaos'' by Paizo (Pathfinder)

Spells in ''Ultimate Psionics'' by Dreamscarred Press (Pathfinder) - [[Doug Limmer]] did most of the work on the source

''Rise of the Runelords Anniversary Edition Players Guide'' by Paizo (Pathfinder)

''The Genius Guide to Air Magic'' by Super Genius Games (Pathfinder)

''Krazy Kragnar's Alchemical Surplus Shop'' by Super Genius Games (Pathfinder)

''Adventurer's Handbook'' by Super Genius Games (Pathfinder)

Much of ''Seekers of Secrets'' by Paizo (Pathfinder) - Terry Milnes did the early work

Bestiary & completion of ''Inner Sea World Guide'' by Paizo (Pathfinder) - [[Stefan Radermacher]] did most of the work on the source

Completion of ''Dragon Empires Primer'' by Paizo (Pathfinder) - [[Stefan Radermacher]] and swiftbrook also did much on this

Paul Shipley (elro the onk)

2015-01-08T13:11:43Z

Elro the onk: Created page with "{| align="right" | __TOC__ |} =Introduction= Paul Shipley (aka elro the onk) volunteered for Data entry way back in 2010. =Teams I belong to= {| border=1 |- ! Team !! R..."

{| align="right"
| __TOC__
|}

=Introduction=

Paul Shipley (aka elro the onk) volunteered for Data entry way back in 2010.

=Teams I belong to=
{| border=1
|-
! Team !! Rank
|-
| [[Data]] || [[Explanation_of_Teams#Tamarin|Tamarin]]
|}

=Contact Details=
{| border=1
|-
| Timezone || GMT+0 (UK)
|-
| Email || paul_shipley@tesco.net

|}

=Previous Work=
''Book of the Damned 2: Lords of Chaos'' by Paizo (Pathfinder)

Spells in ''Ultimate Psionics'' by Dreamscarred Press (Pathfinder) - [[Doug Limmer]] did most of the work on the source

''Rise of the Runelords Anniversary Edition Players Guide'' by Paizo (Pathfinder)

''The Genius Guide to Air Magic'' by Super Genius Games (Pathfinder)

''Krazy Kragnar's Alchemical Surplus Shop'' by Super Genius Games (Pathfinder)

''Adventurer's Handbook'' by Super Genius Games (Pathfinder)

Much of ''Seekers of Secrets'' by Paizo (Pathfinder) - Terry Milnes did the early work

Bestiary & completion of ''Inner Sea World Guide'' by Paizo (Pathfinder) - [[Stefan Radermacher]] did most of the work on the source

Completion of ''Dragon Empires Primer'' by Paizo (Pathfinder) - [[Stefan Radermacher]] and swiftbrook also did much on this

GITHUB and proper procedures

2015-01-08T12:44:41Z

Elro the onk: Added link to NewSource howto help page on GitHub

==Intro==
GITHUB is a wonderful collaboration tool for developers. We at PCGen are migrating from the SVN repository we host of SF to the free hosting at GITHUB. Most people should be familiar with GIT and GITHUB, but we'll go over what our procedures are:

===Contributor Setup===
If you plan on being a developer and contributing follow these steps:

* 1) Sign in to github with your account. (You should have a SSH key)
* 2) Navigate to the pcgen project you wish to contribute too and click the FORK button. (See below for link)
* 3) Navigate to your FORK of the pcgen project and use the SHH link for cloning a local copy
* 4) Choose a local folder to house your local copy and clone the copy there.
* 5) Add a remote repository and link it to the main pcgen project (or upstream) -- OPTIONAL STEP: This allows fast update to your local copy from the main project, see https://help.github.com/articles/syncing-a-fork/.
* 6) Once your local copy is downloaded, do a git checkout and name your branch* (See Branch Naming practices below)
* 7) Once you have finished working on your feature/bug branch, do the git equivalent of 'add', 'commit', and then 'push' those changes to your remote repository. (See GIT Commit Summary Practices)
* 8) Do a PR (Pull Request) from your repository to the main pcgen repository, using the branch you pushed in - make an explanation summary or JIRA ID

===Just want a Copy of a project===
If you want to maintain an up-to-date copy of the pcgen project repository, but do not have plans to contribute in the near future, you may easily do the following:
* 1) Navigate to the pcgen project repository (See below for link)
* 2) Click the "Link" of your choice for cloning a local copy - SSH is superior, but you may opt for https.
* 3) Choose a local folder to house your local copy and clone the copy there.
* NOTE: This will allow you to grab updates from the project, but not push any changes.

Of course, you are always able to use the download, to get a snapshot of the project. This is the least recommended method of having access to the project.

===Feature/Bug Branch Naming Practices:===
* All Features or Bugs should have a corresponding JIRA ID, example: CODE-1234, or DATA-4321. Your Branch should be JIRA-ID_Title, example: DATA-1234_Fix_Bard_Skills

SSH Keys are useful and should be used whenever possible. For Windows, PuttyGen will allow you to create your own SSH Key.

===Git Commit Summary Practices===
* Each Commit you make should include the JIRA-ID for point of reference and JIRA integration tracking
* Each Commit you make should include enough detail to understand what you were working on

* Before PUSHING, you may do any number of things to clean up before you PUSH to the remote. Please review the options from reputable GIT information sites for proper usage.
* Ideally, you should squash your commits into one commit before pushing into your remote.

There is a useful aide-memoire on GitHub, https://github.com/PCGen/pcgen-newsources/wiki/Contributing-to-NewSources.

===PCGen Projects===
All Active PCGen Repositories are held under the Username "PCGen" which is our organization on github.com. You can find the repositories we host here: https://github.com/PCGen

* Our Main Development Program is "PCGen" - git@github.com:PCGen/pcgen.git
* Our New Source Development is NewSources (Active Now) - git@github.com:PCGen/pcgen-newsources.git

===GIT TOOLS===
* Command line for GIT is by far the superior method. However, we have found tools that our developers like to use and recommend them as easier alternatives to the command line if you choose to do so.

====Windows====
* Atlassian's free SourceTree GUI program
* TortoiseGIT (Shell integration)

====Mac====
* ...Pending...

====Linux====
* RabbitVCS (Gnome only, integrates with Nautilus)

GITHUB and proper procedures

2015-01-08T12:42:20Z

Elro the onk: Adding link to fork syncing help page on GitHub

==Intro==
GITHUB is a wonderful collaboration tool for developers. We at PCGen are migrating from the SVN repository we host of SF to the free hosting at GITHUB. Most people should be familiar with GIT and GITHUB, but we'll go over what our procedures are:

===Contributor Setup===
If you plan on being a developer and contributing follow these steps:

* 1) Sign in to github with your account. (You should have a SSH key)
* 2) Navigate to the pcgen project you wish to contribute too and click the FORK button. (See below for link)
* 3) Navigate to your FORK of the pcgen project and use the SHH link for cloning a local copy
* 4) Choose a local folder to house your local copy and clone the copy there.
* 5) Add a remote repository and link it to the main pcgen project (or upstream) -- OPTIONAL STEP: This allows fast update to your local copy from the main project, see https://help.github.com/articles/syncing-a-fork/.
* 6) Once your local copy is downloaded, do a git checkout and name your branch* (See Branch Naming practices below)
* 7) Once you have finished working on your feature/bug branch, do the git equivalent of 'add', 'commit', and then 'push' those changes to your remote repository. (See GIT Commit Summary Practices)
* 8) Do a PR (Pull Request) from your repository to the main pcgen repository, using the branch you pushed in - make an explanation summary or JIRA ID

===Just want a Copy of a project===
If you want to maintain an up-to-date copy of the pcgen project repository, but do not have plans to contribute in the near future, you may easily do the following:
* 1) Navigate to the pcgen project repository (See below for link)
* 2) Click the "Link" of your choice for cloning a local copy - SSH is superior, but you may opt for https.
* 3) Choose a local folder to house your local copy and clone the copy there.
* NOTE: This will allow you to grab updates from the project, but not push any changes.

Of course, you are always able to use the download, to get a snapshot of the project. This is the least recommended method of having access to the project.

===Feature/Bug Branch Naming Practices:===
* All Features or Bugs should have a corresponding JIRA ID, example: CODE-1234, or DATA-4321. Your Branch should be JIRA-ID_Title, example: DATA-1234_Fix_Bard_Skills

SSH Keys are useful and should be used whenever possible. For Windows, PuttyGen will allow you to create your own SSH Key.

===Git Commit Summary Practices===
* Each Commit you make should include the JIRA-ID for point of reference and JIRA integration tracking
* Each Commit you make should include enough detail to understand what you were working on

* Before PUSHING, you may do any number of things to clean up before you PUSH to the remote. Please review the options from reputable GIT information sites for proper usage.
* Ideally, you should squash your commits into one commit before pushing into your remote.

===PCGen Projects===
All Active PCGen Repositories are held under the Username "PCGen" which is our organization on github.com. You can find the repositories we host here: https://github.com/PCGen

* Our Main Development Program is "PCGen" - git@github.com:PCGen/pcgen.git
* Our New Source Development is NewSources (Active Now) - git@github.com:PCGen/pcgen-newsources.git

===GIT TOOLS===
* Command line for GIT is by far the superior method. However, we have found tools that our developers like to use and recommend them as easier alternatives to the command line if you choose to do so.

====Windows====
* Atlassian's free SourceTree GUI program
* TortoiseGIT (Shell integration)

====Mac====
* ...Pending...

====Linux====
* RabbitVCS (Gnome only, integrates with Nautilus)

Data

2014-10-08T18:09:49Z

Elro the onk: Added my Tamarin rank :-)

{| align="right"
| __TOC__
|}
=Introduction=

Welcome to the Wiki section of the Data team! The data team is a sub team under the umbrella of the [[Content]] team.

=Mission Statement=
To create data (books) for PCGen that encompasses all aspects of character creation, is true to the publisher's intent and results in output that is correct and complete for the end-user.

=Data Meetings=
* [[Data Meeting Availability]]
* [[Data Meeting Logs]]

=Books Requested by Users=
* [[Content Requests]]

=Conversion Logs for 6.0=
* [[GameMode35e]]
* [[GameMode_3e]]
* [[GameMode_Pathfinder]]
* [[GameMode_deadlands]]

=Active Proposals=
* [[Redesigning COMPANIONLIST and Companion Leveladjustment]]
* [[COMPANIONTYPE| COMPANIONTYPE a new token to make grouping companions together]]
* [[Dragons redesigned]]
* [[NATURALATTACK the new system]]

=Resources=
* [[Joining the Data Team]]

* [[Video Lessons]]

* [[Data Team Tools]]
* [[Dataset Creation/Maintenance]]
* [[Dataset Testing]]
* [[PCGen Data Team Processes (JIRA)]]
* [[PCGen Data Team FAQ]]
* [[PCGen Data Team Useful Links]]

* [[Lst File How To]]

* [[Data Team Resource Page]]

* [[Quality Assurance Team]]

=Active Team Members=
Members of this team (and areas of specialty/responsibility) are:

===[[Explanation of Teams#Silverback|Silverback]]===
* [[Chris Chandler|Barak]]

===[[Explanation of Teams#Second|2nd]]===
* [[LegacyKing|Andrew Maitland]]

===[[Explanation of Teams#Chimp|Chimp]]===
* [[Chris Chandler|Barak]] - Tag design, consulting (CMP datasets)
* [[User:Nylanfs|Paul Grosse]]
* [[LegacyKing|Andrew Maitland]]
* [[Stefan Radermacher]]
* [[Eddy Anthony]]
* [[Eric C Smith|Maredudd]]

===[[Explanation of Teams#Gibbon|Gibbon]]===
* [[Paul W. King|Paul King]]
* Phantom of Krankor - Need real name
* [[David R. Bender]]

===[[Explanation of Teams#Tamarin|Tamarin]]===
* [[Shelley Stephen]]
* [[Paul Shipley (elro the onk)]]

===[[Explanation of Teams#Lemur|Lemur]]===
{| border=1
|-
| NAME || Working On || Active as of
|-
| Peter Yovich || Patcher - Minor Bug Fixes || May 7th, 2011
|-
| [[Distant_Scholar|Doug Limmer]] || Minor Bugs || May 7th, 2011
|-
| Ainvar Garrettson || No Assigned Tasks || May 7th, 2011
|-
| [[Allen Cohn]] || No Assigned Tasks || May 7th, 2011
|-
| Terry Milnes || Q&A, Patches || May 7th, 2011
|-
| Anestis Kozakis || No Assigned Tasks || May 7th, 2011
|}

[No Response to inquiry on 5.6.2011 Yet]
* Arjan van Ginneken
* Thomas Cooper
* [[Tod Milam]]
* Harvey Howell
* Henk Slaaf - Q&A, Patches
* Swiftbrook - Pathfinder
* John Bauldree
* Monty, aka Fabio Montanari - 3.5e
* Jonathan A. Arnold - Homebrew Help

* [[Terry FitzSimons]]

===Special Titles===
{| border=1
|-
| [[Shelley Stephen]] || 1st flunky in charge of finding weird bugs
|-
| [[Tir Gwaith]] || [[Strange Monkey]]
|}

=Inactive Team Members=

===[[Explanation of Teams#Silverback|Silverback]]===
* [[Eddy Anthony]]
* [[Frank Kliewe]]

===[[Explanation of Teams#Chimp|Chimp]]===
* [[Tir Gwaith]] - 3e, 3.5e, Races, Classes, Prettylst
* Michael Gray (taluroniscandar) - 3e and 3.5e Psionics
* Aaron Divinsky, Default Monster Kits, [[Internationalization]]

===[[Explanation of Teams#Tamarin|Tamarin]]===
* Ratheof Blithwyn

===[[Explanation of Teams#Lemur|Lemur]]===
* [[Andargor]]
* David Saulnier
* Dennis Baker
* Eric Jarman
* [[Jason Horner]]
* Phillip Ryan - PrettyLst
* Fluxxdog
* [[Martijn Verburg]]

===Special Titles===
{| border=1
|-
| [[Andargor]] || Amoeba
|}

Full Team Member Listing

2013-06-09T15:39:31Z

Elro the onk: Added some more details for me - and I think I'm still active :-)

{| align="right"
| __TOC__
|}

=Introduction=

PCGen has been blessed with an amazing amount of volunteers over the course of its history. A historical listing of those who have contributed (past and present) can be seen in the [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/acknowledgments/contributors.html Contributors] section of our Documentation. The current team is listed below:

=Active Volunteers=
These volunteers are currently active on the PCGen project

{| border="1"
|-
! align="left"|SF Team Name !! align="left"|Real Name !! align="left"|SF ID !! align="left"|Yahoo ID !! align="left"|AIM ID !! align="left"|ICQ !! align="left"|Teams
|-
| [[Andrew Wilson]] || Andrew Wilson || nuance || ytitendi || - || - || C, Da
|-
| [[Anestis Kozakis]] || Anestis Kozakis || kenosti || xeno_h || Xeno1970 || 837313 || '''B''', W
|-
| [[Chris Chandler|Barak]] || [[Chris Chandler]] || barako || Barak20021 || - || - || '''B''', Da, Do, O
|-
| [[Chuck Pint|chuckpint]] || [[Chuck Pint]] || chuckpint || chuckpint || - || - || '''B''', O
|-
| [[Connor Petty]] || [[Connor Petty]] || cpmeister || mistercpp2000 || MrBooyah314 || - || A, C
|-
| [[Devon Jones]] || Devon Jones || soulcatcher || hunterd_us || - || - || A, (formerly B), C
|-
| [[Doug Limmer]] || [[Doug Limmer]] || distant-scholar || - || - || - || Da
|-
| elrotheonk || Paul Shipley || elrotheonk || pshipley || - || - || Da
|-
| [[Chris Griffin]] || [[Chris Griffin]] || gjorbjond || - || - || - || Da
|-
| [[James Dempsey]] || [[James Dempsey]] || jdempsey || james_dempsey_au || tallandir || 21047253 || A, '''B''', C, R, W
|-
| [[LegacyKing]] || [[LegacyKing|Andrew Maitland]] || amaitland || drew0500 || paramedic4553 || 5830737 || '''B''', Da, Do, O, R, T, W, P
|-
| [[Martijn Verburg]] || [[Martijn Verburg]] || karianna || karianna03 || karianna02 || 39886145 || '''B''', C, Da, Do, O, T, W
|-
| [[Eric C Smith|Maredudd]] || [[Eric C Smith]] || maredudd800 || maredudd800 || Maredudd || - || Ad, '''B''', Da, Do, DL, P, T, W, R
|-
| [[User:Nylanfs|Paul Grosse]] || [[User:Nylanfs|Paul Grosse]] || nylanfs || Nylanfs || Nylan8 || 14397299 || Ad, '''B''', Da, DL, P, T
|-
| [[Stefan Radermacher]] || [[Stefan Radermacher]] || zaister || zaister || - || 6510566 || C, Da, Do, W
|}

=Passive Volunteers=
These volunteers are currently passive on the PCGen project, that usually means they have insightful things to say on our internal mailing lists, but don't have enough time left over from RL to add code etc :). '''Please do not remove these people from SF'''

{| border="1"
|-
! align="left"|SF Team Name !! align="left"|Real Name !! align="left"|SF ID !! align="left"|Yahoo ID !! align="left"|AIM ID !! align="left"|ICQ !! align="left"|Teams
|-
| '''[[Bryan McRoberts]]''' || '''[[Bryan McRoberts]]''' || '''merton_monk''' || '''merton_monk''' || - || - || '''B,C'''
|-
| B. K. Oxley (binkley) || B. K. Oxley || binkley || - || - || - || C
|-
| [[Greg Bingleman]] || [[Greg Bingleman]] || byngl || gsbingl || - || - || C
|-
| Paul M. Lambert || Paul M. Lambert || plambert || - || - || - || -
|-
| Thomas Clegg || Thomas Clegg || arknight || - || - || - || C
|}

=Inactive Volunteers=
These volunteers are currently inactive on the PCGen project
{| border="1"
|-
! align="left"|SF Team Name !! align="left"|Real Name !! align="left"|SF ID !! align="left"|Yahoo ID !! align="left"|AIM ID !! align="left"|ICQ !! align="left"|Teams
|-
| [[David R. Bender]] || [[David R. Bender]] || papa_drb || Papa_DRB || - || - || Ad, '''B''', Da, P, Q, T
|-
| [[Henk Slaaf]] || [[Henk Slaaf]] || henkslaaf2 || - || - || - || Da
|-
| [[Alec Ross]] || [[Alec Ross]] || haelduksf || haelduksf || haelduksf || 50824602 || C
|-
| [[Tir Gwaith|Andrew McDougall]] || [[Tir Gwaith|Andrew McDougall]] || tir-gwaith || tir_gwaith || TirGwaith || - || Ad, '''B''', C, Da, Do, DL, R, O, T, W
|-
| Aaron Divinsky || Aaron Divinsky || boomer70 || boomer70 || - || - || C, Da, Do
|-
| [[Andargor]] || - || Andargor || andargor || - || - || C, Da
|-
| Thomas Cooper || Thomas Cooper || lordoxide || - || - || - || C, D, W
|-
| [[Tod Milam]] || [[Tod Milam]] || tmilam || twmilam || - || - || C, Da, R
|-
| [[Tom Parker]] || [[Tom Parker]] || thpr || thpr || - || - || A, '''B''', C, T
|-
| Zacharia Bickley || Zacharia Bickley || kapnbanjo || - || - || - || -
|-
| [[Paul W. King]] || [[Paul W. King]] || kingpaul || pkingdnd || ShutUpPaul || - || '''B''', Da, DL, O, P, T
|-
| Per Christian Henden || Per Christian Henden || perchrh || perchrh || - || 48325984 || C
|-
| Peter Yovich || Peter Yovich ||pyovich|| pyovich || - || - || Da
|-
| Phantom of Krankor || Phantom of Krankor || y2krankor || - || - || - || Da
|-
| Robert Ward || Robert Ward || rward30 || rward_30 || - || - || R
|-
| [[Shelley Stephen|Shelley]] || [[Shelley Stephen]] || takenote61 || takenote61 || takenote61 || - || Da
|-
| ankur rathi || Ankur Rathi || ankurrathi || - || - || - || C
|-
| Arjan van Ginneken || Arjan van Ginneken || Sjappo || Arjan_van_Ginneken || - || - || Da
|-
| Brad Stiles || Brad Stiles || bsmeister || - || - || - || C, R
|-
| Dark Mike || - || swtrse || - || - || - || C
|-
| Dave Cheever || David Cheever || takeyabue || - || - || - || Do
|-
| [[Eddy Anthony]] || [[Eddy Anthony]] || eddyanthony || eddyanthony || - || - || (formerly '''B'''), C, Da, Do, O, R, T, W
|-
| [[Terry FitzSimons|Fitzs]] || [[Terry FitzSimons]] || fitzs || Fitzsimons_T_J || - || - || Da, Do
|-
| Fluxxdog || [[Michael W. Fender]] || fluxxdog || fluxxdog || fluxxdog || 346992562 || Da, Do, O, T
|-

| Hades Lucifer || - || hadeslucifer || - || - || - || C
|-
| Jason Buchanan || Jason Buchanan || lonejedi || - || CMPLoneJedi70 || - || C
|-
| Jayme Cox || Jayme Cox || jaymecox || - || - || - || C
|-
| [[Jonas Karlson|Jonas Karlsson]] || [[Jonas Karlson|Jonas Karlsson]] || jujutsunerd || pjak || jonask42 || 2345481 || C
|-
| MotorViper || Mark Jeffries || motorviper || MotorViper || || || C

|-
| apsen || Andriy Sen || apsen || - || - || - || C
|-
| Bart || Bart Rompelman || necrodeath || - || - || - || T
|-
| Bill || Bill Neumann || lodivigo || - || - || - || -
|-
| Brian || - || telechus || - || - || - || C
|-
| Briarius || Brian Spurling || briarius || sirbriarius || SirBriari1 || 9007056 || -
|-
| Chad || - || litesgod || - || - || - || -
|-
| Charles || Chuck Hazard || chuckhazard || - || - || - || -
|-
| [[Charles Burkett]] || [[Charles Burkett]] || Kyth || Charlesb_06 || Phule50000 || - || Do, P
|-
| Schporto || Chris Donohue || chrisdonohue || - || - || - || -
|-
| Dan Parks || [[Dan Parks]] || dbd22 || misanthropiclo || thedbd22 || - || C
|-
| David Lim || David Lim || aberrant80 || aberrant80 || - || - || Do
|-
| David || David Rosenthal || rimbeaux || - || - || - || W
|-
| David Saulnier || David Saulnier || dsaulinar || - || - || - || Da
|-
| deltadave || David Lockwood || deltadave || roninkelt || deltadave || - || -
|-
| Dennis Baker || Dennis Baker || mtbOgre || - || mtbogre || - || Da
|-

| [[Eduard Martinescu]] || [[Eduard Martinescu]] || arvoreen || - || - || - || C
|-
| Edwin C Holley || Edwin C Holley || glasswalker || GlassWalkerTheurge1968 || - || - || R
|-
| Eric Jarman || Eric Jarman || oracleofbargth || - || - || - || C, Da
|-
| [[Frank Kliewe]] || [[Frank Kliewe]] || frank_kliewe || frank_kliewe || - || - || Da, Do, O, T
|-
| gawaine42 || Richard Bowers || gawaine42 || richardsbowers || richardsbowers || - || O
|-
| [[Jason Horner]] || [[Jason Horner]] || jlhorner1974 || jlhorner1974 || - || - || Da, O
|-
| Jasper Spaans || Jasper Spaans || jasperspaans || jasperspaans || - || - || C
|-
| [[Joe Frazier, Jr.]] || [[Joe Frazier, Jr.]] || jfrazierjr || joefrazierjr || jfrazierjr || - || C
|-
| John Zittlau || John Zittlau || naarok || naarok || naarok17 || - || -
|-
| Josh || Josh Johnston || pucspifo || - || - || - || -
|-
| Julio Esslinger Viegas || Julio Esslinger Viegas || julio_ev || - || - || - || C
|-
| Dracorat || Keith Ratliff || dracorat || - || - || - || -
|-
| [[Kent Behrends]] || [[Kent Behrends]] || bci || kent_behrends || KentAtBci || - || -
|-
| [[Kevin Fernandes]] || [[Kevin Fernandes]] || darkstorm999 || kevin_fernandes01453 || darkstorm0000 || - || C
|-
| [[Koen Van Daele]] || [[Koen Van Daele]] || vandaelek || koen_van_daele || Kador99 || - || C, W
|-
| Kurt Wimmer || Kurt Wimmer || kwimmer || - || - || - || C
|-
| Michael Beaver || Michael Beaver || michaelbeaver || - || - || - || B
|-
| Michael Durant || Michael Durant || miked_msn || miked_msn || - || - || Do
|-
| Michael Gray || Michael Gray || mhgj || - || - || - || Da
|-
| Mike || - || javadrinker || - || - || - || -
|-
| Peter Barker || Peter Barker || pjdb || - || - || - || C
|-
| PK Lucas || PK Lucas || pklucas || pklucas || - || - || -
|-
| Phillip Ryan || Phillip Ryan || historyphil || phillipryan49 || - || - || Da
|-
| Ratheof Blithwyn || Anders Lindgren || blithwyn || - || - || - || Da
|-
| Reed Thornton || Reed Thornton || rthornton13 || - || - || - || -
|-
| [[Rick Ryker]] || [[Rick Ryker]] || kerrik || rick_ryker || Rick Ryker || - || C
|-
| Sigurdur H. Olafsson || Sigurdur H. Olafsson || sholafsson || - || - || - || Do
|-
| Theryon Stormrune || David T Jacobson || shadowcat || - || - || - || R
|-
| Tistur || Miriam Sexton || tistur || gryphondreams || tistur || - || Do
|-
| tlavalle || Tony Lavalle || tlavalle || - || - || - || C, O
|-
| Tymophil || Philippe Aube || tymophil_fr || - || - || - || -
|-
| Vincent || Vincent Yanda || lunaticlord || lunaticlord || - || - || -
|-
| Walter Duncan || Walter Duncan || wduncan || - || - || - || C
|-
| Walter Duncan || Walter Duncan || pcgen_autobuild || - || - || - || C
|}

=Teams Key=

{| border="1"
|-
! align="left"|Key !! align="left"|Team
|-
| A || [[Architecture]]
|-
| Ad || [[Advertising]]
|-
| B || [[Board of Directors]]
|-
| C || [[Code]]
|-
| Da || [[Data]]
|-
| Do || [[Documentation]]
|-
| DL || [[Data License]]
|-
| O || [[Output Sheets]]
|-
| P || [[Publisher Liaison]]
|-
| Q || [[QA Monkey]]
|-
| R || [[Release]]
|-
| T || [[Tracker]]
|-
| W || [[Website]]
|}

Data

2010-10-28T20:09:59Z

Elro the onk: Added self to Data lemur list

{| align="right"
| __TOC__
|}
=Introduction=

Welcome to the Wiki section of the Data team! The data team is a sub team under the umbrella of the [[Content]] team.

=Mission Statement=
To create data for PCGen that encompasses all aspects of character creation, is true to the publisher's intents and results in output that is correct and complete.

=Data Meetings=
* [[Data Meeting Availability]]
* [[Data Meeting Logs]]

=Resources=
* [[Joining the Data Team]]

* [[Data Team Tools]]
* [[Dataset Creation/Maintenance]]
* [[Dataset Testing]]
* [[PCGen Data Team Processes (JIRA)]]
* [[PCGen Data Team FAQ]]
* [[PCGen Data Team Useful Links]]

* [[Data Team Resource Page]]

=Active Team Members=
Members of this team (and areas of specialty/responsibility) are:

===[[Explanation of Teams#Silverback|Silverback]]===
* [[Chris Chandler|Barak]]

===[[Explanation of Teams#Second|2nd]]===
* [[LegacyKing|Andrew Maitland]]

===[[Explanation of Teams#Chimp|Chimp]]===
* [[Chris Chandler|Barak]] - Tag design, consulting (CMP datasets)
* [[User:Nylanfs|Paul Grosse]]
* [[LegacyKing|Andrew Maitland]]
* [[Stefan Radermacher]], [[Pathfinder RPG]]
* [[Eddy Anthony]]

===[[Explanation of Teams#Gibbon|Gibbon]]===
* [[Paul W. King|Paul King]]
* Phantom of Krankor
* [[Eric C Smith]]

===[[Explanation of Teams#Tamarin|Tamarin]]===
* [[Shelley Stephen]]

===[[Explanation of Teams#Lemur|Lemur]]===
* Arjan van Ginneken
* [[David R. Bender]]
* Fluxxdog
* [[Martijn Verburg]]
* [[Terry FitzSimons]]
* Thomas Cooper
* [[Tod Milam]]
* Ainvar Garrettson

* [[Allen Cohn]]
* Harvey Howell
* Henk Slaaf - Q&A, Patches
* Terry Milnes - Q&A, Patches
* Swiftbrook - Pathfinder
* John Bauldree
* Anestis Kozakis
* Monty, aka Fabio Montanari - 3.5e
* Peter Y. - Pathfinder
* Jonathan A. Arnold - Homebrew Help
* [[Distant_Scholar]] - Has experience
* Paul Shipley (aka elro the onk)

===Special Titles===
{| border=1
|-
| [[Shelley Stephen]] || 1st flunky in charge of finding weird bugs
|-
| [[Tir Gwaith]] || [[Strange Monkey]]
|}

=Inactive Team Members=

===[[Explanation of Teams#Silverback|Silverback]]===
* [[Eddy Anthony]]
* [[Frank Kliewe]]

===[[Explanation of Teams#Chimp|Chimp]]===
* [[Tir Gwaith]] - 3e, 3.5e, Races, Classes, Prettylst
* Michael Gray (taluroniscandar) - 3e and 3.5e Psionics
* Aaron Divinsky, Default Monster Kits, [[Internationalization]]

===[[Explanation of Teams#Tamarin|Tamarin]]===
* Ratheof Blithwyn

===[[Explanation of Teams#Lemur|Lemur]]===
* [[Andargor]]
* David Saulnier
* Dennis Baker
* Eric Jarman
* [[Jason Horner]]
* Phillip Ryan - PrettyLst

===Special Titles===
{| border=1
|-
| [[Andargor]] || Amoeba
|}