How to approach existing libraries to consider joining Django Commons

Packages
1

[This post was originally a Django Commons discussion and moved to the Django Forum]

I’m curious if folks have any ideas on how Django Commons could or should approach existing libraries.

I view our value proposition as the last repo transfer you’ll have to do because you’ll know the package is permanently in a place that will have maintainers.

Now, that’s not to say every package will be maintained, we need people to do that. However this org is focused on sustainability and reliability through redundancy from the top down. I think that’s worth something and package maintainers will value that enough to spend the couple hours moving it over.

I guess I have two questions:

  1. Does the above match your thoughts?
  2. Do you have ideas on how to phrase this to maintainers?
2

i don’t have a solution for this exact question

but i think one thing that will help a lot is making django-commons more known

this will help with a few things:

  1. more users will find packages, and the attraction of more users can be a reason to move to django-commons.

  2. more developers will come for contribution and maintainer roles, which can be a point of interest for maintainers.

  3. maintainers are more likely to move to a well known org

1 Like
3

Agreed! That’s one of the reasons why we’re shifting our public discussions to the Django Forum.