OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: OASIS Editor's Manual -- Request for Feedback


The following has worked for us and some further recommendations:

[1] A single coherent document is a good endpoint, but splitting this into individual pieces at the start was a good "divide and rule" tactic as it kept track changes manageable and different folks on the TC, with different levels of expertise and interest in the different parts, could "hold the pen" for the individual pieces. The merge allowed another level of review on overall coherence. 
[2] Having a "best practice" final structure was a real help - we used the TOSCA YAML but perhaps there are others. Perhaps OASIS has only 3 or 4 different types of specification so a new TC could use the best practice document that was closest to their expected needs.
[3] Weekly calls help drive progress (this feels like an agile approach - the artefact is the work in progress, no prep or update presentations, keep managing the backlog on the issues log).
[4] Having a clear idiots guide to what normative means and how to segment normative from non-normative material would help.
[5] Having a specification "mentor" for the TC from OASIS itself would help - although the TC must own the content and technical specs, a mentor could help guide the process of creation and editing.
[6] A broad base of skills in the TC is a good idea. In fact planning on expanding the TC as time progresses is also a good idea.
[7] Having an implemented instance is a tremendous advantage in building a quality specification.
[8] Having a few early F2F meetings helps the team gel, so that as time progresses they work well together.

Take care:
    Dr. David Snelling < David . Snelling . UK . Fujitsu . com >
    Senior Research Fellow / Fujitsu Distinguished Engineer
    Fujitsu Laboratories of Europe Ltd.
    +44-7590-293439 (Mobile)

> -----Original Message-----
> From: Kevin Mangold [mailto:kevin.mangold@nist.gov]
> Sent: 24 April 2017 16:54
> To: Snelling, David <david.snelling@uk.fujitsu.com>
> Subject: OASIS Editor's Manual -- Request for Feedback
> David,
> I am contacting you on behalf of the OASIS Technical Advisory Board (TAB).
> We are putting together a manual that new and existing editors can use to
> facilitate development of their respective project(s). We are hoping that
> your experience as a TC Chair that you would be able to help provide some
> feedback (this email is only going out to TC Chairs and Secretaries -- you may
> wish to forward this to your TC for further discussion).
> If you could provide a couple of items/topics you would think would add
> value to this manual, that would be fantastic! Also, any tips or tricks you or
> your TC has learned through its own development is helpful, too.
> Thank you and your help is much appreciated!
> Kevin Mangold

Unless otherwise stated, this email has been sent from Fujitsu Services Limited (registered in England No 96056); Fujitsu EMEA PLC (registered in England No 2216100) both with registered offices at: 22 Baker Street, London W1U 3BW;  PFU (EMEA) Limited, (registered in England No 1578652) and Fujitsu Laboratories of Europe Limited (registered in England No. 4153469) both with registered offices at: Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE. 
This email is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu does not guarantee that this email has not been intercepted and amended or that it is virus-free.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]