<div dir="ltr">Hi Codrina,<div>GRASS would be a great test case project, which is one of the largest and oldest OSGeo projects, and as such is likely one of the projects most in need of a glossary.</div><div>Yes, it would be great to have a meeting with Vaclav. Feel free to loop me into any conversations you'd like to set up.</div><div>I suspect Reese, Ron and Naini would be keen to join too. (It will likely be difficult to find a timezone which the Americas can make if you loop in APEC). </div><div>Maybe this timeslot (plus or minus a couple of hours):</div><div><a href="https://www.timeanddate.com/worldclock/meetingtime.html?day=6&month=11&year=2020&p1=22&p2=240&p3=47&p4=248&p5=102&p6=44&p7=26&p8=136&p9=179&p10=220&p11=224&iv=0">https://www.timeanddate.com/worldclock/meetingtime.html?day=6&month=11&year=2020&p1=22&p2=240&p3=47&p4=248&p5=102&p6=44&p7=26&p8=136&p9=179&p10=220&p11=224&iv=0</a></div><div>Feel free to invite me to a meeting, or reach out on slack to coordinate a time.</div><div><br></div><div>An OSGeo code sprint around glossaries sounds like a good idea, if we can get a clear scope in place, and then have people on hand to help. I'll be available for a few hours on the morning for the first day (EU time) but will be busy with another conference and time poor for the rest. But it would be a great chance to set up a few cross-team discussions. Again, there are a few in our team who I suspect would be up for helping.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 4 Nov 2020 at 11:58, Codrina Maria Ilie <<a href="mailto:codrina@geo-spatial.org">codrina@geo-spatial.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi, Cameron,<br>
<br>
Yes, I agree with you and even more - especially for the people that <br>
I've reached out to - I think, they are careful with where they invest <br>
their volunteering time and we are in tough competition with bug fixing <br>
and developing new exciting things.<br>
<br>
One the other hand, I think we might have a first pilot project and that <br>
is GRASS GIS. Apparently, working on terminology was among the results <br>
of a recent usability survey in order to improve and it is not the first <br>
time it came up. So, I've been emailing with Vaclav and now he is <br>
raising some questions that require details on the processes used in <br>
establishing terms and writing definitions, details that I don't know.<br>
Thus, I would like, with your permission, Cameron, to invite you in the <br>
conversation, aka email thread.<br>
<br>
Regarding your question, I am not sure that - at least in this <br>
particular case - inserting a new tab into our spreadsheet would be very <br>
appealing. I mentioned about Geolexica and he was particular excited <br>
about its languages support.<br>
<br>
I would also like to announce that the OSGeo Code Sprint is approaching. <br>
Due to covid-19, the Athena code sprint was canceled and after a <br>
community polling, we decided to have a virtual one on 17-19 November. I <br>
think it would be a good opportunity to connect with people. What say you?<br>
<br>
<br>
Cheers,<br>
Codrina<br>
<br>
<br>
On 02/11/2020 22:31, Cameron Shorter wrote:<br>
> Thanks Codrina,<br>
> I can see you are connecting with all the right people.<br>
> This early stage of a project, before you have built credibility with a <br>
> real deliverable, is always difficult and lonely with lots of setbacks.<br>
> One of the lessons you see in open source research is that successful <br>
> projects typically do a very good job of making first contributions very <br>
> easy. This correlates with psychological research into "Nudge Theory" - <br>
> used positively to help populations to stop smoking and to start <br>
> exercising, or not-so-positively to ... <add favourite gripe here>.<br>
> <br>
> So why don't we start by adding a tab to our spreadsheet of terms [1] <br>
> which just contains:<br>
> Term, Description, Project1 (Y/N), Project2 (Y/N)<br>
> <br>
> Ideally we should fill out one project first. Codrina, you might know <br>
> one project well enough to do a first pass? It is okay if it is not perfect.<br>
> <br>
> Then we ask Arnika or Naini to send the bulk email to all projects (I <br>
> can walk you through the process of using the spreadsheet mailmerge).<br>
> <br>
> Any objections or suggestions to this?<br>
> <br>
> Reese, would you mind setting up the extra tab in your spreadsheet?<br>
> <br>
> [1] <br>
> <a href="https://docs.google.com/spreadsheets/d/1keonRLT3chmqlRZsMMF9UaCI_vzNEHmJx6t9LB3jBjM/edit#gid=1083334541" rel="noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1keonRLT3chmqlRZsMMF9UaCI_vzNEHmJx6t9LB3jBjM/edit#gid=1083334541</a><br>
> <br>
> On Mon, 2 Nov 2020 at 20:48, Codrina Maria Ilie <<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a> <br>
> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a>>> wrote:<br>
> <br>
> Hi, Cameron,<br>
> <br>
> I've reached out to the following people:<br>
> <br>
> Andrea Aime, Jody Garnett, Ian Turton - GeoServer, GeoTools,<br>
> GeoNetwork,<br>
> GeoNode, JTS, uDig<br>
> <br>
> Markus Neteler, Anna Petrasova, Veronica Andreo, Vaclav Petras, Moritz<br>
> Lennert - GRASS<br>
> <br>
> Matthias Kuhn - QGIS<br>
> <br>
> Pirmin Kalberer - spatialite, QGIS server<br>
> <br>
> Astrid Emde - Mapbender<br>
> <br>
> Johan Van de Wauw - SAGA<br>
> <br>
> Vicky Vergara - pgrouting<br>
> <br>
> Álvaro Anguix - gvSIG<br>
> <br>
> Stephan Meiss - EOxServer<br>
> <br>
> Gérald Fenoy, Nicolas Bozon - ZOO-Project<br>
> <br>
> <br>
> My invitation for contributions were not limited strictly to their main<br>
> OSGeo project, but for any other initiative their involved in, of<br>
> course, in the limit of their availability. At this time, I have no<br>
> hard<br>
> commitment to share.<br>
> <br>
> A good example from the community why we need this work is this<br>
> document<br>
> that I've used to exemplify my detailing<br>
> <a href="https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS</a>.<br>
> <br>
> <br>
> <br>
> Cheers,<br>
> Codrina<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> On 01/11/2020 00:37, Cameron Shorter wrote:<br>
> > I've reminded myself how to send a mail merge from our<br>
> > osgeolive contacts spreadsheet.<br>
> ><br>
> <a href="https://docs.google.com/spreadsheets/d/1Dem6RYkokaX61N8VcomebtqZvcUP-OOt14jt6GPL2TY/edit#gid=1679238205" rel="noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1Dem6RYkokaX61N8VcomebtqZvcUP-OOt14jt6GPL2TY/edit#gid=1679238205</a><br>
> > If we are going to hit our soft release date at the start of Dec, we<br>
> > will need to get an email out in the next day or two.<br>
> ><br>
> > Codrina, who have you connected with so far? Unless someone beats<br>
> me to<br>
> > it, I'll send an email to the remainder. (Or possibly everyone.)<br>
> ><br>
> > This is what I propose is sent:<br>
> ><br>
> > Hi ${"First"}, I'm wondering if you think we should create a<br>
> glossary<br>
> > for ${"Application Id"}? If so, we'd love some help. We are<br>
> looking for<br>
> > someone in the project to review our spreadsheet of OSGeo terms<br>
> [1] and<br>
> > tick those that are applicable for ${"Application Id"}. You might<br>
> also<br>
> > have suggestions for extra terms we should add. Is this something<br>
> you<br>
> > can help us with over the next few weeks?<br>
> ><br>
> > [1]<br>
> ><br>
> <a href="https://docs.google.com/spreadsheets/d/1keonRLT3chmqlRZsMMF9UaCI_vzNEHmJx6t9LB3jBjM/edit#gid=1083334541On" rel="noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1keonRLT3chmqlRZsMMF9UaCI_vzNEHmJx6t9LB3jBjM/edit#gid=1083334541On</a><br>
> <br>
> > Wed, 14 Oct 2020 at 19:44, Codrina Maria Ilie wrote: > Hi all, ><br>
> > I am<br>
> > writing to let you know of a new initiative within our community<br>
> - > the<br>
> > OSGeo Glossary - led by the Lexicon committee (in formation) with<br>
> > the<br>
> > scope of defining and managing geospatial terms across<br>
> communities. ><br>
> > First operative steps have already been made with setting up OSGeo ><br>
> > Geolexica [1] for managing the lexicon database, as well as an<br>
> initial ><br>
> > load of terms that was done by a bulk load from cleaned terms and ><br>
> > definitions compiled by the GeoForAll group. > > The work is done in<br>
> > collaboration with folks from ISO/TC 211, OGC and > The Good Docs<br>
> > Project [2] that have joined the Lexicon committee, which > is very<br>
> > constructive given their decades long experience in terminology,<br>
> > as<br>
> > well as helping us with cross-organization alignment of concepts<br>
> or ><br>
> > avoiding term duplication. > > Gracefully helping us with the<br>
> groundwork<br>
> > are two experienced technical > writers that I’d like to<br>
> introduce to<br>
> > our community, Ankita and Naini - > in cc. Their contributions will<br>
> > support us in doing a clean, sharp job > when it comes to the actual<br>
> > process of glossary construction. > > A next big step for the<br>
> Lexicon<br>
> > Committee is setting up pilot glossary > projects for specific OSGeo<br>
> > projects, irrespective of their status, > incubated, in the<br>
> process or<br>
> > community. So, if this could be of interest > to you, please let me,<br>
> > Cameron, Ankita or Naini know or by joining and > presenting<br>
> yourself on<br>
> > the Lexicon mailing list [3] or Slack channel [4]. > > > Cheers<br>
> and stay<br>
> > safe, > Codrina<br>
> ><br>
> ><br>
> <br>
> <br>
> <br>
> -- <br>
> Cameron Shorter<br>
> Technical Writer, Google<br>
> <br>
> <br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div><span style="font-size:12.8px">Cameron Shorter</span><br></div><div>Technical Writer, Google</div></div><div><br><br></div></div></div></div></div></div></div></div></div></div></div>