Difference between revisions of "AB"

From W3C Wiki
Jump to: navigation, search
(Suggestions: move some background to history.)
(Twitter access shared, no longer unofficial, move mtgs section down lower)
Line 12: Line 12:
 
=== Use of Github at W3C ===
 
=== Use of Github at W3C ===
 
* See [[Github]].
 
* See [[Github]].
 
== Meetings ==
 
Taxi sharing for meetings is organized on the wiki: [[MeetingTaxis]]
 
  
 
== Twitter Account ==
 
== Twitter Account ==
Freshly created 2013-06-04, there's an unofficial [https://twitter.com/w3cab @W3CAB] Twitter account.
+
The Advisory Board has a Twitter account: [https://twitter.com/w3cab @W3CAB]
  
It would be great to grant permission to every AB member to post anything regarding AB-related matters.
+
Nearly the entire AB has access and can post anything regarding AB-related matters. The methodology is to empower individual responsibility and trust by default, especially in such a small group. This method has worked well with the [[CSSWG]] (any CSSWG member may "have the keys" to [https://twitter.com/csswg @CSSWG]) and it's been hugely successful in engaging the broader developer community.  
  
The methodology is to empower individual responsibility and trust by default, especially in such a small group. This method has worked well with the [[CSSWG]] (any CSSWG member may "have the keys" to [https://twitter.com/csswg @CSSWG]) and it's been hugely successful in engaging the broader developer community.  
+
If you are a [http://www.w3.org/2002/ab/ member of the AB], contact [[User:Tantekelik|Tantek Çelik]] on a secure communications channel and he'll gladly share access to @W3CAB.
  
 
+
* 2013-09-18 access broadly shared with AB members
If you are a [http://www.w3.org/2002/ab/ member of the AB], contact [[User:Tantekelik|Tantek Çelik]] on a secure communications channel and he'll gladly share access to @W3CAB.
+
* 2013-06-04 @W3CAB Twitter created.
  
 
== Suggestions ==
 
== Suggestions ==
Line 30: Line 27:
  
 
=== Minor Process Tweaks ===
 
=== Minor Process Tweaks ===
 
 
The Process document hasn't really been maintained in many years. There's talk of overhauling the Process, but meanwhile, how about making some simple changes that address particularly frustrating points in the Process?
 
The Process document hasn't really been maintained in many years. There's talk of overhauling the Process, but meanwhile, how about making some simple changes that address particularly frustrating points in the Process?
  
Line 42: Line 38:
 
* ...
 
* ...
 
and sign it with <nowiki>~~~~</nowiki> (four tildas)
 
and sign it with <nowiki>~~~~</nowiki> (four tildas)
 +
 +
== Meetings ==
 +
Taxi sharing for meetings is organized on the wiki: [[MeetingTaxis]]
  
 
== Background ==
 
== Background ==
Line 53: Line 52:
 
== See Also ==
 
== See Also ==
 
* [http://www.w3.org/2002/ab/ Official W3C Advisory Board home page]
 
* [http://www.w3.org/2002/ab/ Official W3C Advisory Board home page]
* [https://twitter.com/w3cab Unofficial W3C Advisory Board Twitter]
+
* [https://twitter.com/w3cab W3C Advisory Board Twitter]

Revision as of 22:28, 18 September 2013

This article is a stub. You can help the W3C wiki by expanding it.

The AB refers to the W3C Advisory Board.

Projects

W3C Process

W3C process improvements are discussed in the community group:

See process for more details.

Use of Github at W3C

Twitter Account

The Advisory Board has a Twitter account: @W3CAB

Nearly the entire AB has access and can post anything regarding AB-related matters. The methodology is to empower individual responsibility and trust by default, especially in such a small group. This method has worked well with the CSSWG (any CSSWG member may "have the keys" to @CSSWG) and it's been hugely successful in engaging the broader developer community.

If you are a member of the AB, contact Tantek Çelik on a secure communications channel and he'll gladly share access to @W3CAB.

  • 2013-09-18 access broadly shared with AB members
  • 2013-06-04 @W3CAB Twitter created.

Suggestions

Suggestions for the AB.

Minor Process Tweaks

The Process document hasn't really been maintained in many years. There's talk of overhauling the Process, but meanwhile, how about making some simple changes that address particularly frustrating points in the Process?

  • Allowing REC to refer to CR (treating PR as a transitional phase, like LC). fantasai 04:52, 7 June 2013 (UTC)
    • Agreed. I'll see what I can do to help this along. - Tantek Çelik 14:30, 8 July 2013 (UTC)
    • Inter-W3C-spec normative referencing policy is apparently not an explicit part of the Process Document. See CG W3Process issue 33 for more info/updates on this. - Tantek Çelik 14:54, 8 July 2013 (UTC)
  • Creating a "Proposed Edited Candidate Recommendation" stage (or pick a better name) to allow CRs to be updated without going back to Working Draft. This would be identical to LC--just a renaming of an existing process--so qualifies as a Dead Simple Change. fantasai 04:52, 7 June 2013 (UTC)
    • What about simply combining LC and CR, and allowing a document in that phase to be updated and stay at that phase? - Tantek Çelik 14:30, 8 July 2013 (UTC)

Add Your Suggestion Here ...

  • ...

and sign it with ~~~~ (four tildas)

Meetings

Taxi sharing for meetings is organized on the wiki: MeetingTaxis

Background

Background about this page.

I (Tantek Çelik) ran for the AB on a platform of greater openness in how we do things. As part of that, feel free to add your suggestions for improving the AB and W3C Process as a whole here and I'll see what I can about them. I'm going to encourage other AB members to similarly consider using input from the wiki as another source. Thanks, - Tantek Çelik 04:44, 7 June 2013 (UTC)

Resources

See Also