impl: Create new project lifecycle process #981
Conversation
As discussed in the 2023-10-09 specification meeting, create a new "Project lifecycle" for major projects (new version, new track, etc). The main idea is to assign a "project shepherd" to oversee the project. This person is responsible for moving the project along. The reason for creating this is that many projects seem to stagnate without a single responsible person. This commit populates the initial list of projects as per our discussion at the meeting. Signed-off-by: Mark Lodato <lodato@google.com>
✅ Deploy Preview for slsa canceled.
|
Co-authored-by: Marcela Melara <marcela.melara@intel.com> Signed-off-by: Mark Lodato <lodatom@gmail.com>
Signed-off-by: Mark Lodato <lodato@google.com>
Signed-off-by: Mark Lodato <lodato@google.com>
|
Hmm, sorry for not responding sooner but I do have to say that the use of the term "project" in this case is unfortunate. "Projects" are a type of "Technical Initiatives" under the OpenSSF charter for which the TAC has defined a project lifecycle. It would be best to avoid overload that term here... As a side note: I've mentioned before that, technically, SLSA is currently a SIG rather than a Project under the current OpenSSF governance structure. I have however proposed to extend the definition of a Project to encompass specification development (see TAC PR #205) and it is broadly supported by TAC members. So, SLSA should indeed officially become a Project soon. :-) But that's one more reason not to create a new type of "project". |
|
Oops, thanks for catching this. Let's go with "workstream". Sent out #990. |
As pointed out in slsa-framework#981, the term "project" is used for SLSA overall. For example, see the top of CONTRIBUTING.md. To avoid overloading that term, rename to "workstream". This seems to imply the same concept. Signed-off-by: Mark Lodato <lodato@google.com>
As pointed out in #981, the term "project" is used for SLSA overall. For example, see the top of CONTRIBUTING.md. To avoid overloading that term, rename to "workstream". This seems to imply the same concept. Signed-off-by: Mark Lodato <lodato@google.com>
As discussed in the 2023-10-09 specification meeting, create a new
"Project lifecycle" for major projects (new version, new track, etc).
The main idea is to assign a "project shepherd" to oversee the project.
This person is responsible for moving the project along. The reason for
creating this is that many projects seem to stagnate without a single
responsible person.
This commit populates the initial list of projects as per our discussion
at the meeting.