public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
* [cip-dev] New IRC channel for #cip
@ 2016-09-19 16:32 Agustin Benito Bethencourt
  2016-09-24 11:52 ` Gleim, Urs
  0 siblings, 1 reply; 3+ messages in thread
From: Agustin Benito Bethencourt @ 2016-09-19 16:32 UTC (permalink / raw)
  To: cip-dev

Hi,

CIP has a new IRC channel. #cip in irc.freenode.net. Please check the 
logs at https://irclogs.baserock.org/cip/

I would welcome if you can report that you successfully accessed to it 
through webchat. Some corporations do not provide access to IRC through 
the default ports. Maybe accessing through web would be the alternative.

Best regards

-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [cip-dev] New IRC channel for #cip
  2016-09-19 16:32 [cip-dev] New IRC channel for #cip Agustin Benito Bethencourt
@ 2016-09-24 11:52 ` Gleim, Urs
  2016-09-24 17:53   ` Paul Sherwood
  0 siblings, 1 reply; 3+ messages in thread
From: Gleim, Urs @ 2016-09-24 11:52 UTC (permalink / raw)
  To: cip-dev

Hi,

just a remark: we have some proxy restrictions in the company which
result in the fact that IRC is not really practically usable. So our
main communication channel would be the mailing list I am afraid.

best regards,
Urs


On 19.09.2016 18:32, Agustin Benito Bethencourt wrote:
> Hi,
>
> CIP has a new IRC channel. #cip in irc.freenode.net. Please check the
> logs at https://irclogs.baserock.org/cip/
>
> I would welcome if you can report that you successfully accessed to it
> through webchat. Some corporations do not provide access to IRC
> through the default ports. Maybe accessing through web would be the
> alternative.
>
> Best regards
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20160924/779ba938/attachment.html>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [cip-dev] New IRC channel for #cip
  2016-09-24 11:52 ` Gleim, Urs
@ 2016-09-24 17:53   ` Paul Sherwood
  0 siblings, 0 replies; 3+ messages in thread
From: Paul Sherwood @ 2016-09-24 17:53 UTC (permalink / raw)
  To: cip-dev

On 2016-09-24 12:52, Gleim, Urs wrote:
> just a remark: we have some proxy restrictions in the company which
> result in the fact that IRC is not really practically usable. So our
> main communication channel would be the mailing list I am afraid.

This is a problem for many companies, actually, but I hope we can still 
encourage people to participate in IRC, mainly because there are so many 
established FOSS projects and contributors actively using IRC. It's 
old-school, but it has been working very well for several decades now. 
Using the newer services (Slack, Google Groups etc) may seem to achieve 
similar functionality but they don't achieve the same direct connection 
to other communities.

Codethink's default recommendation to get IRC in the situation you have 
at Siemens would be to setup a web-based service. We've had success with 
Shout [1] and its fork The Lounge [2]. Basically these allow people to 
participate in IRC directly from a web-browser. Normally people run the 
server on a tiny/cheap cloud machine, eg AWS. Both relatively easy to 
setup, either by members directly, or maybe by Linux Foundation?

Alternatively we'd be happy to create accounts on our existing Shout 
instance [3] if that's of interest.

br
Paul

[1] https://github.com/erming/shout
[2] https://thelounge.github.io
[3] https://chat.codethink.co.uk

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-09-24 17:53 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-09-19 16:32 [cip-dev] New IRC channel for #cip Agustin Benito Bethencourt
2016-09-24 11:52 ` Gleim, Urs
2016-09-24 17:53   ` Paul Sherwood

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox