> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Thursday, December 20, 2012 9:54 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Concerns about our community health and collaboration process
>
> On Thu, Dec 20, 2012 at 12:4
On Thu, Dec 20, 2012 at 12:46 PM, Marcus Sorensen wrote:
> Thanks for the followup Chip, I think I have a better idea now.
>
> The silence == consent thing is a bit hard for me to take; as a committer I
> have the ability to really screw things up, and so there's a lot of
> potential fallout from
Thanks for the followup Chip, I think I have a better idea now.
The silence == consent thing is a bit hard for me to take; as a committer I
have the ability to really screw things up, and so there's a lot of
potential fallout from moving forward with something only to find out that
someone missed
On Mon, Dec 17, 2012 at 6:07 AM, Sebastien Goasguen wrote:
>
> On Dec 15, 2012, at 12:42 AM, Marcus Sorensen wrote:
>
>> I agree, I certainly don't want to implement something only to have the
>> community do the same later(and in an incompatible manner). It behooves
>> consumers of the project
On Thu, Dec 13, 2012 at 4:30 PM, Joe Brockmeier wrote:
> On Fri, Dec 14, 2012 at 03:12:43PM -0500, Chip Childers wrote:
>> This is a bit long, but needs to be shared. Please do take time the time
>> to read it.
>
> Thanks for raising this. In my experience, it's a rare project that
> moves from a
On Fri, Dec 14, 2012 at 4:40 PM, Animesh Chaturvedi
wrote:
> In my opinion we should lean as much as possible towards "collaborating on
> all features".
>
+1
> The reason is two-fold firstly community is a place to learn and explore if
> we do not share ideas we would never know what commun
On Fri, Dec 14, 2012 at 4:16 PM, Marcus Sorensen wrote:
> I think this is a great discussion to have, but I think it would help if
> there were specific examples you could share so that we all have a better
> understanding.
I'd like to avoid picking out specific examples from the recent past,
bec
On Dec 15, 2012, at 12:42 AM, Marcus Sorensen wrote:
> I agree, I certainly don't want to implement something only to have the
> community do the same later(and in an incompatible manner). It behooves
> consumers of the project to work with the project. I just wanted
> clarification because I r
I agree, I certainly don't want to implement something only to have the
community do the same later(and in an incompatible manner). It behooves
consumers of the project to work with the project. I just wanted
clarification because I read this to mean essentially "hey guys, don't just
drop patches
On Fri, Dec 14, 2012 at 02:16:58PM -0700, Marcus Sorensen wrote:
> 3. If it's generic enough that it makes sense for upstream CloudStack (and
> believe me anything we can push back we want to), we post to the list to
> see if anyone else is working on it or interested in it.
>
> 4. We get feedback
On Fri, Dec 14, 2012 at 03:12:43PM -0500, Chip Childers wrote:
> This is a bit long, but needs to be shared. Please do take time the time
> to read it.
Thanks for raising this. In my experience, it's a rare project that
moves from a single-sponsor model to a full-blown community model that
doesn'
enarios we also help educate the community
on what matters most to the end users.
Thanks
Animesh
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Friday, December 14, 2012 1:17 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Con
I think this is a great discussion to have, but I think it would help if
there were specific examples you could share so that we all have a better
understanding. For example, I think I'm guilty of this in some respects,
but I'm not sure if this is what you're talking about. Let me post one of
my ex
On Fri, Dec 14, 2012 at 3:12 PM, Chip Childers
wrote:
> Hi all,
>
> I'm writing this email with my PPMC member hat on, but not speaking
> *for* the PPMC.
>
> This is a bit long, but needs to be shared. Please do take time the time
> to read it.
>
> Recently, some of us have been struggling with h
14 matches
Mail list logo
