From: Steven Johnson <sjohnson@sakuraindustries.com>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Current Status of Insight
Date: Mon, 16 May 2005 22:07:00 -0000 [thread overview]
Message-ID: <428A4FB8.7090608@sakuraindustries.com> (raw)
In-Reply-To: <1115950737.4491.95.camel@lindt.uglyboxes.com>
> Christofer Fayler Wrote:
> 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
And I add
8) Review and Apply user submited patches
> .....
> The project is only "dead" because no one is actively caring for it.
> Making it part of gdb does not mean that someone will magically appear
> to keep it alive. You still need people to do that.
>
It is apparent that there are a reasonable number of people that want to
get involved, from the various replies.
For my part, I want to help with
(1 - already doing it now
(2 - linux in an X Debug envirnoment for MPC8XX and ARM
(3 - A Major Requirement, which im happy to do
(4 - Im also happy to update the web site, to the limit of my
- meagre HTML and WEB Design skills.
(5 - Should be part of the review process for new
- patches/features. Cant or shouldnt go in without appropriate
- documentation. Similar to what happens with core
- gdb.
(6 - Id like to add the ability to view memory as an
- arbitrary bitmap, plus put watchpoints on memory
- dumps
(7 - As far as my capability and ego allow.
(8 - Im happy to do it, but my experience level probably means
- I shouldnt.
What next?
Do we have any other new volunteers that are putting up their hands?
Steven Johnson
next prev parent reply other threads:[~2005-05-16 22:07 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
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 [this message]
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=428A4FB8.7090608@sakuraindustries.com \
--to=sjohnson@sakuraindustries.com \
--cc=insight@sources.redhat.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).