If you can come up with widely accepted equivalents for Codes of Conduct and Certification of Origin then that might fall within OSI's remit, but I doubt we will want to "bless" any one formulation.
S.
On Friday, June 7, 2013, Alison Chaiken 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-publishes-Code-of-Conduct-1883853.html
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/