public inbox for
 help / color / mirror / Atom feed
From: David Fernandez <>
To: Jonathan Larmour <>,
	Richard Rauch <>,
Subject: Re: [ECOS] Re: is eCos dying?
Date: Tue, 13 Oct 2015 12:31:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

(resent, as was sent from company email with likely privacy disclaimer 

On 13/10/15 00:57, Jonathan Larmour 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.
>> It seems, they will not put any port to official open source repository if
>> it could disturb commercial interests (eCosCentric/eCosPro...).
> If nothing else, look at the list at the bottom of
> 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.

I would say that nobody looks at the list these days, specially ecos-devel.

I had some things I managed to put in a state I could submit as valid 
patches, but nobody answers the emails, so you end up forgetting about 
it and keeping private patches.

Is there any way people can contribute currently, I mean actively 
contribute, rather than just throw stuff into a black hole?

Otherwise, it might be better to just be clear and say that opensource 
eCos is meant as an evaluation repository, and eCosCentric should be the 
way to go for any real contributions and in business use of eCos.

David Fernandez

Before posting, please read the FAQ:
and search the list archive:

  reply	other threads:[~2015-10-13 12:31 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 [this message]
2015-10-14  0:57     ` Frank Pagliughi
2015-10-13 17:20   ` Grant Edwards
2015-10-13 19:38 ` Alex Schuilenburg
2015-10-14 23:05 ` Sergei Gavrikov
     [not found] <>
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).