AB/2024 Priorities: Difference between revisions
< AB
Chriswilson (talk | contribs) |
Tantekelik (talk | contribs) →Vision: all statement blockers |
||
(14 intermediate revisions by 4 users not shown) | |||
Line 12: | Line 12: | ||
** what CGs do and how they do it | ** what CGs do and how they do it | ||
** https://github.com/w3c/AB-memberonly/issues/81 | ** https://github.com/w3c/AB-memberonly/issues/81 | ||
** work in progress: https://github.com/w3c/AB-memberonly/blob/main/documents/Incubation.md | |||
** previously wiki page to gather prior work, blog posts, questions: [[Incubation]] | |||
* | |||
* | |||
** | |||
== Vision == | == Vision == | ||
* Leads: Tzviya, Chris | * Leads: Tzviya, Chris, Tantek | ||
* Participants: | * Participants: [[AB/VisionTF|Vision TF]] | ||
* Summary: Publish the Vision, bring it forward in W3.org/W3C documentation. | * Summary: Publish the Vision, bring it forward in W3.org/W3C documentation. | ||
* Goals: | * Goals: | ||
** | ** Main list: [[AB/VisionTF#Goals]] | ||
** | ** Remaining key items: | ||
** | *** Triage and resolve all Statement-blocker issues (including potential FOs) | ||
*** Publish a Statement draft for approval by the AC | |||
*** Official W3C Statement published | |||
* Related issues and references: | * Related issues and references: | ||
** https://w3c.github.io/AB-public/Vision | ** https://w3c.github.io/AB-public/Vision | ||
Line 34: | Line 30: | ||
== Interoperability and the Role of Independent Implementations == | == Interoperability and the Role of Independent Implementations == | ||
AKA "3Is" project. | |||
* Leads: Tantek | * Leads: Tantek | ||
* Participants: Chris, Florian, Wendy, QingAn | * Participants: Chris, Florian, Wendy, QingAn | ||
Line 42: | Line 39: | ||
** Document risks, e.g. monoculture, from the entirety of a spec (e.g. WebSQL), to a common library every implemementation uses (Fonts?) | ** Document risks, e.g. monoculture, from the entirety of a spec (e.g. WebSQL), to a common library every implemementation uses (Fonts?) | ||
** Role of tests and test suites | ** Role of tests and test suites | ||
* Related issues and references: | * Related work, issues, and references: | ||
** https://github.com/w3c/AB-memberonly/issues/81#issuecomment-1658902979 | ** [[interoperable]] | ||
** [[independent]] | |||
** [[implementation]] | |||
** context regarding [[incubation]]: https://github.com/w3c/AB-memberonly/issues/81#issuecomment-1658902979 | |||
== Improving W3C community == | == Improving W3C community == | ||
Line 60: | Line 60: | ||
== Exploring New Horizons == | == Exploring New Horizons == | ||
* Leads: Dingwei, ? | * Leads: Dingwei, ? | ||
* Participants: Igarashi, Chris | * Participants: Igarashi, Chris, Song | ||
* Summary: Discuss how we identify "what" new technologies come to W3C, and how we identify important coming tech trends and help bring tech to incubation. | * Summary: Discuss how we identify "what" new technologies come to W3C, and how we identify important coming tech trends and help bring tech to incubation. | ||
* Goals: | * Goals: | ||
Line 67: | Line 67: | ||
** "what" trends should come to W3C, how do we identify them | ** "what" trends should come to W3C, how do we identify them | ||
** work with the Team to achieve this (incubation funnel) meetings and AC spring meeting. | ** work with the Team to achieve this (incubation funnel) meetings and AC spring meeting. | ||
* Related issues and references: | |||
** https://github.com/w3c/AB-memberonly/issues/204 | |||
== New Meeting Formats == | |||
* Leads: Chris (interim) | |||
* Participants: Seth, Avneesh, Florian, Tantek, igarashi | |||
* Summary: Form a task force to review current meeting formats and explore potential changes to how the W3C Community meets. | |||
* Goals: | |||
** Improve attendance and participation in W3C events | |||
** Find ways to make in-person time more effective for participants | |||
** Better consideration of cultural and geographic factors in meeting planning | |||
** Explore topics like co-location with conferences/industry events, member meetings | |||
** Addressing the needs of new attendees, working groups, long-time participants, etc. | |||
* Related issues and references: | |||
** https://github.com/w3c/AB-memberonly/issues/216 | |||
** https://lists.w3.org/Archives/Member/w3c-ac-forum/2024AprJun/0011.html | |||
= Ongoing Priorities = | = Ongoing Priorities = | ||
Line 98: | Line 114: | ||
** revamping the W3C Ombuds program and dispute resolution documentation | ** revamping the W3C Ombuds program and dispute resolution documentation | ||
** continued revision of the CoC | ** continued revision of the CoC | ||
== Goals for Diversity and Inclusion == | |||
* Leads: Avneesh, Wendy | |||
* Participants: | |||
* Summary: high level project management so that AB+W3C have direction in next steps to take | |||
* Goals: | |||
** Identify short-, medium- and long-term goals for DEI (and what short/medium/long mean) | |||
** Consolidate existing tracking of DEI, and identify what further tracking we should be doing and how to do it | |||
= Previously = | = Previously = | ||
* [[AB/2023_Priorities]] | * [[AB/2023_Priorities]] |
Latest revision as of 16:29, 15 July 2024
AB Priorities for 2023-2024
Incubation
- Leads: Chris
- Participants: Florian, Tantek
- Summary: Start defining "how" we bring new work to W3C and how we move work through incubation into the REC track.
- Goals:
- Define expectations & guidance for advancing work in incubation and when to move it out (both to a WG or to a closing report)
- Related issues and references:
- revise chartering Process and practices (possible input into Process)
- what CGs do and how they do it
- https://github.com/w3c/AB-memberonly/issues/81
- work in progress: https://github.com/w3c/AB-memberonly/blob/main/documents/Incubation.md
- previously wiki page to gather prior work, blog posts, questions: Incubation
Vision
- Leads: Tzviya, Chris, Tantek
- Participants: Vision TF
- Summary: Publish the Vision, bring it forward in W3.org/W3C documentation.
- Goals:
- Main list: AB/VisionTF#Goals
- Remaining key items:
- Triage and resolve all Statement-blocker issues (including potential FOs)
- Publish a Statement draft for approval by the AC
- Official W3C Statement published
- Related issues and references:
Interoperability and the Role of Independent Implementations
AKA "3Is" project.
- Leads: Tantek
- Participants: Chris, Florian, Wendy, QingAn
- Summary: Define the role of independent interoperable implementations - in incubation, transition to REC track and chartering, transition from CR to REC, etc.
- Goals:
- Document which user problems we are solving (being able to switch implementations, lowering switching friction)
- More precise definitions for interoperable, independent, and implementation
- Document risks, e.g. monoculture, from the entirety of a spec (e.g. WebSQL), to a common library every implemementation uses (Fonts?)
- Role of tests and test suites
- Related work, issues, and references:
Improving W3C community
- Leads: Wendy
- Participants: Tzviya, Igarashi, Chris
- Summary: moderating, member meetings, and working well together - including AC facilitation/moderation, work mode improvements, community building, potentially DEI
- Goals:
- explore AC moderation/facilitation efforts
- community-building within W3C
- improvements to the workmode to improve inclusion (automated transcription, etc.)
- improve AC inclusion (I should like to seperate this from the workmode issue Since less inclusion of AC is not just the work mode issue. I have a concern on less participation of AC led meetings and AC spring meeting.
- "welcome to the AC", "welcome to W3C": improved documentation and experience for new members (AC 101 documentation, glossary of terms, etc.)
- Related issues and references:
Exploring New Horizons
- Leads: Dingwei, ?
- Participants: Igarashi, Chris, Song
- Summary: Discuss how we identify "what" new technologies come to W3C, and how we identify important coming tech trends and help bring tech to incubation.
- Goals:
- help bring new tech to incubation
- identifying upcoming technology trends
- "what" trends should come to W3C, how do we identify them
- work with the Team to achieve this (incubation funnel) meetings and AC spring meeting.
- Related issues and references:
New Meeting Formats
- Leads: Chris (interim)
- Participants: Seth, Avneesh, Florian, Tantek, igarashi
- Summary: Form a task force to review current meeting formats and explore potential changes to how the W3C Community meets.
- Goals:
- Improve attendance and participation in W3C events
- Find ways to make in-person time more effective for participants
- Better consideration of cultural and geographic factors in meeting planning
- Explore topics like co-location with conferences/industry events, member meetings
- Addressing the needs of new attendees, working groups, long-time participants, etc.
- Related issues and references:
Ongoing Priorities
Process & governance documents
- Leads: Florian
- Participants: Elika, Chris, Process CG
- Summary: Update and maintain the Process and other governance-related documents
- Goals:
- Council Process follow ups
- Process simplification
- Director-free Patent Policy
- Director-free WHATWG-MoU
- Chartering (Depending on input from the Incubation priority project)
Board Liaison
- Leads: Elika, Tantek
- Participants: N/A
- Summary: Ensure the AB and Board have open and productive communications
- Goals:
- Facilitate healthy cooperation between the Board and the AB
- Support the Board
- Help triage topics into the right venue
- Relay requests / concerns from the Membership
Maintain and Improve the Code of Conduct
- Leads: Tzviya, Wendy
- Participants: PWE CG (including Chris)
- Summary: Maintain the Code of Conduct
- Goals:
- revamping the W3C Ombuds program and dispute resolution documentation
- continued revision of the CoC
Goals for Diversity and Inclusion
- Leads: Avneesh, Wendy
- Participants:
- Summary: high level project management so that AB+W3C have direction in next steps to take
- Goals:
- Identify short-, medium- and long-term goals for DEI (and what short/medium/long mean)
- Consolidate existing tracking of DEI, and identify what further tracking we should be doing and how to do it