public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: Steven Johnson <sjohnson@sakuraindustries.com>,
	insight@sources.redhat.com, "Hans W. Horn" <hannes@2horns.com>
Subject: Re: Current Status of Insight
Date: Fri, 13 May 2005 14:29:00 -0000	[thread overview]
Message-ID: <20050513142931.GB13263@trixie.casa.cgf.cx> (raw)
In-Reply-To: <005c01c557c6$38d12960$6400a8c0@almaden.ibm.com>

On Fri, May 13, 2005 at 07:10:13AM -0700, Hans W. Horn wrote:
>I, Hans Horn,  care too!
>Pls add me to the list!
>H.

There are 160 people or so in this mailing list.  Isn't it a safe bet
that the majority of them care about insight?

It seems like the only thing missing is volunteers to actively work on
the project.

So, we shouldn't be composing a list of people who care, we should be
composing a list of volunteers.

AFAICT, we need people to:

  1) fix bugs

  2) test (on linux/unix/cygwin)

  3) produce snapshots and releases

  4) maintain and update the web page

  5) maintain and update the documentation

  6) add new features

  7) respond to queries on the mailing list

All of the above are possible within the current system.  We just need
actual people to do the actual work.

cgf

  reply	other threads:[~2005-05-13 14:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12 10:07 Steven Johnson
2005-05-12 10:13 ` Jon Beniston
     [not found]   ` <2636500f05051203276a294e8f@mail.gmail.com>
2005-05-12 10:29     ` Nickolay Kolchin
2005-05-12 15:17 ` Keith Seitz
2005-05-12 21:46   ` Steven Johnson
2005-05-12 22:42     ` Duane Ellis
2005-05-12 22:45     ` Duane Ellis
2005-05-13  2:09     ` Christopher Faylor
2005-05-13  2:19       ` Keith Seitz
2005-05-13 13:53         ` Steven Johnson
2005-05-13 14:05           ` Christopher Faylor
2005-05-13 14:18             ` Jon Beniston
2005-05-13 14:21               ` Christopher Faylor
2005-05-13 14:16           ` Hans W. Horn
2005-05-13 14:29             ` Christopher Faylor [this message]
2005-05-13 14:33           ` James Lemke
2005-05-14 11:14           ` Nickolay Kolchin
2005-05-17 12:51             ` Fernando Nasser
2005-05-16 22:07         ` Steven Johnson
2005-05-13  1:15 Paul Schlie
2005-05-13  8:14 Roland Schwingel
     [not found] <1115992411.3092.ezmlm@sources.redhat.com>
2005-05-13 15:44 ` E. Weddington
2005-05-13 17:15   ` Christopher Faylor
2005-05-13 17:35     ` Bernhard Walle
2005-05-13 17:45       ` Christopher Faylor
2005-05-13 17:58         ` Bernhard Walle
2005-05-13 21:51           ` Fernando Nasser
2005-05-14 14:54             ` Duane Ellis
2005-05-14 17:25               ` Bernhard Walle
2005-05-17 19:38               ` Fernando Nasser
2005-05-14 22:13 Paul Schlie
2005-05-16  5:35 ` Steven Johnson
2005-05-17 19:33   ` Fernando Nasser
2005-05-16 16:10 ` Christopher Faylor
2005-05-16 17:18   ` Paul Schlie
2005-05-16 23:45 Paul Schlie
2005-05-17  8:26 Roland Schwingel
2005-05-17 10:18 ` Steven Johnson

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=20050513142931.GB13263@trixie.casa.cgf.cx \
    --to=me@cgf.cx \
    --cc=hannes@2horns.com \
    --cc=insight@sources.redhat.com \
    --cc=sjohnson@sakuraindustries.com \
    /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).