[todo] Discuss creation of documentation based on discussion output.

[cnygardtw]

One of the goals of the working group is to provide some independent documentation around the use of Backstage in FinTech Regulated environments. To make progress toward this goal, we propose to create documentation in this repository that could be used to generate a "micro-site" hosted as github pages.

As part of this process, we propose a workflow where issue tickets remain in "In Progress" until the notes from the discussion can be harvested and incorporated into the documentation. Commits to the documentation should be related back to the issue from which they originate.

Questions:
[ ] - Should documentation changes go through PR approval process? If so, who should be involved?
[ ] - Do we need to provide docs in a specific location or format to conform with devops-automation gh-pages? @mcleo-d

Decisions:

• Run Backstage on FINOS AWS infrastructure
• Target FINOS use-cases first, look for wider FINOS collaboration
• Evolve toward reference implementation
• Contributors need to meet FINOS CCLA requirements
• Create new devops-backstage repository for backstage implementation
• Think about lint/scan to help prevent proprietary info being committed

[cnygardtw]

[ ] - Ask Mark Jorgensen and Lloyds if possible to white label pitch deck / value prop info from internal initiative efforts