django-prometheus
django-prometheus copied to clipboard
korfuri
Status of this project?
Hi y'all,
First of all: Amazing work everyone. I've implemented django-prometheus pretty smoothly.
I had a question regarding the 62 issues and 17 pull requests, combined with the last release over a year ago.
What is the current status of this project? Are maintainers/contributors needed?
I must ask: have you actually looked at the issue queue here before posting this? There's a pinned issue here, https://github.com/korfuri/django-prometheus/issues/121, that actually makes it pretty clear that the stewardship of this project has been shifting, pretty much exactly matching the timeline you mention here.
There's even an issue specifically about making a new release, https://github.com/korfuri/django-prometheus/issues/422, and another issue that this here is basically a full dupe of, https://github.com/korfuri/django-prometheus/issues/332.
I can't speak for the new maintainer, but I think it's clear any help is welcome...
@asherf and @korfuri would you consider contributing this repository to Jazzband?
The community has come to rely on this project but the many PRs and Open Issues are not welcoming for new projects. Contributing this repository to be maintained by Jazzband would give it the attention it deserves, at least by integrating some of the open PRs.
Jazzband has a good track record of maintaining Django repositories.
I don't have permissions to do it. so this is something @korfuri will have to do.
@asherf thank you, that's great to know! Let's wait for @korfuri.
In the meanwhile, is there any way I can help cleanup current issues/PRs?
Hi all, apologies for the delayed answer, I was offline for the whole week.
I'm not opposed to moving this to Jazzband and I agree this project needs a better forever home. Would django-commons be a better fit than Jazzband, with its mission more focused on Django-related projects? Either option works for me, but as I'm not really plugged into the Python/Django ecosystems anymore I would like to hear your thoughts on this.
Hey @korfuri , I was also thinking that django-commons could be the better option. I'd like to help with the process if any help is needed. I'd also like to help with adding Python 3.13 and Django 5.2 supports.
I think/agree that Django commons sounds like a good place for this project 🤩
@asherf Could you help with the migration process? Should we get another approval from @korfuri ?
@asherf Could you help with the migration process? Should we get another approval from @korfuri ?
I don't think I can do it in terms of permissions on this repo @korfuri will have to transfer the repo in coordination with the Django commons org
Hey all, thanks for the conversation. I took a look at the requirements to migrate this project to Django commons. A couple things need to happen:
- We need to adopt their CoC - which looks like a pretty standard variant of the contributor covenant so LGTM, I have no objections. @asherf as the current maintainer is that also OK with you?
- Django-commons kind of requires some of the current maintainers to come along with it. I applied as a member (https://github.com/django-commons/membership/issues/206) just to be in the org to facilitate the transfer but as I've been away from this project and the entire Django ecosystem for years I should not remain as maintainer post move, there's no reason I should hold the keys to this project. @asherf do you want to apply as well?
Cheers,
Hey all, thanks for the conversation. I took a look at the requirements to migrate this project to Django commons. A couple things need to happen:
- We need to adopt their CoC - which looks like a pretty standard variant of the contributor covenant so LGTM, I have no objections. @asherf as the current maintainer is that also OK with you?
- Django-commons kind of requires some of the current maintainers to come along with it. I applied as a member (✋ [MEMBER] - korfuri django-commons/membership#206) just to be in the org to facilitate the transfer but as I've been away from this project and the entire Django ecosystem for years I should not remain as maintainer post move, there's no reason I should hold the keys to this project. @asherf do you want to apply as well?
Cheers,
I am a 100% ok with all of this.
Wonderful!
I've created https://github.com/korfuri/django-prometheus/pull/466 to add the CoC. Thanks for filing for membership!
https://github.com/django-commons/membership/issues/210 is the application to join Django Commons.
@asherf thanks for your continued stewardship of this project! You've done a ton to keep it going over the years and I'm very grateful that this project outlived my involvement.
@ulgens thanks a lot for all your recent support in this project! I encourage you to apply for contributor status on the Django Commons side if you are interested in carrying on :)
Everyone else, thanks as well for pushing me to finally give this project a better home than my personal account :) It was about time!
I think we can close this issue here and continue any discussion related to the adoption on the Django Commons side on the relevant issue there. 🥳