Changes between Version 31 and Version 32 of WikiStart


Ignore:
Timestamp:
Oct 2, 2010, 5:36:07 PM (9 years ago)
Author:
mnot@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v31 v32  
    11= HTTPBIS WG Wiki =
    22
    3 This is the wiki of the IETF HTTPBIS Working Group. See also the links above to our issues list, document sources, etc.
     3This is the wiki of the IETF HTTPBIS Working Group. We're [http://www.ietf.org/html.charters/httpbis-charter.html chartered] to revise and clarify RFC2616 -- the HTTP 1.1 specification -- to improve interoperability and security.
    44
    5 == Relevant Reading ==
    65
    7  * [http://www.ietf.org/NOTEWELL.html NOTE WELL] - ALL contributors and participants MUST read
    8  * [http://www.ietf.org/html.charters/httpbis-charter.html Charter]
    9  * [http://tools.ietf.org/wg/httpbis/ Drafts]
    10  * [http://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/diffs/ Document changes]
    11  * Issue and document changes - [http://trac.tools.ietf.org/wg/httpbis/trac/timeline?ticket=on&changeset=on&milestone=on&max=50&daysback=90&format=rss RSS], [http://twitter.com/httpbis Twitter]
     6== Deliverables ==
    127
    13 == Discussion ==
     8The HTTP specification has been split up into several drafts for readability and modularity; see the [http://tools.ietf.org/wg/httpbis/ Drafts] directory for a snapshot. Related material includes:
    149
    15  * [http://lists.w3.org/Archives/Public/ietf-http-wg/ Mailing list]
    16  * [xmpp://httpbis@jabber.ietf.org?join XMPP/Jabber chat] ([http://jabber.ietf.org/logs/httpbis/ archives])
     10 * [http://trac.tools.ietf.org/wg/httpbis/trac/browser Subversion repository]
     11 * [http://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/diffs/ Document changes], also in [http://trac.tools.ietf.org/wg/httpbis/trac/timeline?ticket=on&changeset=on&milestone=on&max=50&daysback=90&format=rss RSS] and on [http://twitter.com/httpbis Twitter]
     12 
     13
     14== Issue Handling ==
     15
     16Issues with the specifications are kept in our [http://trac.tools.ietf.org/wg/httpbis/trac/report ticket tracker].
     17
     18We have two basic types of issues; Design ([http://trac.tools.ietf.org/wg/httpbis/trac/report/9 open issues]) and Editorial ([http://trac.tools.ietf.org/wg/httpbis/trac/report/10 open issues]).
     19
     20Design issues need to be discussed by the Working Group to reach consensus. This generally happens on the mailing list when the issue is raised, but the editors sometimes incorporate a proposed resolution to a design issue in a draft, so that the WG can see it in-situ. Such tickets aren't fully closed until the group confirms the proposal after it is published; you can see [http://trac.tools.ietf.org/wg/httpbis/trac/report/15 a list of such tickets here].
     21
     22Editorial issues can be resolved by the editors without consultation with the group, although sometimes an editor will poll the group for advice.
     23
     24
     25== Participate ==
     26
     27As with all IETF Working Groups, almost all discussion and decisions are made on our [http://lists.w3.org/Archives/Public/ietf-http-wg/ mailing list]. Joining this list is "joining" the Working Group, and is the best way to participate.
     28
     29We meet at least twice a year at [http://www.ietf.org/meeting/ IETF meetings]; see also  [http://trac.tools.ietf.org/wg/httpbis/trac/browser/wg_materials materials from past meetings].
     30
     31We use a [xmpp://httpbis@jabber.ietf.org?join XMPP/Jabber channel] ([http://jabber.ietf.org/logs/httpbis/ archives]), but usually just during physical meetings.
     32
     33ALL contributors and participants in the Working Group (i.e., on the mailing list and in physical meetings) MUST read and understand the [http://www.ietf.org/NOTEWELL.html NOTE WELL] statement.
     34