[cabfpub] Draft Charter: Forum Infrastructure Working Group

Jos Purvis (jopurvis) jopurvis at cisco.com
Fri May 18 10:14:07 MST 2018

Excellent questions! Some answers, off the top of my head:
I would see the role of Webmaster and List Manager continuing (for now) as they are in the Bylaws, to avoid incorporating Bylaws changes with this WG. However, I would automatically include the Webmaster and List Manager as members of the FIWG, and then adjust the scope of the FIWG to include supporting their roles. At some point, it might make sense for those roles to transition to the FIWG and have the FIWG select them in some way, but I think that’s a future ballot—I’d rather not introduce too many changes straight off the bat.
For the public mail list, I would say the FIWG should manage the Forum-level mailing lists (in support of the List Manager role, who is automatically incorporated into the FIWG). The FIWG could also offer to do the same for any Working Group that wanted them to, but would not have to do that if a WG wanted to do that for themselves.
For document maintenance, I would see the FIWG as ensuring the website is available and that WG members responsible for content posting have access to post content; the FIWG could optionally offer to do content-posting as a service for WGs. That’s why I automatically included the chair of each WG into the FIWG, as they would have content-posting responsibilities and thus have skin in the game for the FIWG. If a WG chair had issues with content posting (time, technical ability, etc.), he or she could either designate someone else as their ‘Webmaster’ and make them the FIWG member, or request the FIWG do it under some sort of specific SLA that met the Bylaws/Charter requirements for content posting (e.g. “You get us the content within 48 hours of your posting deadline and we’ll have it posted” or some such). Content not covered by a specific WG (e.g. the “About the Forum” pages) would be the responsibility of the FIWG to create and maintain.

-- Jos


Jos Purvis (jopurvis at cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)



From: Ryan Sleevi <sleevi at google.com>
Date: Friday, 18 May, 2018 at 12:45 
To: "Jos Purvis (jopurvis)" <jopurvis at cisco.com>, CA/Browser Forum Public Discussion List <public at cabforum.org>
Subject: Re: [cabfpub] Draft Charter: Forum Infrastructure Working Group


Thanks Jos. This looks like an exciting CWG and a great model of a charter, especially the ruling of things out of scope (for the time being). 


A few things of note:

- What role or relationship will the FIWG have with respect to the Webmaster (per Section 5.2 of the Bylaws). I realize you call out the FIWG doesn't supplant that role, but it might be good to clarify that relationship.

- What role or relationship will the FIWG have with the Public Mail List - does that fall under the aegis of the current web software (i.e. https://cabforum.org/mailman/listinfo/ ) or do you see that as separate? It might be good to clarify.

- What role or relationship will the FIWG have with document maintenance for the publication to the Website, if any?


Overall looks good, and figured there were some gray areas in between worth clarifying.


On Fri, May 18, 2018 at 12:14 PM, Jos Purvis (jopurvis) via Public <public at cabforum.org> wrote:

Per this week’s call, please find below a rough first pass at a charter for a Forum Infrastructure Working Group, to take on management of the website and wiki for the Forum. All comments, feedback, kibitzing, etc. welcome. :)


Forum Infrastructure Working Group

Upon approval of the CAB Forum by ballot, the Forum Infrastructure Working Group (“FIWG”) is created to perform the activities as specified in this Charter, subject to the terms and conditions of the CA/Browser Forum Bylaws and Intellectual Property Rights (IPR) Policy, as such documents may change from time to time. The definitions found in the Forum’s Bylaws shall apply to capitalized terms in this Charter.


The authorized scope of the Forum Infrastructure Working Group shall be as follows:
To oversee the acquisition, operation, and maintenance of the common CA/Browser Forum website and wiki resources;
To coordinate updates to public and Forum-facing web and wiki content;
To create and manage the division of access and content spaces required to ensure separation under the IP Rights Agreement that governs the Forum;
To perform other activities ancillary to the primary activities listed above.
Out of Scope

The Forum Infrastructure Working Group ("FIWG") will not address coordination of Forum or Working Group face-to-face meetings. The FIWG will not at this time address the acquisition or maintenance of software or services used for online meetings of the Forum Plenary or Working Groups. The work of the FIWG in managing content updates to online content shall not supplant the responsibilities of Forum chairs or members to do so under the requirements of the Bylaws.

Anticipated End Date

The Working Group shall be chartered for a period of two years, to begin from the date of the adoption of this charter by the Forum. At the end of that period, the Forum may extend the charter of this group according to the provisions of the Bylaws.

Initial Chairs and Contacts


Members Eligible to Participate


The membership of the FIWG shall automatically include the Chair of all other Forum Working Groups, or those Chairs' specifically delegated representatives as indicated in an annual note to the FIWG mailing list. The FIWG welcomes the participation of any member of the Forum Plenary interested in this work, and also invites Interested Parties and Associate Members as defined in the Bylaws to participate in its meetings and work. 

Voting and Voting Structure

Voting in the FIWG shall be limited to FIWG members who are listed as a voting member of any other Working Group in the Forum. Voting shall be egalitarian, with one vote granted to each member organization. Ballots shall be adopted by the FIWG if the number of votes cast meets Quorum, and the number of votes in favor exceeds 50% of the votes cast. Quorum is defined as the average number of Member organizations that have participated in the last three FIWG Meetings or Teleconferences (not counting subcommittee meetings thereof). For transition purposes, if three meetings have not yet occurred, quorum is five (5).

Summary of Major WG Deliverables and Guidelines

The deliverables of the FIWG are primarily defined in the Scope section above. In addition to the general focus of the Working Group, however, the following specific deliverables are defined:
A review of the current web and wiki software in use to ensure it meets the security and content needs of the Forum;
Creation of separate wiki space for each Working Group, to enable the division of content as required by the IP Rights Agreement;
A review of the current web content and reorganization as required to support the new Forum Working Group changes.
Primary Means of Communication

The FIWG will communicate primarily through listserv-based email, and shall conduct periodic calls or face-to-face meetings as needed.

IPR Policy

As with all Forum Working Group activity, the CA/Browser Forum Intellectual Rights Policy v1.3 or later shall apply to all activities and work of the FIWG.





Jos Purvis (jopurvis at cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)


Public mailing list
Public at cabforum.org


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/public/attachments/20180518/fce137bc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2095 bytes
Desc: not available
URL: <http://cabforum.org/pipermail/public/attachments/20180518/fce137bc/attachment-0001.p7s>

More information about the Public mailing list