What is the procedure for nominating plugin functionality to go in trac core? I've seen a bit on this list's archives, but (without scouring the list) nothing that's really answered how the process works.
As far as the specific case I'm concerned with, I've written http://trac-hacks.org/wiki/AutoQueryPlugin which I find generally useful (it turns the displayed fields on a ticket to links to queries for tickets with the same values). The reasons I think it might belong in trac core is: * it would be a trivial patch to make * it provides additional functionality in a non-intrusive way * I think (and have heard from others) that this would be a good thing for trac to have I'm more than happy to make a patch and do the work and I don't have any particular timetable for doing this. I'm interested both in the answer to this specific case and also to the general process question. Thanks. Jeff http://www.openplans.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
