Create summary of the four archetypes categories discussed
- Business-to-business (B2B) Open Source – My opinion is that we won’t see many if any of these kind of projects. I don’t believe we will be the host for the next Android or Chromium project.
- Multi-Vendor Infrastructure – Similar to #1 (closed), I doubt SA Open will be chosen for this kind of project.
- Rocket Ship to Mars – While I doubt any of our projects will be as aspirational as the name of this archetype suggests, we may have some ambitious efforts that may be standards related or come out of some other organization such as humanitarian activities.
- Controlled Ecosystem – This may be similar to #1 (closed) and #2 (closed) and be less likely within SA Open.
- Wide Open – I can imagine these kind of projects arising within IEEE. They would likely not be standards related but perhaps they could be.
- Mass Market – Like #1 (closed), #2 (closed), and #4 (closed), these kind of projects probably won’t be common on SA Open.
- Specialty Library – I can imagine a number of IEEE standards where a library of functions related to a standard would be applicable.
- Trusted Vendor – I think this is more of a commercial activity like #1 (closed), #2 (closed), #4 (closed), and #6 (closed) and would be less common.
- Upstream Dependency – I think this could be common when the dependency is a standard.
- Bathwater – I could see a number of standards projects where someone writes reference or example code and then throws it over the wall.
Josh: Over all, I think we should focus on: 3, 5, 7, 9, and 10 first and then take a stab at the others
Evan suggested combining some of the above and addressing a limited number of them.
Josh: 3 and 5 can be combined, 7 and 9 can be combined and 10 would be separate.
After more discussion: Evan suggested also combining 1,2 and 4 as well for a total of 4 project categories.