On Sat, Nov 16, 2013 at 9:09 AM, Monty Taylor wrote:
> Can I suggest that you don't try purely mechanical filtering into
> folders? Instead, for a while, try using a threaded client, and
> configure it to show threads unexpanded by default.
>
if we are into mail client tips, Emacs GNUS has an a
Morgan Fainberg wrote:
> TL;DR Don't split the community, work to improve the tools for those
> who are overwhelmed. (Email clients, enforcing use of subject tags,
> etc)
Thanks everyone for the insightful comments ! Like I said earlier, we
can keep it the way it is, but I just wanted to make sure
A couple of quick points.
1) I think that splitting the list is the wrong approach.
2) Perhaps we need to look at adding a mechanism that enforces the use
of tags in the subject line (send a nice "sorry, but you need to
indicate the topic(s) you are mailing about" error back if it doesn't
exist, ke
I am one of those horizontal people (working on docs and basically one of
the people responsible at my organization for keeping a handle on what's
going on) and I'm totally against a split.
Of COURSE we need to maintain the integrated/incubated/proposed spectrum.
Saying that we need to keep all tr
On 11/16/2013 02:52 AM, Monty Taylor wrote:
On 11/15/2013 05:06 AM, Thierry Carrez wrote:
Wow, lots of different opinions! let's try to summarize:
Arguments in favor of splitting openstack-dev / stackforge-dev
* People can easily filter out all non-openstack discussions
* Traffic would drop by
On Saturday, November 16, 2013 2:09:35 AM, Monty Taylor wrote:
On 11/15/2013 12:08 PM, Thierry Carrez wrote:
Adrian Otto wrote:
If OpenStack starts a culture of exclusion instead of inclusion, that would start a
dangerous trend that sets the wrong tone. It would quickly reach the point whe
On 11/15/2013 12:08 PM, Thierry Carrez wrote:
> Adrian Otto wrote:
>> If OpenStack starts a culture of exclusion instead of inclusion, that would
>> start a dangerous trend that sets the wrong tone. It would quickly reach the
>> point where new projects like mine would simply not come here. We
On 11/15/2013 05:06 AM, Thierry Carrez wrote:
> Wow, lots of different opinions! let's try to summarize:
>
> Arguments in favor of splitting openstack-dev / stackforge-dev
> * People can easily filter out all non-openstack discussions
> * Traffic would drop by about 25%
> * Removes confusion as
Coming from QA/Ops, I agree that there are horizontal teams that need to get
info from the mailing list(s) across the spectrum. I also agree with Clint's
and Adrian's statements about the synergies and serendipities of all the
developers on one list. But I also understand the feeling of drowni
Another thing that I remember from talking with people who work at yahoo
on the hadoop project and was an insight early on for me. I remember those
folks saying that about 2 hours of there day is spent on catching up on
mailing list emails and reviews. This is/was a change in how they operated
when
Excerpts from Stefano Maffulli's message of 2013-11-15 09:12:05 -0800:
> On 11/15/2013 02:06 AM, Thierry Carrez wrote:
> > Arguments in favor of splitting openstack-dev / stackforge-dev
> > * People can easily filter out all non-openstack discussions
> > * Traffic would drop by about 25%
>
> I'm n
On 11/15/2013 02:06 AM, Thierry Carrez wrote:
> Arguments in favor of splitting openstack-dev / stackforge-dev
> * People can easily filter out all non-openstack discussions
> * Traffic would drop by about 25%
I'm not so convinced about this figure, as others pointed out.
> * Removes confusion as
Adrian Otto wrote:
> If OpenStack starts a culture of exclusion instead of inclusion, that would
> start a dangerous trend that sets the wrong tone. It would quickly reach the
> point where new projects like mine would simply not come here. We would go
> somewhere else that does have a culture o
On Nov 15, 2013, at 2:06 AM, Thierry Carrez wrote:
> Wow, lots of different opinions! let's try to summarize:
>
> Arguments in favor of splitting openstack-dev / stackforge-dev
> * People can easily filter out all non-openstack discussions
> * Traffic would drop by about 25%
> * Removes confusi
Definitely +1 for splitting -- it becomes overwhelmed. We'll soon need
regexps just to handle the incoming emails :) Having separate mailing lists
would make it easier to stay focused and concentrate on needed projects.
On Fri, Nov 15, 2013 at 12:18 PM, Flavio Percoco wrote:
> On 15/11/13 11:06
On 15/11/13 11:06 +0100, Thierry Carrez wrote:
Wow, lots of different opinions! let's try to summarize:
Arguments in favor of splitting openstack-dev / stackforge-dev
* People can easily filter out all non-openstack discussions
* Traffic would drop by about 25%
* Removes confusion as to which pr
Wow, lots of different opinions! let's try to summarize:
Arguments in favor of splitting openstack-dev / stackforge-dev
* People can easily filter out all non-openstack discussions
* Traffic would drop by about 25%
* Removes confusion as to which projects are actually "in openstack"
Arguments in
17 matches
Mail list logo
