W3C home > Mailing lists > Public > public-w3process@w3.org > August 2014

Feedback on Process-20140801 section 2

From: <timeless@gmail.com>
Date: Tue, 12 Aug 2014 18:44:15 -0400
Message-ID: <20140812224415.25579611.4250.1975@gmail.com>
To: public-w3process@w3.org
I'm sorry that I didn't send this feedback on [8] earlier, I've been busy. 

I sent notes about ProcessTransition2014 [1], Ian has made some changes [2] to it in response.


‎{Section 2 Members/AC/Team/AB/TAG}
> Advisory Committee representatives have appeal powers for some processes described in this document.

*ambiguous*
If those appeal powers are described in this document, it should say "as described in this document"
If the powers are elsewhere, it should say where


> However, an individual MAY join W3C as an Affiliate Member. 
Affiliate Member should be linked


> Use of the W3C Member logo on promotional material and to publicize the Member's participation in W3C. For more information, please refer to the Member logo usage policy described in the New Member Orientation [MEM4].

The logo usage policy isn't described in [MEM4], it's at [4]

Ian is increasingly reluctant to have detailed URIs in the proc doc since the W3 site is likely to change. W3 can try to maintain the URIs. but...

What we did here clearly failed miserably. I think the right approach is an Index page for links And possibly have that page include a list of things linking to it for each term so that people are aware


> In Working Groups, Interest Groups, and Coordination Groups.
> In Workshops and Symposia;
> On the Team, as W3C Fellows.

That first <.> should be a <;>


> In the case (described in paragraph 5g of the Membership Agreement), where a Member organization is itself a consortium, user society, or otherwise has members or sponsors, the organization's paid staff and Advisory Committee representative exercise all the rights and privileges of W3C membership. 

Please link where is paragraph 5g to [5]


>  In addition, the Advisory Committee representative MAY designate up to four (or more at the Team's discretion) individuals who, though not employed by the organization, MAY exercise the rights of Member representatives. 

s/the/each/;

Do I assume that the AC rep may change who is designated? and is there a process that monitors these designations?

I've scanned (find-in-document) and haven't found anything on this.


> Arbitration in the case of further disagreement is governed by paragraph 19 of the Membership Agreement. 

Should link to [6] 


> 2.1.3 Advisory Committee (AC)

There needs to be a line saying that organizations should inform w3 when their AC is no-longer employed and should identify a replacement :/


> This list is read-only for Advisory Committee representatives.

That <is> should probably use RFC terminology


> The Team organizes a face-to-face meeting for the Advisory Committee twice a year. 

Should that use RFC terminology?
(it also doesn't appear in the Team section of the document)


> The Team MUST announce the date and location of each Advisory Committee meeting no later than at the end of the previous meeting; one year's notice is preferred.

Should <is preferred> be RFC "should"?


> Note: W3C is not currently incorporated. For legal contracts, W3C is represented by three "Host" institutions: 

That's stale. I'd suggest linking to the Member Agreement [7] and the term "Hosts".


> a public discussion (not just input) list for issues of Web architecture. The TAG will conduct its public business on this list.

Change <will> to rfc <should>?

Does the TAG have the appointed and elected churn both high/both low on a given year? or does it alternate?
Is the turnover in a given year is 1-someone and 2-someone with the other as 2/3, or is it 2/2 and 1/3 ?
Because I think the document doesn't specify, and I shouldn't have to figure it out :)

Ian notes that AB and TAG are talking about changing TAG participation in any case. If that's likely, perhaps a warning could be inserted about that?


> When more than one individual is involved, the verifiable random selection procedure described below will be used to choose one person for continued participation.

Technically you could have multiple concurrent incompatibilities
That sentence probably would need work
(If e.g. companies A, B, C and D all have seats, and A and B merge and C and D merge)


> If after 30 days the situation has not been resolved, the Chair will declare one participant's seat to be vacant.

Does Chair here mean W3C, AB, or TAG?
(it probably means W3C)

Actually, that whole thing is confusing
In the simple case where one person manages to be AB+TAG, we probably want the <W3C> Chair to declare one of the person's two seats vacant
But the lone sentence as written seems to allow for some Chair to just vacate a seat, and then contemplate the next sentence

1. It'd be good to cover the multiple person case before the single person case
2. Clarity


> Less than the number of available seats, Calls for Nominations are issued until a sufficient number of people have been nominated. Those already nominated do not need to be renominated after a renewed call.

It'd be nice to say "don't need to be renominated as they will be considered in the election"
or 
-> Less than the number of available seats, Calls for Nominations are issued until a sufficient number of people have been nominated (including previous rounds of nominations for the same election)

Dying/entering a coma (of some duration?) should be treated as resigning
(Also the generic "no longer being in the employ of any Member company within the last 30 days" or something like that (in case text for dying/coma fails to catch things -- but even this is hard to construct correctly)


> When an appointed TAG seat is vacated, the Director MAY re-appoint someone immediately, but no later than the next regularly scheduled election.

The <no later than> is odd
It feels like a MUST/SHOULD
What happens if the director doesn't?
ok... I think this is enough content for a single message


[1] https://www.w3.org/wiki/ProcessTransition2014
[2] https://www.w3.org/wiki/index.php?title=ProcessTransition2014&diff=75757&oldid=75351
[3] http://www.w3.org/2014/Process-20140801/#tr-end
[4] https://www.w3.org/Member/promotion#logos
[5] http://www.w3.org/2009/12/Member-Agreement#also-consortium
[6] http://www.w3.org/2009/12/Member-Agreement#arbitration
[7] http://www.w3.org/2009/12/Member-Agreement
[8] ‎http://www.w3.org/2014/Process-20140801/
Received on Tuesday, 12 August 2014 22:44:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:11 UTC