| [eclipse.org-architecture-council] FEEP: AC's recommendations for areas of improvement |
| 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:
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 |