Be inclusive of process specifications
The EFSP was designed specifically to deal with technical specifications that include technical things like APIs and TCKs. While it avoids specifically defining technical artifacts and I believe that it possible to interpret the EFSP to make those things optional, it's very evident that technical specifications are first class.
Let's see what we can do to make it treat process specifications as first class things.
Update (April 5 2024) :
I've created a draft and a diff:
- Eclipse Foundation Specification Process 1.4 (DRAFT)
- Differences between version 1.3.2 and 1.4 (DRAFT)
I've also created a presentation that walks through the differences:
Edited by Wayne Beaton