...

Hi, I just saw the list of pending packages for pharo-dev and I noted that there is a package made by me (OB-Algernon), it is a little package with few changes to algernon...

I if I might make a suggestion, in my left hand I have a database of names and initials of people who have signed up, in the right some code that looks at each method in the Pharo image, and tags any with a pragma if it can't figure out who owns it, or if the author isn't in the database. Run it before each release, post exceptions somewhere. Frankly any centralized initial, name registration going forward should capture an email address for later usage.... -- = = = ======================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Hi henrik (I should check that your fax arrived :) Ideally we should check that the guy sign the squeak MIT agreement but this is not clear where this information here to me Matthew? do you know? I could add that next to the list of ok committers. If the code is not MIT we do not look at it.

Speaking of which, I have a related question: The issues marked with "Check:", which are mostly Mantis bug fixes to Squeak, what's the procedure for those? 1. Use the code submitted as fixes as a starting point, and assume it's under a valid licence? 1a. If so, how do we submit as the contributer for unaltered methods the person who made the Squeak patch instead of the person checking it?

you merge with the most recent versions and publish the code in the inbox the method tags of the methods that did not change will be the one of the original author. After any modification is a modification so :)

1b. For derived/removed/extended changes made by the checker, who do we tag as the change author?

the guy doing them.

2. Read the bug descriptions and make corresponding changes to Pharo?

Cheers, Henry

Siterer "Esteban Lorenzano" <estebanlm@gmail.com>:

...

Hi, I just saw the list of pending packages for pharo-dev and I noted that there is a package made by me (OB-Algernon), it is a little package with few changes to algernon... but I have not signed the agreement (because I thought that none of my codes was included in pharo) So I ask: I have to sign the agreement? how? (In any case, I want to sign the agreement "just in case" -that will allow me to contribute to pharo, if I find the time-... is that possible?)

Cheers, Esteban

_______________________________________________ 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

thanks !!! Stef On Feb 28, 2009, at 2:58 AM, Matthew Fulmer wrote:

On Fri, Feb 27, 2009 at 10:38:43AM +0100, St?phane Ducasse wrote:

...

Ideally we should check that the guy sign the squeak MIT agreement but this is not clear where this information here to me Matthew? do you know?

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

-- Matthew Fulmer -- http://mtfulmer.wordpress.com/

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