see inline
On Apr 5, 2007, at 12:05 PM, Mimi Yin wrote:
The new Teams Area is starting to look smokin' hot. http://
wiki.osafoundation.org/Teams/WebHome
I think I've got a pretty consistent look and feel / layout going.
Team Page owners: Philippe (Apps), Katie (Platform, Ops, Desktop),
Ted (Server, Community Area), Sheila (PPD), Aparna (QA), Bear
(Build), Jared (Hosted Service Planning stuff)
Please review the verbiage describing your team. I've taken a pass
at making the language more consistent and want to make sure I
didn't do any damage in the process.
Questions: (Sheila, Ted, Priss, Jared and Katie you have special
questions at the bottom.)
Silence will be taken as: Looks great! Do whatever you think best.
1. Are people okay with having the team member list in the
RIGHTNAV? The idea here being that it gets that info out of the way
so that you don't have to scroll as far to get to meeting notes. If
so, please remove the People section in the body of your Team page.
(I believe Apps, Platform and QA are the only ones with People in
the body.)
As I see it the QA meeting notes do not appear in the RIGHTNAV. THose
notes are each individual's journal notes. So the meeting notes will
continue to reside in the main section.
I will remove the People section since that is already covered in the
RIGHTNAV.
+ If you have additional information that won't fit in the
RIGHTNAV, perhaps we should have an "Areas of Responsibility"
section in the body?
+ If you have more than just team members under people (e.g.
Interns, people who have left) those can be in a section near the
bottom? Not sure that stuff is important
I would prefer having the entire team list on the RIGHTNAV incl
interns for 2 reasons:
1. we aren't dividing up the team into 2 sections
2. adding the interns to the RIGHTNAV would make them feel part of
the team.
Ofcourse that adds the burden of removing the names once they leave
but we would have to remove them from the main section anyways.
2. Do we generally want to have Meeting Notes closer to the top?
Not necessarily for people on the team, but for community members
watching our progress or other OSAF staff who want to keep up-to-
date on what other teams are doing.
3. Should we agree on nomenclature? Old stuff, History = Archive?
+1
4. Also feel free now to edit the RIGHTNAV. I think the content has
stabilized enough.
5. Are we ready to move the Topic-Level Team pages into the Teams
Wiki area and rename them so that they match the page title? (e.g.
Working Group and Project becomes Team. Cosmo becomes Chandler
Server, etc.)
===
Sheila, if you're okay with the new PPD Team page, I can replace
the old Design Group page with this one. http://
wiki.osafoundation.org/Teams/PPDTeam
I can link to the Design Group page from the PPDTeam page as an
Archive item.
Ted, please check Community Area, I futzed around with the old
Intro from CommunityHome: http://wiki.osafoundation.org/Projects/
CommunityArea
Priss, FYI, I have created a new OSAFSERVERSIDEBAR to replace the
old OSAFCOSMOSIDER. http://wiki.osafoundation.org/Journal/
OSAFServerSidebar
I have created a new OSAFSAMPLESIDEBAR so that we can use it as a
RIGHTNAV example for instructions without it getting in the way of
any SERVERSIDEBAR pages. I can send out an updated version of her
instructions to the Wiki Gardeners.
http://wiki.osafoundation.org/Journal/OSAFSampleSidebar
Priss, are you okay with that?
Jared, please check out the Ops Overview for Intro verbiage: http://
wiki.osafoundation.org/Projects/HostedServiceOpsOverview
Also, is there a way to maybe put the roadmap diagrams on a
separate content-level wiki page? The RIGHTNAV is getting pushed
off the view right now. We could also put links to the roadmap
diagrams in the RIGHTNAV.
Katie, I've created a Desktop Team RIGHTNAV template for you to
use: http://wiki.osafoundation.org/Journal/OSAFDesktopSidebar
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
