Re: [pcre-dev] Development Infrastructure

Pàgina inicial
Delete this message
Autor: Bob Rossi
Data:  
A: Nigel Metheringham
CC: pcre-dev
Assumpte: Re: [pcre-dev] Development Infrastructure
On Wed, Feb 21, 2007 at 11:02:07AM +0000, Nigel Metheringham wrote:
> Working from Philip's document:-
>    http://people.pwf.cam.ac.uk/ph10/pcrefuture

>
> Source Maintenance
> ------------------
>
> If we went with subversion then I would be prepared to do the work to
> import the history into the system.


What history? As far as I understand it, PCRE isn't under revision
control currently.

> Development Infrastructure
> --------------------------
>
> Assuming it is politically OK to host on sesame (would you mind
> following that up Philip), then adding mailing lists, website etc is no
> problem and I would be prepared to do that initial work.


Great!

> If we did not have the existing exim baggage I would tend to put PCRE
> under a trac instance (see http://trac.edgewall.org/ ) which gives a
> wiki, ticketing system and nice integration with source control. Given
> that we already have Bugzilla for exim, I am not sure of the best
> approach, although for a relatively small project I think trac might be
> easier....


That could be true. I used trac for a short time, and didn't like it
that much. The problem was, it implements many nice features and
integrates them nicely. However, the problem for me was, it was
reimplementing many nice features that exist standalone applications
that are better. So from my perspective, it might be better to get your
favorite bug tracker, wiki and web browser, or just order the
"Number 5" at the take out restaurant.

With that said, Trac seemed useful and capable, I wouldn't oppose it.
If it were me, I'd set up mediawiki (or your favorite), viewsvn and
your favorite bug tracker.

> However sourceforge and google can provide a very nicely packaged and
> polished form of the same thing. In either of those cases I am willing
> to provide some degree of project support, although doubt I will be
> doing a ton of code :-)


I would definitely not recommend sourceforge. I've hosted a project there for
years. It's simply terrible. Subversion repo's go down, disk space gets
full, email lists get spammed (subscriber only), .... The list goes on
and on, and there isn't a quick phone call or email that can be made to
correct these problems. You go in the queue. I've never used google,
so I can't comment on that subject.

This is just my opinion. I will however be happy to use any
infrastructure setup. Except possibly sourceforge :), but I'll do it
anyways.

Thanks,
Bob Rossi