Hi Leland,
>osflash:
>
>
There's no reason for a root osflash namespace -- it's redundant
(http://osflash.org) :)
> contest:
> current (would list the current contests, basically an index page)
> mascot:
> about
>
>
There's really no need to go overboard with the namespaces. Let's not do
any big-upfront planning :) Thus "mascot contest" is fine as a
namespace, for example, with "gallery" being a page under it. Just use
them whenever you're creating a new section that has pages under it. For
example, each project can/should be in its own namespace.
It would be good to move the "osflash-hosted projects" to the "projects"
namespace and under it have a separete ("external") namespace for
non-osflash-hosted projects.
Thus (eg.):
projects:arp:manual:Application Controller
projects:external:Some External Project Name
Please *do not* create sectionst that you may think will be needed at
some point (ie., no need to design ahead here) -- it's much better to
let the wiki evolve to fit the needs of the community.
All the best,
Aral
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
