HyperVM Source Released… but is LXCenter Dead?
by J. Miller on Nov.10, 2009, under Applications, Computers, Internet, Linux, OpenSource, Operating Systems, Software, Web Hosting
LXCenter, the newly formed community group to replace what was LXLabs, have finally published the HyperVM and Kloxo source-code and opened access to the development and hosting communities… but is LXCenter, and ultimately HyperVM’s community, now dead and deserted by it’s once loyal supporters?
You can find information regarding the source code release here: http://forum.lxcenter.org/index.php?t=msg&th=13296
Mind you it’s taken almost 6 months since the founder’s death back in June (see this article from The Register) for this source code to FINALLY be released. What was going on for those 6 months under the control and management of Danny/Arthur? It seams by Arthur’s own words… NOTHING. Did they secretly sell the source code to a competitor and give them a 5-6 month development head-start on the rest of the community? I doubt it, but we’ll never really know.
What happens when you try and create a “consortium” for a large project such as HyperVM that’s headed up by a teenager with no experience in project management? This…
“I cannot, however, say that much work was done by my team, nor by Danny’s team.”
…This is what happens when you let a high school student attempt to takeover a project that is as large, diverse, and highly technical as HyperVM/Kloxo. (original post)
I mean seriously… HyperVM/Kloxo could have and still might turn into a GREAT opensource community hypervisor for OpenVZ and XEN. I am however quite sure that it won’t be under the incredibly poorly managed LXCenter community.
Asking yourself… Where and how do I download the HyperVM and Kloxo source?
Grab it from the SVN repository while someone’s still hosting it publicly!
svn checkout http://svn.lxcenter.org/svn/hypervm&
svn checkout http://svn.lxcenter.org/svn/kloxo&
svn checkout http://svn.lxcenter.org/svn/lxadmin&
svn checkout http://svn.lxcenter.org/svn/client&
Who knows what is going to happen over the next couple months….
“I do hope those left within the ‘consortium’ can get their act together and keep this system alive. If they really want some professional advice I’m sure there are those out there willing to assist them, including myself if requested. My original offers to the consortium were not even followed up with a response one way or another… just another example of bad project management. I for one await a lively and well managed community fork of HyperVM/Kloxo with patience…”
Involved with the LXCenter Consortium and reading this?
Contact me if you want: john [at] safitech.com
Related posts:

January 28th, 2010 on 11:38 am
Since is GPL, why not forking the project? Do we really need LXCenter?
January 29th, 2010 on 9:47 am
I’m actually quite surprised that a major fork hasn’t popped up yet. I get the feeling most places have taken the code and re-vamped for proprietary commercial uses instead of giving back to the community or creating a better ran fork of LXCenter.
March 12th, 2010 on 9:30 am
The story needs some updates
Anyway, a lot is going on now. After a false start, a new start did happen and developing is acualy started.
We have created job functions and are filling those with vollunteers. Just follow the forum. Soon we post a kind of Roadmap and other information.
Regards,
Danny
LxCenter – System Operations
March 12th, 2010 on 9:45 am
Danny I’m more then happy to do a followup article once a viable roadmap is available and things actually start moving, just get in touch with me again. I’ve noticed some edges being polished, but still no real major changes or a highly structured approach… i.e. Wiki is still in horrible condition, development is BARELY started, and sorry but using the forums as a primary means of communication and source for all information regarding the project is just not right, and quite annoying to be truthful. I will keep an eye on things and will do a followup when changes really warrant one, but overall the whole project is still too ad-hoc for me to be comfortable utilizing HyperVM/Kloxo within a production environment.