Enhance MicroShift Community experience

Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

MicroShift currently has no decent community experience. A subscription / pull secret is needed to get acces. The goal of this feature is to re-vamp microshit.io with a decent community / upstream possibility. E.g. use / integrated with OKD to make upsteam use of MicroShift quick and easy. 

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Complete during New status.

Be able to test-drive MicroShift with pure community bits, no sub, no pull secreted needed.

This relies on making CNI+CSI driver configurable/pluggable to point to e.g. OKD or other community implementations (e.g. flannel for CNI, or NFS for CSI).

Update / enhance the microshift.io website with current documenation and guidance on how to contribute.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

• As community user, I can easily install MicroShift to my Centos Streams system, without the need of a subscription or pull secrets.
• As community developer, I can easily contribute to MicroShift by submitting pull requests.

Questions to Answer (Optional):

How can we leverage materials / processes from OKD?

Out of Scope

Supporting other CNI+CSI drivers then the ones decided for MicroShift currenlty. While community might plug in other providers, it has to be made clear that Red Hat does not provide any support, if other providers are being used.

Background

Community expierence on microshift.io was neglected in the past in favour of getting to GA with MicroShift.

Customer Considerations

None, as this is about community.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

No change to enterpise docs, everything needs to be upstream docs. The assumption is that existing docs on github.com/openshift/microshift can be easily used as community docs.

Interoperability Considerations

Work with OKD team what can be re-used from them.