[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office] A few thoughts on ODF change tracking
robert_weir@us.ibm.com wrote: > Patrick Durusau <patrick@durusau.net> wrote on 09/21/2010 04:19:20 PM: >>> It is a non-goal for me to make everyone happy. It is clear that for >>> every person who will say, "Why did you approve ODF 1.2 without X?" > there >>> is another person already asking, "Why is taking you so long to > complete >>> ODF 1.2 so we can have Y?" >>> >>> >> True, but "we don't have to please everyone" isn't a mantra that is >> going to win many friends. >> >> Maybe what we do in practice but better to appear gracious and >> interested in feature requests. >> > > I certainly am appreciative of feature requests, especially ones like the > change tracking proposal that came with substantial detail. But I'm even > more appreciative of feature requests that arrived before the agreed upon > deadline for new features in ODF 1.2, a date that was over a year ago. > > Note that it is not that I am not interested in new proposals. It is only > that I am not interested in new proposals for this release, since new > proposals at this point can only be considered if we delay the approval > and publication of the enhancements and improvements we have already made > to ODF, items that also have their own constituencies clamoring for them. > So new proposals at this point, naturally end up being deferred to the > next release. +1 > > If you, or anyone else, has a counter-proposal, I'm all ears. > > As for not pleasing everyone, the OASIS rules are quite clear. The > highest level of approval we need is to get the Committee Specification > approved. That requires 2/3 approval with no more than 25% disapproving. > Higher approval is better, but adding new features doesn't automatically > increase your numbers. For example, I'm likely to automatically vote > against any proposal to add new features at this late stage that do not > already have two or more interoperable implementations from TC members. So > I think it is clear that you cannot make everyone happy. That's also an important point. Michael > >> And having a future schedule when features will appear would not be a >> bad thing. > > All JIRA issues have a "due date" field that JIRA editors can set. So > anyone is welcome to adopt a feature in ODF-Next, assign it to themselves > and set the due date. > > I'm hoping we set more of a regular schedule for the next release and the > exactly features that go into that release will depend on TC member's > interests and priorities. Taking ownership of an issue and committing to > a due date are ways of expressing interest and priority. > > -Rob > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > -- Michael Brauer | Oracle Office Development Phone: +49 40 23646 500 Oracle Office GBU ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Rijnzathe 6, 3454PV De Meern, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]