I have a house with 4 adults that are D&D and Pathfinder players and GM's that would be interested in helping with data entry, and I am an expert Java programmer myself with some expertise with FOP (if I can get some pointers on the structure of the code for PCGen).
> On Mar 1, 2017, at 9:57 PM, nylanfs@yahoo.com [pcgen] <pcgen@yahoogroups.com> wrote:
>
>
> Have you noticed that the rate of new books going into each version of PCGen has been slowing? Well there is a reason for that, most notably there is a new formula system coming that will require an overhaul of ALL the data, by hand. This will put a big strain on the remaining data team volunteers.
>
> And I did just say "remaining", you see as an all volunteer project people come and people go, some because RL calls them away and their free time evaporates. Other times people need to step back before they become burned out.
>
> Andrew Maitland is the current Data Lead and will be handling the brunt of the formula changeover, but he is currently holding down a full time-job, going back to school and has family, He is rapidly reaching the burn-out point and plans to step back some and help train the new data volunteers once the new formula system is in place.
>
> What does this mean for you? Have you ever wanted to help the project but found the data intimidating? Here's your chance to get some one-on-one assistance with Andrew and help out your favorite project at the same time.
>
> We are looking for some people to help with the project. We have multiple positions that could use some help, these include (but aren't limited to,) customer support (answer new user's questions mostly), people to help with data entry or deal with data bug fixes, of course we always need people for the Code Team which is the under-the-hood engine of the program.
>
>
>
>
[Non-text portions of this message have been removed]
Posted by: Joseph Bryant <hiucimon@yahoo.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
No comments:
Post a Comment