[Twisted-Python] Ticket Hall of Shame - Current Loser: Brian Warner
radix at twistedmatrix.com
Sat Jan 13 12:31:13 EST 2007
On 1/13/07, Mars Agliullin <griph at mail.ru> wrote:
> glyph at divmod.com пишет:
> > By "responsiveness" I meant responding to people who report bugs, and
> > being clear on what we are vs. are not working on. The problem I am
> > trying to address is best described here:
> > http://www.jwz.org/doc/cadt.html
> Yes! But there is another problem. Say, one wants some feature to be
> supported in twisted. He/she sends a patch, but it is dropped by the
> core team, since they think it should be implemented another way.
> It is OK, but if the implementation had been discussed before, there
> would be less time lost. Correct me, if I miss something, but more
> detailed roadmaps by the core team would be helpful for everyone who
> wants to participate. If there _are_ roadmaps, give me an URL, please.
> For example, I'd be happy to implement SCGI authentication (ticket
> #1300). But it is better to know in advance, how core team want this
> feature to be implemented. Otherwise it is just a lost time for me to
> code and for the core team to view it.
I don't think this is a systemic problem. If you want to work on SCGI
authentication, and you want to know how the developers think it ought
to be implemented, then you 1. look in the ticket for implementing
SCGI authentication to see if any discussion has happened (or make
one, if it doesn't exist), and 2. ASK the developers how they think it
ought to be implemented. If nobody responds, then there is not much
interest and you can probably feel free to do it however you want.
It's as simple as that. As for a roadmap: sure, roadmaps are nice, and
it'd be good if our project had more direction, but this wouldn't
solve your problem. It's impossible to make a roadmap that would lay
out designs for every possible feature anyone would ever want in
International Man of Twistery
More information about the Twisted-Python