Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Join jazzband? #133

Closed
valberg opened this issue Apr 2, 2022 · 11 comments
Closed

Join jazzband? #133

valberg opened this issue Apr 2, 2022 · 11 comments

Comments

@valberg
Copy link
Collaborator

valberg commented Apr 2, 2022

I was thinking that maybe the project could benefit from joining Jazzband (https://jazzband.co)? What do you thing @akx ?

@valberg
Copy link
Collaborator Author

valberg commented Apr 11, 2022

Ping @akx :)

@valberg
Copy link
Collaborator Author

valberg commented Apr 11, 2022

Cool! Should I start the process over in https://github.com/jazzband/help/issues?

@matmair
Copy link

matmair commented Jun 18, 2022

Hi there @valberg and @akx - any movement on this?

@jkaeske
Copy link
Contributor

jkaeske commented Mar 23, 2023

Are there any news on this? @valberg did you create the issue in the jazzband repo?

@valberg
Copy link
Collaborator Author

valberg commented Mar 23, 2023

@jkaeske I did not - I have been waiting for an answer from @akx. We can start the process, but we need the Valohai people to approve it.

@jkaeske
Copy link
Contributor

jkaeske commented Mar 24, 2023

I see, then we probably have to wait for @akx or @ruksi to give input here.
I could prepare the issue for jazzband if it is a problem of time to make the request.

Since allauth is a key package for a lot of application, I think it would be sad to leave this repo unmaintained to be honest.

@akx
Copy link
Member

akx commented Mar 24, 2023

I'm sorry I dropped the ball on this!

To be frank, I'm maybe a bit hesitant on Jazzband, considering they too seem to have a lot on their plates, and having a large group of people managing (i.e. being able to e.g. upload releases of) a security-critical library such as this sounds a bit iffy.

@valberg
Copy link
Collaborator Author

valberg commented Mar 24, 2023

It is only the people who are appointed maintainers of a project who are able to publish new versions PyPI.

But if you wish to keep the repo under Valohai that is fine by me ☺️ I only suggested it to keep the ball rolling. So as long as we can keep said ball rolling it doesn't matter to me what organisation the project is under 😉

@jkaeske
Copy link
Contributor

jkaeske commented Mar 24, 2023

I'm sorry I dropped the ball on this!

To be frank, I'm maybe a bit hesitant on Jazzband, considering they too seem to have a lot on their plates, and having a large group of people managing (i.e. being able to e.g. upload releases of) a security-critical library such as this sounds a bit iffy.

That is for sure a good point.
How could we help you to push things in the right direction?
Can we help planning for a future 1.0 release or what would help you?

@pennersr
Copy link
Contributor

I'm sorry I dropped the ball on this!

To be frank, I'm maybe a bit hesitant on Jazzband, considering they too seem to have a lot on their plates, and having a large group of people managing (i.e. being able to e.g. upload releases of) a security-critical library such as this sounds a bit iffy.

FWIW, there was a similar discussion over at django-allauth: pennersr/django-allauth#3202 (comment)

@valberg
Copy link
Collaborator Author

valberg commented Mar 28, 2023

I believe a decision has been made, so I'm closing this issue. If anyone has an objection just say the word - although I think it has to be some very convincing arguments.

@valberg valberg closed this as completed Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants