> On 11 Jan 2019, at 08:45, Esteban Lorenzano <[email protected]> wrote:
> 
> You know? since we are sharing frustrations, I have to say: we already had 
> that process (which was the old pharo-vm project). In that project, for each 
> version of vmmaker we were loading it, generating a vm and running pharo 
> tests there (since there are no vm-specific tests, this was working at least 
> to test things were not broken). 
> And… we were told this was not good and that we needed to submit to the 
> canonical way of building the vm, which we did to not split more the 
> community. 
> 
> In the process we lost all our validation process. 
> 
> Now we are told that we remove things without caring. 
> But we care, and we spent a lot of time and effort putting in place 
> mechanisms to allow things to continue moving.
> And then we needed to throw it away.
> 
> Maybe now we have a new attempt and possibility of improving, but honestly I 
> already spent one year of the work this community pays me to do to improve 
> things and then it was wasted work. 
> I do not thing I want to spend another “sabatical” year like that.
> 
> Esteban
> 
> Ps: I’m sorry for the frustration rant, but when I see this things emerge I 
> become very-very sad.

One can only image, dream, of a world where VM development decided years ago to 
step into the future with a better process, better code management, modern 
tools, actual CI, tests, open process for real, welcoming more contributors, 
catering for its largest user base.

We live in an ever changing world, resisting change is not the solution.

Open source is about embracing and nurturing community, and yes that is 
sometimes messy, but totally worth it.



Reply via email to