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

Transfer django-simple-history to Django Commons #1391

Open
4 tasks
ddabble opened this issue Sep 15, 2024 · 10 comments
Open
4 tasks

Transfer django-simple-history to Django Commons #1391

ddabble opened this issue Sep 15, 2024 · 10 comments
Labels
meta Issues about the project itself

Comments

@ddabble
Copy link
Member

ddabble commented Sep 15, 2024

This is for tracking the progress of the idea started in django-commons/membership#40 (comment).

To my knowledge, Jazzband has only one admin currently, and adding more has been an ongoing issue for a while now (see jazzband/help#196). Quoting the Django Commons FAQ:

Given the importance of several of these projects it's a major risk to the community at large to have a single point of failure in managing the projects.

A transfer will allow us to merge #1305 and make us better able to avoid similar problems/delays in the future, as I think it's much more likely there will be more admins available.

The only two currently active maintainers, @tim-schilling and I, are both members of Django Commons, so the transfer won't change anything in that regard (other than opening up for more maintainers from Django Commons).

One of the two project leads, @treyhunner, has already expressed support of this decision, and so has Tim.

Remaining work

@ddabble ddabble pinned this issue Sep 15, 2024
@ddabble ddabble added the meta Issues about the project itself label Sep 15, 2024
@ddabble
Copy link
Member Author

ddabble commented Sep 15, 2024

(@-ing all current project leads and members)
@treyhunner @rossmechanic
@tim-schilling @jeking3 @thisisazeez @LeMinaw @valberg @brylie @johanneswilm @ddabble @thesayfulla @mraza007

Taking inspiration from django-commons/membership#34 (comment), who will be the new maintainers(/admins?) of the project? (I'm assuming that it's required of all maintainers to join Django Commons first.)

To mirror what I wrote in the issue description, I guess it would be natural for at least @tim-schilling and I to continue as maintainers.

@ddabble
Copy link
Member Author

ddabble commented Sep 15, 2024

Also, taking inspiration from jazzband/help#369 (comment), who should be contacted for transferal of the repo? @cunla?

@tim-schilling
Copy link
Contributor

tim-schilling commented Sep 15, 2024

@ddabble [edited] when there's consensus to move it over, the scheduling will be coordinated in the django-commons/membership issue for transferring it in.

In regards to my role with django-simple-history, I'm good with it moving over to django-commons. I am curious who among the current releasers still wants to be a releaser and if folks are comfortable handing those keys over to @ddabble (I'm +1 on that).

@cunla
Copy link
Member

cunla commented Sep 16, 2024

Also, taking inspiration from jazzband/help#369 (comment), who should be contacted for transferal of the repo? @cunla?

Hi @ddabble,
Please book some time with me to do the transfer: https://cal.com/daniel-moran/dc-meeting

@ddabble
Copy link
Member Author

ddabble commented Sep 16, 2024

@cunla No, I meant which Django Commons admin should be mentioned in the issue that will be created in jazzband/help - in the same fashion that you're mentioned in jazzband/help#369 (comment) 🙂 Though I guess Tim already answered that:

when there's consensus to move it over, the scheduling will be coordinated in the django-commons/membership issue for transferring it in.

Or did I misunderstand what you meant, and that having a meeting would be useful in any case? If so, then sure 👍

@cunla
Copy link
Member

cunla commented Sep 16, 2024

@cunla No, I meant which Django Commons admin should be mentioned in the issue that will be created in jazzband/help - in the same fashion that you're mentioned in jazzband/help#369 (comment) 🙂 Though I guess Tim already answered that:

when there's consensus to move it over, the scheduling will be coordinated in the django-commons/membership issue for transferring it in.

Or did I misunderstand what you meant, and that having a meeting would be useful in any case? If so, then sure 👍

Oh, I missed what Tim wrote. I agree with him. Once there is a consensus to move it over, then we can schedule some time to do the transfer.

@tim-schilling
Copy link
Contributor

Is @rossmechanic the last person we need to talk with for this move?

@ddabble
Copy link
Member Author

ddabble commented Oct 7, 2024

@tim-schilling Maybe, or perhaps the support of 1/2 project leads is enough - especially if one of them is inactive? I suppose @jezdez could answer that - either here or once we start the move 🙂

@tim-schilling
Copy link
Contributor

tim-schilling commented Oct 8, 2024

I think we need everyone on the same page here.

Edit: I emailed Ross and @ddabble today.

@ddabble
Copy link
Member Author

ddabble commented Oct 8, 2024

Oh great, thanks for taking the initiative! 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues about the project itself
Projects
None yet
Development

No branches or pull requests

3 participants