pagure.io is a general (open) source forge. You're welcome to have any project there that is under a "allowed" license according to Fedora ( https://docs.fedoraproject.org/en-US/legal/allowed-licenses/ ). It doesn't need to be Fedora related. For a dnf package, copr ( https://copr.fedorainfracloud.org ) would make more sense.

We should document this somewhere, but I am not sure where.

Thanks for the clarification.

pagure.io is a general (open) source forge. You're welcome to have any project there that is under a "allowed" license according to Fedora

But actually we are seeing a lot of spam repos here. Like this and this.

They do not even have actual code, and only abuses the "description" field to post ads. Should this be banned?

I think documenting in them About page, or provide links to a wiki page would be nice.

They do not even have actual code, and only abuses the "description" field to post ads. Should this be banned?

They should yes. We tried to manually purge them every now and then but I guess
we haven't done this cleaning in a while at this point.

I think documenting in them About page, or provide links to a wiki page would be nice.

The about page is likely the proper place indeed

We tried to manually purge them every now and then but I guess
we haven't done this cleaning in a while at this point.

I think just including a policy of "empty repo will be deleted after 14 days" should ward off those ad-posters not willing to setup a git workflow, which, I believe, is the majority of them. This could be implemented by a cron job via the API so no major changes would be made to pagure itself.

I have deleted all those and about 40 more. :(

Some projects do only use issues or docs, so it might need to make sure all of those are empty...

But yeah, we could do a cron, PR welcome!

Some projects do only use issues or docs

This is actually confusing (imagine you are a user and see a "this repo is brand new" when you are looking for issues and docs).

It would be better if we can ask the maintainers of those projects to put up a short README.md in their main repo (This project is used solely for documentation/issue tracking), if this is convenient. It would also make future maintenance and analytics a lot easier.

Apart from this, I don't think pagure has a plugin architecture now, so it would be unwise to add this functionality into main, or we risk feature bloating. A separate project running as a cron job on the server would be nice, (and convertible to a plugin in I hope would be a near future)

Apart from this, I don't think pagure has a plugin architecture now, so it would be unwise to add this functionality into main, or we risk feature bloating. A separate project running as a cron job on the server would be nice, (and convertible to a plugin in I hope would be a near future)

There is the pagure-utils project that contains a few utility scripts to
interact with pagure