sounds great! sebastian
o/ > On 01/10/2014, at 12:41, Esteban Lorenzano <esteba...@gmail.com> wrote: > > Hi, > > As you might or might not seen, we are moving Pharo into a different > architecture: From a monolitic "one-image-is-all", we are (very slowly) going > into an small kernel and a set of sub-projects who will populate the image > and provide all required features. > In general, the idea is that the final state, what we call "Pharo" will stay > as an unity with all the tools/frameworks/libraries you already know and > love, but the building process will be completely different, allowing us to > better manage the release process and allowing users to build their own > versions of specific pharos (I can imagine, for example, morphic-less pharos > used in server applications, etc.). > > Well... this direction we are taking just made his first change, that can > annoy a bit the community, until we find a new equillibrium :) > Until now, most changes, bugfixes, etc. were contributed using old know > SLICES, who make a good job in this monilitic approach. > And starting now, there are certain subprojects that cannot be managed like > that anymore and has to be managed through regular contributions to their > repositories. Then, responsible guys from those projects will submit an > "Integration request" (something like a pull request), when they consider is > necesary an update to Pharo. > > Those projects are, for now: > > - Zinc (responsible is Sven) > - GTools (responsibles are Doru and Andrei) > - OSWindow (responsible is Igor) > > We hope, with time, to move all non-kernel code into their respective > sub-projects, all with their responsibles, but for now, we started with this > ones :) > > (I hope this mail is understandable... I feel I'm being super confusing :P) > > cheers, > Esteban
