<div dir="ltr"><div dir="ltr"><div dir="ltr">Jan / Cameron:<div><br></div><div>Checking in briefly, sorry I have been overset with activities lately and hope everyone is staying well. The incubation checklist list available for other members of the committee to work through also; I am quite found of the GeoStyler project and it is an impressive and useful project.</div><div><br></div><div>Indeed because of my (small) contributions it may be best of a mother committee member has a look?</div><div><br></div><div><ol style="margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(37,37,37)"><li style="margin-bottom:0.1em"><font face="arial, sans-serif">Be geospatial </font><ul style="list-style-type:disc;margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em"><font face="arial, sans-serif">Confirm by checking README or project description</font></li><li style="margin-bottom:0.1em"><font face="arial, sans-serif">project page on the osgeo website</font></li><li style="margin-bottom:0.1em"><font face="arial, sans-serif">We ask projects have some user documentation, for example an OSGeo Live quickstart</font></li></ul></li><li style="margin-bottom:0.1em"><font face="arial, sans-serif">Have a free license or an open source license.</font><ul style="list-style-type:disc;margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em"><font face="arial, sans-serif">The license must be OSI approved</font></li><li style="margin-bottom:0.1em"><font face="arial, sans-serif">We ask that the project team check the file headers and double check the license has been appropriately applied</font></li></ul></li><li style="margin-bottom:0.1em"><font face="arial, sans-serif">Welcome participation and new contributors.</font><ul style="list-style-type:disc;margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em"><font face="arial, sans-serif">We look for a clear contribution policy</font></li><li style="margin-bottom:0.1em"><font face="arial, sans-serif">We ask that the project demonstrate collaboration, perhaps with a history of bug report or pull requests</font></li><li style="margin-bottom:0.1em"><font face="arial, sans-serif">Projects are required to have a code of conduct</font></li></ul></li></ol></div><div><br></div><div>Reference: <a href="https://wiki.osgeo.org/wiki/OSGeo_Community_Projects">https://wiki.osgeo.org/wiki/OSGeo_Community_Projects</a> </div><div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>-- </div><div>Jody Garnett</div></div></div></div></div></div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 24 Mar 2020 at 15:18, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div>
<p>Hi Jan,</p>
<p>Sorry for the delayed response. I'm hoping one of the more active
members of the incubation committee would speak up.</p>
<p>Assuming GeoStyler fits Jody's checklist (which it looks like it
does), I'm strongly in favour of including GeoStyler as an OSGeo
community project.<br>
</p>
<p>From what I can see, GeoStyler addresses a pain point that many
of us in the OSGeo community have faced at some point, and I'd
love to see it promoted and grow. In particular, I'd love to see
GeoStyler included in OSGeoLive, <a href="http://live.osgeo.org" target="_blank">http://live.osgeo.org</a></p>
<p>The application process here:<a href="https://trac.osgeo.org/osgeolive/wiki/Projects/How_to_apply" target="_blank">
https://trac.osgeo.org/osgeolive/wiki/Projects/How_to_apply</a>.
Would you be interested in joining OSGeoLive? (Note the ongoing
commitment required in questions).<br>
</p>
<p>Cheers, Cameron<br>
</p>
<p><br>
</p>
<div>On 19/3/20 3:19 am, Jan Suleiman wrote:<br>
</div>
<blockquote type="cite">Dear
Incubation Committee,
<br>
<br>
we would like to introduce our Open Source project "GeoStyler".
<br>
<br>
GeoStyler is an Open Source JavaScript library that enables users
to style maps with the help of a Graphical User Interface.
<br>
The goal of GeoStyler is a universally applicable GUI that works
with any given style format; may it be SLD, QML, OpenLayers, etc.
<br>
<br>
In order to achieve that goal, we follow a plugin-approach where
so called "style-parsers" can be plugged into the UI. These style
parsers work as a conversion tool to bidirectionally convert
between any external style and our internal style format.
<br>
As a positive side effect, we are able to convert from one
external format to another one (e.g. from QML to SLD, etc.).
<br>
<br>
The GUI library is written in react but also provides browser
builds to enable its usage outside of any react application.
<br>
<br>
With thanks to currently 16 different contributors, we
successfully maintain 15 repositories in our GitHub organisation,
including the UI library and documentation, different
style-parsers, data-parsers, type definitions, a demo application
and a tutorial. The majority of these was also already published
on NPM. On the OSGeo Bolsena Code Sprint 2019, a GeoServer
Community Extension was written that integrates GeoStyler and
allows the creation of styles within GeoServer by using our GUI.
<br>
<br>
The GitHub organisation can be found here:
<a href="https://github.com/geostyler/geostyler" target="_blank">https://github.com/geostyler/geostyler</a>
<br>
The Demo Application including links to Docs, GitHub and NPM can
be found here: <a href="https://geostyler.org" target="_blank">https://geostyler.org</a>
<br>
The GeoServer Plugin here:
<a href="https://docs.geoserver.org/master/en/user/community/geostyler/index.html" target="_blank">https://docs.geoserver.org/master/en/user/community/geostyler/index.html</a>
<br>
FOSS4G 2019 Talk:
<a href="https://media.ccc.de/v/bucharest-204-geostyler-a-generic-graphical-style-editor-for-geodata" target="_blank">https://media.ccc.de/v/bucharest-204-geostyler-a-generic-graphical-style-editor-for-geodata</a><br>
FOSSGIS 2019 Talk (German):
<a href="https://media.ccc.de/v/fossgis2019-478-geostyler-ein-generischer-grafischer-stileditor-fr-geodaten" target="_blank">https://media.ccc.de/v/fossgis2019-478-geostyler-ein-generischer-grafischer-stileditor-fr-geodaten</a><br>
AGIT 2019 Talk (German): <a href="https://av.tib.eu/media/43048" target="_blank">https://av.tib.eu/media/43048</a>
<br>
FOSSGIS 2020 Talk (German):
<a href="https://media.ccc.de/v/fossgis2020-3027-neues-vom-geostyler" target="_blank">https://media.ccc.de/v/fossgis2020-3027-neues-vom-geostyler</a>
<br>
<br>
The licenses are BSD-2-Clause and we are very happy and eager to
extend the list of contributors. Our first goal would be to be
listed on the OSGeo webpage and in the long run to release
GeoStyler as an OSGeo Community Project.
<br>
<br>
In the future, we would like to provide additional style-parsers
(e.g. for mapserver) and extend the UI library with additional
components to further simplify styling maps.
<br>
<br>
<br>
We are happy to receive your support, if there are any questions,
we are happy to help!
<br>
<br>
Kind regards
<br>
<br>
Jan Suleiman
<br>
<br>
</blockquote>
<pre cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</div>
_______________________________________________<br>
osgeolive mailing list<br>
<a href="mailto:osgeolive@lists.osgeo.org" target="_blank">osgeolive@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/osgeolive" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/osgeolive</a><br>
</blockquote></div>