Community
Participate
Working Groups
Many external plug-ins are required to get a fully functional Eclipse. Yet some of those plug-ins are also what gives Eclipse a bad name, either because they are cluttering the menus, the toolbars or because they have performance problems. We should go through the top 10/12 of plug-ins and make sure they are good citizens, if not then clean them up.
(In reply to Pascal Rapicault from comment #0) > We should go through the top 10/12 of plug-ins and make sure they are good > citizens, if not then clean them up. What do you think of when saying "[we] clean them up."?
(In reply to Marcel Bruch from comment #1) > (In reply to Pascal Rapicault from comment #0) > > We should go through the top 10/12 of plug-ins and make sure they are good > > citizens, if not then clean them up. > > What do you think of when saying "[we] clean them up."? This could either be volunteering from existing committers, running a contest, using FEEP money on the projects.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This issue has been migrated to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/219.
