I'm thinking the Ick project is getting to the stage where it makes sense to write down the stakeholders and requirements for Ick the software. This will go on the website, and be living documents, not fixed into an immutable state. It doesn't need to be formal or grandiose, but it'll help us think and talk about the software in the future. Here's a start on stakeholders: * USERS: Those who develop of projects, and need a CI or CD system for helping them do that. They will use an Ick hosted by a HOSTER (which might be themselves, wearing another hat). * HOSTERS: Those who host Ick for others to use. * CONTRIBUTORS: Those who contribute to Ick itself. This includes those who write code for Ick, or documentation, translate the software or documentation, those who support Ick users, etc. Am I missing some group? Here's a start on requiements: * Ick should be free software. * Ick should be "hostable": those interested in doing so, should be able to provide an Ick instance for other people to use, without having to truse those other people. Hosters should be able to charge money for hosting Ick. * Users should be able to pick any Ick instance they trust, and migrate between instances. Ick users should feel safe that their projects, builds, and build artifacts are unaffected and secure from prying by other users. * Ick should provide users with a secure way to store "secrets", such as SSH keys, PGP keys, and API access tokens, and use them securely in their projects, without the secrets leaking to other users. * Ick should run builds reasonbly fast, without causing much overhead. * Ick should be able to build different projects concurrently, whether for the same user or several. * Ick should be able to build parts of a project concurrently, when the parts don't depend on each other. I'm sure there's other requirements, and the above can be made more clear and precise. Comments? Please? -- I want to build worthwhile things that might last. --joeyh