Describe the process for establishing a specification process in a working group
I don't think that we have this captured anywhere. I'm thinking that we need to extend the working group process operations guide, the specification process operations guide, or both to include more information about standing up a specification process. We should also build a presentation with this content.
Correction: The Working Group Operations Guide makes this statement:
A working group that engages in specification development must implement the Eclipse Foundation Specification Process (EFSP). Prior to the Working Group engaging in any specification work, the Steering Committee must vote to adopt a particular version of the EFSP or derivative thereof. The Steering Committee must further vote to adopt a default Patent License (either Compatible Patent License or Implementation Patent License) as defined by the Eclipse Foundation Intellectual Property Policy.
I'm creating this issue to provide a means to discuss those aspects of this process that require discussing.
I'll summarise the pieces in this description, but then create comments to elaborate and provide a place to discuss. Use the "reply to comment" feature to respond to specific comments (rather than create a new comment that breaks the thread).
I will update this comment periodically based on the discussion.
Steps:
- Steering committee establishes the specification committee in the working group charter;
- Steering committee decides what projects operate under the purview of the working group;
- Steering committee sets the default patent licence;
- Specification committee establishes best practices, naming conventions, etc.; and
- Establish communication channels.