ELEPHANT MEETING, 23. Nov 2023, 19:00 - ca. 20:30
present: F.D., F.G., A.K., E.R.

PROBLEMS
- we do not meet in real life.
- different languages
- different cultures (e.g. D: processus, rules, say no; F: easy consensus)
  "saying no" is good to protect structures
  - collaboration in different cultures
    - pick up phone and call versus
    - sending an e-mail and having an answer days later

TIME is not a question of a lot free time,
TIME is a question of motivation.

Today, there is not really collaboration.
The situation is not toxic, there is no dispute, but it is acid, it is dangerous and is slowing everything.
1. There is no one from the starting people still with us (probably a group of friends in Australia)
2. There was a "war" ca. 10 years ago that rined a lot, people left or resigned.
3. There is nearly no renewal neither at the committee nor at the teams nor at the community.

If we are inefficient, our work becomes useless; the worst situation.
- We need a professional attitude
  - how do we interact with each other, our behaviour, our values
    - Under no circumstances should we make the work of others appear pointless. 
      e.g. code review does not happen = the coder's work is pointless.

TO DISCUSS
1. Reviews: How to get reviewers? How to get reviews done?
2. Resolve problems: May be once a month a Resolving Round Table (video conference) with all involved (e.g. infra, support, software, reviews, crit.) and do it together as much possible in one hour.
3. In critical situations, someone should decide, give orders. The others then carry it out. Brian, for example, has a lot of experience here.
4. Every week a work session of 3 hours online with an open window for each group, open mics only from my group:
   - starting on time
   - finishing on time
   - split up the group in two, if two different things are to do
   reward (monetarian or non-monetarian)

Even with volunteers, you can say: this is good, this is not good.
That is helpful, that is of little use

Who is standing on the commando bridge? Who do we see, the people in front of us, when they think of CAcert?
 
TASKS TO DO UNTIL 7. Dec. 2023
FD: Presentation
FG: Motion
ER: Minutes
AK: List of most important technical issues


Aleš Kastner sagt:known problems. 
Aleš Kastner sagt:Sins is a joke. 
Aleš Kastner sagt:I must admit I am a bit like JanDD, possibly with a lot of understanding for users. 
20:30
Aleš Kastner sagt:I have a little to say to this topic. 
20:32
Aleš Kastner sagt:I am used to work alone, 
Aleš Kastner sagt:but time to time get out of my tower. 
Aleš Kastner sagt:so i think i can adapt 
Aleš Kastner sagt:i was an expert all over my lifetime. 
Aleš Kastner sagt:the international collaboration is not quite new for me, 
Aleš Kastner sagt:but little experience 
Aleš Kastner sagt:all over i agree with FD 
20:43
Aleš Kastner sagt:perhaps the roots of this "useless disease" are in the disrecognising of CAcert and an unsuccessful audit. 

Aleš Kastner sagt:True. 
Aleš Kastner sagt:for rigid rules, you mean? 
Aleš Kastner sagt:Volonteer can then say? I quit. No leverage against him. 
Aleš Kastner sagt:advocatus diaboůi: and is the work in CAcert teally attractive? with that elephant? 
Aleš Kastner sagt:diaboli 
21:10
Frédéric Dumas
Frédéric Dumas sagt:devil's advocate 😃 
21:18
Ich sage:
http://www.igaelic.net/wp-content/uploads/2014/07/SALT-on-a-Shoestring.pdf
 
21:23
Aleš Kastner sagt:Priorities will be most important. Perhaps 1. to set a previous status what concerns certs by Class 3 
Aleš Kastner sagt:that includes 2-3 problems, unfortunately... 
Aleš Kastner sagt:the list 3rd ver is ready! 


20:51
Links to open reviews:
https://blog.cacert.org/2023/05/papillon-vient-voir-les-bugs/
https://blog.cacert.org/2023/05/join-the-cacert-spring-offensive/