How can I get administrator rights to django-prometheus

[spapas]

Hey friends, I recently joined django-commons with the sole purpose of getting administrator rights to the django-prometheus project so as to finally create a new release with support for Django 6.0 (see this issue django-commons/django-prometheus#494). Please notice that the corresponding PR is already merged django-commons/django-prometheus#489 however there's no new release for more than 1 month now.

This issue is blocking many people (including me of course) from upgrading to Django 6.0.

Can you help me with the next steps on how to become an admin to this project? Or if this ain't possible right now, can somebody nudge the current admins/maintainers so as to create a new release that would help us upgrade?

PS I know I can point to the master branch directly in my reqs but this always leads to problems in my setup so I avoid it unless it is absolutely required (abandoned projects).

[tim-schilling]

Hi @spapas. I believe we would only grant admin rights to someone if the project was abandoned. I would not consider a month of inactivity to indicate abandonment. I think we'd also want to look at who has committed to the project in the past as well as prospects' prior contributions to the python and Django ecosystems.

Regarding "pinging the maintainers", I can see about 7 or 8 comments over the past month on the issue or PR. Let's give the maintainers the benefit of the doubt here. They are volunteering their time and OSS typically ends up being a lower priority when compared to a paying job, family and life.

[tim-schilling]

Regardless I'll bring this up in the next @django-commons/admins meeting.

[spapas]

Thank you @tim-schilling for your kind responce. Yes probably 1 month isn't very much. We'll wait and hopefully somebody will release a new version soon.

Kind regards,
Serafeim

[Stormheg]

Agree with Tim - the maintainer should be allowed more time to respond before us Django Commons admins step in do something without the current maintainers explicit consent.

It looks like django-prometheus has only one maintainer. If this project is important to you, I would encourage you to open a new issue and offer to help out with maintenance. Additional help is likely going to be welcomed by the current maintainer.

[spapas]

Hello friends, I'm coming back to this issue after 1 month. Still there's no response from the current maintainer(s) for when a new version with Django 6.0 will be released django-commons/django-prometheus#494.

I've also opened an issue in case the project needs help maintaining as @Stormheg proposed (django-commons/django-prometheus#495) but no response also.

Is it possible that somebody knows them and nudge the current maintainer(s) so as to give some love to this project? It's almost 3 months since Django 6.0 was released.

My understanding is that the primary purpose of django-commons is to prevent situations like this: Projects failing to support the latest Django versions. This is harmful not only for this specific project, but also for the broader Django ecosystem and its adoption overall.

Consider a new Django user who installs the latest version of Django and then attempts to integrate it with Prometheus. If they discover that the most popular library for this integration is no longer maintained, they will probably be disappointed and may even conclude that Django is not a viable or well-supported choice. I know because I've passed from this stage with a different ecosystem (Elixir).

Thank you

[ryancheley]

@spapas I have reached out to the maintainers directly with the contact information I have

[EliShteinman]

Did they answer anything?

[tim-schilling]

We're still waiting on a response.

[spapas]

Hey friends, I think that the whole purpose of django-commons is to not have situations like this.

@tim-schilling I see that you have prepared a new release in this PR https://github.com/django-commons/django-prometheus/pull/507/changes

Please continue and merge it and release a new version in pypi. There a re a lot of people that are already using this version without problems. The django community will thank you.

[Stormheg]

Hi @spapas, you are absolutely right that Django Commons was created to avoid situations like this one.

Please also understand our position as admins: we do not wish to interfere with a project without explicit consent from the maintainer unless absolutely necessary (e.g. the maintainer continues to be unresponsive). We will (again) discuss this case during our admin meeting later today and I'm pushing to confirm a date by which we will take action if we continue hearing nothing from the maintainer.

We should also more clearly document what happens in situations like this one and what and when our community can expect the admins to take action.

Thank you for your continued patience 🙏

[Stormheg]

I want to rectify what I said 2 hours ago:

you are absolutely right that Django Commons was created to avoid situations like this one.

^ this is how I personally see the role of Django Commons. In my opinion, the admins can and should step in when a project appears abandoned. Not making a compatibility release for some amount of time supports the case of abandonment in my eyes. But this is not the official Django Commons Admin's position.

I wasn't aware that there was actually a bit of activity recently, such as django-commons/django-prometheus#505 being merged. This makes the situation less clear-cut. For this and other reasons I can't go into, we couldn't come to an unanimous decision during our admin meeting just now. Expect a follow up message from us.

We're really counting on @asherf to communicate with us and give consent to either one of us admins making a release, on-boarding a new maintainer, or something else.

Unless we can get in touch with Asher soon, you should be prepared to wait many more months. That's just something you (and everyone else) will have to deal with, sorry.

[ryancheley]

To @spapas and the broader community — thank you for your patience and continued engagement here.

It's worth noting that there has been activity in the repository recently — #505 was merged within the last three weeks. That context matters when determining whether a project meets the bar for abandonment.

While PEP 541 strictly governs PyPI package name retention and doesn't directly apply to Django Commons, it serves as a useful benchmark for how the broader Python ecosystem thinks about abandonment. Under that framework, a project is considered abandoned only when all of the following are true: the owner is unreachable, there have been no releases in the past twelve months, and there is no activity from the owner on the project's home page. Crucially, it also states that a project should never be reassigned against the wishes of a reachable owner. We think that's a reasonable standard to hold ourselves to as well.

Django Commons exists to give projects a sustainable home — not to arbitrarily reassign or override maintainers who have put real work into building something. Stepping in unilaterally without consent, except in cases of true abandonment, would undermine the trust that makes the whole model work. That's a line we take seriously.

We are continuing to try to reach @asherf directly, and we will provide a clearer update once our admin team has aligned on next steps.

[spapas]

@ryancheley that makes sense. I think we still have time and after all people that want to use Django 6 can clone the github repo.

However I would urge you to add a hard deadline: The end of Django 5.2 support (which is in two years). So if no new release with support for Django 6.2 has been released until then the admins should intervene and release the new version.