Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Feel free to add your idea or elaborate on an existing one. This listing is intended for prospective contributors, Google Summer of Code students, and others interesting in becoming part of the Mylar developer community.
- bug 116487: create performance test harness
- Identify key performance bottlenecks and address existing performance bugs.
- Wiki integration (existing plug-ins: wikipedia, confluence): structure, rich editing (wysiwyg, render comments), use status whiteboard for a base wiki URL
Structure bridges connect Mylar's task context model and task-focused UI to domain-specific tools and artifacts. Note that some bridge implementations fall out of the scope of the Mylar project itself and should reside in the projects that they integrate with. For documentation see: Context API
- bug 162558: C/C++ via CDT
- bug 150772: RadRails
- bug 176804: PHP via PDT
- bug 167456: PHPEclipse
- bug 161829: Texlipse Latex
- bug 144564: AspectJ
- bug 111700: active folding for WTP XML editor
* Address book & identity management (buddy list bug) * Duplicate detection * Statistics reporting for Mylar Monitor
- Example csv-based 'local' repository (example of local repository)
- Maven tasks plug-in: http://maven-plugins.sourceforge.net/maven-tasks-plugin/
- PDE Wizards for connectors: https://bugs.eclipse.org/bugs/show_bug.cgi?id=170395 (cheat sheets)
Many bug reports request improvements for Mylar's support of development workflows. An example is to trigger a commit when a bug is closed.
Goals for the project:
- Make necessary changes to the Mylar API to support integration across all connectors
- Implement a user interface for customizations of workflows