From: "Ken Yee" <kenkyee@excite.com>
To: ecos-discuss@sourceware.org
Subject: [ECOS] Re: Is eCosPro a fork of eCos?
Date: Sun, 31 Mar 2013 22:33:00 -0000 [thread overview]
Message-ID: <20130331183301.17691@web005.roc2.bluetie.com> (raw)
I haven't posted to this list in a while, but I still get it in digest form for some reason.
Just wanted to say that either eCosPro or eCosCentric holding back bug fixes from the main tree should not be done.
You guys should do the consulting thing and create new packages, etc. to stack on top of eCos to make money,
but IMHO leaving known bugs unfixed so you can tell customers "we have many hard won bugs fixed if you buy our product" isn't a good way to keep the ecosystem alive. People will try eCos and hit the bugs and say it's crap...they won't say "maybe we should have tried the 'Pro' version because it's less buggy".
I project I was on was killed off because there were too many bugs w/ the networking stack and PPP.
And IMHO, yes, anything where you take a copy of the mainline and only keep your own copy of it to fix or add features to is obvously a fork...that's the basic definition of a fork....
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2013-03-31 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 22:33 Ken Yee [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-28 14:40 [ECOS] " Liam Knight
2013-03-28 16:25 ` [ECOS] " John Dallaway
2013-03-28 18:40 ` Liam Knight
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=20130331183301.17691@web005.roc2.bluetie.com \
--to=kenkyee@excite.com \
--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).