How-to guide - how a project can become a sub-project of a master glossary

[camerons]

This task is to create a how-to which a project (such as an OSGeo Project like QGIS) can follow so that they can get a subset of terms from a central glossary (such as the OSGeo Foundation glossary).

It would result in a glossary being produced which can somehow be exported to a web page or similar within the project.

I don't think this involves standing up a separate glossary to the OSGeo Foundation, but it might. Details to be debated.

[Naini-K]

Considering alternatives to the word 'Master': Parent, Source, Root, Central, Hub, Main,, etc However, if we consider the different relationships that this glossary might have with other glossaries: parent, peer, etc. can we use a tree-based term? The main glossary can be called 'Trunk' and depending on the relationship it has with other glossaries, they can be branches, roots, off-shoots, etc.

[camerons]

Good catch @Naini-K , I've changed "master" to "central".