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 -~----------~----~----~----~------~----~------~--~---
