Re: Genealogy_Gedcom Development
| From: | Daniel O'Connor | Date: | Thu, 18 Feb 2010 21:58:28 +0000 |
| Subject: | Re: Genealogy_Gedcom Development | ||
| References: | 1 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-5600@lists.php.net to get a copy of this message | ||
On Fri, Feb 19, 2010 at 12:43 AM, Ed Thompson <ed4becky@gmail.com> wrote:
> I have been looking into the code for Genealogy_Gedcom and the 3 (?) open
> bugs, one of which I reported. I have rewritten the code to change how the
> tree is that is parsed is created and navigated and enhanced it to address
> the current open bugs.
>
In the process I am updating it in support of GEDCOM 5.5 standard, which
> makes some of the functionality obsolete.
>
Are you all interested in this code as a contributed upgrade to the
> Genealogy_Gedcom package or should I just keep it for myself?
>
>
Patches are certainly welcome.
> If you are interested, does it still need to support pre GEDCOM5.5? Can it
> be upgraded to PHP 5, removing deprecated practices?
>
>
Unfortunately, this package has hit 'stable', so must retain PHP4
compatibility. This makes it tricky to remove all of the deprecated bits and
pieces, and means you can't use a lot of PHP5's goodness.
> If you are interested in my contribution, I will need some guidance,, this
> may be a 2.0, which if I read the PEAR doc right means a separate package?
>
>
That's one option - the process to go through is known as PEPR (
http://pear.php.net/pepr/). Basically, you set up a package
and we pick on
design elements. Things we look for tend to be coding style, unit test
coverage, avoiding statics, global state, etc. It can be a bit daunting and
disheartening, but it's well worth it.
I'll do you a deal - have a chat to me via irc (irc.efnet.org #pear
clockwerx) or any of the others there; and I'll get off my behind at look at
some of the bug reports to try and get something sorted.