Emmanuel Blot wrote:
+0 : I'm ok with the out-of-core implementation, but I think the related discussion about "official" vs. "unofficial" plugins must be discussed first and a decision should be made.For a plugin as important as this one ("important" in terms of how many users need/use it - I don't), the Trac project should guarantee somehow that the MasterTicket plugin will be updated and maintained, especially when some Trac API is broken. I'd favor moving "official" plugins back to t.e.o. so they have a status close to the WebAdmin plugin - before it got merged to the core - and they can be closely managed through a dedicated Trac ticket component, along with Trac Core. From my perspective, there are at least 3 majors plugins out there: AccountManager, MasterTicket and XmlRpc. XmlRpc plugin has been broken or half-working for most of the 0.11 development cycle, and this should not happen again (and again) for 0.12.
I've been forced to concede on the XmlRpc front (as my plans for the ninja branch will require effectively exposing the ticket API over JSON-RPC). I would also add IniAdmin to that list, as I think a lot of people expect total web admin stuffs.
To sum up: let's take a statement about "official" plugins before closing those ones.
Fair enough. If its just an issue of PR, I don't care where the code sits. --Noah
signature.asc
Description: OpenPGP digital signature
