Strat edits #625
Strat edits #625
Conversation
|
cc @ianbjacobs for the CG bits. |
| <li>Monitor responses from the industries, SDOs (including W3C CGs, TPAC Breakout sessions, Workshops, Liaison Reports), and Open Source communities on those trends. Work with W3C Team to invite W3C Liaisons to SDOs or other insightful SDOs experts, reporting back on potential areas of investigations;</li> | ||
| <li>Prioritize the trends and propose organizing Workshops, publishing Reports or creating topic oriented Task Forces, for further elaboration;</li> | ||
| <li>Propose chartering potential topics to the Strategy Funnel at the stage of incubation;</li> | ||
| <li>Monitor responses from the industries, SDOs (including W3C CGs, TPAC Breakout sessions, <a href='https://www.w3.org/events/workshops/'>Workshops</a>, <a href='https://www.w3.org/liaisons/'>Liaison Reports</a>), and Open Source communities on those trends. Work with W3C Team to invite W3C Liaisons to SDOs or other insightful SDOs experts, reporting back on potential areas of investigations;</li> |
There was a problem hiding this comment.
| <li>Monitor responses from the industries, SDOs (including W3C CGs, TPAC Breakout sessions, <a href='https://www.w3.org/events/workshops/'>Workshops</a>, <a href='https://www.w3.org/liaisons/'>Liaison Reports</a>), and Open Source communities on those trends. Work with W3C Team to invite W3C Liaisons to SDOs or other insightful SDOs experts, reporting back on potential areas of investigations;</li> | |
| <li>Monitor responses from the industries, SDOs (including W3C CGs, TPAC Breakout sessions, <a href='https://www.w3.org/events/workshops/'>Workshops</a>, <a href='https://www.w3.org/liaisons/'>Liaison Reports</a>), and Open Source communities on those trends. When asked by the W3C Team, work with them to invite W3C Liaisons to SDOs or other insightful SDO experts, reporting back on potential areas of investigations;</li> |
There was a problem hiding this comment.
Not sure about "When asked by the W3C Team". The IG can certainly propose.
There was a problem hiding this comment.
It's true that anyone can propose ideas to the Team. Do we need charter language in that case? How about deleting the second sentence? That makes it clearer that the scope of activity of the IG is to monitor the ecosystem, which seems like the true focus here.
Co-authored-by: ianbjacobs <[email protected]>
Co-authored-by: ianbjacobs <[email protected]>
| <li>Prioritize the trends and propose organizing Workshops, publishing Reports or creating topic oriented Task Forces, for further elaboration;</li> | ||
| <li>Propose chartering potential topics to the Strategy Funnel at the stage of incubation;</li> | ||
| <li>Monitor responses from the industries, SDOs (including W3C CGs, TPAC Breakout sessions, <a href='https://www.w3.org/events/workshops/'>Workshops</a>, <a href='https://www.w3.org/liaisons/'>Liaison Reports</a>), and Open Source communities on those trends. Work with W3C Team to invite W3C Liaisons to SDOs or other insightful SDOs experts, reporting back on potential areas of investigations;</li> | ||
| <li>Prioritize the trends and propose to the W3C Team <a href='https://github.com/w3c/strategy/labels/workshop'>organizing Workshops</a>, publishing Reports or creating topic oriented Task Forces, for further elaboration;</li> |
There was a problem hiding this comment.
I'm not sure of adding "to the W3C Team" here. I think that's implied for Workshops, so not necessary to mention; but publishing Reports or creating Task Forces of this IG doesn't seem to need to be proposed "to the Team" -- the IG can just do it.
There was a problem hiding this comment.
I think there's no need to mention creation of task forces in the charter. The IG can organize its work however it wants.
|
I'm closing this pull request. There is new wording in w3c/strategy#451 (comment) which is the result of conversations with Ian and Dingwei. |
This clarifies the motivation/background section:
As a side, it also adds useful links in the scope section.
cc @dennis-dingwei for review
This is part of w3c/strategy#451