Add clarity wrt SIGs that need to be projects #348
Conversation
When SIGs produce code or specification, they need to be projects, but this was not fully clear before. Aiming to clarify this. Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>
|
@mihaimaruseac Thanks for your PR. While I agree that clarifications in the process are needed, the distinction between SIG and Project isn't strictly about code vs. no code. It's about scope, rather. SIGs are meant to be more independently managed within the hosting TI, considerably narrower in scope, and have a shorter lifetime. But this doesn't preclude the SIG from producing code that is experimental or a PoC for a spec. On the other hand, if the SIG eventually intends to create production-quality software beyond PoC, that's when I think it makes sense to migrate to a Project designation a Project designation since the Project lifecycle includes more software-related requirements. Again, I think our process docs would benefit from clarity around these details, but I don't think we should discourage SIGs from producing any code at all. These are my thoughts at least, others on the TAC may have a different view. |
|
I agree with @marcelamelara. I think the proposed wording is a bit too strong. Our [governance structure]9https://github.com/ossf/tac/blob/main/organizational-structure-overview.md) states that the "primary output" of a SIG is "not software". This implies that it could be a secondary output and clearly does not prohibit any software development. |
Signed-off-by: Mihai Maruseac <mihai.maruseac@gmail.com>
|
Thank you for reviewing. I've made some amendments to the wording to include the feedback. |
marcelamelara
added
the
Content
|
I also think we need a changelog entry for this one? Or should we consider this an editorial change? |
Co-authored-by: Marcela Melara <marcela.melara@intel.com> Signed-off-by: Mihai Maruseac <mihai.maruseac@gmail.com>
I can add one if needed. |
Signed-off-by: Mihai Maruseac <mihai.maruseac@gmail.com>
mihaimaruseac
force-pushed
the
update-documentation
branch
from
b9d5446 to
8220606
Compare
|
Thanks so much @mihaimaruseac ! |
When SIGs produce code or specification, they need to be projects, but this was not fully clear before. Aiming to clarify this.