Hi, Reading this thread I makes me think about the Eclipse way, specially the whole plugin infrastructure is designed after eclipse:
http://trac.edgewall.org/wiki/TracDev/ComponentArchitecture > IMO it makes sense to "standardize existing practice" -- that is, begin > a program of bringing widely-used and stable plugin functionality into > the trac codebase. Architecurally it could remain "a plug-in," but it > would be officially supported and automatically available. That would > mitigate the "can't run a really nice Trac without installing plugins" > phenomenon and would encourage a sense of continuity between plugin and > core developers. I think having a "trac-europa" or even ganimed "trac-distribtution" contains the mentioned "best-practice plugins" can help to convenience the user and plugin developer while not putting everything in the core and overload the few core developer. Holger --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
