From: paul.sherwood@codethink.co.uk (Paul Sherwood)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] New IRC channel for #cip
Date: Sat, 24 Sep 2016 18:53:20 +0100 [thread overview]
Message-ID: <c34a68bfe1821819a7f2397f111a9f54@codethink.co.uk> (raw)
In-Reply-To: <3f48e9be-d159-c3a9-ce76-79fe6e2f17f6@siemens.com>
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
prev parent reply other threads:[~2016-09-24 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c34a68bfe1821819a7f2397f111a9f54@codethink.co.uk \
--to=paul.sherwood@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox