First of all, thank you for the feedback thus far. This has been very
helpful to me. I take the following key points from this discussion:
- Keep it simple
- Give TCs the flexibility to accomplish the key goals however works
best for them
- Ensure that said "key goals" are clear so that TCs know what is expected
- Give TCs a cookbook with the options and the procedures so that
they need not spend time trying to come up with their own solution
- Provide options
- Spread sheets work just for many TCs. Give them a template or two
to work from
- JIRA works for other TCs.
- Some TCs may prefer to work in word processing documents or in the
TC's wiki - provide guidelines / templates on how to do that
- Specifically for JIRA
- The vanilla configuration currently in place doesn't make usuing
JIRA as straightforward as it might be.
- To improve JIRA, gather input from some volunteers and propose a
JIRA configuration that better suits the workflow requirements for
developing standards.
Please let me know if you have other thoughts, if I missed something
in the dialog, etc. I will consider this a project and organize next
steps on that basis. You can expect to see a call for input on
improving JIRA sometime next week.
/chet
On Tue, Apr 24, 2012 at 6:21 PM, Chet Ensign <> wrote:
> TC Chairs,
>
> Recently, I have had several discussions with people on comment
> resolution logs. As I'm sure you know from the TC Process, TCs are
> required to maintain logs of comments received and their resolution
> and provide them at several different points throughout the process.
> Specifically, in section 3.2 Public Review of a Committee Draft
> (http://www.oasis-open.org/policies-guidelines/tc-process#publicReview),
> the process reads:
>
> "The TC must acknowledge the receipt of each comment, track the
> comments received, and post to its primary e-mail list its disposition
> of each comment at the end of the review period."
>
> Our growing liaisons with other standards bodies is making getting
> this right even more important.
>
> I believe it is becoming more and more important that we accomplish
> both the letter and the spirit of this requirement in order to make it
> easier for commenters to learn of the disposition of their feedback,
> for reviewers to learn what has happened between one public review and
> the next, and for voters to get a full picture of the history of a
> Committee Specification when it is advanced as a Candidate OASIS
> Standard.
>
> I would appreciate hearing your thoughts on how best to accomplish
> this, how best to provide you with the flexibility you need while
> ensuring that the record of comments and resolutions is maintained and
> made available over time. For example,
>
> - Some TCs are using JIRA successfully to track, manage and report on
> comments. Would training in using JIRA for this process be useful?
>
> - Some TCs are using spread sheets to track and report on feedback.
> Would template spread sheets help you adopt this approach?
>
> - Would a document on best practices help you and your TC put a
> mechanism in place to successfully track and report on comments.
>
> Please take a minute to share your thoughts with me on how we can make
> this work conveniently and securely. I want to gather the fruits of
> your experience and thoughts, as well as the feedback from your TC,
> before making any proposals for next steps.
>
> I look forward to hearing from you and meanwhile, thank you for all
> the work that you do here at OASIS.
>
> Best regards,
>
> /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
>
> Follow OASIS on:
> LinkedIn: http://linkd.in/OASISopen
> Twitter: http://twitter.com/OASISopen
> Facebook: http://facebook.com/oasis.open
--
/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
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
