<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Hi all,<br></div><div><br></div><div>After further discussions at FOSS4G 2023, and hearing from various people and projects who are using mappyfile I'd like to resume the application to become an OSGeo Community project. <br></div><div>I think I've covered all the requirements previously, but as this was a few years ago there may be new requirements for an application?<br></div><div><br></div><div>Details are in the email chain, but in summary:<br></div><div><br></div><div> - mappyfile is a Python parser for working with MapServer MapFiles<br></div><div> - User docs at <a href="https://mappyfile.readthedocs.io/en/latest/">https://mappyfile.readthedocs.io/en/latest/</a><br></div><div> - ReadMe at <a href="https://github.com/geographika/mappyfile/blob/master/README.rst">https://github.com/geographika/mappyfile/blob/master/README.rst</a><br></div><div> - Is included in OSGeoLive (see [1])<br></div><div> - Is included in ubuntugis-stable (package archive) [2]<br></div><div> - I've created a draft project page on <a href="https://www.osgeo.org/">https://www.osgeo.org/</a> - see [3]<br></div><div><br></div><div>[1] <a href="https://github.com/OSGeo/OSGeoLive/commit/2df427d7744fc2adc0e9889af7a8f6c80dd9c11b">https://github.com/OSGeo/OSGeoLive/commit/2df427d7744fc2adc0e9889af7a8f6c80dd9c11b</a><br></div><div>[2] <a href="https://launchpad.net/~ubuntugis/+archive/ubuntu/ppa">https://launchpad.net/~ubuntugis/+archive/ubuntu/ppa</a><br></div><div>[3] <a href="https://www.osgeo.org/?post_type=project&p=12880&preview=true">https://www.osgeo.org/?post_type=project&p=12880&preview=true</a><br></div><div><br></div><div>I look forward to hearing from the committee,<br></div><div><br></div><div>Seth<br></div><div><br></div><div id="sig62266145"><div class="signature">--<br></div><div class="signature">web:<a href="https://geographika.net">https://geographika.net</a> & <a href="https://mapserverstudio.net">https://mapserverstudio.net</a><br></div><div class="signature">twitter: @geographika<br></div></div><div><br></div><div>On Wed, Sep 9, 2020, at 3:27 PM, Jody Garnett wrote:<br></div><blockquote type="cite" id="qt" style=""><div dir="ltr"><div dir="ltr"><div>Looks fine, and the real benefit is you are aware of and are respecting the open source licenses.<br></div><div>In the future you may find it advantageous to use "Copyright (c) 2020 Seth Girvin and others" for files like this.<br></div><div><br></div><div>If that is the last thing can we resume reviewing mappyfile project for the osgeo community program?<br></div><div><div><div dir="ltr" class="qt-gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>--<br></div><div>Jody Garnett<br></div></div></div></div></div></div><div><br></div></div></div></div><div><br></div><div class="qt-gmail_quote"><div dir="ltr" class="qt-gmail_attr">On Wed, 9 Sep 2020 at 04:42, Seth G <<a href="mailto:sethg@geographika.co.uk">sethg@geographika.co.uk</a>> wrote:<br></div><blockquote class="qt-gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div><u></u><br></div><div><div>Hi Jody,<br></div><div><br></div><div>Thanks for getting back on this.<br></div><div>I added attribution as best I could to the top of the file in question - <a href="https://github.com/geographika/mappyfile/blob/master/mappyfile/ordereddict.py#L3" target="_blank">https://github.com/geographika/mappyfile/blob/master/mappyfile/ordereddict.py#L3</a><br></div><div>Not sure if there is much else I can do beyond this?<br></div><div><br></div><div>Seth<br></div><div><br></div><div id="qt-gmail-m_-3798368542974108442sig62266145"><div>--<br></div><div>web:<a href="http://geographika.co.uk" target="_blank">http://geographika.co.uk</a><br></div><div>twitter: @geographika<br></div></div><div><br></div><div><br></div><div>On Wed, Sep 9, 2020, at 7:22 AM, Jody Garnett wrote:<br></div><blockquote type="cite" id="qt-gmail-m_-3798368542974108442qt"><div dir="ltr"><div>Did you ever finish sorting out your code providence review?<br></div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>--<br></div><div>Jody Garnett<br></div></div></div></div></div></div><div><br></div></div><div><br></div><div><div dir="ltr">On Fri, 14 Feb 2020 at 14:33, Seth G <<a href="mailto:sethg@geographika.co.uk" target="_blank">sethg@geographika.co.uk</a>> wrote:<br></div><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div><u></u><br></div><div><div>Hi Jody,<br></div><div><br></div><div>Thanks for the feedback.<br></div><div><br></div><ul><li>I've updated the logo based on the provided image size, and with a white background. I'm not sure it looks better with the white background, but admittedly it isn't much of a logo!<br></li><li>I tried the laptop border with a different screenshot, but it was too small to be legible, so I've left as is.<br></li><li>I think the Facebook row was added by default? I've removed and added my Twitter account, which I use to mention new releases of the project (although it is not a project specific account - so not sure if it should be included?).<br></li></ul><div><br></div><div>With regard to copyright I noticed a few different styles:<br></div><div><br></div><div>- Short copyright header e.g. in pywps: <a href="https://github.com/geopython/pywps/blob/master/pywps/configuration.py" target="_blank">https://github.com/geopython/pywps/blob/master/pywps/configuration.py</a><br></div><div>- Full copyright header: e.g. in pygeoapi: <a href="https://github.com/geopython/pygeoapi/blob/master/tests/load_es_data.py" target="_blank">https://github.com/geopython/pygeoapi/blob/master/tests/load_es_data.py</a><br></div><div>- No copyright header: e.g. in Shapely <a href="https://github.com/Toblerity/Shapely/blob/master/shapely/coords.py" target="_blank">https://github.com/Toblerity/Shapely/blob/master/shapely/coords.py</a><br></div><div><br></div><div>I went with the full header (a few of the source files have joint authorship), but only on the sourcecode *.py files, not on all the test files. Does join authorship imply joint copyright? Or if the second author agrees can it be a single copyright?<br></div><div><br></div><div>While reviewing the authorship I have run into something I'm unsure how to best deal with. The file <a href="https://github.com/geographika/mappyfile/blob/master/mappyfile/ordereddict.py" target="_blank">https://github.com/geographika/mappyfile/blob/master/mappyfile/ordereddict.py</a> is based on an implementation of an OrderedDict from StackOverflow which is in turn based on another piece of code on the web. I found the authors names and added them to the header (and already had links to the implementations). The code has since been modified by myself a few times, and is a fairly standard way of implementing OrderedDicts, but I did use their approach as a starting point.<br></div><div>Is there anything I have to do in this case?<br></div><div><br></div><div>Regards,<br></div><div><br></div><div>Seth<br></div><div><br></div><div><br></div><div id="qt-gmail-m_-3798368542974108442qt-gmail-m_1984955496549441920sig62266145"><div>--<br></div><div>web:<a href="http://geographika.co.uk" target="_blank">http://geographika.co.uk</a><br></div><div>twitter: @geographika<br></div></div><div><br></div><div><br></div><div>On Fri, Feb 14, 2020, at 1:07 PM, Jody Garnett wrote:<br></div><blockquote type="cite" id="qt-gmail-m_-3798368542974108442qt-gmail-m_1984955496549441920qt"><div dir="ltr"><div>Very quickly, thanks for your email!<br></div><div><br></div><div>We want to make sure you have checked you have the permission to distribute each file (either wrote it yourself or a contributor agreed to make it open source). We have found in our research that having a copyright header is not a legal requirement, but it is a smart thing to do socially (for folks that discover your code via searching).<br></div><div><br></div><div>Your project page is one of the best first attempts we have seen here, some feedback:<br></div><div>- please make sure that your logo is placed on a white background (the sample image size is <a href="https://www.osgeo.org/wp-content/uploads/template_tile.png" target="_blank">here</a>). Without this it looks bad when displayed in a list or at the top of the page on a green background.<br></div><div>- your diagram is very interesting, but I am not sure if it is a screen snap or not? We have a border <a href="https://github.com/OSGeo/osgeo/tree/master/marketing/photos" target="_blank">here</a> to provide a laptop frame<br></div><div>- you have a link to Facebook, but it does not go anywhere (but perhaps that is an issue with the preview)<br></div><div><div><br></div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>--<br></div><div>Jody Garnett<br></div></div></div></div></div></div><div><br></div></div></div><div><br></div><div><div dir="ltr">On Fri, 14 Feb 2020 at 00:11, Seth G <<a href="mailto:sethg@geographika.co.uk" target="_blank">sethg@geographika.co.uk</a>> wrote:<br></div><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div>Hi all,<br></div><div><br></div><div>I'd like to apply for OSGeo Community Project status for the mappyfile project. mappyfile is a Python library to create, parse, modify, and format MapServer Mapfiles.<br></div><div><br></div><div>It has been around for 3 years, with continuous development and contributions, and is used as a library in several public projects (see [1]), and many more non-public projects. It was first presented at FOSS4G-Europe (Paris) in 2017 (see slides at [2]). I've gone through the criteria listed on the OSGeo site [3] and added links and details below:<br></div><div><br></div><div>- Be geospatial<br></div><div><br></div><div> - mappyfile is a Python parser for working with MapServer MapFiles<br></div><div> - User docs at <a rel="noreferrer" href="https://mappyfile.readthedocs.io/en/latest/" target="_blank">https://mappyfile.readthedocs.io/en/latest/</a><br></div><div> - ReadMe at <a rel="noreferrer" href="https://github.com/geographika/mappyfile/blob/master/README.rst" target="_blank">https://github.com/geographika/mappyfile/blob/master/README.rst</a><br></div><div> - Is included in OSGeoLive (see [4])<br></div><div> - Is included in ubuntugis-stable (package archive) [5]<br></div><div> - I've created a draft project page on <a rel="noreferrer" href="https://www.osgeo.org/" target="_blank">https://www.osgeo.org/</a> - see [6]<br></div><div><br></div><div>- Have a free licence or an open source licence<br></div><div><br></div><div> - Uses the MIT Licence: <a rel="noreferrer" href="https://github.com/geographika/mappyfile/blob/master/LICENSE" target="_blank">https://github.com/geographika/mappyfile/blob/master/LICENSE</a><br></div><div> - I'm unsure if each individual .py file requires a copyright header<br></div><div><br></div><div>- Welcome participation and new contributors.<br></div><div><br></div><div> - Has a small community of contributors see: <a rel="noreferrer" href="https://github.com/geographika/mappyfile/graphs/contributors" target="_blank">https://github.com/geographika/mappyfile/graphs/contributors</a><br></div><div> - Has a contribution policy: <a rel="noreferrer" href="https://github.com/geographika/mappyfile/blob/master/CONTRIBUTING.md" target="_blank">https://github.com/geographika/mappyfile/blob/master/CONTRIBUTING.md</a><br></div><div> - Has a code of conduct: <a rel="noreferrer" href="https://github.com/geographika/mappyfile/blob/master/code-of-conduct.md" target="_blank">https://github.com/geographika/mappyfile/blob/master/code-of-conduct.md</a><br></div><div><br></div><div>I'm happy to answer any questions on the project, and please let me know what other criteria need to be met to apply for community project status (as noted above I'm unsure if each individual file requires a copyright header).<br></div><div><br></div><div>Regards,<br></div><div><br></div><div>Seth<br></div><div><br></div><div>[1] <a rel="noreferrer" href="https://github.com/geographika/mappyfile/network/dependents" target="_blank">https://github.com/geographika/mappyfile/network/dependents</a><br></div><div>[2] <a rel="noreferrer" href="https://github.com/geographika/mappyfile/blob/master/docs/_static/foss4ge2017_mappyfile_sgirvin.pdf" target="_blank">https://github.com/geographika/mappyfile/blob/master/docs/_static/foss4ge2017_mappyfile_sgirvin.pdf</a><br></div><div>[3] <a rel="noreferrer" href="https://wiki.osgeo.org/wiki/OSGeo_Community_Projects#Qualifying_As_An_OSGeo_Community_Project" target="_blank">https://wiki.osgeo.org/wiki/OSGeo_Community_Projects#Qualifying_As_An_OSGeo_Community_Project</a><br></div><div>[4] <a rel="noreferrer" href="https://github.com/OSGeo/OSGeoLive/commit/2df427d7744fc2adc0e9889af7a8f6c80dd9c11b" target="_blank">https://github.com/OSGeo/OSGeoLive/commit/2df427d7744fc2adc0e9889af7a8f6c80dd9c11b</a><br></div><div>[5] <a rel="noreferrer" href="https://launchpad.net/~ubuntugis/+archive/ubuntu/ppa" target="_blank">https://launchpad.net/~ubuntugis/+archive/ubuntu/ppa</a><br></div><div>[6] <a rel="noreferrer" href="https://www.osgeo.org/?post_type=project&p=12880&preview=true" target="_blank">https://www.osgeo.org/?post_type=project&p=12880&preview=true</a><br></div><div><br></div><div><br></div><div>--<br></div><div>web:<a rel="noreferrer" href="http://geographika.co.uk" target="_blank">http://geographika.co.uk</a><br></div><div>twitter: @geographika<br></div><div>_______________________________________________<br></div><div>Incubator mailing list<br></div><div><a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a><br></div><div><a rel="noreferrer" href="https://lists.osgeo.org/mailman/listinfo/incubator" target="_blank">https://lists.osgeo.org/mailman/listinfo/incubator</a><br></div></blockquote></div></blockquote><div><br></div></div></blockquote></div></blockquote><div><br></div></div></blockquote></div></blockquote><div><br></div></body></html>