[Vm-dev] VM Automated builds update

Levente Uzonyi leves at elte.hu
Thu Mar 17 15:22:09 UTC 2011


On Thu, 17 Mar 2011, stephane ducasse wrote:

>
> Dear levente
>
>>>>>
>>> Actually, the fact that it is open and cloneable, means that if it doesn't meet your needs, you've got everything you need (except possibly the skills - not a dig, I don't know) to clone and extend it so that it does, and then contribute back your extensions.
>>
>> You only quoted the last sentence of Stephane's mail, read the rest of it to get my point.
>> Also take into account that there's an existing infrastructure used by VM developers and
>> the announcement of the new infrastructure didn't get a warm welcome from them.
>
> You can continue to bash us saying that we are nasty newbies. Right now we are building an **open** and welcoming architecture
> to sustain real open development VMs. This is ok that you do not like it, this is ok too that you bash us. If this helps you feel better
> I cannot do much about it.

Did I bash you? No, I said it's "nice and great".

>
> We want VMs to be maintained not just a small (tiny, microscopic) club of people that may be
> distracted/not willing to communicate/not have the time to build a vms. We want to make sure that if a guy has time to improve a vm he will not get frustrated because of millions of stupid details: this is what is called software engineering (vs. handcraft). Having a solid automated process is the key to progress in constraints resources. We want to minimize risk for business.

Great.

>
> Also we want to send a clear message to smart C, assembler people that lurk at our technology: they are welcome to participate and help
> because the architecture is open. They do not have to ask for a blessing (knights period is over). They can clone, hack and push/share changes and people can cherry pick the changes without having to have the permissions to publish.

That sounds good, but it may not be true.
Do you mean that there won't be official VM releases anymore?
Or if there will be, then who will decide which changes/features will be 
included in those?

>
> For example, igor sent a fix for the Windows vm for the semaphore input more than a year ago and it was never integrated.

Yeah, that's annoying, I had the same experience earlier.

> I'm happy that igor decided to stay in our community. Now we can ask ourselves (lot of people don't and after complain that smalltalk is a dead language) how many people came and left. Sharing is key.
>
> Now we will have a Windows VM built everyday (this is a fresh news ;) and more than 8 years I'm dreaming about that.
> And all the community will be able to use it, if they want. Nobody forces you to use our infrastructure but there will be a lot of advantages. It is free and maintained.

Great.

>
> We want to make sure that if people with ideas get in contact with our technology, their venture capitalists do not ask simple and naive questions such as
> 	- do you have a process
> 	- how do you control your quality
> 	- what happens if the Unix/windows guys breaks his legs or fly to mars
> and come to the conclusion that the risk is too high and ask to develop everything in Java.
>
> We are thinking and working hard to build a company around moose http://www.moosetechnology.org/ and we do not want to be forced to rewrite everything in Java as this happens a lot around us. May be you do not know everything at this level....

Which level?


Levente

>
> Stef


More information about the Vm-dev mailing list