On 12 April 2017 at 14:08, Esteban Lorenzano <esteba...@gmail.com> wrote:
> It is in my TODO list. > … along with other milliards of things with more priority ;) > > I will welcome any Pull Request, in any area but specially on that one :D > I can potentially make some time to help out with VM maintenance. I have already volunteered to maintain the NixOS packaging for Pharo and that is what leads me here in the first place, I will need to successfully build the VM myself before I can help anybody else though :). Before committing time I would like to understand the situation a little bit better. How come nobody in the Pharo community sees it as a priority to make a VM source release that is compatible with the current image version (5.0)? I had imagined that a compatible VM would be released at the same time as the image. So I am obviously missing some point about why other people see the VM source release as such a low priority. Is it just that everybody is running zeroconf binaries distributed by Jenkins and that I am one of very few people who wants to build from source (without bootstrapping from another Pharo)? Context: I am a relative newbie who wants to develop an application based on Pharo. It's much harder than I expected to get started!
