Select solution for shared Crew/Ops Knowledgebase

Evaluate and ultimately select a solution for a 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.

Requirements below. Take a look first at TWiki.org . It is the gold standard for simplicity.

1) Strong preference for open source.
2) Strong preference for dual deployments - both local and in cloud, with synchronization
3) Unique user names for all crew members across all crews going forward
4) support for attachments
5) desirable to uniquely label off-site links, if possible (similar to what wikipedia does)
6) support for tags/labels on articles
7) KEY - frictionless content creation. Needs to have automatic page creation and linking.

Start by reviewing TWiki.org and compare it with the listed requirements: open-source licensing, local/cloud deployment and synchronization, identity, attachments, links, tags, and frictionless content creation. Done means selecting and documenting a shared knowledge-base solution that supports Crew Ops and crew self-service across crews and time.

Written by the indexing model from the issue text.