This seems like a good point to me. Expanding upon it and playing devil's advocate here... perhaps the symfony repository should not serve as the home for all the plugins, but only 'official' plugins? Between Google Code, Github, and all the rest there are plenty of good free homes for smaller open source projects like plugins. And, multiple projects sharing the same repository (even if many of them are plugins) only leads to an inconsistent repository. Some plugins have their own tags/branches/trunk structure, others don't, etc.
I'm looking at jQuery as my example here. They have quite an extensive plugin-creating community, but all they host on their own site are the packaged releases of the plugins. The individual plugins manage their own repositories, although admittedly some of them don't even bother and just post releases with no visibility into their dev process. If this kind of approach frees up some brain waves from slogging through ancient tickets for possibly abandoned plugins, those brain waves could be spent on something more fun like polishing a rating system for plugins, similar to CPAN or jQuery, or some other mechanism for making sure the cream floats to the top. What do you think? David Brewer On Tue, Sep 15, 2009 at 9:10 AM, Tom Boutell <[email protected]> wrote: > > I do appreciate that limitations of trac are involved here. Bigger > plugins probably need tracs or similar of their own. > > Which is why I'm still so much in favor of the symfony site becoming > an openid provider. > > That way you don't have to log in separately on the symfony trac and > the main symfony plugins site... or on third party community sites, > either. One identity for all of them = a good thing. > > On Tue, Sep 15, 2009 at 11:29 AM, Fabian Lange > <[email protected]> wrote: >> >> Hi, >> >> @Marijn, yes inactivity timeframes are a good idea to come up with. It >> is certainly not a trivial thing to define. >> I also noticed we have quite some empty directories. I dont know exactly >> why... >> >> @Tom, yeah I came across this. Its quite a limitation of the current >> system. "If" there would be a component for each plugin, we could >> manage to associate the ticket. >> Currently fabien owns most of them, and I am in progress of assigning >> them to the user that had the most svn activity on the plugin >> recently. >> I think we can still improve here. >> On the other hand, I don't think that some more or less minor issues >> with trac really hinder "caring" developers to maintain their plugins. >> >> Fabian >> >> > >> > > > > -- > Tom Boutell > P'unk Avenue > 215 755 1330 > punkave.com > window.punkave.com > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
