Re: About the django-core mailing list

I would say that any information on why a structure exists is good. There is no difference have developers a confidential list, a chat or they communicate by phone, right? It has no relation to structure. It is a natural way for the decision not public problems. -- You received this

Re: About the django-core mailing list

On Fri, Sep 10, 2010 at 1:17 AM, Anton Bessonov wrote: > >> I disagree. Although it is normal for a project to have private >> mailing lists, such as -security > > You disagree, but it is normal? Decide for you first. I disagree that there was no explanation necessary. As

Re: About the django-core mailing list

I disagree. Although it is normal for a project to have private mailing lists, such as -security You disagree, but it is normal? Decide for you first. I'm very glad Jacob took the time to explain the need for its presence in Django. There is a difference about knowledge of the confidential

Re: About the django-core mailing list

On Sep 10, 8:41 am, Anton Bessonov wrote: > +1. Explaining existence of private  core-list is needless. I would say that any information on why a structure exists is good. The Apache Software Foundation would be a good example of where a lot of effort has been taken to

Re: About the django-core mailing list

On Thu, 2010-09-09 at 12:30 -0500, Jacob Kaplan-Moss wrote: > 1. Security-related issues. When we receive a security report, we need > to discuss it in private. Just as a data point... I'm a committer on a widely-used open source application, and we discuss these things on a "packagers" list. As

Re: About the django-core mailing list

I disagree. Although it is normal for a project to have private mailing lists, such as -security, I'm very glad Jacob took the time to explain the need for its presence in Django. And a big +1 on scheduling releases in public. J. Leclanche On Thu, Sep 9, 2010 at 11:41 PM, Anton Bessonov

Re: About the django-core mailing list

+1. Explaining existence of private core-list is needless. But also +1 for other points in Eric's presentation. Thanks Jacob, I don't understand why we are discussing about it. It's quite obvious that if there is a core team, there's also a mailing list. S -- You received this message

Re: About the django-core mailing list

Thanks Jacob, I don't understand why we are discussing about it. It's quite obvious that if there is a core team, there's also a mailing list. S On Thu, Sep 9, 2010 at 19:30, Jacob Kaplan-Moss wrote: > Hi folks -- > > A bit of context before I dive in: at DjangoCon, Eric

Re: About the django-core mailing list

On do, 2010-09-09 at 12:30 -0500, Jacob Kaplan-Moss wrote: > The goal is to only be private when we absolutely *must*, and if we're > not sufficiently transparent *please* say something. Thanks Jacob, for explaining this. This makes a good amount of sense, and Django is not unique here. I am

About the django-core mailing list

Hi folks -- A bit of context before I dive in: at DjangoCon, Eric Florenzano gave a "what's broken about Django" talk. I sadly had to miss DjangoCon, and so I'm anxiously waiting to see the video, but I did see one thing in the slides I thought I should address right away. Actually, this is