bmidgley / bmidgley/mars-evalink
Copy documentation from Google Drive to shared Crew/Ops Knowledgebase
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Some of the documentation we've generated during the development of EVALink will be useful for both Crew Ops/Support and for crews themselves. We need to identify that content and copy it to the new shared knowledge base. It will be used both by Crew Ops and by crews themselves. Crew Ops will use it for help-desk-like support and troubleshooting articles. Crews themselves will be able to use the same content self-service, Also Crews can create their own content. Content will span multiple crews over all time. Each crew and user should be uniquely identified.
1) Identify content in EVALink project google drive
2) update if necessary, using consistent structure/formatting/templates
3) copy to shared Crew/Ops Knowledgebase, following consistent structure/formatting/templates
4) include reference/link to source Google drive in KB article
5) add appropriate KB tags
Contributor guide
No contributing guide indexed for this repository
Research direction
No repository files, tests, or entry points are named. Start by identifying the relevant EVALink documents in Google Drive and the shared Crew/Ops Knowledgebase structure; done means selected content is updated, copied with consistent templates and tags, linked to its source, and covers the stated crew and user identification needs.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100