From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2584 invoked by alias); 2 May 2002 01:52:11 -0000 Mailing-List: contact sourcenav-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sourcenav-owner@sources.redhat.com Received: (qmail 2556 invoked from network); 2 May 2002 01:52:09 -0000 Received: from unknown (HELO sydvwall01.citrix.com.au) (203.24.91.8) by sources.redhat.com with SMTP; 2 May 2002 01:52:09 -0000 Received: from 10.43.1.131 by sydvwall01.citrix.com.au (InterScan E-Mail VirusWall NT); Thu, 02 May 2002 11:51:56 +1000 Received: by sydexch01.citrix.com.au with Internet Mail Service (5.5.2655.55) id ; Thu, 2 May 2002 11:51:56 +1000 Message-ID: <34611C909B4FD611BB2000508BA8EEEA0C1A74@sydexch01.citrix.com.au> From: "David Robinson (AU)" To: 'Mo DeJong' Cc: "'sourcenav@sources.redhat.com'" Subject: RE: Source-Navigator moves to SourceForge! Date: Wed, 01 May 2002 18:52:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2002-q2/txt/msg00033.txt.bz2 Hello Mo Thanks for your hard work. This is a great step forward for Source Navigator. It is curiously escaping the shackles of an open source company. I have a personal interest in the code parsing and cross-reference database. In fact I have never seriously run the IDE. There were discussions on the mailing list a while ago about redesigning the core components into a standalone library. Are there any serious plans to do this work? David Robinson. david-work@robinson-au.net -----Original Message----- From: Mo DeJong [mailto:supermo@bayarea.net] Sent: Tuesday, 30 April 2002 23:24 To: sourcenav Subject: Source-Navigator moves to SourceForge! 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 sources.redhat.com, 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: http://sourcenav.sourceforge.net/ The SourceForge page for developers is here: http://sourceforge.net/projects/sourcenav There are also a couple of new mailing lists. http://sourcenav.sourceforge.net/mail.html 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. http://sourcenav.sourceforge.net/download.html 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 source.redhat.com. 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. cheers Mo DeJong