Hi Fabian, I agree there's a lot of old and unmaintained plugins, but I would suggest to be careful. These plugins may still be used in projects, for instance with svn:externals. If we go about and delete the plugins, then this might have an effect on the users of those plugins.
I would suggest the plugins you nominate for deletions are put in a "deep freeze". By this I mean make them read-only in svn for now, notify the lead developer and all contributors of it's status, and clearly put a notice in the plugin system of the status of the plugin at this point. Then we could put a blog post on the symfony blog listing all plugins marked for deletion, with a final call to the community for fresh contributors. After a given period (to be determined), when there is no response from the community, we give a final warning on the blog with a list of plugins that are to be deleted (so that people can pull a final version from svn if they still use it), and then after a certain period, we can delete the plugin. This will take quite some time, but surely this is something we need to be very careful with, because there may be users out there that we don't know. Stefan On Tue, Sep 15, 2009 at 5:05 PM, Fabian Lange <[email protected]> wrote: > > Hi, > We have plugins. a lot. > We have tickets for plugins. a lot. > We have plugins that have not been maintained since 2 years. > > What shall we do? > > I am currently trying to bring trac back into a living system, but > there is a lot of dead stuff inside. > > 1. I deleted all plugins from the components drop down that had less > than 3 tickets. I think until we have a separate bug tracker for > plugins they should use "plugins" as component > 2. There are Plugins which have tickets assigned to the plugin owner > that had no response for quite a while (>1yr). I propose to close the > tickets as won't fix. > 3. There are also Plugins that have many tickets and no source code > changes. I propose to delete the plugin, because it is obviously > abandoned bad code. > 4. There are Plugins that do not have a release and no development > activity. I propose to delete the plugin, because it is abandoned code > that cannot be found in the plugin system > 5. There are Plugins that seem to be used by very few people and have > no activity. But they dont have quality issues. I think we should > introduce a review process to delete duplicate, trivial, pointless > plugins > > Dont get me worng, I really like plugins, I like community activity. > But if we dont do some housekeeping from time to time, the plugin repo > gets a filthy pile of junk :-) > > Comments? Ideas? Proposals? > Fabian > > > > -- Stefan Koopmanschap Symfony Community Manager [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
