> I think you have a full right to decide what [not] to include in Pharo. > Keith mentioned that you making many changes to many different parts > of system , which supposed to be maintained by original authour(s) or > currently active team(s), without giving a feedback or credit or > consulting with them about promoting such changes. > Okay, i think you're not stepping into other's domain.. it would be rude.. > But its going to be tricky, when you change the package X (not > maintained by anyone), from which depends a lot of work, which doing > in parallel by other team for package Y, which depends on X. > Here lies the problem, which can be solved by communicating with > people. Of course it requires the good will of both sides :) > >
Igor, I am not understanding your logic. You appear to be saying that if package X has got current maintainers, then it is not rude to make your own version of Package X. And that if you fork a package that has no maintainer then you will be in trouble. I am saying the opposite - that if you fork a package that has got current maintainers, you a) insult the maintainers, b) you undermine the progress that they may have made, c) you undermine any efforts thay have made to build a team and communication around that project. d) you prevent future progress by the existing team e) you make extra work for the exisiting team because you dont communicate with them and they are forced to play catch up to you all the time f) you send out the message that volunteering to maintain any part of the kernel is a hapless task, and will ultimately be a waste of time and effort. Keith _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
