public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: is eCos dying?
Date: Tue, 13 Oct 2015 17:20:00 -0000	[thread overview]
Message-ID: <mvjegp$ji8$1@ger.gmane.org> (raw)
In-Reply-To: <561C48D9.1010608@jifvik.org>

On 2015-10-12, Jonathan Larmour <jifl@jifvik.org> wrote:
> On 06/10/15 08:51, Richard Rauch wrote:
>> You do not see a lot of activities in the eCos community because of politics
>> and commercial interests.
> [snip]
>> This is just a guess, but in my opinion the reason for this is, that the
>> maintainers of public eCos are as well strongly commercial oriented.

Well... I do rather like to eat, and the bank that owns my house gets
a bit uppity if I stop sending mortgage payments. So yes I am
"strongly commercial oriented" in that I do dedicate a considerable
amount of my waking time to earning a living rather than maintaining
eCos.  I also have a number of non-eCos-related things I like to do
when I'm not actively working to earn a living.

>> It seems, they will not put any port to official open source
>> repository if it could disturb commercial interests
>> (eCosCentric/eCosPro...).

No.  Just no. I certainly am not refusing to commit anything out of
deference to the commercial interests of eCosCentric.  I'd be very
shocked if any of the other maintainers were.  [And I can't believe
that they (eCosCentric et alia) would ask/expect any of us to do so.]

> If nothing else, look at the list at the bottom of
> http://ecos.sourceware.org/intouch.html and you'll see that only two
> of the maintainers (myself and Nick) are in eCosCentric - severely
> outnumbered! If a maintainer has the time and ability to go through,
> review and potentially rework any submission, then any of them can.
> If you think there has been some secret agreement behind-the-scenes
> between all maintainers to deliberately stop contributions being
> committed you are very mistaken.

Speaking only for myself, the main reasons are 1) lack of spare time,
and 2) insufficient depth of knowlege in various areas of the kernel
to feel comfortable reviewing most of the submissions.

-- 
Grant Edwards               grant.b.edwards        Yow! Maybe I should have
                                  at               asked for my Neutron Bomb
                              gmail.com            in PAISLEY --


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2015-10-13 17:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  7:51 Richard Rauch
2015-10-06 12:59 ` Mikhail Matusov
2015-10-07  9:59   ` AW: " Richard Rauch
2015-10-12 23:57 ` Jonathan Larmour
2015-10-13 12:31   ` David Fernandez
2015-10-14  0:57     ` Frank Pagliughi
2015-10-13 17:20   ` Grant Edwards [this message]
2015-10-13 19:38 ` Alex Schuilenburg
2015-10-14 23:05 ` Sergei Gavrikov
     [not found] <349750926.354427.1443800101065.JavaMail.yahoo@mail.yahoo.com>
2015-10-03  8:15 ` John Dallaway
2015-10-04  8:30   ` Stanislav Meduna
2015-10-04 15:00     ` Grant Edwards

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='mvjegp$ji8$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=ecos-discuss@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).