Simone Giannecchini ha scritto: > I agree with you Andrea, > I would tackle obstacles once at a time, therefore I'd start with > including the licenses.txt in our release and then, once we will have > straightened out the PMC thing, I guess we will be able to tackle to > possibility of changing the license. > > Do you (anyone :-) ) think I should make a formal proposal for this step?
Mumble, just to include the licenses file? I guess a vote on the ml is enough. It would be good to ratify the community modules handling procedures thought. When one graduates a module, or when one modifies the dependencies of a module that is already in supported land, he should keep the licenses file is kept up to date. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
