[cabf_governance] Remaining issues to resolve in Ballot 206

[Kirk Hall]

Dean, sorry if I overstepped my bounds, but I sense people are getting fatigued by this project - they want to see it finished -  and I doubt you will get a lot more people on the bi-weekly calls.

Plus, it was my impression from the WG reports that the WG is close to finished, and just wanted some guidance from members on direction on a few remaining issue to finish up.  That's why I asked what the remaining issue and choices were.

From: Dean Coclin [mailto:Dean_Coclin at symantec.com]
Sent: Monday, October 16, 2017 9:42 PM
To: Kirk Hall <Kirk.Hall at entrustdatacard.com>; CA/Browser Forum Governance WG List <govreform at cabforum.org>
Subject: [EXTERNAL]RE: Remaining issues to resolve in Ballot 206

What is driving this rush?  We are working on the issues as best we can. When we are satisfied that we've answered all the open items, we will post. We need to get a majority of members on the next call to make substantial progress.

Dean

From: Govreform [mailto:govreform-bounces at cabforum.org] On Behalf Of Kirk Hall via Govreform
Sent: Monday, October 16, 2017 11:36 AM
To: CA/Browser Forum Governance WG List <govreform at cabforum.org<mailto:govreform at cabforum.org>>
Subject: [cabf_governance] Remaining issues to resolve in Ballot 206

Working Group members - your next meeting is Tuesday, Oct. 24.  Do you think you can decide all open items at that meeting, and then finish drafting Ballot 206 over the following two weeks so the final ballot is ready next month?

What would you describe as the remaining open issues that must be decided?  Could you create a series of simple email messages (one for each open issue) with the main options available, and with a Doodle poll you can use to test the preferences of the members?

I'll help if I can - but let's get this wrapped up as soon as we can.

Kirk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/govreform/attachments/20171017/37100ae1/attachment.html>