Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] FEEP: AC's recommendations for areas of improvement


Foundation is now looking for a full time platform developer, which is IMHO very good news. Not sure if that will affect the FEEP program has it was originally planned.

Best regards, Lars

On Mon, Jan 18, 2016 at 8:20 AM, Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx> wrote:
Dear EMO,

as requested, the AC discussed how and in which areas the FEEP funding could be spent to improve the Eclipse IDE. The discussion took place on the AC mailing list and AC meetings. The goal of these discussions was to come up with a prioritized list of (potential) FEEP topics or areas of improvements. The results of this discussion are summarized below.

List of potential topics and areas of improvements:

479686[FEEP] Improve GTK 3.0 support1,522
480176[FEEP] Allow user to discover plugins to edit a specific type of file1,521
482409[FEEP] Fix issues in Mac SWT port1,419
482236[FEEP] JVM selection UI in the launcher1,320
482034[FEEP] p2 improvements1,119
480547[FEEP] Prompt user to install additional plugins0,920
480177[FEEP] WTP XML editor technology face-lift0,820
482037[FEEP][platform] Fund a developer to triage and fix the most frequently occurring errors in Platform UI0,620
479536[FEEP] Improve Tooling Support for NullPointerAnalysis0,420
480551[FEEP] Enable "refresh using native hooks"0,420
480024[FEEP][jdt] Fund a developer to triage and fix the most frequently occurring errors in JDT0,420
480546[FEEP] Make everything available in Eclipse Marketplace0,320
481227[FEEP] Improve Dark Theme0,120
479541[FEEP] New Project Website for our IDE-2,02
480550[FEEP] Tips & tricks dialog-0,120
480553[FEEP] Review most used marketplace plug-ins-0,820

The individual AC member voting is available at [1]. This list of topics is considered as a recommendation to the EF but not binding in any sense. 

General Note:

It might be noteworthy that AC members have a different opinions on how concrete a FEEP-funded development task should be: Open-ended topics like „Funding a developer to triage and fix […] bugs in the platform UI“ were discussed controversial. Some requested a concrete list of bugs to fix before FEEP funding should be used; others would be fine to leave it the the person chosen by the EF or the project lead to prioritize which issues to fix. Consequently the voting and granule of the topics varies a lot from proposal to proposal. 

However, the AC appreciates the new potential to improve Eclipse and is looking forward to the results of the first iteration of FEEP. 

Best regards,
Marcel for the Architecture Council

_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web:

Back to the top