[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] MVP Discussion
Since we are talking in/out list primarily, perhaps we could just have a checkbox for each option? Checking yes means “In for 2.0” and leaving the checkbox empty means “out for 2.0” with no additional clarity about abstain/2.x/never.
Personally I think the important decision in front of the group is the in/out list; the rest of the detail is IMO a nice to have and not necessary to proceed on 2.0 work. This list is something that people will point to for a while, so I’d like to do our
best to get it into the OASIS ballot facility.
Thank you.
-Mark
From: <cti@lists.oasis-open.org> on behalf of Chet Ensign <chet.ensign@oasis-open.org>
Date: Tuesday, April 5, 2016 at 5:35 PM To: "Piazza, Rich" <rpiazza@mitre.org> Cc: "Jordan, Bret" <bret.jordan@bluecoat.com>, "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> Subject: Re: [cti] MVP Discussion All,
Bret and I talked about what sort of information he'd be looking to collect. Something along the lines of...
Option 1: Yes, No, Maybe, Abstain, 2.0, 2.1, 2.x, Never
Option 2: Yes, No, Maybe, Abstain, 2.0, 2.1, 2.x, Never
...
It is indeed difficult to see how that could be done with the OASIS ballot facility. My two concerns are (a) that whatever ballot mode is used must be available to all members and (b) that
there must be some way to ensure the results of such a ballot are available for the long haul in the TC's archives.
I doubt that anyone would be blocked from using SM so no problem there. So I'm ok with doing it this way:
- Bret (or whoever) posts an email to the TC mailing list pointing to the survey and giving an end date when it will be closed.
- When the survey is closed, the detailed results are downloaded and loaded to the TC's or Subcommittee's document repository. The email that is generated when a document is loaded can be
annotated to state that these are the results of the survey mentioned over there.
That way, 3 or 4 years from now, if someone asks 'how did you come up with that list' there is an audit trail to point to.
We also discussed an approach to making the issues being debated in Slack easier for those outside the discussion group to track. More to follow on that but one key thing I suggested was a
disciplined use of an issue tracking system. While we are in discussions to migrate the existing open source projects to OASIS, I told Bret that you should all feel free to request that we start projects for you now if it would be useful (and not redundant
I suppose). The steps for doing that are explained in https://www.oasis-open.org/resources/open-repositories/faq
Best,
/chet
On Tue, Apr 5, 2016 at 1:14 PM, Piazza, Rich
<rpiazza@mitre.org> wrote:
/chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]