governance document

[bhpayne]

I'm not sure where an SST governance document belongs, so if sst-core isn't a good place let me know where to move it too.

What could be included:

What's the goal of SST? Are there priorities (e.g., performance? stability?)

Are there different roles in the SST community? User, developer, contributor, owner

example: https://www.gem5.org/governance/

advice from JLP: don't be creative or original. Copy existing wording.

Support:

• Explain deprecation policies for features.
• what are the best channels for questions? (Stackoverflow, github issues, direct email, in-person meetings, monthly virtual calls, message boards)

Philosophy:

• What features would be rejected and why?
• how are roadmap decisions made?
• where can the roadmap be found?
• are there opportunities to fund development of SST? Sponsorship?
• what distinguishes primary elements from less supported elements?
• what sets the release tempo?
• what platforms and compilers and libraries are supported?
• why are some features publicly accessible in SST and others not?