From: Larry McVoy <lm@bitmover.com>
To: Timothy Covell <timothy.covell@ashavan.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: Linux Bug Tracking & Feature Tracking DB
Date: Sat, 29 Dec 2001 10:55:25 -0800 [thread overview]
Message-ID: <20011229105525.C19306@work.bitmover.com> (raw)
In-Reply-To: <200112290657.fBT6vMSr008000@svr3.applink.net>
In-Reply-To: <200112290657.fBT6vMSr008000@svr3.applink.net>; from timothy.covell@ashavan.org on Sat, Dec 29, 2001 at 12:53:39AM -0600
On Sat, Dec 29, 2001 at 12:53:39AM -0600, Timothy Covell wrote:
> 1. The maintainer of this DB would need to receive patches
> along with patch.lsm and feature.lsm like files from the code
> maintainers. That means that Linus, Alan, Marcello, Dave
> Jones, et al., might have to be involved.
>
> 2. DB would be a high volume site (at least that's the idea!)
>
> 3. Would would pay for and maintain it? (I know, since I'm
> the one putting forth the idea, it's mine to run with. However,
> a. I ain't rich. b. following from a., I have no bandwidth 24kbps
> dialup.)
OK, we've got a prototype of something like this already, I don't claim
it is ready for prime time, but you can go look at it here:
http://bugs.bkbits.net/bugs.html
You can run queries, etc.
This is a fairly early version, so be gentle. The data in it is the
current BitKeeper bug list (feel free to fix some :-)
There are other ways to access the data, both command line and email
are supported. Long term, I'd like to make the bug db be an NNTP server
so you could do everything via a news reader, which would be bitchin'.
If this is a first order approximation of what you want, we'll host
it here if you like. We have a T1 line with lots of spare bandwidth
at the moment. The machine that you are poking at is the same machine
which hosts various BK repos, such as the Linux/PPC trees, Ted's linux24
tree, Ted's e2fsprogs, NTP trees, GregKH's trees, Chris Wright's trees
(he has a 25 tree based on Ted's 24 tree), Rik's VM tree, among others.
We haven't talked about this very much because we don't have all the
nifty sourceforge like indices and statistics, but long term this is
headed towards something somewhat like a distributed sourceforge.
We never liked the centralized model that sourceforge has, it becomes
a single point of failure.
One interesting, perhaps, point is that bugdb is a BitKeeper repository,
which means you can clone it and take *all* of the data with you,
unlike sourceforge. So if you were to become dependent on this and
we ran out of bandwidth or something, you can clone the bug db and set
up your own bug server elsewhere. In general, for both databases and
source, that's the approach we want, i.e., we're happy to host it here
to get you started but if you have needs that we can't meet, we'll make
it easy for you to host elsewhere.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-12-29 18:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 6:53 RFC: Linux Bug Tracking & Feature Tracking DB Timothy Covell
2001-12-29 7:20 ` Anuradha Ratnaweera
2001-12-29 18:55 ` Larry McVoy [this message]
2001-12-29 19:08 ` Edgar Toernig
2001-12-29 22:13 ` Daniel Phillips
2001-12-29 22:52 ` Edgar Toernig
2001-12-29 23:02 ` Larry McVoy
2001-12-29 23:29 ` Edgar Toernig
2001-12-29 23:45 ` Larry McVoy
2001-12-29 19:16 ` Timothy Covell
2001-12-29 23:32 ` Stewart Smith
2001-12-29 23:45 ` Dave Jones
2001-12-30 5:24 ` Stewart Smith
2001-12-30 12:12 ` Dave Jones
2001-12-31 0:42 ` Richard Gooch
2001-12-31 0:44 ` H. Peter Anvin
2001-12-31 0:47 ` Richard Gooch
2001-12-31 0:52 ` H. Peter Anvin
2001-12-31 1:16 ` Richard Gooch
2001-12-31 4:58 ` H. Peter Anvin
2001-12-31 5:07 ` Richard Gooch
2001-12-31 0:47 ` Arnaldo Carvalho de Melo
2001-12-31 0:49 ` Dave Jones
2001-12-31 21:50 ` Rob Landley
2001-12-31 19:40 ` David Ford
2001-12-31 19:27 ` David Ford
2001-12-31 20:00 ` Dave Jones
2002-01-02 2:27 ` David Ford
2002-01-01 6:35 ` Horst von Brand
2002-01-02 2:46 ` David Ford
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=20011229105525.C19306@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=timothy.covell@ashavan.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