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

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

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


Subject: Re: [docbook-tc] DocBook TC Minutes: 20 January 2016


My apoligies for dropping the ball on this week's meeting. I've been traveling and in meetings all week, and did not even look at my calendar.

I'll adjust the Kavi calendar as Scott suggested.

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net

On 1/20/2016 11:17 AM, Norman Walsh wrote:
DocBook Technical Committee Meeting Agenda: 20 January 2016
=============================================================

Agenda

1. Roll call

Present: Norm, Larry, Scott, Dick

3. Next meeting

Norm at risk. Any objections to moving to 24 February?

None heard. The next meeting will be 24 February.

4. Review of the agenda.

Norm proposes a single item:

What we need to do to move DocBook 5.1 forward.

5. What we need to do to move DocBook 5.1 forward.

Next step is to collect 3 Statements of Use. At least one SoU must
come from an OASIS member. A SoU must include the title, version
number and approval date of the Committee Specification. It also needs
to state whether the implementation meets all conformance clauses or
just some, and if only some, then specify which. It also needs to
state whether or not its use includes interoperation of multiple
independent implementations (e.g. my editor x produces DocBook
documents successfully process by other tools). For OASIS member SoUs,
the company's primary rep must confirm the SoU. The TC needs to pass a
resolution accepting the SoUs.

The form that a minimal SoU takes is typically something like this:

"<your company name> has successfully used DocBook Version 5.1
Committee Specification 01 approved 11 November 2015 in accordance
with the conformance clauses contained in Section 4 Conformance. The
implementation successfully interoperated with multiple independent
implementations."

Norm: I wonder what “multiple independent implementations” means in
this context.

ACTION: Norm to check what “independent implementations” means.

ACTION: Norm to check if it has to be an institutional member.

ACTION: Everyone: beat the bushes for SoUs.

Any other business?

Scott: Once we get to the voting stage, we can get a spreadsheet of
voting members. We can divy those up and reach out to contact them.

None heard.

                                         Be seeing you,
                                           norm

--
Norman Walsh <ndw@nwalsh.com>      | Curiosity will conquer fear even
http://www.oasis-open.org/docbook/ | more than bravery will.--James
Chair, DocBook Technical Committee | Stephens



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