Currently, the software causes the following problems:
- users manually have to ask to be added to the Codeberg-e.V. organization within Codeberg itself, resulting in moderate repeated effort on our side
- there is no verification of the email address, and people can become member with an incorrect one (either paying or not), this happens from time to time
- there is no feedback on the status of the application (accepted or not)
One solution to rule 1 & 2, and partly 3 could look like this:
The reg-server requires an active Codeberg.org account through OAuth. This ensures the email address is valid.
There is a checkbox that allows to link the Codeberg account, and sets a field for the Codeberg username, which is available via OAuth.
Optional: The user is automatically added to a "Pending" Team in Codeberg-e.V. which makes it easier to spot who has signed up recently. Once confirmed, the user is moved to the correct "Members" team, indicating the application was accepted.
Currently, the software causes the following problems:
- users manually have to ask to be added to the Codeberg-e.V. organization within Codeberg itself, resulting in moderate repeated effort on our side
- there is no verification of the email address, and people can become member with an incorrect one (either paying or not), this happens from time to time
- there is no feedback on the status of the application (accepted or not)
One solution to rule 1 & 2, and partly 3 could look like this:
The reg-server requires an active Codeberg.org account through OAuth. This ensures the email address is valid.
There is a checkbox that allows to link the Codeberg account, and sets a field for the Codeberg username, which is available via OAuth.
Optional: The user is automatically added to a "Pending" Team in Codeberg-e.V. which makes it easier to spot who has signed up recently. Once confirmed, the user is moved to the correct "Members" team, indicating the application was accepted.