<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>Alas the OSI has been highly unresponsive and even hostile to the needs of the GOSS community.</div>
<div><br>
</div>
<div>We go around and around where GOSS lawyers state “we need X for compliance” and the response is “no you don’t, just use Apache”.</div>
<div><br>
</div>
<div>Even something as simple as CC0 can’t pass muster.</div>
<div><br>
</div>
<div>I agree with Larry...we should be allowing new license terms that meet current 201x community needs if it passes the OSD and not just block every attempt to change. The community can decide to adopt the license or not.</div>
<div><br>
</div>
<div>While “badgeware” might be a little annoying, agencies spend a significant amount on software and while it is arguable that it should be open source it isn’t unreasonable for agencies to insist that it’s clearly labeled as GOSS to be able to get future
funding for similar efforts and developers and agencies get credit for that work.</div>
<div><br>
</div>
<div>This is critically important for projects intended to be reused because while its a sometimes easy to get the initial GOSS public release done, fighting for continued funding for sustainment is a yearly battle. GOSS projects are typically underfunded
and community contributions are limited even when the product is being used. Just being able to fund technical and community organization is difficult much less new development.</div>
<div><br>
</div>
<div class="x_gw_quote" style="border-top:#b5c4df 1pt solid; padding-top:6px; font-size:14px">
<div><b>From: </b><span>Stephen Michael Kellat <<a href="mailto:smkellat@yahoo.com">smkellat@yahoo.com</a>></span></div>
<div><b>Date: </b><span>Tuesday, Dec 04, 2018, 8:24 PM</span></div>
<div><b>To: </b><span>license-discuss@lists.opensource.org <<a href="mailto:license-discuss@lists.opensource.org">license-discuss@lists.opensource.org</a>></span></div>
<div><b>Subject: </b><span>Re: [License-discuss] Open source license with obligation to display an attribution?</span></div>
</div>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On Tue, Dec 04, 2018 at 07:53:17PM +0000, Simon.Cox@csiro.au wrote:<br>
> [Apologies - I subscribed in digest mode so my response to your initial comments was not threaded, and this won't be either - fixed now.]<br>
> <br>
> <br>
> I guess what we are after is what you have referred to as a 'gesture'. Probably shouldn't have used the term 'obligation' in the subject line - I've been looking at the ODRL model, so am used to thinking in terms of permissions/restrictions/obligations.<br>
> <br>
> <br>
> I'm fully aware that - as with pretty much all IP law - enforcement is up to us, so there is always a scalability challenge. But mention within a license at least provides a starting point. In my initial post it appeared that I was jumping to a solution
prior to laying out the requirement, so I attempted to clarify the use-case in a follow-up message.<br>
> <br>
> <br>
> What would make our bosses happy (and thus willing to continue to support our contributions) would be: where a site uses our product as the primary basis for a publicly-available service, that a gesture of acknowledgment is publicly-visible. In non-legal
English something like "if you use this software as the primary basis for a service with a publicly visible UI, even if under a new skin, whatever, then please acknowledge us on or around your landing page. Our preference would be that you display [this logo]
with a link to [our webpage]".<br>
> <br>
> A standard-ish formulation would be nice.<br>
> <br>
> Simon J D Cox<br>
> Research Scientist<br>
> Land and Water<<a href="http://www.csiro.au/Organisation-Structure/Flagships/Land-and-Water">http://www.csiro.au/Organisation-Structure/Flagships/Land-and-Water</a>><br>
> CSIRO<br>
<br>
Since I am a fellow bureaucrat but for a different nation's federal government, I may suggest in blunter language my view of what Mr. Cox is suggesting.<br>
<br>
A concern with any government agency is ensuring that funding streams remain intact. My employing bureau in the US Treasury is stuck under interim funding as the Congress continues to fail to pass full year appropriations. That leads to the absurdity that
the sharp, pointy end of the spear has full legal appropriations to spend money while the actual tax collectors could wind up working without pay if something goes haywire in our specific legislation.<br>
<br>
Having open source output is a great thing for any organization. It can be difficult to quantify in a more tangible form when you are facing legislators and ranking agency officials who are considering your budget. Badgeware would conceptually be a way for
agency middle management to try to appease the political layer to better show what the results of all the spending happen to be. I'm not saying it is a good idea but it is a normal bureaucratic response.<br>
<br>
In this particular instance, since CSIRO is the Commonwealth Scientific and Industrial Research Organisation in Australia, consideration on-list would be best if we looked at examples from the DoD and NASA. CSIRO is a government agency that does good things.
I learned about them when I was in-region attached to the American Samoa Community College under the government of the Territory of American Samoa.<br>
<br>
Mr. Cox can confirm if this is a better restatement of the problem.<br>
<br>
Stephen Michael Kellat<br>
Ashtabula, Ohio<br>
<br>
Standard Disclaimer: <a href="http://skellat.freeshell.org/blog/pages/about-this-blog.html">
http://skellat.freeshell.org/blog/pages/about-this-blog.html</a><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
License-discuss mailing list<br>
License-discuss@lists.opensource.org<br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
</div>
</span></font>
</body>
</html>