Migrating wiki-based product docs into git

[pki-bot]

This issue was migrated from Pagure Issue #2858. Originally filed by edewata (@edewata) on 2017-11-28 23:37:32:

• Assigned to nobody

---

Product docs (e.g. install guide, upgrade procedure, CLI guide) are version-specific. However, the current upstream docs are stored on wiki and not well versioned. Some pages contain information about multiple versions which can be confusing to read. It is better to convert these docs into Markdown docs in GitHub so the content will match the code in the same git branch. The use of Markdown in GitHub allows the doc to be read and updated with a browser like wiki.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-11-29 01:09:40

Metadata Update from @mharmsen:

• Custom field component adjusted to None
• Custom field feature adjusted to None
• Custom field origin adjusted to None
• Custom field proposedmilestone adjusted to None
• Custom field proposedpriority adjusted to None
• Custom field reviewer adjusted to None
• Custom field type adjusted to None
• Custom field version adjusted to None
• Issue set to the milestone: 0.0 NEEDS_TRIAGE

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-11-30 16:36:57

Although this is more of a "Task" than a "Bug", in the PKI Team Meeting of 20171130, it was determined to place this in 10.6 - critical to provide greater visibility.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-11-30 16:36:58

Metadata Update from @mharmsen:

• Issue priority set to: critical
• Issue set to the milestone: 10.6 (was: 0.0 NEEDS_TRIAGE)

[pki-bot]

Comment from edewata (@edewata) at 2018-03-19 23:39:27

Metadata Update from @edewata:

• Issue priority set to: major (was: critical)