🛬 [INBOUND] - django-simple-history

[ddabble]

What's the URL to the project?

https://github.com/jazzband/django-simple-history

Who are the current maintainers?

Active:

@ddabble and @tim-schilling

Project leads:

@treyhunner and @rossmechanic

Other maintainers:

@jeking3 @thisisazeez @LeMinaw @valberg @brylie @johanneswilm @thesayfulla @mraza007

Does the project have the required attributes?

• Does the project have tests?
• Does the project have documentation?
• Has the project adopted Django Commons's Code of Conduct?
  • Will be done with Switch repo to Django Commons jazzband/django-simple-history#1429

Who will be the new maintainers of the project?

@ddabble and @tim-schilling, as mentioned in jazzband/django-simple-history#1391 (comment)

Do you use test PyPI or want to test the packaging process?

• Does the project have a test.pypi.org project?
  • Looks like it: https://test.pypi.org/project/django-simple-history/
• Would you like to test your deployments with uploads to test.pypi.org (you'll need to create the project first)?
  • Sounds like something that could be useful, but I'm not familiar with this at all 😅

---

Related Issues

• django-simple-history discussion issue: Transfer django-simple-history to Django Commons jazzband/django-simple-history#1391 (mentioned above)
• Jazzband transfer issue: Transfer out: django-simple-history jazzband/help#382

[github-actions]

User django-simple-history does not exist.

[ddabble]

Whoops, pressed enter by accident 😅 Hold on while I edit the description..

[tim-schilling]

@ddabble correct me if I'm wrong about the merge options:

"django-simple-history" = {
  description = "Store model history and view/revert changes from admin site. "
  allow_merge_commit = true # Allow merge commits on pull requests
  allow_rebase_merge = false # Allow rebase and merge commits on pull requests
  allow_squash_merge = true # Allow squash and merge commits on pull requests
  allow_update_branch = true # Allow updating source branch on pull requests
  admins = [
    # Include people who can release new versions
    "ddabble",
    "tim-schilling",
  ]
  committers = [
    # Include people who can commit to main / merge changes
  ]
  members = [
    # Include people who can assign/triage tickets
  ]
}

[tim-schilling]

@treyhunner any chance you have owner permissions for one or both of the the pypi.org and test.pypi.org projects?

[tim-schilling]

I should have clarified, can you add cunla (Daniel), stormheg (Storm) and CodenameTim (myself)? We will take over ownership of the project on the PyPI sites. This would involve removing folks after 30 days who are not on the repo's administrators team (currently it's @ddabble and I).

@ddabble if you have an account on those sites, can you please list it as well?

[ddabble]

@ddabble correct me if I'm wrong about the merge options:
[...]

(Am I understanding it correctly that this is some textual configuration of the repo settings?)
Sure, that looks good, though a personal preference is to not use rebase merging, as rebasing usually makes it more difficult getting a picture of which commits came from which PR. So I'd vote for setting allow_rebase_merge = false, but I'm fine with whatever 🙂

[ddabble]

@ddabble if you have an account on those sites, can you please list it as well?

Yes, it's dabble on both sites :) (PyPI; TestPyPI)

[tim-schilling]

You're understanding of that config is correct!

And interesting, I tend to like the rebase option because I find the merge commits a bit awkward and confusing compared to a linear history. I'm good with removing it though. It'll force me to try something new (my theme for 2025).

[treyhunner]

I should have clarified, can you add cunla (Daniel), stormheg (Storm) and CodenameTim (myself)? We will take over ownership of the project on the PyPI sites. This would involve removing folks after 30 days who are not on the repo's administrators team (currently it's @ddabble and I).

@ddabble if you have an account on those sites, can you please list it as well?

I wasn't sure whether you needed maintainer or owner access. I've added cunla, stormheg, dabble as maintainers and CodenameTim as an owner. @tim-schilling feel free to increase the access privileges of all as needed.

Would brianarmstrong, kyledseever, rossmechanic, ThePumpingLemma, macro1, and jazzband (and possibly me) be removed from the PyPI after 30 days as well? Or would the project leads stay on PyPI also?

[Stormheg]

@treyhunner, I just received the PyPI invite - thank you 👍

However, it permits us maintainer access only. Are you able to change our roles to owner?

Edit: I see you changed it, thanks! @tim-schilling did not explicitly mention what access we need, but it should always be 'owner' so we can properly administer.

[treyhunner]

@treyhunner, I just received the PyPI invite - thank you 👍

However, it permits us maintainer access only. Are you able to change our roles to owner?

I was able to increase access for all but @ddabble. They'll need to accept the pending invite before someone can increase access from maintainer to owner.

[ddabble]

@treyhunner, I just received the PyPI invite - thank you 👍

However, it permits us maintainer access only. Are you able to change our roles to owner?

I was able to increase access for all but @ddabble. They'll need to accept the pending invite before someone can increase access from maintainer to owner.

Accepted now :)

[treyhunner]

@treyhunner, I just received the PyPI invite - thank you 👍
However, it permits us maintainer access only. Are you able to change our roles to owner?

I was able to increase access for all but @ddabble. They'll need to accept the pending invite before someone can increase access from maintainer to owner.

Accepted now :)

Just made you an owner 👍

[tim-schilling]

Would brianarmstrong, kyledseever, rossmechanic, ThePumpingLemma, macro1, and jazzband (and possibly me) be removed from the PyPI after 30 days as well? Or would the project leads stay on PyPI also?

@treyhunner Yes, that would be the plan. Any of you are welcome to opt-in to staying on as an admin though! I don't believe anyone has over the few issues that exist, so @ddabble have been operating with the understanding that we would take over management of the repo.

[macro1]

it's been quite a while since i've been actively involved. happy to help if the need is there, but the project seems to be in capable hands with @ddabble and @rossmechanic before that. i'm fine to have my access decreased or removed if that's what you all think is best

[ddabble]

Thank you for your trust, @macro1, and also to you other guys for entrusting me with PyPI ownership! 😊