Anything is possible. In the end the TC decides based on its votes. I'm
more interested right now in figuring out how we can converge on a shared
vision without too much bloodshed.
One approach would be to have another call for proposals period. We did a
public one before. And we collected member submissions before. But the
TC membership is different than it was back in 2008, so we should probably
solicit for proposals again.
So first, thing, have another call for proposals. Maybe this can be done
in conjunction with a public review of the ODF-Next paper? In any case,
get all of these proposals in JIRA, categorized as ODF-Next.
Then, have some sort of voting procedure. For example, give each TC
member 20 "points" which they can allocate across any of the proposals.
They could give 20 different proposals 1 point each, or 1 proposal 20
points. Anything that adds up to 20. Well, maybe not anything. Giving
-1000 votes to one proposal and 1020 to another would not be good!
At the same time, ask for volunteers to own the specification of any
particular feature.
We then agree to work on the proposals which have the highest number of
points and which have a volunteer.
-Rob
Hanssens Bart <> wrote on 07/16/2010 03:02:32 PM:
>
> RE: [office] Re: [office-requirements] Current status
>
> Mmz, what about releasing a ODF 1.2.1 / 1.3 first, focusing on
> change tracking ?
>
