Let's start it (Re: SN backend GPL or LGPL?)

[Eray Ozkural <erayo@cs.bilkent.edu.tr>]

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

Hey there,

IMHO, we don't need a license different from GPL. Let it remain free...

We still have to decide on a name. I suggested sourcebase, and Mo said fuzzyp
(but that's a fuzzy name ;). It's probably going to be hosted on
sources.redhat.com so we have to do an initial import to start the work. I
suggest that we start with the source/snavigator directory, with all its
contents (we don't build gui/ though). That way, we'll be forced to drop
hacked versions of tcl/tk and the old db. It's easy to use upstream tcl/tk in
the part of the code we're going to adapt. It was said on this list before
that the old berkeley db was used for performance, but is that really true?
We can go for the latest berkeley db instead of that one. It might also allow
us to use a few advanced features, those people are crazy for performance.

With that directory, we're going to have to work on the build system and do
some changes (hopefully minor) for a preliminary version. I tried the
feasibility of that and it doesn't seem hard, I've got it half-working here.

We can keep the C and tcl/tk interfaces in, and simply disable all GUI stuff.

Then, we can progress to work on the API. (Like refining library API, writing 
a C++ wrapper, an abstract database interface, etc.)

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

iD8DBQE8bUhdfAeuFodNU5wRAgbxAKCV2HfCq7VEs1lKnNIECW7gI+SncQCfZiPg
iqKm9lk6tEDV0yFmlEHfHSY=
=Crmp
-----END PGP SIGNATURE-----