public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Commercial postings on ecos-discuss etc
Date: Tue, 02 Mar 2010 13:54:00 -0000	[thread overview]
Message-ID: <4B8D1877.4060106@jifvik.org> (raw)
In-Reply-To: <4B892F8D.5090104@ecoscentric.com>

On 27/02/10 14:43, Alex Schuilenburg wrote:
> Dear Maintainers,
> 
> I am made unclear about the policy of the maintainers to commercial
> postings to eCos discuss due to the posting yesterday by John Dallaway
> where I believe he is using his maintainer position to post or gather
> information of a commercial nature for his company's benefit. 
> Previously, the guidelines stated that such postings should contain
> [COMMERCIAL] in the subject to alert subscribers to the nature of the
> content.

If they are commercial or contain advertising, yes.

> If this is not a commercial post, unfortunately his posting was not
> clear as to the nature, reasoning and backing of this research.

Does it need to be? If it was like some of those spam telephone calls
one can get where they purport to be "doing a survey" (to get around
telemarketing rules) but actually doing advertising/sales, that would be
one thing. But this contains no insidious promotion, marketing or sales.
It's just a request for people to do a straightforward survey.

> I would
> be most interested to see laid open what development plans the ecos
> maintainers may have for host tool development, as has been strongly
> advocated in the past.

I think we both know that there aren't concrete plans here.

>  I would also enquire as to why the results are
> not being made public for the benefit of the community.

Apparently the results are being made available to those who enter the
survey, which is more than sufficient.

> However, if this is a commercial post, then I would like to ask how the
> policy regarding commercial postings has changed. In addition, if John
> is conducting this survey for the benefit of his company, I would like
> to point out to him and you that I believe the survey does not comply
> fully to either the Companies Act 2006 or the Data Protection Act 1998.

That's not an issue for the maintainers.

> I would also like further clarification regarding netiquette and
> commercial postings on ecos-discuss in this regard.

No mention was made of John's company. There was no advertising, no
promotion, and results were available to those who filled in the survey.

I fully expect John to use the outcome of the survey to guide his
company's actions, but that doesn't make the post commercial IMO.

I'm afraid I really can't see a problem here.

Jifl

  parent reply	other threads:[~2010-03-02 13:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27 14:43 Alex Schuilenburg
2010-02-27 17:15 ` John Dallaway
2010-02-27 21:58   ` Alex Schuilenburg
2010-03-02 13:54 ` Jonathan Larmour [this message]
     [not found]   ` <4B8D4ABD.3060305@ecoscentric.com>
2010-03-02 20:10     ` Jonathan Larmour
2010-03-02 21:06       ` Gary Thomas
     [not found]       ` <4B8D9B39.8080905@ecoscentric.com>
2010-03-02 23:29         ` Jonathan Larmour
2010-03-03  0:21 Alex Schuilenburg
2010-03-03  0:22 Alex Schuilenburg

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=4B8D1877.4060106@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=alexs@ecoscentric.com \
    --cc=ecos-maintainers@ecos.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).