On 2012-02-15, at 17:09, Lukas Renggli wrote:
Regarding the refactoring engine: I will continue to maintain the code in the spirit of the original authors in my own repository.
Of course Pharo is free to fork any open-souce repository, but then the maintainers should not complain if they end up with outdated and broken code nobody has time to maintain (as it recently happend with the one-click builder).
well the one click thingy should just be a jenkins job on our build server, that would be fine.
Furthermore, it would be appreciated if the projects were renamed and and would use a different namespace. For example, I cannot load any package that depends on the official version of FS.
bah, basically this shows that squeaksources sucks at comunity based multi version code :D to bad that we're not yet on github for that reason... I don't feel like changing the namespaces either since that makes including updates and changes even harder...
A quick comparison shows that the Pharo fork is based on outdated code and has some methods of the public API renamed.
where's the other code located? I would like to check that.
Lukas
On Wednesday, February 15, 2012, Camillo Bruni <camillobruni@gmail.com> wrote:
If the corresponding project admins would agree it would be cool to move the development to ss3 on gemstone of the following projects I ported so far:
- Citezen http://ss3.gemstone.com/ss/citezen - FSFilesystem http://ss3.gemstone.com/ss/fs - FSGit http://ss3.gemstone.com/ss/fs-git - PetitMarkdown http://www.squeaksource.com/PetitMarkdown - PharoRB http://ss3.gemstone.com/ss/rb-pharo - Refactoring Engine http://ss3.gemstone.com/ss/rb - Soup http://ss3.gemstone.com/ss/soup - XMLSupport http://ss3.gemstone.com/ss/xmlsupport
I tried to add people from the old projects as admins Please let me know
-- Lukas Renggli (mobile) http://www.lukas-renggli.ch