AB/2014-2015 Priorities: Difference between revisions

This document enumerates priorities for the W3C's Advisory Board, including proposed or candidate tasks/projects that have not been prioritized as well as agreed priorities for various tasks.

This document is a DRAFT, i.e. it is a WorkInProgress (WIP). Feedback is welcome, preferably by directly editing this document or by sending feedback to the public-w3process@w3.org e-mail list (archive) with a Subject: prefix of [ABPriorities].

Non-prioritized Candidate Tasks 2014-2015

At their June face-to-face meeting, the Advisory Board brainstormed and created a draft list of candidate priorities for 2014-2015, for the (new) AB to discuss and prioritise over the summer.

Prioritizing the current investments of W3C

1. Identify work that is going on the wrong track or not destined for success. The AB could develop approaches for W3C to identify work that is not destined for success (for any of several possible reasons - competing alternatives, lack of adoption, not solving a real problem, missed the time window). Alternatively, the AB could analyse our portfolio and identify specific WGs that are not destined for success. [JJ, CMN] H [DWS] M
2. Consortium Priorities/Maximise Resources. How - at a time of limited resources and greater demands - should W3C maximise the impact of its resources. What are the most important priorities for the consortium? [DWS] L
3. What are the most important priorities for the Web? Be forward looking about future priorities for the Web and map it back to current focus of W3C. [JJ, DWS] H [Lead] JJ (DWS, merge with the one below)
4. What are the most important priorities for the Web and W3C. This is similar to the above project, but focuses more narrowly on the priorities as it relates to W3C as an organisation, or how it relates to our current Membership. [CMN] H
5. Survey the Membership on their priorities [CMN] H [Lead] CMN [DWS] L (not a strong believer in surveys)[VGa] H

Overall structure of the W3C

1. Long-term stability. Financial: see the June 2014 Consolidated Financial Report for data about 2014 budget deficit and projection for 2015 deficit, Process: [CMN] H
   1. Is the Consortium's current heavy weight structure that was created in 1994 still needed now? CMN: We don't use the process we had in 1995 or even in 2005. This question is rhetorically sound but irrelevant.
   2. Why not move to an open working group participation structure like the IETF uses to enable broader participation? (Broader participation is apparently a key goal of the so-called Webizen proposal.
2. Membership Fees
   1. What changes in the Consortium's organizational structure could and should be made to help reduce Membership fees? CMN: This is the same as prioritising overall work.
   2. Full, for-profit European Members pay approximately $25K USD per year more than their US counterparts What needs to be done to reduce European membership fees to be equivalent to US membership levels? [CMN] H [DWS] M

Improving the W3C Process broadly, or best practices to implement the process

1. Improve agility unrelated to W3C Process. In many cases, WGs seem to overly burden themselves with requirements, slowing down work in ways that the process does not require. This could be, for example, by bureaucratically running the WG process - asking for greater consensus at intermediate stages than the process requires. How can we improve agility without changing the process? How do we manage the necessary bureaucracy to the rare defined places where it is needed? How do we train Chairs on this? [CMN, JJ, MC] H [DWS] M
2. Work-mode (related to above project). What are Best Practices of WG work-mode that enhance agility? [DWS] M
3. W3C Process Revision 2015. In the AB meeting we discussed an approach to produce the next revision of the Process in time for approval at the May 2015 AC meeting. This needs to be re-evaluated due to delays introduced by the Formal Objection to the 2014 process revision. [CMN, JJ, DWS] H [participate] CMN
4. Supergroups. Continuation of last year's project. Two main focus areas. (1) Getting the "easy" changes incorporated into W3C Process 2015 (see project 4). (2) Determining which harder changes are worth doing and convening the stakeholders to work on them. [DWS] M
5. Trademark Policy and Licensing. Continuation of last year's project. First focus is to understand whether the industry would align with utilising the "W3C HTML5" terminology to determine whether trademarking would be helpful or embarrassing due to apathy. [JJ, MC, TÇ, DWS] H [CMN] 0 [M} Lead
6. Meetings and Workshops work mode using 1) web tools (e.g. WebEx, Moderator, Etherpad) and 2) the Process and a culture for following it - e.g. providing adequate notice for people to attend events. This continues and expands the dialog we started last year. It relates to project 2, but is more narrowly focused. [MC] H
7. The graveyard of /TR. It is very challenging, as a user, to understand the current status of specifications - particularly, if a given TR has been superceded, or is in the process of being superceded by current works-in-progress, or if it is a dead end. Something along the lines of the warning on http://tabatkins.github.io/specs/respimg/ would be good; a more dynamically-updatable "status" section for recommendations would be another idea. [DWS] M
8. Provenance of spec texts. Assess whether we need to do more work on process or best practices to ensure that spec texts that enter Working Groups are coming with sufficient IP coverage. [CMN, DWS] H

AB role and function

1. Open AB. Continuation of last year's project. Focus on ac-forum/process CG discussions of ways to further open the AB. [TÇ] ? [DWS] L
2. How does the AB better represent the AC? In the threads related to the structure of the AB, a question arose whether the AC even needs an AB - perhaps the AC can represent itself in dialog with the Team. A common response - that the AB can be a cohesive and representative team of a larger AC - caused the AB to ask what mechanisms it has available to ensure that it is truly representing the broad interests of the AC. [JJ] H [DWS] L
3. Can we clearly articulate the role of the AB? We have the impression that the AC does not understand the role of the AB, so that raises the question how to better articulate it. [DWS] M

Voting

1. Improve the quality of information that the W3C team has about the goals and priorities of W3C Members from elections. [DWS] M
2. TAG exclusionary rules removal [JJ, CMN] H (to address the issue, but I would not prejudge the outcome) [DWS] L
   1. See the Is the TAG structure harmful? email thread on www-tag
3. Create a proposal to conduct several elections experimenting with different voting approaches (proposal due from Chaals in July meeting). [JJ, CMN] H [Lead] CMN (with the team) [DWS] H (but see the first above)

New demands on the consortium

1. Broader industry collaboration on the Open Web Platform. W3C is a consortium that focuses on technical standards for the Web, but naturally comprehends weaknesses that the OWP has. Some of these weaknesses (e.g. developer tools) are beyond the scope of W3C. Can the AB propose means for industry to collaborate (with or without W3C) to address these weaknesses. [JJ] H [Lead] JJ [DWS] M
2. New stakeholders at W3C. The OWP is increasingly being adopted by vertical industries, but W3C as a small organisation does not have the connectivity to find key people in those industries to join W3C. Can the consortium, with the leadership of the AB, help introduce the value of W3C to these new stakeholders. [JJ] H [Lead] JJ CMN: It would be helpful to introduce such people to how W3C already works, but that might be a different topic. (DWS connect to CI.3)
3. Tools and process to allow W3C to make all W3C deliverables consistent from a technical and strategic point of view. In other words, how does W3C promote synchronization between activity leaders, editors and chairs across working groups. For example, if "Promises" is the right technology base for the future, how do we ensure that this is adopted consistently? This may require some coordination with the TAG. [MC] H

Operations

1. Build Chairs community. Assign buddies (new/experienced chairs). Update the Guide. FAQ. Improve how we express gratitude. Mention them on Intro Day (speed dating). [CMN] H [DWS] M
2. AC Meeting prep. Continuation of last year's project. [DWS] H (making sure we run the place well and use the AC reps and their time wisely)

Agreed Task Priorities 2014-2015

(DWS, I used H=High -> we should do it now, M=Medium -> we should do this sometime, L=Low or not marked -> not sure if we should or ever will get to this)

High Priority

Medium Priority

Low Priority

Little to No interest