>
> If we did split it out, would you be interested in being a maintainer?
>
>
I was against this at first but the more I've thought about it, I would be
interested. Has anyone else expressed any interest or will I be the only
maintainer?
I have another project coming up that will most likely
On 03.06.2014, at 14:53, Josh Smeaton wrote:
> 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 carro
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
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 inter
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 th
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-develo
The company I'm currently contracting for, makes heavy use of formtools,
I'd be disappointed to see it go.
On Monday, May 26, 2014 6:04:31 PM UTC-4, Tim Graham wrote:
>
> My observation is that not many core developers seem interested in
> contrib.formtools these days. It was added by Adrian in
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
If we did split it out, would you be interested in being a maintainer?
On Monday, May 26, 2014 6:51:13 PM UTC-4, Gordon wrote:
>
>
>
> On Monday, May 26, 2014 6:04:31 PM UTC-4, Tim Graham wrote:
>>
>> My observation is that not many core developers seem interested in
>> contrib.formtools these da
On Monday, May 26, 2014 6:04:31 PM UTC-4, Tim Graham wrote:
>
> My observation is that not many core developers seem interested in
> contrib.formtools these days. It was added by Adrian in 2006, but as far as
> I can see from the commit history, it hasn't received much love lately. If
> would
My observation is that not many core developers seem interested in
contrib.formtools these days. It was added by Adrian in 2006, but as far as
I can see from the commit history, it hasn't received much love lately. If
would be a good candidate for deprecation from Django itself, in my opinion.
Hello,
I have posted an implementation/proof of concept to ticket 21644
(https://code.djangoproject.com/ticket/21644). The implementation is
currently written as a mixin because I need to be able to use it now and I
don't like maintaining a custom fork of django for my projects. If changed
t
12 matches
Mail list logo
