On Aug 7, 2014, at 9:47 AM, stepharo <stepharo@free.fr> wrote:
Itâs up to the community to be involved with the tools they love and to submit patches, and youâre totally right to remind everyone that itâs up to us to improve Pharo if we want to keep it alive, but itâs up to the core team to make sure that itâs easy for us to do so, and I think that Pharoâs not doing terribly well on that front right now.
We add a description on the old web site but he got lost. Now in a nutshell, to submit a fix
- donwload latest image (there is a script on download) - do a fix for a giving bug - publish a slice press (+ slice) in MC, add the dirty packages - publish it in the inbox (click on inbox and press save) - take a fresh image. - reload it and check that it fixes the problem (open MC and click on inbox + open).
Does it help? Was it so complex?
Yep, it helps. The issue isnât that it was complex; itâs that it was undocumented. The new links are helpful.