>> In addition, one could initiate a TEP by first proposing an idea, >> and if >> that idea takes off (voting), one could propose a solution for that >> TEP >> that is then to be integrated into trac based on code review etc. > > 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.
Of course, what can be done in a plugin should be done in a plugin. But what I meant, was of course, a forum where one could propose more fundamental changes to track and put them up for vote, first, describing the change verbally, and, after that some interest was stirred (votes), provide a patch that could then be reviewed by none, one or all of the voters :) That way, perhaps, evolving trac would be more than simply just act on behalf of open tickets and feature requests in the ticket database. And this system could also be used to for example propose individual plugins which have been found useful, to be incorporated into the standard distribution of trac. -- Carsten Klein -- 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.
