public inbox for
 help / color / mirror / Atom feed
From: Doug Fraser <>
To: 'Eray Ozkural' <>,
	Doug Fraser <>,
	'Mo DeJong' <>,
	sourcenav <>
Subject: RE: New CVS module to checkout.
Date: Fri, 22 Feb 2002 10:26:00 -0000	[thread overview]
Message-ID: <> (raw)

Oh, I think sourcebase would be fine.
I really do. I was just thinking of something
more poetic, more artful. A library is what
you are building, in both senses. A linkable
library that acts as a backend to other development
tools and also a library as in sense 4 of the
American Heritage Dictionary:

	4. An organized collection of recorded data
		arranged for ease of use.

but then, sourcebase is more descriptive.

Alexandria would not immediately imply to the casual
web surfer that they had just encountered the neatest
source discovery tools anywhere in the solar system.
Sourcebase may just clue them in that direction....


> -----Original Message-----
> From: Eray Ozkural []


> How about simply sticking with 'sourcebase'? Mo had said 'sourceDB'. 
> sourcebase means a database of sources, a la knowledge base.
> Thanks,
> - -- 
> Eray Ozkural (exa) <>

             reply	other threads:[~2002-02-22 18:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 10:26 Doug Fraser [this message]
2002-02-22 13:55 ` Khamis Abuelkomboz
  -- strict thread matches above, loose matches on Subject: below --
2002-02-22  8:16 Doug Fraser
2002-02-22 10:05 ` Eray Ozkural
2002-02-22 11:08 ` Gilles J. Seguin
2002-02-22 13:07   ` Ian Roxborough
2002-02-20 16:12 Ian Roxborough
2002-02-20 17:51 ` Mo DeJong
2002-02-21  1:51   ` Mo DeJong
2002-02-21 14:48 ` Eray Ozkural
2002-02-21 15:35   ` Ian Roxborough
2002-02-22  0:16     ` Eray Ozkural
2002-02-22  2:43       ` Mo DeJong
2002-02-21 16:43   ` Mo DeJong
2002-02-21 18:17     ` Eray Ozkural

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