Status of localflavor recombination

165 views
Skip to first unread message

Jannis Leidel

unread,
Jun 9, 2013, 7:33:28 AM6/9/13
to django-d...@googlegroups.com
Hi all,

I'm writing you today to report on the status of the recombination of the localflavor app I've proposed a little while ago on the developer list: https://groups.google.com/d/topic/django-developers/vxCStIvpXc4/discussion

To recap: we've handled the handover of the localflavor app to the broader community badly to the extent that we only had 7 out of 44 localflavors re-released on PyPI. That's a ~15% success rate, which I believe stems from the increased maintenance friction of the small packages. We also lost the ability to use Transifex to handle translations and didn't provide a unified test support.

I've BCC'd the team owners of the relevant localflavors from Github in case they are not subscribed to the -developers mailing list and found out that there are two non-Django localflavor already on Github (Greek and Lithuanian) whose authors I've also reached out to separately.

I've given the maintainers of the django-localflavor-* apps access to the django-localflavor repo.

It took longer than expected to actually merge everything together again, since some packages had diverged drastically. But I'm happy to announce that the code is now ready for another look by everyone interested:

https://github.com/django/django-localflavor

I've extended the documentation somewhat and decided to use Sphinx' autodoc extension for it -- I hope it's pleasant enough:

http://django-localflavor.readthedocs.org/

184 Tests pass on Python 2.6-3.3, 1.5 and trunk:

https://travis-ci.org/django/django-localflavor

There is a new Transifex project (under the umbrella of the Django hub, that shares translators and strings):

https://www.transifex.com/projects/p/django-localflavor/

My next steps are:

- see if there are any side issues I overlooked
- collect author information for the AUTHORS file
- deactivate existing django-localflavor-* projects (probably going to use Github's new repo redirects)
- figure out how to handle already made PyPI releases of django-localflavor-* apps
- write some generic porting instruction for django-localflavor-* > django-localflavor
- update the Django docs to point to the new django-localflavor app
- update django-localflavor docs to be more specific about adding new localflavors, releases etc
- do PyPI release

Please let me know if you have any questions or if anything of the above doesn't make sense.

Thanks,
Jannis

PS: the one-time port script I used at the start can be found here: https://github.com/django/django-localflavor/blob/master/scripts/port.py

Jacob Kaplan-Moss

unread,
Jun 9, 2013, 11:24:17 AM6/9/13
to django-developers
Thanks for doing this! That's a lot of not-entirely-fun grunt work,
thanks for making it happen.

Jacob
> --
> You received this message because you are subscribed to the Google Groups "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
> To post to this group, send email to django-d...@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Jannis Leidel

unread,
Jun 10, 2013, 4:32:31 AM6/10/13
to django-d...@googlegroups.com
Quick update:

The maintainers of the non-Django localflavors (Greece and Lithuania) both agreed to join in, too! \o/

Best,
Jannis
Reply all
Reply to author
Forward
0 new messages