RE: [chairs] OASIS IRC

["Wachob, Gabe" <gwachob@visa.com>]

This is a *great* step forward. I strongly encourage folks to use
realtime communications channels like IRC on a regular basis.

Several questions:

1) Why start a new IRC server/network? Freenode in particular is
*well-suited* to the uses described here and already has a number of
open standards efforts occuring there.

2) I'd strongly suggest providing logging bot for channels that want it.
Real time chat is great in the sense that it promotes highly efficient
back and forth, but suffers in that the record of discussion is often
lost. Logging bots address this issue well by copying a complete log of
channel traffic to a web archive. In addition, there are other types of
bots (e.g. a chumpbot that logs URLs and comments to those URLs and
meeting bots that allow a form of order in a big room that has an agenda
and a meeting leader, etc). 

3) Provide a way for folks like myself, who are isolated from IRC due to
http proxies, a way to access IRC. There are several methods - I
personally use CGI:IRC (cgiirc.sourceforge.net) - a web-based (no client
applet - all javascript and HTML) IRC interface. Strongly recommended. 

Once again, with the recent wiki support and now IRC support, OASIS is
taking a big step forward and I wholeheartedly encourage more
experimentation in this direction.

	-Gabe

> -----Original Message-----
> From: James Bryce Clark [mailto:jamie.clark@oasis-open.org] 
> Sent: Thursday, September 22, 2005 12:01 PM
> To: chairs@lists.oasis-open.org
> Cc: support@oasis-open.org; tc-admin@oasis-open.org
> Subject: [chairs] OASIS IRC
> 
>      In response to member requests for the functionality, 
> OASIS is running 
> an IRC server available at [irc.oasis-open.org] on both ports 6667 
> (default) and 6669.
> 
>      PURPOSE    This server is available as a convenient, transient 
> side-channel for real-time meeting coordination and similar 
> intermittent 
> unofficial communications.   It is NOT access-limited, and does NOT 
> constitute official records of the TC, nor a channel for 
> contributions of 
> work.  Contents of the IRC channels are NOT necessarily 
> spooled or archived 
> to the official TC records, during this beta phase.  Any 
> official work of 
> the TC must be placed elsewhere:  reflected in e-mail, 
> meeting minutes, 
> documents uploaded to the TC's repository or other official channels.
> 
>      USAGE     During its initial beta use, we suggest that TCs use a 
> single local channel (preface = "&") and a name string 
> identical to their 
> TC short name (main e-mail list name).
>      Thus, "&fwsi" "&soa-rm", "&wsbpel", "&ws-rx", "&xacml;" etc.
>      One can create a channel, if it is not already created, 
> simply by 
> joining the channel.  The first person to create the channel 
> will be the 
> channel's operator.  We suggest that a TC chair or their 
> designee serve as 
> operator.
> 
>      We welcome your feedback.  Please direct any questions about the 
> technical operation of the service to our IT manager, Rob 
> Figenbaum, and 
> his staff via our support address, [support@oasis-open.org] copied 
> here.   Please direct any questions about proper use of the 
> service to our 
> standards development staff at [tc-admin@oasis-open.org].
>      Thanks for your help in identifying the functions the consortium 
> should support.  You will see some additional announcements 
> here over the 
> next week.  Regards  JBC
> 
>