Skip to main content
Jump to: navigation, search

Mylyn/Contribution Ideas

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. Projects that fall outside of the scope of the Mylar codebase are marked "(external)" or provide a link to the project involved.


  • Provide lightweight workflow actions (e.g. trigger a commit when a bug is closed). This involves adding workflow support to the Tasks framework and implementing task editor actions for for workflow (e.g. check-box for performing commit, action for running task context tests). Query current wofklow bugs
  • bug 152415: add a buddy list to ease task assignments and CCs.
  • bug 161877: improve duplicate detection mechanism and heuristics.
  • Provide wiki integration. This involves providing mechanisms for rich editing and viewing of task repository comments in wiki format, potentially adding wiki editing.
  • Improve the new user's experinece. This could involve creating a welcome page, cheat sheets, and streamlining the process of going from installing Mylar to having a task repository.



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 170894: create an example connector project to be used by integrators as a template. This connector should be simple, for example, it could provide integration with a local comma-delimited value (CSV) as the repository.
  • bug 170395: create PDE wizards for automatically generating task repository connectors. These would be similar to the current PDE wizards for creating plug-in projects.

Back to the top