moved some stuff around, probably outdated overload report.

[feisty_meow.git] / readme.txt

diff --git a/readme.txt b/readme.txt
index e34bb580ff2a0790526e34a3a335b79c3a4b707b..7c3496390dccb69254d620fb4e968754ee29437b 100644 (file)
--- a/readme.txt
+++ b/readme.txt
@@ -1,9 +1,9 @@
 
-This is the "feisty meow (TM) concerns" codebase top folder.
+This is the "feisty meow® concerns" codebase top folder.
 
-Feisty Meow (TM) Concerns codebase comprises some but probably not all of several projects that
+Feisty Meow® Concerns codebase comprises some but probably not all of several projects that
 have come before.  These include the Twain.COM library scripts, the Yeti / YetiCode library
-scripts, the HOOPLE 1 and HOOPLE 2 C++ Codebases, the Fred Huffhines opensource LSL scripts,
+scripts, the HOOPLE 1 and HOOPLE 2 C++ Codebases, the Fred Huffhines open source LSL scripts,
 the CLAM build system, and a variety of other efforts.
 
 Directories and files of interest here...
@@ -13,7 +13,7 @@ scripts/
     languages, such as bash and perl.  These were the core of the YetiCode scripts library.
 
 nucleus/
-    Source for the basic modules of the Feisty Meow (TM) codebase.  This includes generic
+    Source for the basic modules of the Feisty Meow® codebase.  This includes generic
     data structures, useful utilities, and the like.  This hierarchy, plus octopi and graphiq,
     formed the major parts of hoople1 and hoople2.
 
@@ -44,6 +44,11 @@ kona/
     Our burgeoning Java libraries.  Not much to see here yet, but there is some code piling
     up for these that we will try to release soon.
 
+osgi/
+    Some example bundles for Java OSGi.  These may eventually fill out with real material,
+    but currently they are just tracking the investigation we did into creating bundles and
+    running using them.
+
 production/
     Machinery for getting releases out the door, including the generated files such as binaries
     and build system tools.