Attachment '2022-10-06.txt'
Download 1 bdmc
2 Greetings Etienne and Michael.
3 20:58:27
4 Etienne
5 Hello Brian!
6 20:58:31
7 → KimNilsson est entré
8 20:58:40
9 Etienne
10 Hello Kim!
11 20:58:48
12 bdmc
13 I see that Dirk may or may not be here.
14 20:58:48
15 Etienne
16 Hello Michael!
17 20:59:00
18 bdmc
19 I don't see Kim yet.
20 20:59:57
21 KimNilsson
22 yo yo yo
23 21:00:05
24 Etienne
25 Michael is absent for the moment.
26 21:00:06
27 bdmc
28 Now I do!
29 21:00:20
30 Welcome all.
31 21:00:36
32 Until we have more than three of us, I think that we should delay the start.
33 21:01:59
34 Etienne
35 From a formal point of view, we are able to make a decision.
36 21:03:28
37 egal
38 the decision to start? ;-)
39 21:03:37
40 Etienne
41 @KimNilsson: Did the background check work? I was offline for three days. It didn't make sense to answer retroactively.
42 21:03:40
43 bdmc
44 B-)
45 21:04:14
46 I'll wait until XX:05 and then go.
47 21:04:39
48 egal
49 time to make a "small" cup of tea ... ;-)
50 21:04:52
51 Etienne
52 https://wiki.cacert.org/Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2022-10-06
53 21:05:08
54 https://wiki.cacert.org/Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2022-09-01#Minutes
55 21:05:29
56 KimNilsson
57 Etienne: no, since neither you nor Dirk were presesnt, we couldn't do it. Ted will reach out again to plan another session.
58 21:06:00
59 bdmc
60 Well, the time has come, as the Walrus said.....
61 21:06:14
62 I hereby call this meeting of the Board of CAcert to order.
63 21:06:43
64 Etienne
65 Agend: first link; Minutes: second link (given at xx:05)
66 21:06:52
67 bdmc
68 Thank you.
69 21:07:16
70 Yes, I called it to order at XX:05, didn't I?
71 21:07:43
72 OK, anything in either the Board or Board Private mailing lists that should be brought forard?
73 21:07:46
74 KimNilsson
75 Live minutes (soon with some content). https://nextcloud.cacert.org/apps/files/?dir=/CAcert%20board/CAcert%20-%20Committee%20meetings&openf...
76 21:08:59
77 bdmc
78 Nothing heard. Would someone like to discuss anything in last month's minutes?
79 21:09:18
80 Otherwise, I will ask for a motion to accept them.
81 21:09:19
82 Etienne
83 I move to accept the minutes of the committee meeting of 1st of September 2022.
84 21:10:23
85 KimNilsson
86 Seconded
87 21:10:27
88 Etienne
89 aye
90 21:10:32
91 bdmc
92 Aye
93 21:10:57
94 ( I will record that Kim voted Aye, too. )
95 21:11:12
96 Etienne
97 Recorded at the motion system.
98 21:11:24
99 bdmc
100 ( I know, picky, but it is how I inherited the procedure. )
101 21:11:54
102 KimNilsson
103 Goodie
104 21:12:05
105 Etienne
106 bdmc: you may skip quick decisions, as there are none.
107 21:12:14
108 bdmc
109 As I suspected.
110 21:12:51
111 I see that Items under 2.2 are also to be skipped.
112 21:12:59
113 Etienne
114 :-(
115 21:13:13
116 bdmc
117 Moving on.
118 21:13:48
119 Item 2.3.1 -- New ERP -- Any news?
120 21:14:25
121 Item 2.3.2 -- Base contract. -- Etienne, any news?
122 21:14:43
123 Etienne
124 I am in contact with the treasurer and the bank as well. The EUR IBAN is expectet for the next week.
125 21:14:57
126 KimNilsson
127 2.3.1 ERP - Both Michael and FD absent, and they are the ones involved.
128 21:14:58
129 bdmc
130 Item 2.3.3 -- EUR Account -- Etienne, News?
131 21:15:30
132 Etienne
133 I am in contact with the bank as well. The EUR IBAN is expectet for the next week.
134 21:15:48
135 bdmc
136 So you are answering both 2.3.2 and 2.3.3. OK
137 21:15:53
138 Etienne
139 :-)
140 21:16:24
141 KimNilsson
142 lovel the efficiency
143 21:16:33
144 Etienne
145 Michael had hoped to prepare the draft statements for the board to approve
146 21:16:33
147 before the AGM. That can't happen easily because I didn't bring the right
148 21:16:33
149 credentials with my laptop, and the VNC access to what I need is too slow.
150 21:16:33
151 I will get this finished on the weekend after I return to Ottawa.
152 21:17:01
153 (I=he)
154 21:17:14
155 bdmc
156 Item 2.4 -- I am still waiting for Jan. He wanted to do some work on the infrastructure before I continued. I will be working with him to expedite this matter.
157 21:17:27
158 ( Thank you, Etienne )
159 21:18:02
160 egal
161 do you know, which work on infra should be done?
162 21:18:04
163 bdmc
164 Item 2.5 -- Shutdown of SecureU and transfer to CAcert -- Any news?
165 21:18:27
166 egal: This is development side "stuff."
167 21:18:46
168 Etienne
169 I got an e-mail from BIT that my c.o. e-mail address was added in their system as a contact.
170 21:18:49
171 egal
172 okay ... i'll ping jandd for details ... ;-)
173 21:18:57
174 Etienne
175 Thank you egal
176 21:19:05
177 bdmc
178 egal: thank you, too.
179 21:19:48
180 Item 2.5????
181 21:19:50
182 egal
183 regarding secure-u ... had way to much business and personal work in the last weeks, so i'm unaware of a new status ... ;(
184 21:19:57
185 bdmc
186 OK
187 21:20:27
188 Item 2.6 -- Overall Background Checks -- News?
189 21:20:55
190 Etienne
191 Ted, Kim and me will do another try in october.
192 21:21:05
193 KimNilsson
194 Mine didn't happen. I have no info about the rest.
195 21:22:08
196 bdmc
197 It appears that two of them are waiting on a date, the other one is waiting for final results.
198 21:22:42
199 KimNilsson
200 ok
201 21:22:50
202 bdmc
203 Item 2.7 -- LCA -- Etienne, do you know the date of this event on the other side of the world?
204 21:24:06
205 KimNilsson
206 LCA != Lutheran Church of Australia, I'm assuming...
207 21:24:19
208 bdmc
209 Not exactly. B-)
210 21:24:40
211 KimNilsson
212 Nor "Life Cycle Assessment and Urban Sustainability ICLCAUS"
213 21:25:04
214 bdmc
215 That sounds like an interesting thing.
216 21:25:07
217 Etienne
218 I am sorry, the date was not announced yet.
219 21:25:13
220 bdmc
221 Thanks.
222 21:25:21
223 Etienne
224 https://lists.cacert.org/wws/arc/cacert-members/2022-09/msg00000.html
225 21:26:01
226 bdmc
227 Item 2.8 -- Remote Assurance -- I have not yet heard anything more. Do you know more, egal?
228 21:27:22
229 egal
230 currently not ... ;-(
231 21:27:47
232 bdmc
233 Good enough. We will wait another month to report.
234 21:27:48
235 Etienne
236 It would be great if you two could start this with Eva mis by 3 November. Then we would have good news at the last session of the legislature and a great announcement on 12 November (AGM).
237 21:27:55
238 egal
239 (maybe you ping her early next week again ... ;-) )
240 21:28:07
241 bdmc
242 Will do. Not sooner?
243 21:28:56
244 Item 2.9 -- AGM
245 21:29:06
246 Etienne, anything that you want us to know?
247 21:29:21
248 Etienne
249 https://wiki.cacert.org/AGM/Next
250 21:29:58
251 All you have to know i on the bottom o f the page: members get iinfo, teams got two infos for team reports.
252 21:30:00
253 bdmc
254 or discuss.
255 21:30:24
256 Oh, you want us to actually read, do you?
257 21:30:34
258 Etienne
259 we too have to write our reports.
260 21:30:48
261 bdmc
262 Yes, I plan to be ready sometime before the meeting is over. B-)
263 21:31:10
264 Etienne
265 No, no need to read the page, just to be ready ;-)
266 21:32:08
267 But if we are to fast to finish this meeting, we could have a look to our goals 21/22.
268 21:32:24
269 bdmc
270 Well, that seems to finish the the Business section of the meeting.
271 21:32:46
272 We could skip on down to that section, or ask for Questions.
273 21:33:12
274 I have never heard of that group, Etienne. Yes, I saw your message, but got distracted by work.
275 21:33:40
276 egal
277 regarding AGM ... when will the info be sent to member regarding payment/... ?
278 21:34:28
279 Etienne
280 egal: in the next days.
281 21:35:07
282 bdmc: codetriage: Recently, Mr Schneemann wrote to me. He has a site codetriage.org where volunteers are enrolled and every week they get a mini task emailed to them from open source projects to help out a little.
283 21:35:17
284 egal
285 okay ... don't forget to give members time for ordinary/special resultions/nominations
286 21:35:59
287 KimNilsson
288 CodeTriage sounds like a cool idea, for code that can be published. Maybe snippets, if core bits can't be public.
289 21:36:10
290 bdmc
291 Etienne: Hmmm. Interesting. That is certainly something that Ted, Jandd and Egal will be interested in, as well, perhaps, as others.
292 21:37:23
293 bdmc
294 KimNilsson: Also a good point. There are certainly sections of our code that are probably "trade secrets!"
295 21:38:43
296 egal
297 our code is public (except passwords/keys/... ;-) )
298 21:39:13
299 bdmc
300 B-) I know. Public and ancient.
301 21:39:28
302 egal
303 so nothing to hide ... but ... we need more persons checking if the work we do/did is done correctly ... ;-)
304 21:39:47
305 bdmc
306 Yes, we were talking yesterday, and volunteered Kim to do that.
307 21:39:49
308 egal
309 (yep ... i'm talking about reviews/software-assessment ... not coding itself)
310 21:40:40
311 bdmc
312 I wonder whether CodeTriage.org's people would be up to that. It certainly seems like something that they could do.
313 21:41:02
314 However, would the BGC get in the way of that?
315 21:42:14
316 KimNilsson
317 I always said I can help test things. I can't read/understand complex code, but when testing I can at least verify if code is doing the things you say it should.
318 21:42:43
319 Etienne
320 Sorry, it is not .org, it is codetriage.com
321 21:43:15
322 KimNilsson
323 Perhaps that depends on which code it is? Asking as I don't know, but perhaps super-critical code still _also_ needs to be reviewed by a BGC'd person?
324 21:43:30
325 bdmc
326 KimNilsson: That and some of Dirk's software assessments such as comparing two certificate fingerprints would be easy for you to do.
327 21:43:30
328 KimNilsson
329 Etienne: yup, saw when I googled the address.
330 21:43:38
331 exactly
332 21:45:11
333 bdmc
334 OK, let's look at Etienne's ( and ours ) list of "Things to Remember." Section 3.4.
335 21:45:37
336 Too bad that some of our missing members aren't here, particularly Frederic.
337 21:45:59
338 Etienne
339 push OrgA: My task for 22/23 to push Guy to push it ;-)
340 21:46:06
341 bdmc
342 B-)
343 21:46:26
344 egal
345 as i said before at some time: everybody could do a review of changes ... but i (as software teamlead or critical teamlead) can ask for a more qualified one for more complex code changes ... ;-)
346 21:46:36
347 Etienne
348 expand PR: I help Alex until we find a new or a second PR officer
349 21:46:45
350 KimNilsson
351 egal: spot on
352 21:46:53
353 Etienne
354 support secureU: obsolete
355 21:46:57
356 bdmc
357 The next two items are mostly done.
358 21:47:20
359 Certificate Creation is a development project, isn't it?
360 21:48:04
361 It would appear to be too big for a "mini task" for CodeTriage, but it might be worth examining.
362 21:48:09
363 Etienne
364 probably. The idea: easy click click as before in the browser.
365 21:48:31
366 As easy as your grandma can do it in 4 minutes.
367 21:48:35
368 bdmc
369 Needs some a Technical Design before the Developers start coding.
370 21:48:45
371 Etienne
372 excactly
373 21:49:06
374 bdmc
375 Sure, we can wave our hands and say "here is what will happen," but that is not enough.
376 21:50:05
377 Can we ask Ted if any of us could help, or is he too busy with other things?
378 21:50:46
379 Etienne
380 I will write a non-technical concept that technicians can transform in a technical one
381 21:51:10
382 bdmc
383 That would be a good start, thank you.
384 21:51:21
385 Etienne
386 remote assurance: probably one of the big things in 22/23.
387 21:51:36
388 KimNilsson
389 bdmc: I'm fairly sure Jan also had some ideas on certificate creation.
390 21:51:48
391 bdmc
392 egal: can you say anything about the replacement CSR software?
393 21:52:02
394 egal
395 nope ... only regarding ocsp ... ;-)
396 21:52:09
397 bdmc
398 KimNilsson: I would be surprised if he didn't.
399 21:52:28
400 egal: thanks.
401 21:52:45
402 KimNilsson
403 bdmc: hehe, he even has a test version available according to the bug
404 21:53:03
405 https://bugs.cacert.org/view.php?id=1417#c6131
406 21:53:22
407 bdmc
408 Etienne: I agree -- however, I see that tied to the "easy certificate creation" project.
409 21:53:56
410 KimNilsson
411 Agree, hard to get people assured if they can't get a cert
412 21:54:03
413 bdmc
414 ( Group: I suspect that we could tie this up in around an hour. )
415 21:54:49
416 Etienne
417 Kim: thank you for the link. There I see another goal: PHP7.
418 21:55:20
419 bdmc
420 Or perhaps PHP 8.
421 21:55:26
422 Now.
423 21:55:29
424 egal
425 php7 requires a lot of code changes, which need to be reviewed ... ;-(
426 21:55:52
427 (and we didn't even get the mysqli-changes reviewed ... ;-(
428 21:55:52
429 bdmc
430 Some versions of PHP 7 are relatively easy, but as we advance....
431 21:55:59
432 Etienne
433 bdmc: I'll take a look at it and then ask my grandmother.
434 21:56:08
435 bdmc
436 B-)
437 21:56:55
438 ( I was talking about this meeting, not the project. )
439 21:57:30
440 egal
441 finished with this part? ... may i give some news from critical team? ;-)
442 21:57:41
443 bdmc
444 Absolutely.
445 21:58:11
446 KimNilsson
447 (I'm just going to insert this, so I don't forget.) A regular discussion during our Wednesday meetings have been to make cacert.com/net easier to access (meaning not require a CAcert root installed pre-visiting). It has been viewed by all involved as a good idea. Keeping cacert.org the only host requiring cacert root.
448 21:58:47
449 Etienne
450 +1
451 21:59:14
452 bdmc
453 egal: After your news, do you want a motion to do that, or is it a larger project, or ....
454 21:59:45
455 egal
456 if cacert.com/net should be used somehow static, it can be done on an existing container ... just ping jandd ...
457 22:00:25
458 bdmc
459 I guess that we should discuss what it is that we want those web sites to show.
460 22:00:39
461 egal
462 if there should be some dynamic content cacert.com/net, we need an additional lxc-container (and obviously the decision regarding the software)
463 22:00:59
464 ... but then ping jandd, too ... ;-)
465 22:00:59
466 KimNilsson
467 com/net having general content, public marketing, stuff you want to know _before_ becoming a member and signing up - with org having member specific content
468 22:01:35
469 bdmc
470 Which sounds like a static page or two.
471 22:02:28
472 KimNilsson: Would you like to be responsible for drafting that content? Perhaps show it to us next month?
473 22:03:36
474 KimNilsson
475 bdmc: Alright, taking that on.
476 22:04:36
477 Noted in the minuts.
478 22:04:40
479 bdmc
480 Etienne: Please add that to next month's Agenda.
481 22:05:01
482 Etienne
483 yes
484 22:05:08
485 bdmc
486 egal: We are still eagerly waiting for Critical Team's news.
487 22:05:50
488 egal
489 okay ... we had some issues about expired certificates yesterday on OCSP-server ... ;-(
490 22:06:17
491 bdmc
492 But only one of the three, correct?
493 22:06:37
494 egal
495 ... therefore i moved ocsp.cacert.org to new ocsp-server for ipv4 yesterday during the day ...
496 22:07:04
497 within in the next days ipv6 will follow ..
498 22:07:40
499 ... as this is the last active service running on sun3, i could power of sun3 in some days ...
500 22:07:55
501 (if no issues come up during the next days ... ;-) )
502 22:08:05
503 bdmc
504 And save a LOT on our power bill. B-)
505 22:09:04
506 egal
507 yep ... during the next visit (either planned in 2 weeks or in 5 weeks) i could then remove the machine (as well as the old switch) from the rack
508 22:09:54
509 bdmc
510 Well, unless anybody else has something to bring to us, any more questions, I think that we could finish this meeting.
511 22:10:19
512 egal
513 nothing more from my site ... ;-)
514 22:10:21
515 Etienne
516 Agree on date of the next Committee Meeting: 3. Nov. 2022 18:00 UTC
517 22:10:37
518 do not forget 12 nov 2022 AGM
519 22:10:50
520 following meeting dates: maybe 1. Dez. 2022, maybe 5. Jan., maybe 2. Feb. 2023
521 22:11:12
522 bdmc
523 Yes, we have one more meeting before the AGM.
524 22:11:22
525 egal
526 november 12 ? didn't we agree on november 5?
527 22:11:45
528 KimNilsson
529 nope 12th
530 22:11:48
531 Etienne
532 I hope we can then close some chapters (as IBAN) and open some new ones (as remote assurance)
533 22:12:12
534 https://wiki.cacert.org/AGM/Next
535 22:12:13
536 egal
537 (okay ... have adjust my memory to 12th ... ;-) )
538 22:12:27
539 Etienne
540 20:00 UTC
541 22:12:35
542 KimNilsson
543 yes, late meeting
544 22:12:37
545 Etienne
546 (normal time)
547 22:13:03
548 KimNilsson
549 but, it's after DST ends, so sameas this really?
550 22:13:28
551 even if our bodies may not agree
552 22:13:29
553 egal
554 don't forget the daylight-saving-change at end of october ... and the adjustments regarding UTC in europe ...
555 22:13:38
556 ... and maybe other parts of the world ... ;-)
557 22:13:39
558 Etienne
559 Kim: 20 UTC normal time is as today 19 UTC DST
560 22:14:00
561 KimNilsson
562 Etienne: yeah, what I thought
563 22:14:00
564 Etienne
565 21 central european (summer/normal) time
566 22:14:22
567 KimNilsson
568 egal: they still haven't finalised when they are going to sop messing with the time, are they?
569 22:14:27
570 stop
571 22:14:35
572 egal
573 19 UTC = 21:00 in summer and 20:00 in winter
574 22:16:01
575 KimNilsson
576 bdmc: I clocked the end as 20:15 UTC in the minutes -good, right?
577 22:16:25
578 As we talked right over your actual call for the end a while ago :-)
579 22:18:00
580 bdmc
581 Well, if that is done, I will call this meeting finished and closed. See you all next month.
582 22:18:28
583 KimNilsson: Yes, I was saying that we were near to the end, not that we were at the end.
584 22:18:35
585 Yes, your time is good.
586 22:18:36
587 egal
588 or during wednesday calls ... ;-)
589 22:18:51
590 bdmc
591 egal: Always ( almost ) those.
592 22:19:34
593 Etienne
594 Thank you and good bye. egal:jitsi
595 22:19:53
596 KimNilsson
597 great, bye
598 22:37:39
599 → FD est entré
600 22:55:19
601 ← FD est parti du salon
602 23:14:59
603 ← bdmc a quitté (Quit: leaving)
Attached Files
To refer to attachments on a page, use attachment:filename, as shown below in the list of files. Do NOT use the URL of the [get] link, since this is subject to change and can break easily.You are not allowed to attach a file to this page.