Committee Meeting 2021-01-07 (2021-01-08 in Australia)

The meeting will take place at 20:00 UTC in the IRC channel #board-meeting on the CAcert IRC network.

Northern Winter: 08:00 PM GMT = 21:00 CET = 15:00 New York EST = 07:00 Australia AEDT
Northern Summer: 08:00 PM GMT = 22:00 CEST = 16:00 New York EDT = 06:00 Australia AEST

Feel free to add a business item within the acceptance period of 48 hours or your question to the board below. Non-committee Members: Committee may choose to convert any business proposed as a question in the questions section.

This will be a short meeting. You may miss some of your favourite topics that takes a lot of time. You may vote about minutes, agendas, etc. later. The goal of this meeting is to make at least two decisions so that the teams can continue to work as hard as they did in the past weeks. If there is remaining time, we may share some information.

Agenda

  1. Preliminaries
    1. Chair opens the Committee Meeting
    2. Who is making minutes?
    3. Is there a time limit? Who is time keeper?
    4. Chair asks whether cacert-board-private or cacert-board maillist includes any items that need to be disclosed to Members.

  2. Business

    Acceptance of Businesses 48 Hours before beginning of Committee Meeting latest!

    1. Most pressing subjects
      1. How to: information about CCA change. Two proposals: Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2021-01-07/CCA-info (discussion)

      2. Treasurer (discussion; formal decision?)
      3. Financial team (who, tasks): information about elections (Bret did not accept his election. Maybe we should change the focus, instead look for a treasurer, look for an volunteer-accountant - not board member and a 7th board member. One of the board members, called "treasurer", will only be the contact to the accountant (the rest of the time, he can do other things).) Details see here: Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2021-01-07/FinancialTeam

      4. ABC: Ted would like to know if board is comfortable with the idea that the Background Check itself will not be any kind of test anymore, but more some kind of "risk mitigation advisory session". If this direction of action is OK, he'd like to announce some workshop on policy mailing list for end of next week, which should try to create the checklist of topics to discuss during that session... Unless he hears any protest during this meeting, he will write some invitation and publish it on the policy list. Does anyone think that a wider publication (like on the cacert mailing list or by a blog post) would make any sense?
      5. Bug 1499 Re-Sign-Signer-Class-3-Certificate-processus: invite ... to start and critical admin to take over when it is time.

      6. ....
      7. .... who takes care of what? who work together with who?
    2. ??? Future
      1. Arbitration: report on the progress with applicants (FD)
      2. Business Model "security hardware appliances" (FD)
        1. Interview with the project leader of the "CAcert for safety hardware equipment" idea.
        2. Interview with the project leader of the " CAcert for blockchain " idea.
    3. Infrastructure Status
      1. Applicants: Welcome meetings
    4. Software Team
      1. Bug 1482: https://bugs.cacert.org/view.php?id=1482 (Limit validity period of new HTTPS certificates to one year)

      2. PHP http://bugs.cacert.org/view.php?id=1444 (Brian)

      3. Keygen http://bugs.cacert.org/view.php?id=1417 (Ted)

    5. ??? Critical Team (decision)
      1. Status of applications for Critical/Infrastructure team (Frederic/Dirk/Candidate)
  3. Question Time

    Questions from CAcert.org Community Members can be added until beginning of Committee Meeting! As well questions can be asked at "Question Time", without added Question here

    1. "Question One." added by Your Name Comment: Replace "Question One" by your Question and add your name

      • ..
    2. Closing
      1. Agree on date of the next Committee Meeting: 4. Feb. 2021

Logfile

Logfile from meeting 2020-10-01

Minutes

Minutes were written in parallel to the meeting, with tasks listed in action items and actions of this document.

Participants

By alphabetical order.

Members of the Committee being present:

* Brian McCullough

* Etienne Ruedin

* Frédéric Dumas

* Sascha Ternes

Members of the Committee being absent or silent:

* Guy Scharinger

* Peter Nunn (apologised)

Members of the CAcert community and other guests, having been active during the meeting:

* Dirk Astrath

Committee meeting - 2021-01-07

  1. Preliminaries
    1. Chair opens the Committee Meeting at 20:11 UTC
    2. The secretary is making minutes?
    3. Is there a time limit? Who is time keeper?
    4. Chair asks whether cacert-board-private or cacert-board maillist includes any items that need to be disclosed to Members.

  2. Business
    1. Most pressing subjects
      1. How to: information about CCA change. Two proposals: Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2021-01-07/CCA-info (discussion)

        • The board opts for an opt-out solution. The argument was, that opt-in is only possible if all arbitration proceedings are terminated beforehand. MOTION: I move that a notification be prepared and distributed to all current CAcert Members, describing recent changes to the CCA, saying that if they agree with these changes, there is nothing more to do, and offering the option of opting out of CAcert via the usual procedures. (aye 3; naye 0)
      2. Treasurer (discussion; formal decision?)
      3. Financial team (who, tasks): information about elections (Bret did not accept his election. Maybe we should change the focus, instead look for a treasurer, look for an volunteer-accountant - not board member and a 7th board member. One of the board members, called "treasurer", will only be the contact to the accountant (the rest of the time, he can do other things).) Details see here: Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2021-01-07/FinancialTeam

        • We had discussed the possibility of a financial (accounting) "team," with one member being a Board Member, the Treasurer. That position could be just a representative, and not actually doing any of the accounting work. The president has prepared a spreadsheet (CSV file) of a dozen people who mentioned this in their "volunteer statement." That makes a nice team with a small post for everyone (even if there are only six at the end). We will try to call all of them in their mother tongue.
      4. ABC: Ted would like to know if board is comfortable with the idea that the Background Check itself will not be any kind of test anymore, but more some kind of "risk mitigation advisory session". If this direction of action is OK, he'd like to announce some workshop on policy mailing list for end of next week, which should try to create the checklist of topics to discuss during that session... Unless he hears any protest during this meeting, he will write some invitation and publish it on the policy list. Does anyone think that a wider publication (like on the cacert mailing list or by a blog post) would make any sense?
        • The ABC, resp an new_BC or community_BC (CBC) is important. Our priority should be to reduce barriers and constraints, i.e. to open the CBC practice fairly widely to known, active, and good willing members. Teamleader usually trigger the ABC, so they may be conflicted, board members may be confliced to, as the have to accept (or deny) the decision of the interviewers. It is important to konw the conflicts and address them.
      5. Bug 1499 Re-Sign-Signer-Class-3-Certificate-processus: invite ... to start and critical admin to take over when it is time.

        • Some time ago, the board noticed that the class 3 certificate is expiring soon, so it got concerned. Currently it don't need a motion about class-3-resigning, but as soon as the resigning is done at BIT, the critical sys admin needs the OK to activate the resigned class-3-root-certificate.
      6. ....
      7. .... who takes care of what? who work together with who?
    2. Infrastructure Status
      1. Applicants: Welcome meetings
        • A first telephone conference was held to welcome new support volunteers. Another telephone conference will be organised for infrastructure.
    3. Software Team
      1. Bug 1482: https://bugs.cacert.org/view.php?id=1482 (Limit validity period of new HTTPS certificates to one year)

      2. PHP http://bugs.cacert.org/view.php?id=1444 (Brian)

      3. Keygen http://bugs.cacert.org/view.php?id=1417 (Ted)

  3. Question Time
    1. "Question One." added by Your Name Comment: Replace "Question One" by your Question and add your name

    2. Closing
      1. There will be socialising events on Wednesday at 12.30 UTC on Jitsi
      2. Agree on date of the next Committee Meeting: 4. Feb. 2021, 4. Mar. 2021, 1. Apr. 2021 (usually the first Thursday of the month)
      3. The president closes the meeting at 22.21 UTC, followed by an after work party on Jitsi

Motions

* m20200830.2: Motion to accept Minutes of the meeting of the 13th of August, 2020

Actions

Who

Status

Action

Minutemaker

wip

prepare Agenda and Minutes for the next meeting


Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2021-01-07 (last edited 2021-01-31 22:43:50 by EtienneRuedin)