| Summary: | support project planning, e.g. via Gantt chart views | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Filip Hoeven <filip.hoeven> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | Keywords: | helpwanted |
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Filip Hoeven
When should I expect a bug report to be answered? Or shouldn't I? There is some calendaring support on a roadmap, but it is unclear if it will make to 2.0 release. We also discussed some ideas for introducing special types of connectors for time management and calendaring tools that would allow to synchronize their data with Mylar's Task List. Sorry for the slow responses on this Filip, you hit our busiest time of year with EclipseCon and Platform API freezes. As Eugene points out, here's what's in scope for Mylar 2.0: http://wiki.eclipse.org/index.php/Mylar_2.0_Plan Our strategy is not to try to re-create planning tools ourselves, but to integrate with existing planning tools via connectors. The XPlanner integration is set to be our reference implementation for planning tools: bug 130240. That said I'm going to leave this bug open and mark it helpwanted in case anyone is interested in contributing additional planning support on the Mylar side. Not enough scope or UI specification for bugday. Also, a contribution of this scope would need to be maintained by the contribor(s). Let's use this bug to discuss implementation in case there is interest in such a contribution. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |