That is, if someone interested and new to OSFlash goes to the website and looks at the list of projects and their sometimes "quirky" names, they would have no idea what any of them did without going to each project individually.
Even if seperated by target audience ("developer", "end-user", etc), would anyone be able to tell what "Fluge", "fosFORO", "Mikrokosmos", "OFD", "Ripple", or "Fling" _do_ if they all happened to be grouped together? But, if they were at least better defined by tag, people interested in "GUI" or "video" or "framework" would be able to better sort through all the projects and only have to browse a few instead of all (even if they overlapped).
Perhaps if it's too much to impliment tags, a simple "View Projects by Category" link to another page would do... ??
Just my take. :-)
g.
* = I've got three different projects that i'm debating about releasing as OS (one of which already is, just not real "available" atm)... Hopefully before too long... :-)
On 8/13/06, Sönke Rohde <[EMAIL PROTECTED]> wrote:
[...]
Hi,
I also had such categories in mind.
But it's true that some projects would match multiple categories and it
would be hard to find/set the right one.
So what about tagging the projects and a nice tagcloud on the
osflash-startpage?
Tags could be: as2, as3, debugging, server, video, flex, ui-framework,
commandline-tool, generator, compiler, code-library, logging, IDE ...
Cheers,
Sönke
P.s.
don't beat me because of the web 2.0 wording ;)
_______________________________________________
osflash mailing list
osflash@osflash.org
http://osflash.org/mailman/listinfo/osflash_osflash.org
--
weblog: broadcast.artificialcolors.com
blazePDF: www.blazepdf.com
band: www.cutratebox.com
_______________________________________________ osflash mailing list osflash@osflash.org http://osflash.org/mailman/listinfo/osflash_osflash.org
