[Lexicon] Getting started with Glossarist: contributing to the terminology workflow
Jorge Gustavo Rocha
jgr at osgeopt.pt
Tue Jul 7 08:12:19 PDT 2020
Hi Ron,
Thanks for the feedback. Now I think I understood the entire workflow
(which is really the usual git workflow). I think it is a very nice way
to have people contributing to the terminology in a open and transparent
way. For developers, the workflow is quite simple.
I'll wait for the update to the osgeo-glossary repo.
By the way, who will have permission to merge PR on this osgeo-glossary
repo? Is this already defined?
Regards,
Jorge
On 07/07/20 11:21, Ronald Tse wrote:
> Hi Jorge,
>
> Thank you for trying out Glossarist!
>
> Actually the OSGeo glossary repository needs to be updated to suit the
> latest version of Glossarist — which we are going to do so today. The
> current repo is using an older data schema. The unexpected diffs are due
> to this reason.
>
> In order to submit change requests, you will need write access to the
> repository. Should the group discuss about it?
>
> Now to the questions:
>> 2) To change something, I must start a change request and make my
>> changes, right?
>
> Yes, you’re right. A change request can contain multiple changes.
>
>> 3) Afterwards, in my local
>> ~/.config/Electron/glossarist-database/change-requests I have the
>> changes from my change request.
>
> Correct. The git “upstream” remote is a deprecated artifact, it will be
> removed in the next version of Glossarist.
>
>> 4) Question: If I want to contribute to the OSGeo terminology, what
>> should I do next?
>>
>> Should I push my changes from the command line or there is some button
>> on Glossarist to submit the change request?
>
> Glossarist has the Review pane where you can “Propose” a CR, after which
> you can “Sync” (top left of window) — it will upload the CR.
>
> In this case, since you don’t have direct write access, you could:
> 1. First, work on your fork of the repository — i.e. fork
> https://github.com/geolexica/osgeo-glossary , and make that your new
> remote in Glossarist.
> 2. Create a CR in your own fork
> 3. Make a Pull Request to submit your CR to the master branch of
> https://github.com/geolexica/osgeo-glossary
> 4. Whoever has access to merge can bring in your CR to master and
> review/approve the CR.
>
> Would you mind waiting until tomorrow for the new version of Glossarist
> (due tonight) and the upgrade of the data repo schema?
>
> Thanks!
>
> Ron
>
> _____________________________________
>
> Ronald Tse
> Ribose Inc.
>
> +=========================================================+
> This message may contain confidential and/or privileged
> information. If you are not the addressee or authorized to
> receive this for the addressee, you must not use, copy,
> disclose or take any action based on this message or any
> information herein. If you have received this message in
> error, please advise the sender immediately by reply e-mail
> and delete this message. Thank you for your cooperation.
> +=========================================================+
>
>> On Jul 7, 2020, at 5:03 PM, Jorge Gustavo Rocha <jgr at osgeopt.pt
>> <mailto:jgr at osgeopt.pt>> wrote:
>>
>> Hi all,
>>
>> I've clone the Glossarist desktop tool repo and started to use it. It
>> work pretty well on my Ubuntu. Thanks for those working on it.
>>
>> I would like to understand the workflow behind it and how can we use it
>> in OSGeo.
>>
>> 1) I've started Glossarist, identified my self with my Github account. I
>> can browse existent entries and the application is working smoothly.
>> Great!
>>
>> 2) To change something, I must start a change request and make my
>> changes, right?
>>
>> 3) Afterwards, in my local
>> ~/.config/Electron/glossarist-database/change-requests I have the
>> changes from my change request.
>>
>> The folder ~/.config/Electron/glossarist-database is under git control
>> (setup done by Glossarist).
>>
>> The remote repos are:
>>
>> jgr at zoe:~/.config/Electron/glossarist-database$ git remote -v
>> originhttps://github.com/geolexica/osgeo-glossary (fetch)
>> originhttps://github.com/geolexica/osgeo-glossary (push)
>> upstreamhttps://github.com/ISO-TC211/geolexica-database (fetch)
>> upstreamhttps://github.com/ISO-TC211/geolexica-database (push)
>>
>> 4) Question: If I want to contribute to the OSGeo terminology, what
>> should I do next?
>>
>> Should I push my changes from the command line or there is some button
>> on Glossarist to submit the change request?
>>
>> Note: All local files were rewritten and git reports changes in all
>> terms. I didn't expect such changes. As far as I can understand, git
>> should report only changes in `change-requests` folder, right?
>>
>> My local --stats are:
>>
>> jgr at zoe:~/.config/Electron/glossarist-database$ git diff --stat --cached
>> origin/master | head -10
>> change-requests/7a5c63.yaml | 37 +++++++++++++
>> change-requests/bd20b0.yaml | 61 ++++++++++++++++++++++
>> concepts/concept-1.yaml | 30 +++++++++--
>> concepts/concept-10.yaml | 30 +++++++++--
>> concepts/concept-100.yaml | 30 +++++++++--
>> concepts/concept-101.yaml | 30 +++++++++--
>> concepts/concept-102.yaml | 30 +++++++++--
>> concepts/concept-103.yaml | 30 +++++++++--
>> concepts/concept-104.yaml | 30 +++++++++--
>> concepts/concept-105.yaml | 30 +++++++++--
>>
>> Unexpected changes (for me!) are like this one:
>>
>> jgr at zoe:~/.config/Electron/glossarist-database$ git diff --cached
>> origin/master concepts/concept-10.yaml
>> diff --git a/concepts/concept-10.yaml b/concepts/concept-10.yaml
>> index 0c68c10..54ae114 100644
>> --- a/concepts/concept-10.yaml
>> +++ b/concepts/concept-10.yaml
>> @@ -1,4 +1,3 @@
>> ----
>> term: AM/FM
>> termid: 10
>> eng:
>> @@ -8,8 +7,29 @@ eng:
>> notes: []
>> examples: []
>> authoritative_source:
>> - link:
>> https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf
>> + link:
>> 'https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf'
>> terms:
>> - - type: expression
>> - designation: AM/FM
>> - normative_status:
>> + - type: expression
>> + designation: AM/FM
>> + normative_status: null
>> + _revisions:
>> + current: 0c7724
>> + tree:
>> + 0c7724:
>> + object:
>> + id: 10
>> + definition: Automated Mapping/Facilities Management
>> + language_code: eng
>> + notes: []
>> + examples: []
>> + authoritative_source:
>> + link:
>> 'https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf'
>> + terms:
>> + - type: expression
>> + designation: AM/FM
>> + normative_status: null
>> + parents: []
>> + timeCreated: 2020-07-06T21:28:14.660Z
>> + author:
>> + name: Glossarist bot
>> + email: glossarist at ribose.com <mailto:glossarist at ribose.com>
>>
>> Sorry for this newbie question.
>>
>> But soon as I understand the workflow, I can write a short tutorial
>> about how to use Glossarist to maintain and improve OSGeo terminology.
>>
>> Regards,
>>
>> Jorge
>>
>>
>> On 04/07/20 13:47, Richard Duivenvoorde wrote:
>>> Nice Nice!!!
>>>
>>> And good to lift this to an higher (OSGeo) plan!!
>>>
>>> Go go! :-)
>>>
>>> Regards,
>>>
>>> Richard Duivenvoorde
>>>
>>> (bcc to our dutch translation master)
>>>
>>> On 7/4/20 11:01 AM, Jorge Gustavo Rocha wrote:
>>>> Hi Ron,
>>>>
>>>> Thank you for the update.
>>>>
>>>> I've looked in the current https://osgeodev.geolexica.org and on yours
>>>> Glossarist desktop tool. Looks like very promising.
>>>>
>>>> OSGeo and QGIS in particular would benefit from such a well defined
>>>> glossary.
>>>>
>>>> I'll be watching the project. I'll try to contribute with build
>>>> instructions for Linux :-)
>>>>
>>>> Best regards,
>>>>
>>>> Jorge
>>>>
>>>> On 04/07/20 04:56, Ronald Tse wrote:
>>>>> Hi Jorge,
>>>>>
>>>>> Thank you for spreading the news!
>>>>>
>>>>> The current development site with loaded terms is located here:
>>>>> https://osgeodev.geolexica.org
>>>>>
>>>>> I believe the group is still waiting for some confirmation on
>>>>> terminology across OSGeo. As you can see on the site, a number of
>>>>> conflicting definitions exist and the group would need some effort to
>>>>> discuss and attempt to settle these — since they are used across
>>>>> different OSGeo projects.
>>>>>
>>>>> Geolexica has also been working with ISO/TC 211 on their latest efforts
>>>>> in translating the 5th edition of the TC 211 Multi-Lingual Glossary of
>>>>> Terms (MLGT). There is now have a desktop application for managing
>>>>> translations through change requests, all based off a git repository on
>>>>> GitHub:
>>>>> https://www.glossarist.org
>>>>>
>>>>> I agree that more love is needed to the lexicon group to move
>>>>> things ahead!
>>>>>
>>>>> Kind regards,
>>>>> Ron
>>>>>
>>>>> _____________________________________
>>>>>
>>>>> Ronald Tse
>>>>> Ribose Inc.
>>>>>
>>>>> +=========================================================+
>>>>> This message may contain confidential and/or privileged
>>>>> information. If you are not the addressee or authorized to
>>>>> receive this for the addressee, you must not use, copy,
>>>>> disclose or take any action based on this message or any
>>>>> information herein. If you have received this message in
>>>>> error, please advise the sender immediately by reply e-mail
>>>>> and delete this message. Thank you for your cooperation.
>>>>> +=========================================================+
>>>>>
>>>>>> On Jul 4, 2020, at 6:23 AM, Jorge Gustavo Rocha <jgr at di.uminho.pt
>>>>>> <mailto:jgr at di.uminho.pt>> wrote:
>>>>>>
>>>>>> Hi Ian, hi all,
>>>>>>
>>>>>> There are people trying to run an OSGeo "Interest group" on
>>>>>> "Terminology", to be transversal to all OSGeo projects.
>>>>>>
>>>>>> They created a proof of concept, called "geolexica", available at:
>>>>>>
>>>>>> https://osgeo.geolexica.org/concepts/
>>>>>>
>>>>>> Sources on: https://github.com/geolexica/osgeo.geolexica.org
>>>>>>
>>>>>> It would be awesome if we were able to fill the translation for the
>>>>>> different languages associated with the English concept, right on the
>>>>>> origin.
>>>>>>
>>>>>> As far I as know (I'm cc to lexica group), this project needs some
>>>>>> additional "love" to go on.
>>>>>>
>>>>>> Maybe Cameron (in cc) or someone else can make an update on the
>>>>>> lexicon
>>>>>> activities/plans.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Jorge
>>>>>>
>>>>>> On 30/06/20 10:57, Ian Turton wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Tue, 30 Jun 2020 at 10:40, Bo Victor Thomsen
>>>>>>> <bo.victor.thomsen at gmail.com
>>>>>>> <mailto:bo.victor.thomsen at gmail.com>> wrote:
>>>>>>>
>>>>>>> Dear developers:
>>>>>>>
>>>>>>> As a former translator of the Danish version of QGIS I have a
>>>>>>> few -
>>>>>>> very personal, perhaps a bit caustic - comments:
>>>>>>>
>>>>>>> * Create a group or list of highly technical GIS related terms
>>>>>>> that is *not* to be translated. There is a lot of GIS
>>>>>>> terms that
>>>>>>> is English in origin, but haven't a well defined local
>>>>>>> translation. (With some hilarious results if they are
>>>>>>> translated). Not all translators is well versed in every
>>>>>>> aspect
>>>>>>> of GIS.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Is this something that OSGEO can help to oversee and/or maintain as I
>>>>>>> suspect that this list would be useful across many projects.
>>>>>>>
>>>>>>> Ian
>>>>>>>
>>>>>>> --
>>>>>>> Ian Turton
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> QGIS-Developer mailing list
>>>>>>> QGIS-Developer at lists.osgeo.org
>>>>>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>>>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>>>>>
>>>>>>
>>>>>> J. Gustavo
>>>>>> --
>>>>>> Jorge Gustavo Rocha
>>>>>> Departamento de Informática
>>>>>> Universidade do Minho
>>>>>> 4710-057 Braga
>>>>>> Gabinete 3.29 (Piso 3)
>>>>>> Tel: +351 253604480
>>>>>> Fax: +351 253604471
>>>>>> Móvel: +351 910333888
>>>>>> skype: nabocudnosor
>>>>>> _______________________________________________
>>>>>> Lexicon mailing list
>>>>>> Lexicon at lists.osgeo.org
>>>>>> https://lists.osgeo.org/mailman/listinfo/lexicon
>>>>>
>>>>
>>>> J. Gustavo
>>>>
>>>
>>> _______________________________________________
>>> Lexicon mailing list
>>> Lexicon at lists.osgeo.org <mailto:Lexicon at lists.osgeo.org>
>>> https://lists.osgeo.org/mailman/listinfo/lexicon
>>>
>>
>> --
>> OSGeo Portugal
>> NIF: 509588190
>> email: geral at osgeopt.pt <mailto:geral at osgeopt.pt>
>> https://www.osgeopt.pt/
>>
>> Próximo evento: SASIG 2017, 20 a 22 de novembro, Porto
>> Mais informações: http://osgeopt.pt/sasig2017/
>> _______________________________________________
>> Lexicon mailing list
>> Lexicon at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/lexicon
>
--
OSGeo Portugal
NIF: 509588190
email: geral at osgeopt.pt
https://www.osgeopt.pt/
Próximo evento: SASIG 2017, 20 a 22 de novembro, Porto
Mais informações: http://osgeopt.pt/sasig2017/
More information about the Lexicon
mailing list