Hi,

Sheila asked me to compile a list of the remaining wiki tasks to figure out next actions...

Push out
+ Wiki Homepage
+ Planning Wiki Area
+ Engineering Wiki Area
+ Notes Wiki Area

Deprecate
+ Projects
+ Journal

Questions:
+ Do we need to have all of the content in place before we push out the remaining high-level wiki areas? Perhaps we could just put in placeholder text for now? Or get everyone to do a first pass by the end of next week? I'm concerned that if we wait until all of the content is in, we won't leave ourselves enough time to test the next wiki areas.

+ JARED: What are you preparing to put on the wiki for the Service?


LIST OF MISSING CONTENT

Wiki Homepage: http://chandlerproject.org/Product/ChandlerProjectHome
+ Tagline and Project Description: MIMI and KATIE
+ Technologies section: KATIE
+ Review Community stuff: TED
+ Engineering wiki area description: KATIE
+ Planning wiki area description: SHEILA

Community Area: http://chandlerproject.org/Projects/CommunityArea
+ Open Issue: Is it okay for Get Involved to just be a part of the Community Wiki Area? - TED, SHEILA, KATIE?

Planning Area: http://chandlerproject.org/Projects/PlanningArea
+ High level description - SHEILA

Engineering Area: http://chandlerproject.org/Projects/EngineeringArea
+ Open issue: How is what's on this page different from For Developers? - KATIE / TED / PHILIPPE?
- http://chandlerproject.org/Journal/ForDevelopers

Teams Area: http://chandlerproject.org/Teams/WebHome
+ Restructure Chandler Desktop Teams - KATIE

Notes Area: http://chandlerproject.org/Projects/NotesArea
+ I think this is ready to go

Release stuff that's going to be on the wiki that isn't done yet:
+ Product FAQ
+ Report a bug

Am I missing anything?

Mimi

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general

Reply via email to