We are getting a ton of spam projects on pagure.io.
We discussed this on list and the best option seems to be to reconfigure things so you must be a 'contributor' ie, someone in at least one non 'agreement' or base group. This is unfortunate, but seems needed at least for now.
Users who aren't able to make new projects could also file a ticket here to have us make one, or any contributor could just add the project for them and 'give' it to them.
So, this needs:
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
Had a look into the pagure code, and i'm not sure that there is a config setting in pagure to do what we need here.
At the moment, on pagure.io only users with FAS and FPCA are allowed to log in.
There is a setting that is used on distgit pagure that turns off the new project UI on the web UI, but it is an all or nothing setting -- nothing to do with FPCA+1 (setting is ENABLE_UI_NEW_PROJECTS)
@pingou is there something i am missing here? if not i will look into implementing this config setting in Pagure upstream
I think you're correct, there is nothing restricting the creation of new projects to people in a certain group only.
Metadata Update from @ryanlerch: - Issue assigned to ryanlerch
note too that the spammers are now also filing issues on existing projects:
https://pagure.io/fedora-infrastructure/issue/11340
so this change will not fix that sadly
[backlog_refinement] The change was introduced in https://pagure.io/pagure/pull-request/5399 and merged But to enable this change we need to solve https://pagure.io/fedora-infrastructure/issue/10372 first
Metadata Update from @zlopez: - Issue unmarked as depending on: #10372 - Issue tagged with: blocked
Metadata Update from @ryanlerch: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.