Blake,
A few quick thoughts:
I'm excited you're thinking about this as we near the 1.0 release.
I think that VU Lab would appropriately live under http://fluidproject.org/vulab
or some such URL (if you want to do a redirect from a yorku server,
then that seems as though it will be fine). Having said that, VU Lab
is also listed as a product on our newly freshened site -- since it is
a product and deliverable for Fluid. So, let's flesh out the presence
on the products page and then you can also have a page that gets
linked to from the Fluid site. Also, just to reiterate, the current
code should always be in the Fluid repository.
How's that?
Best,
Jess
~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
[email protected]
/ w / 617.326.7753 / c / 919.599.5378
jabber: [email protected]
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~
On Feb 23, 2009, at 5:08 PM, electBlake wrote:
Hello Gang,
As we near this final release date on vulab we are giving some
serious thought as to how this release is going to roll out.
( note, we will be looking for testers by what looks like
wednesday :) )
Keeping vulab as a "product" in mind, today in vulab's weekly
meetup, we discussed possibly having a simple product "homepage".
A product homepage could entail:
Fully branded design
Take the newly co-branded design of vulab and use for for our
product homepage (this was suggested by johnc)
Links to the download page on wiki.fluidproject.org
Simple and visually appealing homepage with basic explanations and
important links (linking to wiki.fluidproject.org)
Links to Support pages
Licensing and Partners Involved.
I would suggest we use vulab.ca for this, and then we can maintain
an updated and working copy of the vulab product on vulab.yorku.ca
(which is now mirrored on vulab.fluidproject.org)
If you think of this "product hompage" basically as a portal to the
important pages on the wiki, this makes sense to me.
We can think of this analogous to:
http://fluidproject.org vs. http://wiki.fluidproject.org
(but our homepage would carry less information, and would be far
less complex given the time constraints we are under)
Any thoughts? Concerns? Ideas of what we should/shouldn't include on
this proposed Product Homepage?
Thanks for your interest, and stayed glued to your inbox. VULab is
growing up (quicker then you think!)
- Blake
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
