Hi, Alison-
Out of deference to our host, and because there is a higher critical
mass of the right people, this discussion is best suited for the
license-discuss mailing list at OSI, not here:
http://projects.opensource.org/cgi-bin/mailman/listinfo/license-discuss
I'd encourage you to summarize the discussion to date here and send
your proposal there.
Thanks!
Luis (OSI license committee chair)
On Thu, Jun 6, 2013 at 11:20 PM, Alison Chaiken <alchaiken(a)gmail.com> wrote:
Thanks to Luis, Simon and Richard for sharing their thoughts about
the
Certificate of Origin. Codes of Conduct is perhaps another area
where OSI could usefully have a compliance specification or approval
process similar to its role with open-source licenses:
http://www.h-online.com/open/news/item/Python-Software-Foundation-publish...
Codes of Conduct and Certificates of Origin, like software licenses,
are areas where larger open-source projects want to adopt accepted
best practices, and smaller communities want to expend minimal effort.
Perhaps OSI could serve as a central source of all the policies
that such communities need to consider, not just software licenses.
Best wishes,
Alison
--
Alison Chaiken
(650) 279-5600 (cell) {she-devel.com,
exerciseforthereader.org}
Your body is governed by ancillary concerns like “stopping the
intolerable pain” and “not dying”. Those types of concerns have no
place in cycling.
-- Velominati,
www.velominati.com/look-pro/look-pro-part-vi-move-sur-la-plaque/
_______________________________________________
copyleft-next mailing list
copyleft-next(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/copyleft-next