Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| howto:gitlab_signup [2025/03/16 03:24] – minor grammar improvements kevinbowen | howto:gitlab_signup [2026/10/03 04:15] (current) – Add back links and minor grammar improvement kevinbowen | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== GitLab Sign-Up Process ====== | + | ~~NOTOC~~ |
| + | ====== | ||
| ===== Summary ===== | ===== Summary ===== | ||
| - | * Starting from 2025-02-15, registering new accounts will be suspended. | + | * As of 2025-02-15, |
| - | * New users should log in using SSO (GitLab.com and GitHub). | + | * New users should log in using SSO (via an existing |
| * New users will be able to create forks without requesting their accounts to be cleared. | * New users will be able to create forks without requesting their accounts to be cleared. | ||
| + | |||
| + | ---- | ||
| ===== Context ===== | ===== Context ===== | ||
| Line 14: | Line 17: | ||
| Recently, we received an email from Google stating that reCAPTCHA now requires a Google Cloud Platform account and a credit card. Yes, we are currently on the free tier, and yes, we do have funds held with Open Collective. However, none of the core developers are motivated to maintain yet another piece of our anti-spam defenses. Moreover, GitLab does not support alternative captchas such as hCaptcha. | Recently, we received an email from Google stating that reCAPTCHA now requires a Google Cloud Platform account and a credit card. Yes, we are currently on the free tier, and yes, we do have funds held with Open Collective. However, none of the core developers are motivated to maintain yet another piece of our anti-spam defenses. Moreover, GitLab does not support alternative captchas such as hCaptcha. | ||
| + | |||
| + | ---- | ||
| ===== Changes to Registration ===== | ===== Changes to Registration ===== | ||
| - | From 2025-02-15 onwards, sign-ups will be disabled. New users will have the option to log in via their GitLab.com or GitHub accounts (SSO). This may sound like a drastic approach, but it's exactly what other projects [[https:// | + | From 2025-02-15 onwards, |
| - | If you still want a regular username/ | + | If you still want a regular username/ |
| As a tentative measure, we will remove the limitation that prevented new users from creating forks. If spammers abuse this again, we will consider reinstating it. | As a tentative measure, we will remove the limitation that prevented new users from creating forks. If spammers abuse this again, we will consider reinstating it. | ||
| + | |||
| + | ---- | ||
| ===== Conclusion ===== | ===== Conclusion ===== | ||
| - | Ultimately, we aim to reduce the time spent fighting spam and unlocking accounts for new contributors | + | Ultimately, we aim to reduce the time spent fighting spam and unlocking accounts for new contributors, time that could be better spent hacking on Xfce. As a side effect, requesting fork permissions will no longer be necessary, which we hope will lower the barrier to entry, somewhat, for prospective contributors. |
| Some people strongly oppose SSO logins, which is why we have kept the possibility of manually creating accounts upon request. | Some people strongly oppose SSO logins, which is why we have kept the possibility of manually creating accounts upon request. | ||
| + | |||
| + | [[|Back to Top]] | ||
| + | ---- | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | [[https:// | ||