Project phases

We'll remain a little flexible on this, but following are the high-level stages of development from draft to production.

I) Migration from Google Drive

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 will be central to our collaborative communication, we'll start with all terms considered so far. See instructions for:

• Migrating glossary terms
• Migrating initial drafts

II) Repository development (current stage)

The first stage is to fill out the working glossary repository with draft files for the terms that were established prior to moving to GitHub. Anyone can do this now, no matter your comfort zone with GitHub:

• you have a GitHub account and know how to make pull requests
• you're new to using GitHub

II) Platform development

When at least 50 definitions articles are fully written and sufficiently debated in the working repository, CSF's web squad will begin creating the production architecture. In fact, conception on production design is already underway, and the discussion boards are the place to pipe in about it if you have something say.

The production location is expected to be glossary.csf.community.

III) Migration

When the production platform is ready, glossary editors will be invited to serve as production technical editors too, along with CSF web hands. Editors will begin the manual process of porting draft articles to the production CMS. This means some willing glossary editors will parse definition article components into the corresponding CMS fields, and CSF's editors will handle the final formatting tweaks and adjustments that are always needed in relation to CMS characteristics.

Again: Additional definitions drafts beyond the initial 50 stated above will be added to the production site as they are ready. Likewise, any other repository changes will reflect in the production site over time.

IV) Evolution

The glossary is rolling — always growing, reducing, refining... — and the repository is the collaborative epicenter where all evolutionary changes are made. The initial count of 50 articles is simply a milestone to move to the next stage (repo development to platform development), it's not a finish point for the glossary drafts. The production site updates in relation to repository changes.

Following the collaboration protocols is key to it working effectively over time.