[cabfpub] Draft Ballot 227: Establish Forum Infrastructure Working Group

Thu Jul 26 18:50:49 UTC 2018

Another minor suggestion: Change “Ballot 227” to “Ballot CABF1” or “Ballot F1” or similar to make it clear it’s a post-governance reform Forum ballot.

-Tim

From: Public <public-bounces at cabforum.org> On Behalf Of Tim Hollebeek via Public
Sent: Thursday, July 26, 2018 12:34 PM
To: Jos Purvis (jopurvis) <jopurvis at cisco.com>; CA/Browser Forum Public Discussion List <public at cabforum.org>
Subject: Re: [cabfpub] Draft Ballot 227: Establish Forum Infrastructure Working Group

Yeah, the Questions List Coordinator is an informal position, not a formal one, but as long as we are documenting and formalizing things, we might as well formalize it too.  Having a documented procedure for how the Forum decides how to answer questions would not be a bad thing.

My biggest problem with end dates is we tend to forget they exist when things are going well, and then have to scramble to deal with the consequences.  

-Tim

From: Jos Purvis (jopurvis) <jopurvis at cisco.com <mailto:jopurvis at cisco.com> > 
Sent: Thursday, July 26, 2018 10:19 AM
To: Tim Hollebeek <tim.hollebeek at digicert.com <mailto:tim.hollebeek at digicert.com> >; CA/Browser Forum Public Discussion List <public at cabforum.org <mailto:public at cabforum.org> >
Subject: Re: [cabfpub] Draft Ballot 227: Establish Forum Infrastructure Working Group

Thanks! I didn’t see the Questions List coordinator in the Bylaws, so I hadn’t included it, but we certainly could: it would easily fall within the parts of the Charter that cover list management.

For the end date, I included one pro forma, on the assumption that once the WG had accomplished the items in the ‘Deliverables’ section, we might have a good idea whether it was needed or not. It’s possible that once we feel like the new systems are solid and there are people formally filling the various specified roles, we don’t need a WG for this anymore, but as you point out we can always dissolve this at any point. If people feel strongly about the end date I can take it out.

            --Jos 

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

From: Tim Hollebeek <tim.hollebeek at digicert.com <mailto:tim.hollebeek at digicert.com> >
Date: Wednesday, 25 July, 2018 at 17:12 
To: "Jos Purvis (jopurvis)" <jopurvis at cisco.com>, CA/B Forum Public List <public at cabforum.org <mailto:public at cabforum.org> >
Subject: RE: [cabfpub] Draft Ballot 227: Establish Forum Infrastructure Working Group

I’ll endorse.

Should the Questions List Coordinator be an official role as well?

Do we need an end date?  We can dissolve the Working Group by ballot at any time we feel it is no longer needed.  I don’t anticipate that happening …

-Tim

From: Public <public-bounces at cabforum.org <mailto:public-bounces at cabforum.org> > On Behalf Of Jos Purvis (jopurvis) via Public
Sent: Wednesday, July 25, 2018 4:52 PM
To: CA/B Forum Public List <public at cabforum.org <mailto:public at cabforum.org> >
Subject: [cabfpub] Draft Ballot 227: Establish Forum Infrastructure Working Group

All,

I’m enclosing the following draft ballot per our discussion a few months ago about creating this group. Note that since this is a Forum-level Working Group, this is a Forum-level ballot. Once I have endorsers for it, I’ll establish dates to start the discussion and voting periods.

Ballot 227: Establish Forum Infrastructure Working Group

Purpose of Ballot

The CA/Browser Forum has grown considerably over the last few years and is now dividing its work in to working groups to more carefully address specific certificate needs. The responsibilities of managing the various pieces of infrastructure the Forum uses in its work, such as the wiki and listserves, has grown considerably. With immense gratitude to each of the Forum members that have helped to provide this infrastructure, the work of managing it should no longer be left as a volunteer best-effort function of any single Forum member. This ballot would establish a working group chartered to ensure the infrastructure supporting the Forum continues to meet its needs.

The following motion has been proposed by Jos Purvis of Cisco and endorsed by XXX and YYY.

— MOTION BEGINS —

Upon approval of the CAB Forum by ballot, the Forum Infrastructure Working Group (“FIWG”) is created as a Working Group of the CA/Browser Forum 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. The definitions found in the Forum’s Bylaws shall apply to capitalized terms in this Charter.

Scope

The authorized scope of the Forum Infrastructure Working Group shall be as follows:

1.	To oversee the acquisition, operation, and maintenance of the common CA/Browser Forum website and wiki resources;
2.	To coordinate updates to public and Forum-facing web and wiki content in support of the Forum Webmaster role established in the Bylaws;
3.	To create and manage the division of access and content spaces required to ensure separation under the IP Rights Agreement that governs the Forum;
4.	To manage the Forum-level email lists and to offer management of working-group and subcommittee mailing lists as needed in support of the Forum List Manager role established in the Bylaws;
5.	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 or teleconference meetings of the Forum Plenary or Working Groups. The work of the FIWG in managing content updates to online content shall be offered to Working Groups and Subcommittees, but 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.

Personnel and Participation

Initial Chairs and Contacts

TBD

Members Eligible to Participate

The membership of the FIWG shall automatically include the Chairs 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 shall also automatically include the Forum List Manager and Forum Webmaster as designated by the Forum Chair. The FIWG welcomes the participation of any Member organization 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.

Membership Declaration

The following people shall be automatically declared as Members of the FIWG:

*	The Forum Plenary Chair;
*	The Forum Plenary Vice-Chair;
*	The Forum Plenary Webmaster;
*	The Forum Plenary List Manager.

The Chair of each Forum Working Group shall be automatically declared a Member of the FIWG unless they specifically designate an alternate in their place. Other Member organizations of the Forum may declare their participation and must do so prior to participating, in accordance with the IPR Policy of the Forum. The Chair of the FIWG shall establish a list for declarations of participation and manage it in accordance with the Bylaws and the IPR Policy.

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). For the purposes of counting votes, automatically included members such as the Forum Webmaster may not cast votes separate from their Member organization.

Summary of Major WG Deliverables and Guidelines

The deliverables of the FIWG are 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, document review, 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 required by the IP Rights Agreement;
*	A review of the current public 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.

— MOTION ENDS —

The procedure for approval of this ballot is as follows:

Discussion Period (7 days)

Start Time:

End Time:

Vote for Approval (7 days)

Start Time:

End Time:

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

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