Calendar Talk:Deprecated:NewRoadmap

jminta's comments

As per IRC discussion, I'm not very completely comfortable with the 0.3 goals listed here. They range from somewhat high-level all the way down to bug-level. In my opinion, roadmaps need to stay out of bugzilla as much as possible. (When was the last time you saw a bug # in a firefox roadmap?) However, we've now been operating for a fair bit of time without a lot of direction, which decreases productivity and increases frustration. As such, I'd like to go ahead and give my own list of proposed high-level goals for 0.3 in both Sunbird and Lightning.

Common goals

• No known dataloss with ics from *any* source (preserve X-Comps/X-Props, handle foreign timezones)
• Bug fixes from previous releases
• Improved task support (recurrence)
• Continue to sync code between Sb and Ltn
• Fix/improve CalDAV
• (maybe) Safety when multiple users edit a calendar

Lightning

• Feature parity with Sunbird
• dog-food iTIP/iMIP
• Localization?

Sunbird

• Be a Modern toolkit app (Prefs, Installer, l10n, etc)
• Feature Parity with 0.2 (calendar loading, offline use?, printing, multiple selection)

Commentary: The bits in parens are only met to be examples for clarification. They are not exhaustive or definitive lists and should not be considered part of the actual roadmap.

I still think we need to make sure that Sunbird 0.3 is a linear step forward from 0.2. This will not only ensure that we will rarely deal with 0.2 support problems, it will also help to encourage migration from the calext to lightning, since the parallels will be clearer.

Parts of this list seem to be reaching a bit far (offline use, mutliple edit safety), but according to the current agreements, we're only going to have a couple releases before 1.0, which means we need to front-load a bit more if we're going to have a chance of meeting that.

During release time we can also point to

• Improved speed
• Restructured recurrence

lilmatt's comments:

jminta: I took most of your stuff and included it verbatim. I waxed poetic on the "tracking bugs vs. blocking flags" subject, and then decided it was best to split it out to its own page.

Feel free to tweak.

ctalbert's comments:

I think these goals are very good. The one recurring theme is "make 0.3 a linear step from Sunbird 0.2". We have listed several high level features that are needed to achieve this, but I feel that we need to get more specific in order to finalize this list. Here is Joey's list with my ideas on where we need to get more specific.

Common goals

• No known dataloss with ics from *any* source (preserve X-Comps/X-Props, handle foreign timezones)
  • This seems to be specific enough.

• Bug fixes from previous releases
  • Has this already been finished? I recall it being mentioned in one of the meetings...

• Improved task support (recurrence)
  • Is this merely adding recurring tasks?
  • What other improvements are needed here?

• Continue to sync code between Sb and Ltn
  • If this is to be included, then what specific components are we going to sync between the two products for 0.3?
  • Can we outline which other components need syncing and during which milestones that work will occur?

• Fix/improve CalDAV
  • Which features need improvement? Can this be broken down further?

Lightning

• Feature parity with Sunbird
  • Can we enumerate these features?

• dog-food iTIP/iMIP
  • I think that a good goal for iMIP/iTIP in 0.3 is to be able to send and receive Lightning meeting requests. The next step would be allowing acceptance of meeting requests from other clients.

• Localization?
  • From lilmatt's work, how much is left to do here?

Sunbird

• Be a Modern toolkit app (Prefs, Installer, l10n, etc)
  • It seems that lilmatt has addressed some of this with Prefs and l10n, what else is needed to be addressed in the 0.3 timeframe, what needs to happen in the future milestones?

• Feature Parity with 0.2 (calendar loading, offline use?, printing, multiple selection)
  • Can we do some of this for 0.3, and push off other items? It really depends on what we need to be a "linear step from Sunbird 0.2". For example, perhaps we allow the user to print only a week view in 0.3, and push other printing support to later releases.

Again, I'd like to reiterate that I don't want to have a list of bugzilla numbers drive the roadmap. There is an intermediate level between the specific bugs and these high level goals. If we outline the specific features we want to see beneath each of these headings, it will make it much easier to prioritize and decide what belongs in 0.3 and what belongs to the future milestones.

Unfortunately, I haven't had the time to take a super detailed look at the differences between current Sunbird and Lightning and the old Sunbird 0.2. I'll take a more detailed look and see if I can help to answer some of these questions. In the meantime, perhaps folks with more experience can chime in.