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

I, Hans Horn,  care too!
Pls add me to the list!
H.

Steven Johnson wrote:
> It seems that there is at least 6 people that care:
> 
> (in no particular order, and sorry if i list you and you dont really
> care) 
> 
> 1. Keith Seitz
> 2. Duane Ellis
> 3. Roland Schwingel
> 4. Paul Schlie
> 5. Christopher Faylor
> 6. Steven Johnson (me)
> And Maybe (although it is less than clear from their posts):
> 7. Nickolay Kolchin
> 8. Jon Beniston
> 
> Anybody else care to add their name to this list of people that care
> about, or at the very least use a version of insight and would like to
> see it continue in some form.
> 
> If we cant join em (FSF GDB and RH Insight) why dont we just fork em?
> 
> We could go to Sourceforge, do a checkout of insight CVS Head, move
> development over to there, and at least then it can progress, we can
> cut releases, etc.  Official insight can stay here, and do whatever
> its 
> going to.  If the FSF and RH ever feel like getting together on this
> they can, and we could merge back our changes.
> 
> We track official GDB (ie merge GDB CVS with our tree daily), and
> release (close to synch with it), but are really independent from it.
> 
> To the extent anyone cares, insight would continue to be (visibly)
> maintained and survive.  If people really stopped caring it would die,
> at least we could attempt to attract new users (1 or 2 of which might
> even contribute something useful), as there would be "stable"
> releases, synched to official GDB the attraction would be greater. 
> It does seem like most of the people that care are using it for
> embedded programming, a few (maybe most) want it to work under
> windows. (I use it under 
> Linux).  In the mean time, we would have a maintainable version.
> 
> CVS_Head of Insight, is that the same level of code as CVS_Head of
> GDB? (ie, does it incorporate CVS_Head of GDB?)
> 
> As a minimum all that needs to happen is ensure that Insight continues
> to build and function on top of current GDB.  And I think thats what
> Keith is basically saying he does with CVS_Head, keep it building and
> functional against CVS_Head of GDB, all im really proposing (as a
> minimum) is making the process a little more transparent, and cutting
> releases (maybe its more work than that? Keith?).
> 
> Anyway is this feasible, of interest, or a waste of time?
> 
> There are a lot of nify features a debugger targeted to embedded
> systems could have, and insight could have them reasonably easily. 
> We could 
> even start re-writing the portions that are Red Hat copyright, over
> time, if we felt like it.  Any new code, could be put in new files and
> assigned to the FSF, over time (maybe years) id suspect the RH code
> would eventually disappear and it would all be assigned to the FSF.
> 
> The first thing to do, i would see is create a new project on
> sourceforge, move the code over there, and cut a first (current)
> version.  Even if it isnt quite GDB 6.3, we could call it "insight
> 6.3D" or some such (D for development release).  BTW, is "insight" a
> RH trademark, would it need to be renamed.  I always fancied
> "oversight" :)  Any new code, could be put in new files and assigned
> to the FSF. 
> over time (maybe years) id suspect the RH code would eventually
> disappear and it would all be assigned to the FSF.
> 
> If this is something ive generated interest with (with others), I will
> even invest in some web space for the project, so it can have its own
> URL (at least for a year or two, depending on its life, and my
> continued ability to fund it).
> 
> Keith, you seem to be the primary maintainer of insight, i dont want
> to mess with your project here, so your comments are of significant
> interest to me, in this regard.  I wouldnt like to see more "code
> hostility" if forking is feasible, then we should do it in a
> constructive way, for the benefit of all users, just to get rid of
> some of the restrictions the code base currently seems to face.
> 
> Also, i realise that i seem to have jumped in here and stirred things
> up, i have been an insight user for a long time, have submitted
> various things in the past (cheers go out to Fernando Nasser if hes
> listening). Its not my intention.  But if there are a lot of people
> building insight from CVS_Head and then using it for real work, then
> i thnk it should be kept going in a visible way, otherwise people
> will think what i thought "insight is dead, boo hoo, how crappy",
> when instead it is really just bubbling along under the surface, not
> progressing in great leaps and bounds, but still breathing.
> 
> Steven Johnson
> 
> Keith Seitz wrote:
> 
>> On Thu, 2005-05-12 at 22:09 -0400, Christopher Faylor wrote:
>> 
>> 
>>> I think past and current employees of Red Hat would probably agree
>>> with you about this sorry state of affairs.
>>> 
>>> Keith, what about a petition to Red Hat?  Think that would work?
>>> 
>>> 
>> 
>> I have no idea. For all I know, it might get me fired! [Okay, I don't
>> actually think it would, but who the heck knows?] I've thought about
>> this and other things.
>> 
>> I know this looks very badly upon Red Hat, but I want to make it
>> absolutely clear: I don't blame them one darn bit for not wanting to
>> take the time (and money) to see all the paperwork done. It does not
>> make economic sense.
>> 
>> I would also like to emphasize that when it comes to programming
>> tools (compilers, debuggers, etc), Red Hat is not a company, IME,
>> that is all take an no give. I've been involved with several
>> projects where Red Hat took AND gave back to the community.
>> 
>> Once again, I think we're finally at the point where we must ask
>> ourselves: Does it matter to anyone?*
>> 
>> Keith
>> 
>> * A question I have been meaning to ask for almost two years, but
>> kept chickening out in the last second...

  parent reply	other threads:[~2005-05-13 14:16 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 [this message]
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
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='005c01c557c6$38d12960$6400a8c0@almaden.ibm.com' \
    --to=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).