sign-up for external developers #335
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#288 external developers empowered to contribute
fediversity/fediversity
#463 secrets may be handled securely w.r.t. use in PRs
fediversity/fediversity
Reference
fediversity/fediversity#335
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As a developer,
I want to be able to participate on the Fediversity forgejo without gatekeeping,
so that I may exchange ideas with its developers.
implementation notes
Gitea/Forgejo have been known to receive bulk sign-ups for SEO spam. Gatekeeping account approval after contact through e.g. our public Matrix channel has functioned as a stop-gap solution for this, but better mitigations, if needed, seem:manually purging bot accountsusing Anubis over the built-in captcha mechanism (#643)adding a single sign-on (c.f. #212), esp. given LDAP (c.f. #337)note that lix for one went out of their way to get SSO integrating with github identityfacilitate user sign-upto sign-up for external developersaddressed for now by setting
/var/lib/forgejo/custom/conf/app.ini'sDISABLE_REGISTRATIONback tofalse- let's see how bad spam sign-ups would get.kiara referenced this issue2025-06-10 20:32:13 +02:00
this requires a better solution to forgejo's lack of secret scoping (#463)
clean-up:
ssh git.fediversity.eudelete users e.g.for i in $(seq 52 53); do sudo su - forgejo -c "nix-shell -p forgejo --run 'forgejo --config /var/lib/forgejo/custom/conf/app.ini admin user delete --id $i --purge'"; done(based on article)if i can automate the former, maybe i can report back at the thread, but forgejo admin seems to lack repo administration.actually, forgejo-guardian seems able to clean up their repos too.