public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Eray Ozkural (exa)" <erayo@cs.bilkent.edu.tr>
To: Mo DeJong <supermo@bayarea.net>
Cc: corsepiu@faw.uni-ulm.de, sourcenav@sources.redhat.com,
	kdevelop-devel@kdevelop.org, snuffeler@gmx.net
Subject: Re: SourceNav release ...
Date: Sat, 19 Jan 2002 09:03:00 -0000	[thread overview]
Message-ID: <E16RymG-0002aj-00@orion.exa.homeip.net> (raw)
In-Reply-To: <20020118065806.4158e85b.supermo@bayarea.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 18 January 2002 16:58, Mo DeJong wrote:
> On Fri, 18 Jan 2002 23:55:53 +0200
> "Eray Ozkural (exa)" <erayo@cs.bilkent.edu.tr> wrote:
>
>
> There are always alternatives in the DB arena. Abstracting the DB interface
> so that it does not strictly rely on Berkeley DB was all I meant.
> Attempting to rewrite working code to make the DB layer more generic is
> about as much fun as poking yourself in the eye (the SN code is guilty of
> this).
>

Well we can lower the priority of an abstract DB interface then. ;)

> Sounds good, as long as #3 (or any other GUI front end) is left outside the
> scope of the project. I think a key to success will be minimizing external
> dependencies so that code can easily be incorporated into other projects.
> Then there is the old C vs C++ debate and the discussion of which
> lame/broken compilers should be supported.
>

Sure. A GUI front end can be hosted on KDE CVS. Possibly kdenonbeta, it might 
be too alpha to include it in kdevelop.

> I would be very interested in helping you get this project going. My
> initial focus would be on a regression test suite and a Java parser. What
> comes next is the age old question of labels and resources. This project
> will need a name and a home. Sourceforge has some great features, but the
> mailing list archives are really lame. I have always been impressed by the
> folks that run sourceware (aka sources.redhat.com), but I don't know if it
> is the best place for such a project.
>

I first thought "libsourcenav" since that is what we are doing: making it 
work better as a library rather than a stand alone application. It would also 
mark the descent of the project better. For a fancier name, I thought 
"sourcemine" since we could actually run data mining programs such as 
association rule mining or sequence rule mining on databases derived from 
sourcenav project databases. Frequency mining is my current research subject, 
so I tend to think of applications of data mining rather quickly. :)

Thanks,

- -- 
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D 539C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8SaUGfAeuFodNU5wRAnOEAJ4pyLACkFJgEh25kCGTKhc2cnsydgCfYD3T
r4Vn1UEfvjnd7B0pi1+GxAc=
=PU57
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2002-01-19 16:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06  0:26 Simonovsky, Pavel
2002-01-06  3:48 ` Mo DeJong
2002-01-06  6:36   ` Ralf Corsepius
2002-01-07 12:04     ` Khamis Abuelkomboz
2002-01-07 13:11       ` Timothy M. Shead
2002-01-18 18:13         ` Mo DeJong
2002-01-07 13:22     ` Ian Roxborough
2002-01-07 13:34       ` Patches...[was: Re: SourceNav release ... ] Ian Roxborough
2002-01-10  4:34       ` SourceNav release Eray Ozkural (exa)
2002-01-11 14:34         ` Mo DeJong
2002-01-18 14:52           ` Eray Ozkural (exa)
2002-01-18 15:33             ` Mo DeJong
2002-01-18 15:58               ` Ian Roxborough
2002-01-24 10:14                 ` Eray Ozkural (exa)
2002-01-19  9:03               ` Eray Ozkural (exa) [this message]
2002-01-19  8:59             ` Khamis Abuelkomboz
  -- strict thread matches above, loose matches on Subject: below --
2002-01-04  2:56 Roman Levenstein
2002-01-04 15:48 ` Khamis Abuelkomboz
2002-01-03 14:30 klmcw yahoo
2002-01-03 15:08 ` Khamis Abuelkomboz

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=E16RymG-0002aj-00@orion.exa.homeip.net \
    --to=erayo@cs.bilkent.edu.tr \
    --cc=corsepiu@faw.uni-ulm.de \
    --cc=kdevelop-devel@kdevelop.org \
    --cc=snuffeler@gmx.net \
    --cc=sourcenav@sources.redhat.com \
    --cc=supermo@bayarea.net \
    /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).