-
Notifications
You must be signed in to change notification settings - Fork 0
Project phases
We'll remain a little flexible on this, but following are the high-level stages of development from draft to production. You might want to see what the Status is too.
To get settled into GitHub, we need to get all prior work in Google Drive migrated over, including decision history of respective terms. For purposes of this stage, and because Using issues and Using issue labels will be central to our collaborative communication, we'll start with all terms considered so far. See instructions for:
This phase is basically the ongoing collaboration routine; from proposing new glossary terms to making associated definition files production ready. Anyone can do this now, no matter your comfort zone with GitHub. See the links under Sign up and set up and Collaborate on the wiki Home to get started.
Monitor Issues. They are the life-blood of this project's collaboration. Read about using issues and using issue labels in relation.
As outside collaborators (writers and editors) continue to develop glossary definitions in phase II, project managers will keep developing the tech side of things, inching the production glossary closer to an ethical product. Besides getting the initial production architecture setup, including optimization of template front matter and use of Jekyll variables, it also means layering in the desired accessibility and semantic schema attributes on glossary templates.
See Production glossary structure for more about production development and design.
Basically this is phase II in "continuous" mode.
The glossary is rolling, meaning it's always growing, reducing, refining... The repository is the collaborative epicenter where all evolutionary changes are made. And when phase III is complete, such changes are automatically reflected in the production site.
Using issues and Using issue labels will be central to the ongoing collaboration process.
README | Glossary index | Terms register (temporary)