RE: [chairs] OASIS IRC

["Matt MacKenzie" <mattm@adobe.com>]

It would be interesting if OASIS could configure their IRC server to
allow connections on port 80.  Many of us are behind restrictive
firewalls with few ways to get through other than port 80.  mIRC can
proxy via a http proxy, but that disables most features of IRC beyond
barebones chat.

--
Matt MacKenzie


-----Original Message-----
From: James Bryce Clark [mailto:jamie.clark@oasis-open.org] 
Sent: Thursday, September 22, 2005 3: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