I've been doing some thinking about our app database and have
some questions/comments about it.
The key question I have is what's the purpose of the database?
Are we just generating a list of apps for LUGs to choose from or
this something that new users can go to and print out for app info?
If the former, when do we say enough is enough? Do we really need
a list with every text editor or ftp client available? I'm not
trying to put down the work that's been done, I think we definetly
need something to help LUGs decide what to demo. I'm just trying to
figure out where we are going with this before we end up rebuilding
freshmeat or linuxberg from scratch.
If we're putting together something for new users, do we have
so much info that we'll end up overloading them?
Maybe instead of following the format we're following now, we
can instead create a list of equivalent apps?
What I'm picturing is a table, where we would list
Windows Apps that perform a certain function on one collumn,
and Linux equivalents in another. For example, MS Office in
one col, and Applix, KOffice, the GNOME stuff, and StarOffice
in the other. I think this would be a lot easier to follow
than just a database of apps. But once again, the question becomes
how many equivalent apps do we list? Should we just stick to
the more popular and well known ones?
Thoughts?
- D
--
[EMAIL PROTECTED] -- www.plexity.net -- ICQ: 17774863
Home: (480)446-0903 Work: (480)554-9339
1999: Year of the Penguin - LinuxDemo Day '99 - http://www.linuxdemo.org
---
This message was automatically sent by the Linux Demo Days mailing list
To remove yourself from this list, email [EMAIL PROTECTED]
with the "unsubcribe" in your message body.
