This team processes the openSUSE membership requests and accepts or rejects them after review.
Being part of the team
Membership officials are appointed by the openSUSE Board. Members are welcome to help us in this team .
To join the Membership Officials Team
- Step 1. Email firstname.lastname@example.org with a link to your connect.opensuse.org Profile
- Step 2. The Board will confirm that you're a Member, and let you know whether or not you're request to join the Membership Officials is accepted (if the team is big enough, new team member may not be necessary)
- Step 3. An existing team member will give you the appropriate permission to the code.opensuse.org project and the mailing list
- email@example.com - This is a closed mailing list so the team can discuss privately applications that might require a debate (unclear contributions, for example).
Currently (as of January 2022) the team consists of the following members:
- Dominique Leuenberger (dimstar)
- Martin Pluskal (pluskalm)
- Wolfgang Rosenauer (wolfir)
- Bill Schouten (ctlinux)
Vote membership requests
- visit https://code.opensuse.org/project/membership/issues (login if required)
- check for new membership requests
- within applications with no claimed contributions ask for more information.
- to vote for applications, provide your reasons in the text field and give an thumbs-up or thumbs-down
- all votes are based on open comments; if a vote should be pulled comment in the issue
- if applications get no downvotes and at least one upvote from a membership official other than yourself (or any future automatic validation tooling), then you can tag the issue with "approved" and should ask the user if there is information missing about the email setup
- when an application is approved the new member has to be added to our member database. In case of doubt what and how to do it, leave the issue open and someone else will pick it up for database inclusion
- if applications get at least one downvote from a membership official other than yourself, and you agree with that, then you can tag the issue with "denied" and close the issue as "Rejected"
- if Membership officials disagree with a fellow officials downvote, they should discuss that amongst themselves, with the possible outcomes being either the downvote being removed, or the request being rejected. If the Officials cannot resolve a disputed application amongst themselves, they can request the Board to mediate.
- Membership officials should strive to resolving applications as fast as possible, as no potential member wishes to remain "in limbo" for a long period of time (new tool should notify Officials when requests are pending)
Administrate @opensuse.org email aliases
To change the email alias or target of a user, the database entry must be modified accordingly. Membership officials and Heroes have the required access. If members would like to request changes the same project can be used and an issue opened.
Administrate irc cloaks
When requesting membership, the users should add their desired freenode cloak and irc username in the issue. Upon accepting the user as member, the membership admins will set these values in the database.
To get the cloak active on freenode, our irc admins download the cloak export from the connect admin page, do a diff with the existing cloaks on freenode, and request the new ones. (TODO: Add reference to the script doing this)
After the new cloaks are registered with freenode, the irc admins paste the list of nicknames to the membership admin page, which triggers a notification mail to the new members, and sets their cloak state to done.
Please send requests regarding your cloak to firstname.lastname@example.org.