> I also applied all of yoshiki's etoys changes to 3.10.2. The > algorithm that Yoshiki seemed to follow when cleaning etoys is: > - If the method can be easily deleted, delete it > - Otherwise, use the historical image [1] to revert to the > latest version before the problematic author > - Fix any bugs this causes > > I think we can use the same procedure. Perhaps Yoshiki will > comment.
Perhaps^^; Does Pharo have ScaledDecimal and it is used? If so, that would be the biggest piece that would be removed. There wouldn't be any serious bugs that would cause major trouble otherwise. > On Wed, Apr 22, 2009 at 11:10:12AM +0200, stephane ducasse wrote: > > I need your guidance for the MIT conversion effort of Pharo > > Do you have some cycles to help me and telling me how to proceed? > > I'm on holidays (so working remotely so I may allocate some time on > > that). > > I can help you after school gets out in a week. I need to > do a quick count of how many lines of code need to be fixed in > squeak for submission to SFLC. I can do the same for Pharo. I > don't know how strenuous you want to be in your license > conversion. What is the reason for Pharo to go with SFLC? > You should chat with Randal Schwartz about what you need to > decide before you can start relicensing, and what you need to > document in case your relicense needs to be reviewed in the > future. Yoshiki and Juan did not do this and thus we have no > evidence yet that Yoshiki's relicense is strong enough. There will be no such evidence. There will be no evidence for a statement like "there is no white crow". -- Yoshiki _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
