[Lexicon] Motion: Set up a glossaries repository within The Good Docs Project

[Cameron Shorter]

Reese,
In open source communities, it is good manners to raise a motion for a high
impact action which affects others. TheGoodDocsProject wouldn't want to
have too many repositories, which is why I ask the community before
creating one.

On Sun, 30 Aug 2020 at 13:37, Reese Plews (ISO/TC211 - TMG) <
rplews at tc211tmg.org> wrote:

> hello Cameron,
>
> i dont have email access to "thegooddocsproject at groups.io" but i will
> keep it in the reply chain. i really dont have any insight into the
> workings or goals of the good docs project yet, so my comments are from
> the stand point of the osgeo lexicon group.
>
> from the three meetings i participated in last week i think the
> discussions were very constructive and are heading in the right
> direction.
>
> i my opinion, i dont see the reason why a motion would be needed on this
> type of issue, as it seems very early in the process to decide if one
> technology or site is better than another. also, making a check to
> create the repo in github or google docs or elsewhere should probably
> not require any motion, in my opinion. unless there are specific rules
> in osgeo to table these motions for such decisions, but it seems a too
> early.
>
> also, in my opinion, i would rather put an emphasis that the discussions
> and planning continue, until the october milestone, to work out this,
> and other issues before any motions are needed.  i believe there are a
> still a number of initial plans to clarify such as the relationships of
> the two groups (gooddocsproj and osgeo lexicon), scope, goals, group
> working vocabulary, and other issues, such as the tools/sites the groups
> that will be use to make this happen.
>
> based on these opinions, i vote -0
>
> rwp
>
>
> ---
>
>
> On 2020-08-30 06:02, Cameron Shorter wrote:
>
> > We kicked off a pilot for Cross domain management of glossaries last
> > Friday, and ~ ten core people interested in contributing as core
> > contributors. We now need to get some logistics in place.
> >
> > First:
> > * We are going to need somewhere to store material we create, and
> > coordinate ourselves with a kanban or similar (as provided by github).
> > * Some material we'll start in Google docs (as we've done already), but
> > we should be moving to somewhere more stable, and for that I'm
> > proposing we put some material into a github repository within The Good
> > Docs Project. (Other material will logically move elsewhere, such as
> > within the GeoLexia project.)
> >
> > Below is a motion to both The Good Docs Project and GeoLexicon
> > communities (please vote):
> > +1 : For
> > +0: Mildly for, but mostly indifferent
> > 0: Indifferent
> > -0: Mildly against, but mostly indifferent
> > -1 : Strongly against. This is expected to be accompanied by a reason.
> > Assuming we achieve rough consensus, I plan to wrap up this motion
> > within 48 hours.
> >
> > Motion: I propose that we create a "glossaries" github repository
> > within https://github.com/thegooddocsproject
> >
> > +1 from me, Cameron
> >
> > --
> >
> > Cameron Shorter
> > Technical Writer, Google
> >
> > _______________________________________________
> > Lexicon mailing list
> > Lexicon at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/lexicon
>


-- 
Cameron Shorter
Technical Writer, Google
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/lexicon/attachments/20200831/c3375ab3/attachment.html>