Committee Meeting 2023-01-05 19:00 UTC

The meeting will take place at 19:00 UTC at https://meet.jit.si/cacert If you do not have audio channel, you may try in the IRC channel #board-meeting on the CAcert IRC network.

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

e

Agenda

Signs that appear in the agenda
<!> Formulated motion on your topic. It will be put to the vote. Adjustments may be made before the vote. A motion must be submitted for resolutions!
{i} Information for your attention. Does not need to be explained or discussed at the meeting. Purpose: Everyone is up to date.

  1. Preliminaries
    1. Chair opens the Committee Meeting
      1. Chair has a question for the attending members
    2. Who is making minutes?

    3. Chair asks whether cacert-board-private or cacert-board maillist includes any items that need to be disclosed to Members.

    4. <!> Accept minutes from 1. Dez 2022 <!> "I move to accept the minutes of the committee meeting of 1st of December 2022."

  2. Business

    Acceptance of new business items no later than 48 hours before the start of the committee meeting!

    1. Quick decisions (none?)
    2. Quick infos (none?)

    3. Finance team (Michael)

      1. New ERP: Info: State of affairs (Frédéric D)
      2. Billing with BIT (workflow)
      3. Money transfer AU-EU (the secretary says thank you for the provided information needed and hopes he get the rest tonight)

    4. OpenID Connect (Brian)

      1. State of affairs openID project
      2. Report for RIPE

    5. OrgAssurer Review (see e-mail from Alex B)

    6. Background Check (Ted)

      1. {i} BGC for Gero: Interview happend (by Ted&Etienne), committee is waiting for the report (has to be sent by Gero).

      2. {i} BGC for Kim: Date is in confirmation phase (by Ted&Etienne)

      3. {i} BGC for Peter is initiated. (date searching; Interview by Ted&Egal)

      4. {i} BGC for Matthias and Sascha are initiated. (date searching started in August)

    7. Events

      1. FOSDEM Brussels (Dirk) https://fosdem.org/2023/

      2. Chemnitzer Linux-Tage (Dirk) https://chemnitzer.linux-tage.de

    8. Remote Assurance (Brian)

      1. {i} Creation of remote assurance sub committee (RASC) on the hold until Eva is available for the policy.

    9. Any other business (board members forgot to ask the secretary to put it on the agenda)
  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. Propose a date of the next Committee Meeting: 2. Feb. 2023
      2. Agree on the following meeting dates: 2. Feb., 2. March 2023 (keep date free, can be changed if necessary)

    3. To remember: Goals 2021/2022 (propositions by board 2020/2021) - Each goal needs a responsible person on the board who keeps an eye on it and reports regularly, keeps in touch with the responsible people. {X} obsolete / (./) started / {OK} waiting for available time

      • push OrgA (Guy)
      • expand PR (Alex cannot do this, wants to hand over)

      • {X} support SecureU (find an active board member for them in Germany)

      • (./) expand background check

      • simplify the certificate creation (this enables the start of various projects from the pipeline)

      • {OK} remote assurance, if accepted by the community;

      • software development and testing

      • (./) delivering the OpenID Connect integration, for which CAcert is funded by the RIPE NCC.

      • New CSR software
    4. Not to forget: Staffing the teams
      1. Applicants to the Infrastructure team
      2. Applicants to the Development team
      3. Applicant to the Critical team

  1. Access to local systems for board members

Person

Board-Private

Committee Archive

Wiki

Nextcloud

Brian

(./)

(./)

(./)

(./)

Etienne

(./)

(./)

Admin

(./)

Frédéric

(./)

(./)

(./)

Admin

Kim

(./)

(./)

(./)

(./)

Michael

(./)

(./)

<!>

(./)

Sascha

(./)

(./)

(./)

Admin

Wacław

<!>

(./)

<!>

?

1. Tasks assigned to Board Members and others

Person

Task

Deadline

Other People Involved

Notes

Brian

Contact QA/QC Volunteers

10 January 2022

Gero Treuner, Peter Nunn, others?

To begin work, they do not need ABC.

Brian

bla

2022

xxx

xx.

Brian

bla

2022

xxx

xx.

  1. Software Team

    1. Issue 1502: Adapt the UI at CAcert.org to deal with the "keygen" feature having been removed in browsers

    2. Issue 1482: Limit validity period of new HTTPS certificates to one year

    3. Issue 1444: PHP - Brian

    4. Issue 1417: Keygen / new CSR software - Bernhard

  2. Organisation Assurance
    1. How to relance OrgA? (Guy)
  3. Grant applications

    1. Protopype Fund https://prototypefund.de/en/ (mail to SW Board only)

      1. The Prototype Fund is a project of the Open Knowledge Foundation Germany, funded by the Federal Ministry of Education and Research (BMBF). This is for residents of Germany only. We could create a group of people that work on a project for CAcert (with all support of the others in the background). It runs for two more years, every 6 month.
      2. Infra does not see any acute need at the moment, and does not have the capacity to provide qualified support.
      3. There are some ideas for software, but in infra's view there is still a lot of conceptual and preparatory work missing. What Infra could imagine is financing people to carry out a requirements analysis and write a requirements and test specification. This could then be used as a basis for a new implementation of the CAcert software (WebDB, Signer and perhaps other things like CATS). But these are just a few ideas of JanDD and he cannot currently recommend any people who would be suitable for this. Potential candidates would have to deal intensively with the existing software on the one hand and with the underlying policies on the other, and would have to identify a lot of missing information, ask for it and make assumptions for discussion. This requires very good analytical and communication skills and a high level of stamina.
  1. Blockchain

    1. see here: https://wiki.cacert.org/Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2018-03-01/ideas#Blockchain (waiting for answer from IanG)

Committee meeting - 2023-01-05

Participants

Members of the Committee:

Present, by alphabetical order

Brian McCullough

Etienne Ruedin

Frédéric Dumas

Frederic Grither

Kim Nilsson

Michael Richardson

Absent or silent, by alphabetical order

...

Members of the CAcert community and other guests

Having been active during the meeting, by alphabetical order

Dirk Astrath

1 Opening

Etienne opens the meeting at 19:15 UTC.

1.1 Organisational matters

Etienne chairs today's meeting.

1.2 Urgent business

None.

1.3 Drafting of the minutes

Kim, Michael, Frédéric write up the minutes of the meeting.

1.4 Approval of the previous meeting's minutes.

Etienne moves to accept the minutes of the committee meeting of 1st of December 2022.

Result of the vote:

Aye: 5 Naye: 0 Abstain: 0

The minutes were accepted.

2 Business

2.3.1 NextERP status

Frederic did not work on the subject in 2022. He explains that it is necessary to put NextERP in an LXC container, to facilitate maintenance afterwards by Jan (infrastructure team). Michael proposes to provide a container on his own infrastructure, to facilitate this step for Frederic. Next Frederic just will have to install NextERP in the container. The container will then be easily replicated on the CAcert infrastructure. Frédéric and Michael agree to meet in the next few days to discuss the technical details of this.

2.3.2 Billing with BIT

Etienne is not receiving the bills by email, BIT's invoices were still set to be secure-u.de, Michael is trying to update this to treasurer@cacert.org. This has to be checked by BIT support, so it is not immediate.

The invoices can be accessed in the portal via: https://portal.bit.nl/invoice/ with a login. Etienne needs to be the one to load them, because only he has access to GKB to pay the bills.

2.3.3 Transfer of funds from West Pac to Graubündner Kantonalbank

The use of Conotoxia was hampered because CAcert, as a Swiss Association, is not registered in such a way that it got an official identification number forn the Swiss authorities; however, Conotoxia requires such a unique ID numer to be provided in order to register any organisation.

Etienne has undertaken to have CAcert registered at the Swiss administration, so that we can open an account at Conotoxia. After that step having been completed, then the international money transfert process could be Paypal to Westpac, then to Conotoxia, and eventually to GKB. We could also yes, use Wise in place of Conotoxia.

Due to AML and KYC regulations, the identities of the elected members of the CAcert committee must be provided to Contoxia, for the purpose of opening an account. This also includes the need to provide their dates of birth. Etienne has gathered this information, too.

2.4 OpenID

A report describing the progress of our development for OpenID should be sent to the RIPE NCC. Deadline was actually on 30 November, 2022. Frederic commits to Etienne to complete within the next few days the document started by Brian. Brian proposed a short online working meeting with Etienne and Frédéric, to validate the drafting of the document. Etienne can then send it to the RIPE NCC.

2.6 Background Check by Community

No progress so far. Etienne has reached out to Bernhard (Ted) again to get future dates when he could conduct Background Checks. Dirk suggested that a Back Ground Check should also be arranged for Brian. Michael suggests that we conduct Background Checks. for all board members.

2.7 Upcoming Events of note

2023-02-04: FOSDEM. Dirk, Michael will attend (without holding a booth), and may be able to conduct assurances.

2.8 Remote Assurance

No progress so far.

3 Question time - open talk

Frédéric asked in general terms how the committee members could help each other to carry out their tasks. He underlines the psychological hindrance of the accumulation of tasks identified but not accomplished, which are reported from meeting to meeting.

4 Closing

Etienne ends the meeting at 20:07 UTC.

Next meeting is scheduled for 2 Feb 2023, at 19:00 UTC

Next meeting is scheduled for 2 Feb 2023, at 19:00 UTC, followed by 2 March 2023.

Logfile

Logfile from meeting 2023-01-05

Motions

Actions

Who

Status

Action

Minutemaker

wip

prepare Agenda and Minutes for the next meeting

Brian

Software meeting

every 2 month

Secretary

bank

accounts, contact with treasurer

Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2023-01-05 (last edited 2023-01-05 20:22:19 by EtienneRuedin)