Bugs, news and stuff: [pcgen] Code Team

Friday, January 22, 2016

[pcgen] Code Team

Hi Team and everyone else,

As you may, or may not, have read, James Dempsey has stepped down from
the position of Code Silverback and active contributions to the PCGen
project. He gave 15 years of committed dedication to the project, and
for that there is never enough gratitude we can express for the long
days and weekends, patching and assisting with development of this
project. We wish him well in his future endeavors and a big hearty
monkey roar of "Thanks for everything James!"

With James' departure, there are some big shoes to be filled, and even
larger gaps that will become apparent.

First, we now have no active Code reviewer for github pull requests.
This is where I ask for everyone on the code team to give a little more,
and participate in the pull request process by reviewing the code and
adding helpful comments. This will aid in moving pull requests forward
as is the intention of peer review.

Of course, we will be looking to fill to vacant position of Code
Silverback, and all the other roles that James had a hand in.

If you have Java programming experience, and feel you can be an active
contributor both to the code base and running pcgen project, we'd love
to hear from you.

For the position position of Code Silverback, if you feel you would be a
good fit, please email me. HELP@PCGEN.ORG.

For an overview of the Code Silverback responsibilities:
1) Manages the Code Team
2) Determines which patches are safe to include during an RC Cycle
3) Veto Power over Releases as the Release 2nd (Under Admin)
4) Participates in Monthly Board of Director Meetings, or designates a
2nd to speak on his/her behalf
5) Reviews Code Trackers and determines what should be worked on
6) Reviews Code Pull Request Submissions for code correctness, proper
licensing headers, etc.
8) Coordinates PCGen Project Direction with other Board Members
9) Coordinates Code Development in conjunction with Content Team and
Architecture Team
10) Helps set release cycle schedules, and determines when a phase is
concluded for a given release series
11) Works on Features and Bugs to improve PCGen
12) Calls and runs code team meetings when deemed necessary

Traditionally, the Autobuild Process and Gradle/Spring fall under code
purview. We manage Github PRs with Jenkins and Jira interfaces.

Extra Knowledge of HTM, XML, XSLT, and FO is optional, but nice to have.

Once again, a big Thank You to James Dempsey, he made a huge impact on
the project with his steady hand, and constant guidance.

Cheers,
Andrew