-
Notifications
You must be signed in to change notification settings - Fork 77
Eclipse IDE ‐ Developers Community Call
Upcoming and past meetings are listed in the Eclipse IDE Community
calendar
Everyone that participates or is interested in participating in the development of the Eclipse core itself is invited to join, newcomers are explicitly encouraged to join too. It is planned as an open meeting without a fixed agenda, where everyone can suggest to discuss general or specific topics, changes or issues or can ask questions. This call is dedicated to the development of the core of Eclipse itself, mainly the top-level projects Eclipse-Platform, Equinox, Eclipse Java development tools (JDT) and Eclipse Plug-in Development Environment (PDE). It is not intended to provide support for users or consumers of Eclipse, for that other channels exists. If specific issues or changes are discussed, the exchanged arguments should be summarized in the corresponding issues or Pull-Requests and if decisions are made they should be justified. Of course others not participating in the call should still have the same chance to influence a decision.
-
The following topics were discussed
- General discussion about 'Corporate Capture' of Eclipse and how it affects the innovation at Eclipse in general and about how to improve the founding situation of smaller, yet essential projects.
- IDE UI "is very chaotic. For example, the context menus are very disorganized. How could they get cleaned up in a meaningful way?"
- Caused by many different contributing projects
- Style guide: https://eclipse-platform.github.io/ui-best-practices https://github.com/eclipse-platform/ui-best-practices
- Reducing duplication and improving the organization requires cross-project coordination.
- Suggestion for more placeholders that can be re-used by different projects in order to reduce duplication in the UI.
- "The documentation is overwhelming for beginners and good resources are hard to find."
- "It's all there but especially the official resources/docs are hard to find"
- "Many unrelated things on the main page"
Suggestions to consider a clean-up of or to make the documentation leaner
Because of overwhelming doc and UI the suggestion was made to discuss if the the position of EPPs Packages should be strengthens with a product-owner for each package that makes sure the default content of these packages looks good and the documentation is cleaned up.
- Where to report issues if the exact project is unknown?
Currently https://github.com/eclipse-platform/.github/issues In the future hopefully in the 'eclipse-ide' GitHub organization