Reply to thread

Message: <blockquote data-quote="thpr" data-source="post: 3289228" data-attributes="member: 48911">Which is what I do because I don't think it's viable to do a chargen in a pure commercial sense ... love for the project has to be your payback.I see another volunteer  <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f600.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":D" title="Big grin    :D"  data-smilie="8"data-shortname=":D" /> Seriously, I respect your concerns over the size of the existing codebase... However, I've only been on the project for about a year... and it's not that bad: no one expects you to know it all.  Besides, there are plenty of places you can help without actually delving into the core part of the code if you want to avoid it.If you really want to help out PCGen, let us know.  I'm sure a number of us - myself or others - would be happy to carry on a discussion of potential things to do, either coding or not.While such a discussion is probably best kept to email (this really isn't the place for it), here are a few thoughts:Since this is of personal interest to me <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)" />, you may have seen the PCGen architecture proposal Devon linked to in a previous thread (the latest version - now 0.2 - is at <a href="http://www.geocities.com/thpr/" target="_blank">http://www.geocities.com/thpr/</a> ).  There are a bunch of opportunities around that: Reviews of the document and solving some of the unresolved issues (architectural work) as well as developing future components (coding).Heck, having someone review the document when that person doesn't know the PCGen code base - but does have devlopment experience and some rules knowledge - would be of great value.  Forcing us to explain it to someone else forces us to think about things in a different way, and that's part of how we learn.  That's also part of why I'm in an open source project - I'm here to learn and teach.  So if anyone out there wants to read the arch doc and ask questions, I'm happy to explain what the thoughts were around any part of it.If you're really into code, some of the new components will be greenfield development (does not depend on the existing codebase).  It's not impacting the current version, but it would be a key component of the next version.  That could be another place to participate.Participating in token development and feature discussions (especially if you have ever worked in LST files) in the pcgen_experimental Yahoo! group is also a good place to be involved and help out (no coding required).Just challenging your size concern... I understand that may not be the sole reason for not joining the PCGen team (but simply the sole publicly stated one), so consider this simply something to think about. TP.--Tom ParkerPCGen Architecture 2nd</blockquote>

Verification