Is this project maintained?

[MikeWooster]

This projects README states that: This project is currently unmaintained.

This message was added to the README in March 2021 - commit.

This was added in version 0.13, and there have been 6 releases since then.

So, is this project actually unmaintained? Or is this message misleading?

I'm asking as seeing this message makes me want to move away from using it.

[timobrembeck]

I think the notice is mostly meant for users who are starting new projects and are looking for long term support – something which is not guaranteed by this package.
But if you're already using this library and don't have specific problems with it, I don't see a reason to migrate to something else. I myself migrated one project to django-treebeard and kind of regret it – it's not maintained much better and also has crucial issues which have been open for a long time.

Also, to quote @matthiask:

That being said, I'm still using django-mptt in a few projects so I'm unlikely to let it rot completely but I want to be clear that I'll not be the driver of large changes to django-mptt (anymore).

– #831 (comment)

[matthiask]

Thanks, that's an excellent summary.

I wrote a lenghty post a few years back which is also linked in the README of django-mptt: https://406.ch/writing/django-tree-queries/

I have retired a few projects which used django-mptt since then (and haven't started any new ones) but some of them will probably still be used for the foreseeable future (at least I hope so since some of them are relatively well paid)

[MikeWooster]

Thanks both for your replies.

So, for clarification: we will continue to get security patches, but will not get any new features?

Apologies for not going through the blog post to see the current status. Is it worth updating the README to update the current status too / support level? Just to make it clear.

[matthiask]

So, for clarification: we will continue to get security patches, but will not get any new features?

Neither is guaranteed. There's no guarantee in (most) projects anyway if there's no contract, and even less in the case of django-mptt. That being said. I will probably continue to review patches and publish releases from time to time since I'm still scratching my own itch here.

Apologies for not going through the blog post to see the current status. Is it worth updating the README to update the current status too / support level? Just to make it clear.

If you want to contribute a clarification, sure! I'm not sure I have anything to add to the blogpost.

Btw, if a project has a smaller community and governance structure than for example the Django project itself you should be asking yourself anyway if you'd be able to either remove the dependency or maintain it yourself should the need arise. I have also written a post on this with some guidance. Since you seem to be asking for free labor ("will we continue to get patches") it might be a worthwile read as well. https://406.ch/writing/run-less-code-in-production-or-youll-end-up-paying-the-price-later/ (No hard feelings from my side.)

[Bragegs]

When you hate that you have to use your own great package. 😂 Anyways -> grateful for every update we get.

[Elger9]

How about we stop pretending that there is another equally functional project and remove the information 'This project is currently unmaintained'?

[matthiask]

@Elger9 Feel free to step up as a maintainer. You can start by triaging issues and reviewing pull requests. That would be helpful. If you can show consistency and good judgement I'll happily grant you the commit bit.