atom feed38 messages in org.apache.incubator.cloudstack-devRE: Drop OVM in 4.0?
FromSent OnAttachments
Edison SuOct 17, 2012 11:25 am 
Kelcey Damage (BBITS)Oct 17, 2012 11:27 am 
Frank ZhangOct 17, 2012 11:35 am 
Kelcey Damage (BBITS)Oct 17, 2012 11:37 am 
Edison SuOct 17, 2012 11:37 am 
Kelcey Damage (BBITS)Oct 17, 2012 11:39 am 
David NalleyOct 17, 2012 11:40 am 
Frank ZhangOct 17, 2012 11:47 am 
David NalleyOct 17, 2012 11:51 am 
Sudha PonnagantiOct 17, 2012 11:53 am 
Sudha PonnagantiOct 17, 2012 12:20 pm 
Will ChanOct 17, 2012 1:55 pm 
Kristoffer Sheather - Cloud CentralOct 17, 2012 2:40 pm 
Outback DingoOct 17, 2012 2:42 pm 
Caleb CallOct 17, 2012 3:01 pm 
Kelcey Damage (BBITS)Oct 17, 2012 3:06 pm 
Chiradeep VittalOct 17, 2012 4:50 pm 
David NalleyOct 17, 2012 4:54 pm 
Edison SuOct 17, 2012 4:55 pm 
Chiradeep VittalOct 17, 2012 4:58 pm 
Frank ZhangOct 17, 2012 6:59 pm 
Joe BrockmeierOct 17, 2012 7:30 pm 
Chip ChildersOct 18, 2012 7:11 am 
Will ChanOct 18, 2012 10:01 am 
John KinsellaOct 18, 2012 10:04 am 
Jessica TomechakOct 18, 2012 10:05 am 
Will ChanOct 18, 2012 10:29 am 
Kevin KlugeOct 18, 2012 11:10 am 
Joe BrockmeierOct 18, 2012 12:36 pm 
David NalleyOct 18, 2012 12:47 pm 
Marcus SorensenOct 18, 2012 12:53 pm 
Edison SuOct 18, 2012 1:53 pm 
Joe BrockmeierOct 18, 2012 2:15 pm 
Edison SuOct 18, 2012 2:59 pm 
Chip ChildersOct 18, 2012 3:04 pm 
Joe BrockmeierOct 18, 2012 4:06 pm 
Caleb CallOct 18, 2012 4:55 pm 
Sudha PonnagantiOct 18, 2012 5:43 pm 
Subject:RE: Drop OVM in 4.0?
From:Sudha Ponnaganti (sudh@citrix.com)
Date:Oct 18, 2012 5:43:02 pm
List:org.apache.incubator.cloudstack-dev

+1 to fix it for 4.0.1 version -1 to drop it

-----Original Message----- From: Chip Childers [mailto:chip@sungard.com] Sent: Thursday, October 18, 2012 3:05 PM To: <clou@incubator.apache.org> Subject: Re: Drop OVM in 4.0?

Also, if it hasn't worked in several past non-Apache releases, are we really
dropping support now?

I'm -1 for considering it a blocker for 4.0.0-incubating. It can always be added
back / fixed / whatever if someone cares about doing that.

I say we move forward without changing the current state (I.e.: it doesn't work)

- chip

Sent from my iPhone.

On Oct 18, 2012, at 6:00 PM, Edison Su <Edis@citrix.com> wrote:

-----Original Message----- From: Joe Brockmeier [mailto:jz@zonker.net] Sent: Thursday, October 18, 2012 2:16 PM To: clou@incubator.apache.org Subject: Re: Drop OVM in 4.0?

On Thu, Oct 18, 2012 at 01:54:03PM -0700, Edison Su wrote:

Yesterday, I read a blog talking about open source project(http://blog.ometer.com/2012/03/15/a-few-thoughts-on-open- projects-with-mention-of-scala/), in the " Project direction and priorities " section, which makes sense to me:

"An open project and its community are the sum of individual people doing what they care about. It's flat-out wrong to think that any healthy open project is a pool of developers who can be assigned priorities that "make sense" globally. There's no product manager. The community priorities are simply the union of all community-member priorities."

No disagreement. But there's another tradition in healthy open source communities of letting people know ahead of time that something is being orphaned. That didn't happen here.

Nobody complains OVM doesn't work in 4.0 before, means nobody use and test it on
4.0 branch since half year ago when we starting to work on 4.0 release. And CloudStack 3.0.x release doesn't support OVM also, at least, I can't find
any information about OVM in
http://download.cloud.com/releases/3.0.0/CloudStack3.0AdminGuide.pdf. If no user and developer cares/complains about a feature for such a long time, is it safe to say "people are really doing what they care about"?:)

Take OVM as an example, apparently, it's not in the Citrix's CloudPlatform team's highest priority. If other people want this feature, the idea situation is to pick it up by yourself. I think Marcus set a great example about how to work with community under this situation. We, the community, are open to bug fix, feature enhancement etc.

And that works fine if we, the community, communicate about things that are going to be dropped so that others have time to pick them up.