If formtools were to be pulled out and released separately, would that theoretically mean that releases could come more frequently than django core (provided there was community interest and maintenance)? I think that would be a decent carrot for community members that rely on its functionality.
Regards, On Tuesday, 3 June 2014 20:25:51 UTC+10, Marc Tamlyn wrote: > > In my opinion, the reasoning for whether something should be a part of > contrib is as follows: > > - The application is of vital importance to the vast majority of Django > sites, and needs to be done "correctly". Examples include auth and > staticfiles, sessions. > - The application closely depends on internal, undocumented features of > Django or is strongly intertwined with the core features like the ORM. Such > applications are often very difficult to maintain their feature support > across multiple versions of Django. Examples include gis, postgres, > contenttypes. > > To me, formtools meets neither of these requirements. It is not a 90%+ use > case application like the admin or auth, and I don't believe there is much > to it that is not workable outside of Django itself. It is useful, and does > not deserve to be abandoned (like comments). Under github.com/django > seems ideal to me. > > Marc > > > On 3 June 2014 11:17, Jannis Leidel <lei...@gmail.com <javascript:>> > wrote: > >> Hi all, >> >> I’ve actually changed my mind about this after we successfully pulled out >> django-localflavor (another niche contrib app) after some initial bumps. >> It’s now maintained under the Django umbrella org on Github: >> https://github.com/django/django-localflavor/ >> >> I would like to propose to do the same with formtools and release it as >> django-formtools. >> >> - Move formtools out of contrib ASAP >> - Allow more maintainers next to Django core devs >> - Release individually from Django on PyPI as django-formtools >> - Maintain backward compatibility similar to localflavor (in short: >> support the currently supported Django versions) >> >> What do you think? >> >> Carl, any change in opinion with regard to that as well? >> >> Best, >> Jannis >> >> On 03.06.2014, at 00:42, Tim Graham <timog...@gmail.com <javascript:>> >> wrote: >> >> > contrib.databrowse is an example of something that was removed from >> Django. It seems to have found a home here: >> https://pypi.python.org/pypi/django-databrowse >> > >> > Deprecation of contrib.formtools was actually proposed on the mailing >> list in 2011, see >> https://groups.google.com/d/topic/django-developers/P_WMxmOCJFY/discussion >> > >> > At that time Carl and Jannis were -0 due to some recent improvements. I >> wonder if they feel any differently now. >> > >> > Jannis: "FYI, formtools is unlikely to go away anytime soon, as we've >> just >> > recently added a new class based views wizard [1]. Next step would >> > be to refactor the form preview tool to be class based, too [2]. >> > 1: https://docs.djangoproject.com/en/dev/releases/1.4/#new-form-wizard >> > 2: https://code.djangoproject.com/ticket/16174 >> > >> > >> > Carl: "-0 on formtools at this point for the same reason Jannis >> > mentioned; it is actually actively maintained and used, and recently got >> > some major improvements. In the abstract I do think that formtools is a >> > fine candidate to be an external app rather than live in contrib, I just >> > think we may as well start with the lower-hanging fruit here." >> > >> > >> > On Monday, June 2, 2014 2:27:07 PM UTC-4, Gordon wrote: >> > How would that work? Being part of contrib is a big plus for the app >> in many ways. I am not familiar with another app that was removed from >> contrib that would show an overview of the process and if it was successful. >> > >> > -- >> > 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 <javascript:>. >> > To post to this group, send email to django-d...@googlegroups.com >> <javascript:>. >> > Visit this group at http://groups.google.com/group/django-developers. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/6ad1f913-4508-41d9-ab8e-e2076f83839f%40googlegroups.com >> . >> > For more options, visit https://groups.google.com/d/optout. >> >> > -- 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/386bad7b-14e8-4e3a-ae44-94f3c8975f54%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
