Am 12.07.2010 04:46, schrieb Noah Kantrowitz:
I said it before on this thread, but it is apparently worth repeating; if you have an idea you do not need our (core commiters) permission for it. Get some people excited, write some code, see what happens. If you write it nicely modularized chances are it can be released as a plugin even if it is decided it is too [big, complex, specific, etc etc] for core.
Honestly, I wrote some code for smaller features (like functional testing infrastructure for plugins, db upgrade for plugins, notifications use ticket change listeners and some more) where I believed that these changes would be met with approval. Some of them were actually mentioned as a good idea to start by some "core devs".
However in the end, all of them were either dismissed because of changed plans, being to invasive or just rot on t.e.o. My time is so limited that I can't justify spending this time without more coordination.
Note: I don't object the 'code first' idea. I think we're pretty much on the same line as far as this is concerned. I learnt from my ventures that I need to invest more time (which I spent coding previously) in coordination and private chats before.
As someone who contributed about a dozen patches to trac so far all I can say is that sometimes it would be helpful if there would be more guidance and mentoring by trac core developers so that outside authors could get their changes committed.
fs -- Best regards, Felix Schwarz Consultant agile42 GmbH www.agile42.com Grünberger Str. 54 10245 Berlin, Germany Office: +49 30 2005 3958 Fax: +49 30 2007 8274 Amtsgericht Charlottenburg: HRB 111402 CEO Marion Eickmann -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-...@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
