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 <edison...@citrix.com> wrote: > > >> -----Original Message----- >> From: Joe Brockmeier [mailto:j...@zonker.net] >> Sent: Thursday, October 18, 2012 2:16 PM >> To: cloudstack-dev@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. >> -- >> Joe Brockmeier >> Twitter: @jzb >> http://dissociatedpress.net/ >
