On 2/9/06, Ian Bicking <[EMAIL PROTECTED]> wrote:
> Ilias Lazaridis wrote:
> > I don't know why there are delays, but I start to feel a little bit
> > uncomfortable within this project.
>
> No one has blackballed you behind the scenes or anything, it's just that
> the project is just in a bit of a limbo.
A better way to put it would be that the project maintainer is doing a
really poor job and that you shouldn't take the lack of response
personally. Allowing potential contributors to become as frustrated as
you've seem to be come is simply inexcusable.
> But that brings up a point -- should we look into moving Pudge to a
> different location? Or, can we open up lesscode to more administrators?
> I think the only real administrative tasks of import are svn
> administration, and potentially Trac administration (if, for instance,
> the Trac instances started getting spammed -- for normal stuff Trac is
> open enough it's not an issue).
We can absolutely do that. David Stanek is going to start managing
releases for Kid so I need to figure out how shell access is going to
work. If someone here wants to take over maintainership for Pudge, I'd
appreciate it immensely and I think the project would have a much
better chance of moving forward.
> Another question is if we should look at moving the code from Pudge
> into, say, docutils, or otherwise merge Pudge into another system. (Not
> necessarily the package itself -- I don't think merging packages is
> constructive -- but merging the groups and development process might be
> helpful. The buildutils stuff should be moved over too -- with
> setuptools entry points you don't need much infrastructure to add a command.
I'd love to see pudge adopted by docutils to be honest. If anyone
wants to pursue that route more formally, they have my blessing :)
Thanks,
--
Ryan Tomayko
[EMAIL PROTECTED]
http://naeblis.cx/rtomayko/
http://lesscode.org/
_______________________________________________
Pudge mailing list
[email protected]
http://lesscode.org/mailman/listinfo/pudge
