I can send in a licence agreement. Bryce On Sun, 2009-05-17 at 19:46 +0200, Adrian Lienhard wrote:
I merged in the additional authors of this repository and I updated the working list on the Wiki [1].
We currently have a total of 243 dirty methods.
Does anybody recognize an author on the list that could be contacted? (one method of Bryce Kampjes is on the list but should not (will fix in the next version)).
Cheers, Adrian
[1] http://code.google.com/p/pharo/wiki/ResultofRelicensing?ts=1242581939
On May 17, 2009, at 16:02 , Stéphane Ducasse wrote:
On May 17, 2
Well, this mail was not really helpful in getting there but I eventually managed (after an hour or two :().
Ok sorry This is a copy of the mail I got from matthew and it worked for me So I thought it was precise enough.
So that others can produce the audit list more easily I added instructions at http://code.google.com/p/pharo/wiki/LicenseCleanEffort?ts=1242566822
Yes I did that. Now you should pay attention that matthew indicated that there are more recent author list available at:
The most up-to-date list of ok contributors is at http://www.squeaksource.com/311/MethodAuthorship-kph.17.mcz See the class-side methods in Authorship, category data
As mentioned there, I created a new version of Methodauthorships and stored it in the PharoTaskForces repository. I added all authors that were previously missing but that signed the Pharo license, or that Stef identified to be his own changes but with wrong initials.
With this I produced an updated list and added it to:
http://code.google.com/p/pharo/wiki/ResultofRelicensing?ts=1242567420
So now we can start working and we need *your* help!
Nicolas did a first step by implementing a new ScaledDecimal. Various stuff can be removed (e.g., the ScaleMorph).
The following may help: - in the zip file (see instructions mentioned above) there are changesets from EToys - http://bugs.squeak.org/view.php?id=6989
Cheers, Adrian
Stef
On May 16, 2009, at 6:01 PM, Adrian Lienhard wrote:
Hi Stef,
How did you produce the list of methods you put on the wiki page?
It seems this will be some work, but its certainly doable. Stuff like ScaleMorph, BlobMorph, SkipList, and ScaledDecimal do not need to be in the core anyway. We can extract them into external packages.
I suggest that when we have an up to date list that takes Pharaoers into account, we start working through it and tag each method that is fixed. Changesets can be gathered in a single task in the tracker.
Adrian
On May 16, 2009, at 09:22 , Stéphane Ducasse wrote:
Hi all
I'm going over the list of authors that did not sign and will produce a list of actions.
http://code.google.com/p/pharo/wiki/ResultofRelicensing
We will have probably to update the authorlist with the one of pharo.
Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project