search

django-commons / membership

Membership repository for the django-commons organization.
MIT License
26 stars 3 forks source link

Define new member requirements #80

Closed tim-schilling closed 1 month ago

tim-schilling commented 1 month ago

My reasoning was similar that of putting the inbound repo requirements here. It's public facing requirements that should be easily accessible by the members. Ideally, anything accessible to members should be in a single place which is this repo. What do you think?

However, it seems like discussions and projects will differ, but we can't control that since it's a GitHug architecture thing.

ryancheley commented 1 month ago

I agree that having the requirements here is a good idea. Can we update the controls repo to be a link back to this repo for membership requirements? That was there shouldn’t be any disagreement between the two repos.

tim-schilling commented 1 month ago

Good call, I overlooked that for sure. I added a reference to this file here: https://github.com/django-commons/controls/pull/59