From: Dan Bethe <dan_bethe@yahoo.com>
To: dan_bethe@yahoo.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: the state of the linuxppc-dev community
Date: Tue, 8 Feb 2000 15:37:09 -0800 (PST) [thread overview]
Message-ID: <20000208233709.17120.qmail@web1001.mail.yahoo.com> (raw)
> So what exactly is the problem? The 2.2.12 source? The .config? The fact
> that LinuxPPC developers appear to break the GPL by not dropping a fresh
> source tarball along each kernel binary?
I happen to know the problem shared by Gabe, me, and anyone else primarily
concerned with the stability, robustness, and ease of use of the whole LinuxPPC
distribution and community authority.
The problem is that LinuxPPC.org has a development environment that is
splintered, unstable, undocumented, obscure, nonintuitive, and basically
impenetrable even to people who are fully dedicated to it such as Gabe and
myself. It is run almost exclusively on tribal knowledge that is only in the
heads of the people who are writing the ppc-specific core of the OS. There are
no procedures and no interface. And there is very little respect toward people
like me and Gabe who have the time, dedication, and skills to clean it all up.
First, obviously, we have to map out how everything currently is, before we
could even suggest anything better. But because 90% of the responses we get
are either dead silence or asinine arguments like yours, we are slowly getting
nowhere. The remaining 10% are the responses of a mob cheering us on just for
having pointed out the silly state of the maintenance of LinuxPPC.
We have definately produced deeds rather than just words. Gabe is a primary
maintainer of Stampede Linux (www.stampede.org), and is working on porting
Stampede to PPC; and I've accepted jhaas's request to be the primary maintainer
of LinuxPPC security and of LinuxPPC Powerbook support. We both use LinuxPPC
on Powerbook for 99% of our daily work.
We are capable of contributing to organizing the random mess that is the
LinuxPPC dev community, and tremendously boosting the quality of the product by
making the community accessible to a lot more people. There are dozens more
likeminded individuals in the linuxppc-user community, who just haven't yet
addressed the root of the issue -- the developers and the distribution
maintainers who are simply incredibly brilliant but disorganized. I get
private emails from end users, cheering on anyone who makes an organizing move.
BUT until I hear from the Head Honchos -- jcarr, jhaas, and at least some of
linuxppc's main kickass developers -- I'm not going to fork from linuxppc.org
just to have an organized environment. We're professionals. This is an
extremely high quality product who deserves better documentation than random
bulk mailing list searches, and better distribution than a hundred random files
in random ftp sites all over the world.
=====
"Don't expect your own messiah; this neverworld which you desire is
only in your mind." -- http://www.dreamtheater.net/songb4.htm#IV5
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-02-08 23:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-08 23:37 Dan Bethe [this message]
2000-02-09 0:13 ` the state of the linuxppc-dev community Tony Mantler
2000-02-09 0:26 ` Tom Rini
2000-02-09 0:46 ` Larry McVoy
2000-02-09 0:51 ` Tom Rini
2000-02-09 1:02 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2000-02-09 1:35 Dan Bethe
[not found] <20000209014216.17047.qmail@web1001.mail.yahoo.com>
2000-02-09 9:22 ` Larry McVoy
[not found] <20000208233505.29535.qmail@web1003.mail.yahoo.com>
2000-02-09 0:09 ` Tom Rini
2000-02-09 11:30 ` Michael Schmitz
2000-02-09 17:19 Jan Nieuwenhuizen
[not found] <20000209100229.B5973@linuxcare.com>
2000-02-09 20:04 ` Michael Schmitz
2000-02-09 22:14 ` Tom Rini
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=20000208233709.17120.qmail@web1001.mail.yahoo.com \
--to=dan_bethe@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).