Basketball Star Slot

2020-07-092020-07-09 by Interpreting the Purpose of the Open Usage Commons Foundation

Yesterday, .

The Open Usage Commons (OUC) foundation announced itself

It is a non-profit which wants to ensure free and fair trademark use of the open source projects under its guidance.

My Twitter feed was quick to denounce the OUC as a vanity foundation

It certainly is not.
A vanity foundation serves to aggrandize its creators, and a name like “The Great Company Open Source Foundation” would then be apt.
This is not the case here.

Rather the OUC makes specific statements about trademark enforcement

so it has a purpose that is not vanity.
Just what is that purpose, and why did existing foundations not fit the bill.

Lets take the second question first: Why did Google

as the owner-steward of the three open source projects given to the foundation (Istio, Angular, Gerrit) not transfer them to the Apache Software Foundation.
I can only speculate, but if trademark enforcement was their goal, .

Google obviously felt existing foundations were too weak for this

According to the current FAQ, the OUC’s mission is to “[…] help projects assert and manage their project identity […] through programs like conformance testing and trademark management.”Open Usage Commons FAQ, 2020-07-09 There it is, the foundations’s purpose, which in its own words makes it “something wildely new in open source.” I admit I haven’t seen “conformance testing” in any other open source foundation’s bylaws, .

And so it depends on how serious the OUC is about this

In the extreme case, it will mean something like a full certification program with criteria design, consultants/trainers, and assessors to certify conformance that allows you to use the trademark to stay in business.
At this stage, it is too early to predict what is coming.
However, here are the two extreme interpretation s, to map out the possible future.
The benign interpretation is that Google wanted to do right by the open source projects and their communities.
In particular Istio contributors and users were getting antsy about being at Google’s mercy re: trademark use.
To give them peace of mind and to grow the ecosystem.

Google transfered the trademark to a neutral authority

the OUC, which creates clear and fair rules on when and how to use the trademark.
Everything is peachy.
The devil’s advocate interpretation is that the OUC’s conformance testing is a tool for keeping competitors away from the open source projects.
The heat is on Istio, a commercially relevant service mesh .
Google wants Istio to be even more popular, so that it can benefit from the project the open source way: Cost savings, innovation, recruiting, standardization , etc.
At the same time, .

Google and its OUC partners may not want AWS or Microsoft to use it

Previous attempts by companies to keep competitors from using their open source projects utilized license shenanigans and created a shitstorm that is still in everyone’s ear.
Maybe using the threat of complex trademark conformance testing and auditing does the same job.
What if a conformance requirement is at odds with how a cloud provider built its architecture.
What if an audit can lead to unwanted disclosures.
This way, those who define the conformance criteria can make life difficult for those who they want it to be difficult for.
Knowing this, the competitor will stay away because uncertainty is costly.

That’s it: The two extremes of the possible future behavior of the OUC

The future is bright, one way or the other.
Be safe and healthy.
Software Industry, 1.3 Open Source Foundations One Reply to “Interpreting the Purpose of the Open Usage Commons Foundation”.
Leave a Reply Cancel reply.
The German Corona Warn App, a Legally Defective Product.
Why Istio Matters to Google Subscribe Categories Select Category 1.
Software Industry  (258)    1.1 Industry (General)  (50)    1.2 Open Source (Industry)  (129)    1.3 Open Source Foundations  (22)    1.4 Commercial Open Source  (39)    1.5 Software Startups  (18) 2.
Building Products  (106)    2.1 Engineering  (19)    2.2 Agile Methods  (7)    2.3 Open Source (Building)  (28)    2.4 Inner Source  (29)    2.5 Architecture and Design  (16)    2.6 Product Management  (11) 3.
Research and Teaching  (106)    3.1 Research (General)  (65)    3.2 Research Methods  (4)    3.3 Teaching (General)  (8)    3.4 The AMOS Project  (25)    3.5 Life of a Professor  (4) 4.
Society-at-large  (42)    4.1 Society (General)  (19)    4.2 Open Source (Society)  (9)    4.3 Wikis and Wikipedia  (14) 5.

Personal Matters  (18)    5.1 Personal (General)  (9)    5.2 Technology  (9)

Archives Select Month September 2020 August 2020 July 2020 June 2020 May 2020 April 2020 March 2020 February 2020 January 2020 December 2019 November 2019 October 2019 September 2019 August 2019 July 2019 June 2019 May 2019 April 2019 March 2019 February 2019 January 2019 December 2018 November 2018 October 2018 September 2018 August 2018 July 2018 June 2018 May 2018 April 2018 February 2018 January 2018 November 2017 October 2017 September 2017 May 2017 April 2017 March 2017 February 2017 December 2016 November 2016 October 2016 September 2016 August 2016 July 2016 June 2016 May 2016 April 2016 March 2016 February 2016 January 2016 December 2015 November 2015 October 2015 September 2015 August 2015 July 2015 May 2015 April 2015 March 2015 February 2015 January 2015 December 2014 November 2014 October 2014 September 2014 August 2014 July 2014 June 2014 May 2014 April 2014 March 2014 February 2014 January 2014 December 2013 November 2013 October 2013 September 2013 August 2013 June 2013 May 2013 April 2013 March 2013 February 2013 January 2013 December 2012 October 2012 August 2012 May 2012 March 2012 February 2012 January 2012 December 2011 November 2011 August 2011 July 2011 June 2011 May 2011 March 2011 February 2011 January 2011 December 2010 November 2010 October 2010 September 2010 August 2010 June 2010 May 2010 April 2010 March 2010 February 2010 January 2010 November 2009 October 2009 September 2009 August 2009 July 2009 June 2009 May 2009 April 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June.

Trả lời

Email của bạn sẽ không được hiển thị công khai. Các trường bắt buộc được đánh dấu *