Trove

[Jason Pincin <chardros@linuxkb.org>]

Just food for thought.

BTW - someone told me that Source Forge published it's code via CVS...
this is not true.  They publish they're code just as Slashdot does.  I
visited they're repository, and they have the CVS module turned OFF for
the SF project.  Bummer.  The reason I was looking was because of this:

https://sourceforge.net/softwaremap/trove_list.php


They have a working Trove Index in place.  For information on Trove,
visit: http://www.tuxedo.org/~esr/trove/

It's a standard being pushed by ESR among others to "(de)centralize"
package maintenance and categorization.  Very interesting, and could have
a big impact on us.  Source Forge is already adopting it.  I visited our
LKB account on SF and investigated how they have project maintainers
placing themselves in the Trove tree, etc.  I read through the entire
Trove site, including all documentation and what they are proposing, and
it would be an excellent fit where we were intending to use FM.  Not that
I'm saying we should do it NOW.

For Beta, copying what FM has, and running with the work we've done on the
topology is fine.  But I think Trove is something to consider for the
future.  


ALSO, BTW - if you notice how SF is doing they're drill down... they are
doing it JUST like we are :).  HA!  I'm not the only one that thought it
was OK!  :)  When you drill down a layer, you don't see any children of
higher levels on SF either.

Anyway - just wanted to toss the Trove thing out there for people to
nibble on.  I joined the list and will be actively participating in it.  

Later.

-- 
Jason Pincin
Linux Knowledge Base Project Leader (http://www.linuxkb.org/)
http://vodka.linuxkb.org/~chardros/