Expanding the scope of OSI to be an "open source best practices" clearinghouse

[Alison Chaiken]

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
[phone]  (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/

[Simon Phipps]

The key to the success of the OSD was defining a meta-standard against
which (relatively) objective qualification could be applied. We attempted
the same thing with open standards and found it much harder. although we
did devise the OSR http://opensource.org/osr which has proved fairly
popular.

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-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
>  [phone]  (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/
>  

-- 
*Simon Phipps*  http://webmink.com
*Meshed Insights Ltd *
*Office:* [phone] *or* [phone]
*Mobile*:  [phone]*
*

[Luis Villa]

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&gt; 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
>  [phone]  (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

[Richard Fontana]

On Sat, Jun 08, 2013 at 08:12:33AM -0700, Luis Villa wrote:
>  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. 
+1