Just to throw in my two cents here. I work in an agency environment (lots of
projects, very few staff) and we follow the LTS cycle for almost all projects.
In my experience, jumping between LTS versions has - all things considered -
not been that big of an issue for us. I still sometimes wake up
Ok
On Sat, Aug 10, 2019 at 6:07 PM Carlton Gibson
wrote:
>
> On 10 Aug 2019, at 18:51, Confi Yobo wrote:
>
> So it should not be expected in 3.0? @ Carlton Gibson
>
>
> No. As per the previous comments, it’s not something likely to be included
> in core. Certainly not for 3.0.
>
> --
> You rece
On Sat, Aug 10, 2019 at 3:30 AM Carlton Gibson
wrote:
> What does it need from Ops? (Is there a `docker run-my-service`? Could we
> leverage djangoproject.com (and GitHub) logins, or are they always going
> to be separate?)
>
Markus has done more investigation on how to run it, though my impress
>
> On 10 Aug 2019, at 18:51, Confi Yobo wrote:
>
> So it should not be expected in 3.0? @ Carlton Gibson
No. As per the previous comments, it’s not something likely to be included in
core. Certainly not for 3.0.
--
You received this message because you are subscribed to the Google Groups
So it should not be expected in 3.0? @ Carlton Gibson
On Thursday, August 1, 2019 at 2:09:21 PM UTC+1, Confi Yobo wrote:
>
> This might be a little redundant as you would say but i see importance in
> it.
>
> Django should come chipped in with websocket implementation rather
> developers using t
Thanks for your feedback. Eventually I found out that the Django Crispy
Forms issue was a CSS bug in our CSS code. Anyway not related to Crispy
Forms, it may take a lot of time and effort to upgrade Django for us, and I
would prefer to keep using Django 1.11 as much as we can.
אורי
u...@speedy.net
This sounds good to me, plus this can be a all in one django spot for
django developer specially new developer
On Sat, 10 Aug, 2019, 8:33 AM Andrew Godwin, wrote:
> Hi everyone,
>
> This might be slightly controversial, but I would like to propose that we
> have a forum for discussing Django de
Just skimming this mailing list occasionally, I find pretty comical all
those "I think you found the wrong mailing list" replies. Not that there is
anything wrong with that, what else can one do? Just imho any new
communication channel should have a way of moving messages to a correct
place. Maybe
Hello,
I'm in favor of trying Discourse.
--
Aymeric.
> On 10 Aug 2019, at 05:03, Andrew Godwin wrote:
>
> Hi everyone,
>
> This might be slightly controversial, but I would like to propose that we
> have a forum for discussing Django development (and potentially user
> support), alongsid
It would be funny if the Django developers forum will use phpBB...
אורי
u...@speedy.net
On Sat, Aug 10, 2019 at 4:02 PM Adam Johnson wrote:
> I'm up for a forum. I started replying on mailing lists because that's
> what there is, but it does get pretty messy and single thread driven.
>
> PHPBB
I'm up for a forum. I started replying on mailing lists because that's what
there is, but it does get pretty messy and single thread driven.
PHPBB anyone? Shame there isn't a mature Django based forum (that I know
of).
On Sat, 10 Aug 2019 at 11:30, Carlton Gibson
wrote:
> I've thought about thi
I've thought about this sort of thing a few times. My concern has always
been that it'd be "just one more channel" when there are already too many
to follow: here, django-users, IRC (multiple channels) and so on.
If we did it under the aegis of the Django (Org/...SF) and we as a group of
activ
Thank you for bringing up the idea, Andrew.
As expressed at PyCon AU, I'd be interested in giving an alternative to a
mailing list a shot. Something that supports subscribing to topics sounds like
a good idea to overcome the amount of mails one may not be interested in.
Cheers, Markus
On Sat,
13 matches
Mail list logo
