From: John Dallaway <john@dallaway.org.uk>
To: eCos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] eCos Developer Network
Date: Wed, 03 Apr 2013 11:30:00 -0000 [thread overview]
Message-ID: <515C12C7.6010405@dallaway.org.uk> (raw)
Liam Knight has made some valid points concerning the eCos Developer
Network group on LinkedIn recently. In retrospect, I do accept that my
use of membership control and content moderation has had an impact on
freedom of speech and I apologise to everyone for any offence that I
have caused.
In response to Liam's points, I have broadened the scope of the group to
include the commercial eCosPro RTOS, removed moderation settings and
appointed an additional manager to the forum. I have also offered
personal apologies to those involved at eCosCentric. eCosCentric has
accepted my apologies and we both consider the matter to be closed.
John Dallaway
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2013-04-03 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=515C12C7.6010405@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).