Feat/add scs 0005 project governance

[fkr]

No description provided.

[garloff]

This looks good to me, though it's not yet marked "Ready for review".
Maybe hit the button, @fkr , so we can proceed?

[frosty-geek]

LGTM

[FriederikeZelke]

Very good!

[fkr]

There is one todo left, that I will add later today:

• Explain the voting mechanism in more detail and elaborate on how/where the voting is done (heliosvoting.org)

[fkr]

There is one major hurdle that I've not solved yet (also posted to Matrix last week):

We assumed that all egible voters are the people in the github org. However for those we do not have e-mail addesses and as such no easy way of reaching out to them and onboard them into the voting system (which requires e-mail).

@garloff any chance we can somehow map the github members <-> Members of the UCS?

[garloff]

@garloff any chance we can somehow map the github members <-> Members of the UCS?

We have no github handles stored in UCS.

We currently have full names for all github users in github-manager, we could leverage the fact that we consistently used Firstname.Lastname on UCS. But this would fail for some cases:

• Some people have multiple names or such, so the username used on UCS may not be obvious from the full name.
• Not every member of our github Org has been onboarded on UCS -- I expect we would miss out on a handful. Obviously, we can identify these and try to contact them and invite them to UCS/nextcloud.

I am checking whether the github API allows for access for public email addresses of users.
This should be possible (using a PAT). However, it would require that users have a public email set which not all users do.

[garloff]

I am checking whether the github API allows for access for public email addresses of users. This should be possible (using a PAT). However, it would require that users have a public email set which not all users do.

37 out of 129 Org members have a public mail address set, 92 do not.
Oh, API access with a PAT does allow to retrieve this, yes.

NAMES=`grep login: data.yaml | sed 's/^[^l]*login: //'`
for name in $NAMES; do echo -n "$name: "; curl -sL   -H "Accept: application/vnd.github+json"   -H "Authorization: Bearer github_pat_REDACTED"   -H "X-GitHub-Api-Version: 2022-11-28"   https://api.github.com/users/$name | jq ".email" | tr -d '"'; done | tee mails

[garloff]

* Some people have multiple names or such, so the username used on UCS may not be obvious from the full name.
* Not every member of our github Org has been onboarded on UCS -- I expect we would miss out on a handful. Obviously, we can identify these and try to contact them and invite them to UCS/nextcloud.

This results in 71 UCS accounts where I expect most of which have functional mail addresses.
58 github SCS Org members can not be found this way. (A few probably could by some heuristics).

FNAMES=`grep name: data.yaml | sed 's/^[^l]*name: //'`
while read first last; do echo -n "$first $last:"; grep username: udm.users | grep -i "$first\\.$last" || echo " null" ; done < <(echo "$FNAMES") > ucs.mails

[garloff]

With some magic to replace umlauts ... I get to 87 UCS accounts with 42 missing. There's ~ a handful more that can be resolved manually. We could of course require voters to

• have a public github address OR
• have a UCS account (and of course offer to onboard folks)

 SEDUML='s/ä/ae/g;s/ö/oe/g;s/ü/ue/g;s/ß/ss/g;s/é/e/g;s/ý/y/g;s/č/c/g;s/Ä/Ae/g;s/Ö/Oe/g;s/Ü/Ue/g'
 while read first last; do if test "$first" = "Dr."; then first=${last%% *}; last=${last# *}; fi; fir=$(echo "$first" | sed "$SEDUML"); las=${last#* }; las=${las%% *}; las=$(echo $las | sed "$SEDUML"); echo -n "$first $last: "; grep username: udm.users | grep -i "$fir\\.$las" | sed 's/ *username: \(.*\)$/\[email protected]/'; if test ${PIPESTATUS[1]} != 0; then echo "null"; fi ; done < <(echo "$FNAMES") > ucs.mails

[fkr]

With some magic to replace umlauts ... I get to 87 UCS accounts with 42 missing. There's ~ a handful more that can be resolved manually. We could of course require voters to

• have a public github address OR
• have a UCS account (and of course offer to onboard folks)

I'm tempted to say we do it that way.

[fkr]

thanks for your suggestions @garloff

[garloff]

@michaelbayr - this looks good to me now and I believe your good questions and suggestions have all been addressed.
However, this is for you to judge, of course. github still believes that you have open change requests, so please mark as resolved or approve explicitly to override this.

[garloff]

Looks good to me now.
Thanks for the excellent work, @fkr, @michaelbayr .

[michaelbayr]

@fkr @garloff thanks for all the work you put into this!
LGTM!

[maxwolfs]

Overall LGTM, just a note on mapping the GitHub Org Roles to SCS Community Members and SCS Project Board Members, with a suggestion for L34-L37. The bullet points can also be removed to be less precise as they are just an idea but could lead to more discussion.

[fkr]

Awesome collaboration - thanks a lot to all involved.