Zowe Assets (beyond code) Access Adjustments

[RASakach]

The BOX folder utilized for Zowe collaboration was almost inadvertently deleted. https://broadcom.ent.box.com/folder/40769632203?s=j9vzv2xrishkcyb61d28wx3tod07p956

Recommend adjusting access, limiting access, and installing periodic reviews of access.

[balhar-jakub]

The related document is here: https://ibm.box.com/s/mnudvbs04na4bifssanj52vv4gmlp542

[jmertic]

My 2 cents - get out of Box. It's hard to get into and be discoverable. It makes the project look closed off and not welcoming.

I'd suggest putting things up in Confluence ( wiki.openmainframeproject.org ). There are access controls for managing edits, but bigger picture the content is discoverable and easier for potential new project participants to see activity.

[balhar-jakub]

The issue is that it's also far more uncomfortable for working together on the creation of the documents. The second part is that we need to store larger things like presentations somewhere and while Box seems closed, even very untechnical people know how to use it well as opposed to Wiki.

But anyway I will keep this option in mind when preparing the proposal.

[jmertic]

In my experience, projects of technical and non-technical folks can use a wiki, especially Confluence. Plus you can upload presentations to the wiki quite easily - I have many projects that do that. Check out these project's wikis for some ideas...

wiki.lfenergy.org https://wiki.lfedge.org/ https://wiki.lfnetworking.org/ https://wiki.hyperledger.org/

[balhar-jakub]

@jmertic This is the issue, I was talking about in https://github.com/zowe/zowe.github.io/pull/881. It's stalled a bit as I am working on other higher priority work around Zowe.

[jmertic]

Makes sense. Let me know what I can do to help here.