Maintainership

[codingjoe]

Hi @philippeowagner,

Let me start by expressing my gratitude towards the hours you and other contributors have sunk into this project.
With that in mind, it would be sad to see this library fade away. Looking that the current state of the repository, it might be time to consider putting this project under new maintainership, to fuel the project with new enthusiasm.

Since you are a @jazzband member yourself, that would certainly be an option. If you prefer a corporate or individual maintainer, that could also be arranged.

Maybe you find the time to share your thoughts.

Best,
Joe

[Mogost]

The project really lacks care. It is very disappointing to prepare changes and wait for an answer for several years without receiving it...
#197

And in general, if nothing changes soon, I will fork this project (since the MIT license allows it).

[codingjoe]

FYI, I just reached out to @philippeowagner via email. I am confident this will yield a response. Let's give a little more time before resorting to a hard fork.

[philippeowagner]

Hi all,

We will find together a solution to get django-hijack forward.

The sources of django-hijack and django-hijack-admin will be moved to https://github.com/django-hijack as soon as possible.

I will call for maintainer once sources have moved.

[Mogost]

Nice to hear that!

[utapyngo]

Any news?

[philippeowagner]

Who'd like to join the party? You @codingjoe and you @Mogost ?

How are we going to organize this?

Any suggestions and experiences from other projects?

I'm talking about this repo and django-hijack/django-hijack-admin by the way.

[Mogost]

I am happy to take part.
I think we need automation for deployments and tests, which I did in #197.

May be interesting for @kedlav

[codingjoe]

Hi @philippeowagner, yes I'd be honored to help.

I guess it would be good to set some ground rules, like mandatory reviews and a release process as well as version support.
Those would be my suggestions:

Releases

I agree with @Mogost to automate this. However, #197 includes to many unrelated changes. I have a very tiny GitHub Action script that enables automated releases on PyPi. I'd be delighted to contribute that.
Besides that, semver is the way to go and every contribution should be released. Changes may be bundled into a single release if they were merged at the same day. Essentially, if you are done reviewing and merging changes for the day, release your changes. With the automation I proposed this would only mean to create a GibHub release with some notes and you're done.

Reviews

One should not merge their own code without a peer review. Every member may merge and release new PiPy versions.

Version support

Updating to new Python and Django versions has been getting easier latetly. It is usually sufficient to support the last two versions. Legacy application may simply jump to an older version of django-hijack.
Django: Latest stable and latest LTS (e.g. 3.1 & 2.2)
Python: Last two releases (e.g. 3.8 & 3.9)

[Mogost]

@codingjoe Agree about GH actions. If I made these changes today, it would be done this way.
In #197 I removed django-compat dependency, now this dependency hinders rather than helps.

Also I see django-hijack-admin as a part of django-hijack. I don't understand why this package comes separately.

[codingjoe]

@Mogost great. I proposed a GH action here #210
I'd also love to review the changes in #197, but it would be much simpler if you could split your changes across multiple pull requests.

[codingjoe]

@philippeowagner I'd also love to do triage on all open issues. There is a lot that simply needs an explanation and could be closed.

Splitting admin support into a separate package seems ambitious. We should test and document support with and without the admin, but I believe it might be more convenient to have this feature be part of this package. Be it only as a contrib and not core behavior.

[philippeowagner]

Ahoy pirates and welcome aboard!

Please welcome our new Captains @codingjoe and Quartermaster @Mogost – or vice versa.

I'm happy to hand over the steering wheel, but we (arteria GmbH) will remain on board as owners for the time being.

If any Sailing Master, Gunner, Powder Monkey, .. wants to join the journey, I'm happy to add more crew members with write access to this organization.

Have fun maneuvering this ship safely into the next harbor.

[philippeowagner]

PS: See #114 why does django-hijack-admin exist. The version numbers should be keeps in sync due to a .deb package. I think @stylesen asked for it.

PPS: Johannes, please email me in case you need my attention. Thank you!

[utapyngo]

I would like to participate as well.

[codingjoe]

The more, the merrier! @utapyngo you can get started on triage and review right away or submit patches.

[codingjoe]

I will close this issue now, since we can create new releases.