new packages requirements

[amirreza8002]

hi
i'm looking around to understand how this org is gonna operate
one thing i'm not sure about is what are the requirements for package to be considered for django-commons?

i see that it should have tests and docs, but there is so many packages that have tests and docs, do you accept all of them?

[Stormheg]

Hello,

You are right many packages already meet most of the requirements to be accepted into Django Commons!

No personal projects

One of the additional requirements that is not yet in incoming_repo_requirements.md is that we won't accept 'personal projects'. Now, what does that mean?

A project is likely considered a 'personal project', if:

• There is no evidence of the project being used by anyone else than the maintainer.

A project likely doesn't qualify as a 'personal project', if:

• There is evidence the project is being used by the community. For example: issues / pull requests are being opened by people other than the maintainer and the package is getting downloads on PyPI.

Maintainer consensus

Besides that, there should be unanimous consensus among the maintainer(s) of a project to move to Commons. This could be demonstrated by opening an issue on the repository and having all maintainers comment on that. We are sympathetic to cases where you aren't able to reach all maintainers. For example, some may have moved on to other things and are unresponsive. If you can demonstrate you have tried to reach out and have allowed enough time for them to respond (say: a couple months) we'll still accept the project into commons.

all of this will be documented soon, we just discussed above points yesterday during an admin check-in video call.

Hope that answers your questions. Please let us know if you have any other questions!

[amirreza8002]

hi
thanks for your time🙏

seems good enough for me

[tim-schilling]

Thank you for asking the question!