[Servercert-wg] Document Versioning

Ryan Sleevi sleevi at google.com
Sat Aug 17 11:21:29 MST 2019

On Sat, Aug 17, 2019 at 3:46 AM Dimitris Zacharopoulos (HARICA) <
dzacharo at harica.gr> wrote:

> Until today, the Chair or Vice-Chair was assigning numbers to documents.
> If you want us to have a consistent numbering scheme with major and minor
> numbers, you could propose such a scheme in a Bylaws update. We could also
> add it in the topics for discussion in an upcoming governance subcommittee.
> This is more of an administrative issue and should be disconnected from
> the ballot language.

Hi Dimitris,

I forked this thread so as to hopefully disconnect. As you no doubt recall,
given that it's come up with numerous F2F and phone conversations, we don't
really have a process in place to allow the Chair and Vice-Chair to make
modifications to Ballots as they're adopted. The inclusion of informative
revision history, within our documents, also means that we can't simply
take the document as-is and allow the chair to ascribe a version to it.

Despite this, you can see I tried to explicitly make it clear in the Ballot
what the Chair or Vice-Chair could change, in order to ensure that these
changes were captured by Ballot. I agree that we could potentially change
our Bylaws or the process for Ballots within the respective CWGs, since it
functionally ties to the Final Guideline / Final Maintenance Guidelines of
the CWGs, to allow the Chair or Vice-Chair additional flexibility here. As
I've stated in the past, I'm supportive of viewing those two respective
sections in our documents (version history and effective dates) as
informative, non-normative sections - i.e. having no binding weight on
members - and thus supportive of allowing flexibility to edit. I also
support that flexibility for versions.

However, as we don't have that flexibility now, I thought it best to play
it safe.

Perhaps you'd like to write down what the Chair or Vice-Chair should be
able to change, and we can see about formulating a Ballot to permit that?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20190817/fc6b2530/attachment.html>

More information about the Servercert-wg mailing list