Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2009-03-12 16:43:08
Size: 1972
Comment:
Revision 4 as of 2009-03-16 03:30:31
Size: 2016
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
[http://www.eclipse.org/mylyn Mylyn] is an Eclipse plugin (a GUI environment) allowing the management of tasks stored in bugtrackers. It is meant to maximize productivity of the developer using Eclipse in order to avoid changing tools between activities like development and bug fixing. [[http://www.eclipse.org/mylyn|Mylyn]] is an Eclipse plugin (a GUI environment) allowing the management of tasks stored in bugtrackers. It is meant to maximize productivity of the developer using Eclipse in order to avoid changing tools between activities like development and bug fixing.
Line 14: Line 14:
There may not be many Debian developers using Eclipse, so it may not be the preferred engine to manage Debian bugs, but on the other hand Mylyn offers a nice GUI for bug management in general. It may be an interesting alternative to existing tools like bug-triage. There may not be many Debian developers using Eclipse, so it may not be the preferred engine to manage Debian bugs, but on the other hand Mylyn offers a nice GUI for bug management in general. It may be an interesting alternative to existing tools like [[http://bug-triage.alioth.debian.org/|bug-triage]].
Line 16: Line 16:
The debbugs server may not support directly at the moment all tools to manage bugs with a synchronous interface, since modification of bugs is mostly done through asynchronous messages (email). Such a protocol may be quite novel for Mylyn, then. Of course, if a [:SummerOfCode2009/DebbugsWebUI: Web interface is developped] for debbugs, this may change. The debbugs server may not support directly at the moment all tools to manage bugs with a synchronous interface, since modification of bugs is mostly done through asynchronous messages (email). Such a protocol may be quite novel for Mylyn, then. Of course, if a [[SummerOfCode2009/DebbugsWebUI| Web interface is developped]] for debbugs, this may change.

Mylyn plugin for Debbugs

  • Mentor: yet undefined, maybe OlivierBerger (although not a DD, just a DM)

  • Summary: Mylyn plugin for manipulating bugs.debian.org's bugs inside Eclipse

  • Required skills:

    • Eclipse plugin development (or Mylyn plugin development) ?
    • Java dévelopment
    • a knowledge of the debbugs use
  • Description:

Mylyn is an Eclipse plugin (a GUI environment) allowing the management of tasks stored in bugtrackers. It is meant to maximize productivity of the developer using Eclipse in order to avoid changing tools between activities like development and bug fixing.

Mylyn has various plugins to access various bugtrackers, but I don't think that any exists for debbugs, the Debian bugtracker (running at http://bugs.debian.org/).

There may not be many Debian developers using Eclipse, so it may not be the preferred engine to manage Debian bugs, but on the other hand Mylyn offers a nice GUI for bug management in general. It may be an interesting alternative to existing tools like bug-triage.

The debbugs server may not support directly at the moment all tools to manage bugs with a synchronous interface, since modification of bugs is mostly done through asynchronous messages (email). Such a protocol may be quite novel for Mylyn, then. Of course, if a Web interface is developped for debbugs, this may change.

The candidate will definitely need to be familiar with Java and the architecture of Eclipse to be fully operational.

Institut Télécom (through Olivier Berger's involvement as a potential mentor) may partly "physically host" the work of a candidate (spending some days in our labs on the campus in Evry, France, having regular meetings with our team working on the Helios project, etc.), in order to make sure he/she won't work completely isolated, and that continuous progress would be made on the project.