django-simple-history

[williln]

Hi @django-commons/django-simple-history! I wanted to take a moment and check in with you about how your project is doing in Django Commons.

• Have you run into any friction having your project in Django Commons, if so, can you describe them?
• Is there anything we can do to help your team or repo out?
• Do you have any questions or concerns for us?

If you'd like to chat with us privately, our email is django-commons-admin@googlegroups.com. Thanks!

[ddabble]

Heey, thanks for checking in! 😊

• No friction that I'm aware of - the main challenge is just finding time to do maintenance work
• Getting more maintainers on board would certainly help, but other than that, I can't think of anything 🤔
• Not right now, but I'll let you know!

I can't speak for @tim-schilling, of course :)

[tim-schilling]

Agreed with what @ddabble said

[tim-schilling]

@ddabble I granted permissions for the Read The Docs App for django-simple-history. I did not enable this for the whole org (let me know if that was your intention), since @django-commons/admins have yet to discuss it.

[ddabble]

Nice, thanks! I wasn't particularly sure that it would actually be useful/necessary to enable it for the whole org when I submitted the request, so glad that you took that decision 😁

For context, I'm migrating our RTD site to the new GitHub App following this blog post :)

[tim-schilling]

Sounds good!

[tim-schilling]

Hi @django-commons/django-simple-history this is just our semi-annual checkin. Let us know if there is anything Django Commons can do to help, or if there is anything else on your mind! Otherwise, happy coding 🥳

As an additional reminder, though not at all a suggestion/requirement. It may be worth looking through who has regularly contributed to your project to see if you'd like to elevate them to be a committer or a maintainer. I mention it because it's easy to forget to review the repositories community and helping people grow. Similarly, if you or anyone else wants to step back, that's fine too! If we can help coordinate, please let us know.

[tim-schilling]

Whoops, forgot some things. There are two other things:

1. Can the @django-commons/django-simple-history-admins please share your emails with us? You can email us at django-commons-admin@googlegroups.com to avoid publishing publicly here.
2. We are working on a new policy around project abandonment. As a community organization, we need to have clear guidelines on when the community should pass the project onto someone else or signaling that the project is in a period of low activity. We'll share this new policy with you when we have it ready for comment. This will include a timeline for adoption. If you have questions, please let us know!

[ddabble]

Thanks for the checkup! 😊

When it comes to me, I think it's no secret that I've been much less active the last couple years or so - after I got a full-time developer job and joined a game development hobby project. And so that - combined with my interests having slightly shifted - means that I think we're a little overdue for getting some additional maintainers on board who can help chip away at the slowly growing number of issues and PRs asking the current maintainers for help and reviews - and understandably so, since replies from us have been few and far between. (I'm glad we've not been hit by waves of AI-generated PRs, though, which I'm aware other projects have been less fortunate with 😅)

And so it's a good shout to consider inviting regular contributors to become maintainers! Now, I don't feel there's been a ton of PR activity recently (and also I've been pretty behind on that front, as mentioned), so I'm personally a little unsure who could be a good fit 🤔 Do you happen to have anyone in mind, Tim? Regardless, I'll definitely keep it in mind going forward!

Btw, I'm still very much available for (and interested in) doing admin stuff, as well as important updates for the project itself (e.g. things like upgrading Django compatibility, fixing the CI, migrating build systems, preparing and publishing releases, etc.)! I might sporadically take the time to do other maintenance work as well, like reviewing PRs and replying to issues, but I don't feel we can count on me getting to the rest of the necessary maintenance work, unfortunately.

---

Regarding the other things you mentioned:

1. Sent an email now :)
2. Sounds good! 👍

[tim-schilling]

No worries! I had someone email me about doing a code-review on this project and I told them this project is the last thing on my priority list unfortunately. I'm fine going into a "keep the lights on" maintenance mode for now, but let's move that to an issue on the repo for others to chime in.

[ddabble]

That sounds fine for me as well; I opened an issue on it now :)