[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-requirements] Current status
cc'ing the main list, at least initially, and reminding everyone there that we're starting up the ODF-Next discussion on the Requirements subcommittee list. Join if you want to participate. So my big question is what do we want to do in ODF-Next. Since that is too big a question to answer outright, I think that leads to the question, how do we determine what ODF-Next will be? It seems we can do a bottom-up approach, where we look at deferred feature requests and public comments, and build a plan around that. And another approach is top-down, where we articulate a broad vision and then fill in the details, including where appropriate deferred features. Or you could do a mix of both approaches. But I think we probably should agree on the general parameters of what ODF-Next is. For example, one set of parameters might be: "ODF-Next is an incremental revision of the standard, intended to be backwards compatible and with a target to publish within 18 months," Another vision might be: "ODF-Next is a purification and modularization of the existing capabilities of ODF, with the intent to make it a more flexible framework for future innovation" And so on. I think that is something we need to come to agreement on sooner rather than later. Is "ODF-Next" something small, incremental and backwards compatible? Or is there something bolder we want to do? -Rob Bob Jolliffe <email@example.com> wrote on 07/16/2010 09:52:24 AM: > > Hello > > I've been looking through the current status of issues targeted for > ODF-Next. These being jira issues with a fix-for-version set as > ODF-Next. > > http://tools.oasis-open.org/issues/browse/OFFICE/fixforversion/10019 > > There are 213 such issues currently, of which 92 have not been > categorized ie. not assigned to a component. I think the first > priority is to work through these and get them classified. Do people > agree? I tried doing this today but there is some problem with my > jira login which I'm still trying to resolve :-(. I really hope I can > solve it soon. Of course the 92 only represent those issues which are > currently tagged odf-next. That number will surely grow as more > issues get relegated into this zone. > > Following that we need to determine how best to convert all of this > into an ordered plan of action. I'd welcome some discussion on how > best to proceed with this. I'm thinking the best approach would be to > go through category by category and try and summarize themes, related > issues, major upheavals vs minor edits etc.