django-suit
django-suit copied to clipboard
darklow
Doubt about the future of the project
Sorry for the question: But I would like to know if the project will have new updates or was discontinued, because the last commit was in March of 2107. I am asking because I am a big fan of this project and would not like to see it die.
It seems like the author is busy with other work. But I agree - we have paid license fees to use this and would be very disappointed it was not maintained.
@mateuspadua To be more precise, last commit was in July, v2 is main dev branch now: https://github.com/darklow/django-suit/tree/v2
I am very busy indeed, however Django suit is first app I install on any of my projects and so far v2 work perfect to me, ~~once I got time I will review Django 2.0 pull requests or feel free to review existing PR and if they do work let me know and I will approve them~~. Django 2.0 support is now added.
Django Suit was always intended as theme for Django Admin with as minimal invasive into Django as possible, it was never intended as being constantly updating with new features every week.
License fees are for commercial projects only because of the added value to your app that you sell to the clients, however code is still open source and anyone can contribute and make improvements.
I'd be willing to promote some users that can review and accept PR if there are volunteers.
Hello @darklow, thanks for reply. I'm asking because I really like (love) the project and I want to see this project getting better and better. Now I'm more relaxed :) to know that version 2.0 is on the way and I'll try to help more because I'm a big fan of this app. Thank you for sharing this amazing project.
The last release was 10 months ago (nobody is talking about 'updating with new features every week').
In that interval many django releases were made, some of which broke django-suit. Luckily some members of the community submitted PRs that fix things.
Someone needing those fixes cannot obtain a package from pypi, so either they need to vendor the code or depend on a branch or tag (which implies installing a git client wherever the package is needed).
Because django-suit is compatible with so many versions of django and python, reviewing and accepting PRs is the task where a django suit expert is needed.
@nwolff I could easily add it to pypi, but because there is no documentation it can create lot of confusion when somebody updates, not being aware of v2 changes.
PS. I never had problems installing with pip install -e git://github.com/darklow/django-suit.git@v2#egg=django-suit
PPS. Django 2.0 support is now added by
@darklow I tweeted, and thanks for the update. I'm new to Django and am REALLY interested in using django-suit, however the bootstrap 2 usage in the current master was a turnoff. I know I can pip-install from git, as you linked, but I'm wary of using v2 (or really any package) that isn't stable.
Speaking just for myself - though I imagine many might be in the same boat - django-suit would seem like a much more attractive option, and one that I'd gladly pay for, if v2 were the official master branch, and the official branch were updated more frequently.
@djpretzel I can assure you v2 is stable, I've used it for more than a year for near 10 different projects, but there is no documentation yet and I understand that may be a stopper for you.
@darklow - to pick up on what @djpretzel was asking: even with no documentation yet, would you be willing to make v2 the official master branch, into which pull requests could go?
(I think updates are a separate issue: I pay for something that is working & hope/expect it gets patched as needed; but actual improvements/expansion are a "nice to have").