contribution model

[pearce8]

0. Need to record maintainers: for systems (one per system config, e.g., nosite-x86_64), and experiments (one per experiment, e.g., amg2023/cuda)
1. New systems

• system owners should define/update the default compilers on the system
• dashboard report of all the experiments that were tested

2. New experiments

• dashboard report of all the platforms tested
• should we require a working test on a neutral platform (e.g., AWS)?

3. Spack package.py and Ramble application.py

• benchpark/repo is the way to test all of the components together
• should commits to the repo trigger PRs to Spack and Ramble? Once those are upstreamed, changes to benchpark/repo need to be made, and ${BENCHMARK1} should point at the upstreamed versions instead of at the repo.

[pszi1ard]

Meanwhile, the users may well prefer to keep their local changes in system and benchmark configs. This may introduce issues if the interfaces of either of the project change, but otherwise may be a desirable usage pattern for our users.

In my first experiments I realized that some benchmark config files (like tpl templates) may depend on/relate to machine configs which adds an additional complication.

[alecbcs]

@pszi1ard interesting, can provide an example of a template you've modified for a specific system?