[OSGeo-Standards] Input required from OSGeo Standards List Members

Bruce Bannerman bruce.bannerman.osgeo at gmail.com
Tue Sep 7 20:48:44 PDT 2021

Many thanks for your insightful comments Greg.

In particular, I think that your comments constraining trade mark licenses are appropriate and warrant further discussion.

Would you be able to expand on this point for those of us who are not so aware of the nuances?

Kind regards,


> On 8 Sep 2021, at 08:35, Greg Troxel <gdt at lexort.com> wrote:
> Tom Kralidis <tomkralidis at gmail.com> writes:
>> Greg: in terms of the draft, I've posted it to
>> https://wiki.osgeo.org/wiki/MoU_OGC/Review_2020/Draft
>> I have not PDF'd the draft in the case that we need to make changes.
> Thanks.  That wiki is a totally acceptable form for a draft, no
> advertising company and revision history is there.  This helps greatly
> as now I can read actual draft text (where draft is softer than
> proposed, but presumably after some perhaps minor changes it would be
> promoted with a call to comment on proposed).  Earlier, I could not
> figure out what was going on at all.
>> Note that this draft is targeted to update Exhibit A of the existing MOU.
>> The MOU "proper" will be drafted
>> once we agree on Exhibit A, at which point it will be put forth for
>> signatures.
> Presumably a proposed replacement MOU will be floated for comments as
> well.
> I sent some comments earlier about adding to the recitations the form of
> nonprofit and a 1-line description of the legal obligations of each
> party.  In the US, 501(c)3 and 501(c)6 have different duties.  That
> applies to the MOU not Appendix A.
> I'll second the comments about trademark licenses for conforming
> implementations for open source projects.  I realize there is some open
> source but commercial activity, and in particular proprietary dual
> licensing.  So it would be reasonable to extend the no-cost trademark
> license to open source projects which do not engage in proprietary dual
> licensing (to include AGPL-or-paid-license schemes and open core
> schemes).
> Greg

More information about the Standards mailing list