Stéphane Ducasse wrote:
Yes we should do something.
Now the question is how to do something that we can actually implement.
I think that we should
- start to identify package of interest (quality/topics////)
- check their license status
- check the author and get access
- create an inbox
Stef
Stef,
speaking of licenses...I was thinking that for mcz files, we should have
a "directory" of each mcz file that contains the license statement for
the code in that _version_ of the mcz file. Most tools would end up
ignoring, but if we started including the license _in_ the mcz file,
then license status would be _much clearer_.
I also assume that a similar addition to mc2 files could/should be done....
Dale
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
