Re: VersionControl_Bzr
| From: | Daniel O'Connor | Date: | Wed, 04 Jan 2012 13:06:36 +0000 |
| Subject: | Re: VersionControl_Bzr | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-54669@lists.php.net to get a copy of this message | ||
On Tue, Jan 3, 2012 at 8:27 AM, Bjorn Wijers <burobjorn@gmail.com> wrote:
> Hi,
>
> I just joined the PEAR list because I'm interested in creating a PHP
> library for dealing with Bzr (Bazaar see http://bazaar.canonical.com¥eU÷
> ñ`’V‹/[Ã).
> Mainly because I want to use it with Phing for my own projects.
>
> I've looked at VersionControl_Git and VersionControl_Hg. The
> implementations seem to differ quite a lot and I would like to know if
> there is some consensus on which approach is recommended.
>
> As far as I can see the VersionControl_Hg implementation is still in the
> proposed phase and the VersionControl_Git is already accepted and in alpha.
> My personal gut feeling is that the VersionControl_Hg is more mature,
> although it's not part of PEAR yet.
>
> I've never created a PEAR package so far and could use some mentoring or
> get some pointers in the right direction. Thanks in advance!
So - general advice; I'd say don't wait for us - start hacking away.
There's Pirium or http://pearhub.org/ which will easily allow
you to
publish your package in a pear installable way.
VersionControl_Git I pushed through because we swapped pearweb to Git...
and kind of needed an provider for some of our packaging.
Don't shoot me for saying it, but PEAR as a group of developers is just
starting to really like github. I have no idea if there's a bzr equivalent,
but it might be worth just getting code out there on github to get enough
interest/eyeballs on it.
In general terms, we don't really mind what your package looks like,
assuming:
You run PHP_CodeSniffer across it once or twice
You pick sensible class/package names
Unit test coverage is a big plus.
Being Dependency injection friendly/avoiding statics - I'm keen on this, as
it promotes testability, I think others also don't mind it.
Most of all - KISS.
I take it you are currently targeting php 5+, not specifically 5.3?
If you are targeting 5.3, I'd have a chat to some of the pear2 devs - they
can give you a bit more guidance around package layout/namespaces/etc.
This mailing list or irc (efnet #pear) is usually a good place to find us
and have a chat.