Hi,
I will start on re-writting this methods:

Number>>reciprocal
Fraction class>>one
Fraction>>reciprocal
Float class>>one
Float>>reciprocal
Integer class>>one

All of this are almost trivial to re-write so I think it's a good start point. My plan is to first write a test case covering this, delete the old method (if present) and re-implement it.

I signed the License Agrement on Friday and sent an scanned copy to Stephane by e-mail (probably he still doesn't update the list).

Thanks,
Gabriel

On Sat, May 23, 2009 at 3:58 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi Gabriel,

On May 23, 2009, at 19:55 , Gabriel Cotelli wrote:

> Hi!
>
> There is somebody coordinating the re-write of non re-licensed
> methods?

As I started working on it last week, I can coordinate.

> I probably could re-write some of this methods but don't want to
> duplicate
> the effort :)

Great!

> Should I take the Pharo-Core image or the Pharo-Dev for this?

The core image.

I already fixed more than half of the methods. What is left can be
seen here:

http://code.google.com/p/pharo/wiki/ResultofRelicensing.

I suggest that whoever starts working on a set of methods announces it
on this mailing list. Like this we don't get a conflict. The easiest
thing is to produce a change set and then attach it to the issue: http://code.google.com/p/pharo/issues/detail?id=842

Thanks,
Adrian

BTW, I don't see you on the list of OK committers. Did you sign the
agreement? Else your changes will reappear on the list of non-clean
methods! ;)

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project