Comments (38)
Also related to the item in the Guide: w3c/Guide#185.
from w3process.
That's an easy addition if we want to make it. Anyone has a reason not to? Not knowing who the chair will be until fairly late in the process can happen, but by the time we get to the AC Review, we're trying to launch the group, so we need to know anyway.
from w3process.
Anyone has a reason not to?
Yes. Two different ones.
Publishing data in two places - in this case publishing the chairs both in charters and in the database - creates redundancy that leads to inconsistency. We would get better consistency by publishing the chairs in only one place.
Additionally, while I generally support the efforts to give the community more input into the chair selection process, there may be some advantages to not having personnel discussions in public fora. So long as chairs serve at the pleasure of Team, as they do now, perhaps we should continue to enjoy those advantages, and continue to allow a charter to be reviewed without naming chairs. Perhaps that only happens in exceptional cases, but I prefer the option exist.
from w3process.
continue to allow a charter to be reviewed without naming chairs
I don't think I've ever been involved in a TTWG rechartering that didn't name chairs. Is it normal for charter reviews to omit chairs?
from w3process.
Responding more directly to the issue: if the Team can change the Chairs independently of rechartering, and no AC review is needed to do so, then we should not even state Chairs in the Charter, let alone require them - in that case no Process change is needed but the charter template should be modified to remove the Chairs and possibly the Guide would need checking to ensure that it doesn't suggest they should be included.
That's a big "if" though! Given that current working practice is to include Chairs in Charters, I suspect that most AC reps consider that they do have the option to object to a Charter based on the selection of Chair, at least in principle.
from w3process.
There has been an unwritten expectation that Chairs be named in proposed charters. The Team has sent however a few charters without proposed chairs in the past. I believe the latest example is the PAT WG charter in 2022, which generated several formal objections because of lack of chairs/team contact.
from w3process.
Indeed.
Particularly for initial group charters, I think it helps engender confidence to know who the chair(s) are intended to be. Yes, the Team could theoretically change them at any time - but this is still a Team Decision that can be Formally Objected to (IIUC), so why not just get it out of the way all at once and make this a requirement?
from w3process.
Related Issues (20)
- "Wide review" is too easy to confuse with "horizontal review" HOT 7
- Veto by inaction HOT 16
- word order "W3C Group Draft Note" -> "Draft W3C Group Note" HOT 28
- living standard / candidate review snapshots need to address wide review issues HOT 12
- Council Composition requirements include Tim Berners-Lee, TAG life member HOT 5
- Disciplinary action HOT 3
- Stop citing the "superseded" TAG charter HOT 2
- Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" HOT 8
- Are the rules for updating Registry Definitions appropriate? HOT 23
- W3C Decision needs better cross-referencing HOT 3
- What kind of Group is for what kind of work? HOT 1
- TAG Appointment Process Shortcomings HOT 25
- AB Role in TAG Appointment HOT 13
- Are TAG Appointments mandatory for the Team to fill?
- Ground the different types of groups / maturity stages in Problem Statements HOT 4
- Strip section 6.2.2.1 “wide review” of the mailing list currently mentioned HOT 1
- Affiliation constraints on TAG membership HOT 17
- The minimum time commitment for participation in the elected bodies is undefined HOT 4
- Run link checker on Process Drafts HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from w3process.