public inbox for
 help / color / mirror / Atom feed
From: Mo DeJong <>
To: sourcenav <>
Subject: Source-Navigator moves to SourceForge!
Date: Tue, 30 Apr 2002 14:19:00 -0000	[thread overview]
Message-ID: <> (raw)

Hello, everyone.

Recently, there has been a lot of discussion about the
status of Source-Navigator, and its future direction.
It has been more than a year since the last release,
and none of the members of the 5.0 engineering team
are currently employed by Red Hat. These problems 
were surmountable, Source-Navigator could have been
hosted on, if not for the copyright
assignment problem. Current Red Hat policy dictates
that contributors to Source-Navigator must assign any
copyrights to Red Hat in addition to agreeing to license
them under the terms of the GPL. This has effectively
shutdown any new development of Source-Navigator since
none of the original development team members are willing
to agree to these terms. As a result, the team has decided
to move the project to SourceForge.

So, without further ado.

The new project homepage can be found at:

The SourceForge page for developers is here:

There are also a couple of new mailing lists.

A significant amount of work has gone into upgrading the
Tcl/Tk version used in Source-Navigator, but this work was
never released. We are happy to announce that a new 5.1
version of Source-Navigator will be ready soon. Developers
can even get a sneak peek via CVS, just follow the instructions
on the download page.

The current CVS version of Source-Navigator is very close
to what will become 5.1. While the code is not yet ready
for release, it should be ready for some early testing.
The code should build without problems under a variety
of Unix systems. Building with VC++ under Windows works,
but a minor patch is needed (sourcenav-devl archive for info).
Also note that GNU grep will have to be accessible on you
PATH as it is no longer bundled with Source-Navigator.

One issue that remains with the migration to SourceForge
is the bug database currently hosted on
We plan on migrating  the data to SourceForge after the 5.1
release. Note that the Tcl/Tk  upgrade fixes a large number
of user interface problems, so those bug reports will not
have to be moved over.

The future of Source-Navigator looks brighter than it has for
some time. However, without corporate sponsorship, it is
imperative that we develop an infrastructure to support
ongoing maintenance and new development. To that end, we
encourage people and organizations to invest in Source-Navigator
and contribute to its development. Contracting with the maintainers
to fix bugs or implement new features can be the most effective
way to move Source-Navigator forward.

Mo DeJong

             reply	other threads:[~2002-04-30 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30 14:19 Mo DeJong [this message]
2002-04-30 17:46 ` Paul Selormey
2002-04-30 21:58   ` Mo DeJong
2002-05-01  0:14   ` Khamis Abuelkomboz
2002-05-01 16:37     ` Mo DeJong
2002-05-01  9:00 Davies, Mike
2002-05-01 13:21 ` Mo DeJong
2002-05-01  9:00 Davies, Mike
2002-05-01 18:52 David Robinson (AU)
2002-05-01 20:56 ` Mo DeJong

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).