We believe your work (MC, SUnit, Sake and Packages) is important enough for an integration into Pharo. We don't want to consider it as an external package.
I think that you should consider it as an external package, because it IS an external package. And it is used by code that is not Pharo code. I think in an open source environment where everyone is short on time and energy it is rude not to. Those who fixed it before, invested their time and energy contributing to a solution and to an ideal, knowing that others would fix it in future and do the same, and it would continue to be useful. I consider the fact that Pharo team ignored Edgars contribution to squeak as extremely rude for the same reason. When I took up the role of maintaining MC1.5, I did so with the express purpose of integrating all of the MC forks for the benefit of the whole community. If I had known that this idea was conceptually a waste of time then I wouldn't have bothered. I did it because I wanted overrides to actually work, and because I thought people would be enthusiastic for it to actually work. How on earth do you do anything practical with MC1? It drove me nuts. There should be one stream of development for MC, any more makes no sense. Again this is a philosophical choice, you either see the sense in it or you don't. The fact that you will not adopt the choice of treating MC as an external package for the benefit of all, and you continue to develop MC1 within pharo is in by book extremely insulting to the amount of effort that has been made on your behalf. I say again it is an external package, and the repo is OPEN, so use it, and if you find it isnt up to scratch (the tests arent), then join in and fix it. Instead you appear to be cocking a snook at everyones contributions, and going your own way. Perhaps you guys are still not understanding what LPF is for. If you want to change something to make it integrate well with Pharo but this would make it incompatible with other squeak, then we have a mechanism for backporting compatibility to older users. That mechanism is LPF, and S/P, thats what it is there for. If you maintain it as an external package.
But for that, Pharo's maintainers must have a look at the code and decide if it is safe to include. Why? As I said its not their package, its an external package. Your code is not of lower quality.
Thanks, my code quality really depends on sleep, there must be a correlation there.
Have a nice day and please continue working on these tools
I am just speaking up because I found code in Pier that was not compatible with Squeak, so I worry where this is all going. Keith