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.
where is such a version?
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.
Me too especially because I committed in FS on squeak source and not in Pharo so that colin can commit. Because originally I worked on PharoTaskForces. I remember doing it on purpose to share our changes. I remember also having lost the comments I added to some methods and classes⦠apparently comments have no value in our world. So I reentered them. Now if colin does not care about we are doing I have no problem with that. In addition I do not see how we can control our life if we cannot publish on the repository of a part that should be central to us. Stef