You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Target Release Date: ___

Community Engagement, Support, and Promotion

Marketing and Communications Direct Outreach

Managed by: Tom Fryer 
Progress: ___

Sub Task
Assigned To
Due Date
Progress

REN community engagement for map participation

  • Approach via Marketing and Communications representatives
  • Solicit participation in map database
  • Solicit participation in WG and Dev Team
Tom Fryer 

Establish public website strategy & scope

Tom Fryer 



Public Website (action pending above)

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Introduction page: project overview




TNC 2021 video link to show more details




Current live GREN Map embeded from main GREN node




Glossary of terms used in the project




Identify (and secure, if necessary) domain name




Select site host, deploy, and connect domain name




Community Outreach

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Identify GREN Hireachy




Reach out to mid-tiers first? [consider delegation]




Divide geographically?




Support Contact Point

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

E-mail list?  Gitlab support desk project?  Other?




Documentation

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Primary user guide documentation: review & update




Deployment process & guidance

SOP for onboarding a new region with it's own node
SOP for onboarding a new region on an existing node



Getting-started guide




Conventions and best practices: example tags & properties, data advice, privacy guidance, etc.




Metadata requirements, suggestions, and best practices review




Central Repository of Common Architecture (e.g. ANA)

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Identify architecture to include




Capture data




Publish (GREN Map node? Gitlab? Website?)




Feature Development

Manage Node v1.0 Development & Release

Managed by: Dan Sellars
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Rules feature

Ryan D

Filter-by-tag feature




Remaining bug fixes and outstanding identified issues (see v1.0 Release Plan document)




Release & Publication




Security & Privacy

Managed by: (CANARIE)
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Select & implement authentication method(s) (FIM? eduGAIN and/or eduTeams?)




In-situ deployed node update mechanism




Document system architecture




Data privacy parameters, statement, and guidance




GRENML Library v1.x Release

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Review & Release




Reference Visualization v1.0 Release to NPM

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Review & Release




Release/Deployment

Code Host

Managed by: Dan S
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Migrate Code to GitLab.com [v1.0, or wait for later?]

Dan S

Release Delivery Process

Managed by: Dan S
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Establish




Document




Deploy Top-Level GREN Node

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Select host & maintainer org




Assign administrators




Deploy & test




Connect at least one map




Test/Pre-Prod Node

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Select host & maintainer




Deploy & test




Process for Adding Polling Sources

Managed by: ___
Progress: ___

Sub Task
Assigned To
Due Date
Progress

Establish process




Document process




Append feature support story to identified requirements list








  • No labels