[ANN]: django-todo 2.0

[Scot Hacker]

“django-todo is a pluggable, multi-user, multi-group, multi-list todo and ticketing system - a reusable app designed to be dropped into any existing Django project. Users can create tasks for themselves or for others, or create ”assigned tasks” that will be filed into a specific list (public tickets).”

That was the original project description, and it hasn’t changed in 10+ years.

When I first created django-todo, it was a simple “let’s learn Django” project idea. I open sourced it, it’s been relatively successful, and the project has received numerous contributions over the years (grateful!). When I heard that it wasn’t compatible with Django 2.0, I looked back on that dusty old code and realized it was time for a major refactor/upgrade. 

The update started small, but by the end, I had made 75 commits and written the first suite of working tests (finally!). Virtually every module and template has been refactored, I  adopted Bootstrap as the default layout engine, and finally got around to creating a live demo site for the project.

django-todo 2.0 requires Django 2.0 and Python 3.x  - no apologies. Unfortunately, this is a backwards-incompatible update (you’ll need to migrate old data manually, if you have any).

Hope it’s useful to a few teams or individuals out there. Contributions still very much welcome.

Demo site: http://django-todo.org/

Docs: http://django-todo.readthedocs.io/

Github: https://github.com/shacker/django-todo

Demo host site (which runs django-todo.org): https://github.com/shacker/gtd

[katuramu henry]

This is awesome work Scot

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/4222bcad-bb6d-4406-936b-3d3e0cc37f06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Derek]

Interesting to hear of this.

Unfortunately we are currently committed to Django 1.11 as it is an LTS, but if you're planning on keeping this in-sync with all 2.x releases, then that opens up the option to look at using this from 2.2 onwards (that's the next LTS).

[Scot Hacker]

On Thursday, April 12, 2018 at 1:47:14 AM UTC-7, Derek wrote:

Interesting to hear of this.

Unfortunately we are currently committed to Django 1.11 as it is an LTS, but if you're planning on keeping this in-sync with all 2.x releases, then that opens up the option to look at using this from 2.2 onwards (that's the next LTS).

I *believe* the only Django 2-only feature in use is the URL routing. While untried, I suspect it would be pretty easy to get it working in a 1.11 project site by copying the provided urls.py into your own project, rewriting it in the old style, and including that from your main urls instead. Would be interested to hear whether this works for you.

./s

 

[Ankush Sharma]

Thanks ! I will try to implement as you suggested !!

--

You received this message because you are subscribed to the Google Groups "Django users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.

To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/114a2982-0355-455e-8edf-1535037ae680%40googlegroups.com.