[Chandler-dev] Can this wiki be saved?

[Katie Capps Parlante]

I'm doing some pre-preview wiki gardening, in particular working on the 
desktop team page and the desktop portion of the "developer area".

We have many "project pages" that are out of date; indeed, maintaining 
so many project pages is perhaps not worth the effort. Wiki pages that 
are primarily documentation, proposals, or track implementation of a 
feature for a particular time period, seem to be more successful.

I'm sending this to the chandler-dev list because I think this is a 
problem specific to the desktop team, a consequence of earlier decisions 
about how to use wiki. (mea culpa!)

Proposal:
- reduce the number of "project pages" where we maintain project status

- make "project pages" obsolete OR turn them into:
   - documentation about implemented features
   - proposals for future features/work
   - release specific tracking for a particular feature

Project pages we should continue to maintain (with owners):
http://chandlerproject.org/Projects/InternationalizationProject (bkirsch)
http://chandlerproject.org/Projects/LocalizationProject (bkirsch)
http://chandlerproject.org/Projects/PerformanceProject (heikki)
http://chandlerproject.org/Projects/AccessibilityProject (heikki)
http://chandlerproject.org/Projects/ZanshinProject (gbaillie)
http://chandlerproject.org/Projects/WxPythonProject (Robin)

Pages that should primarily be documentation (with owners):
http://chandlerproject.org/Projects/SharingProject (morgen)
http://chandlerproject.org/Projects/DumpReload (eim -- morgen)
http://chandlerproject.org/Teams/CpiaFramework (John)

Pages that are proposals for feature work to come, or proposals for 
feature work already implemented:
http://chandlerproject.org/Projects/StylesProject (Philippe)
http://chandlerproject.org/Projects/ChandlerInstallers (bear)

Pages that tracked work particular to a release:
http://chandlerproject.org/Journal/CalendarBugsFeatures20060203
http://chandlerproject.org/Journal/DotSevenFreeBusyEngineering
http://chandlerproject.org/Projects/DotSevenDashboardEngineering
http://chandlerproject.org/Projects/ZeroPointSevenArchitecture
http://chandlerproject.org/Projects/BugzillaComponentsZeroPointSeven
http://chandlerproject.org/Projects/InviteEngineering
http://chandlerproject.org/Projects/EditUpdateTracking
http://chandlerproject.org/Projects/CalendarBlocksProject (0.5)
http://chandlerproject.org/Projects/CalendarRecurrence (0.6)
http://chandlerproject.org/Teams/CpiaScript (0.6)

Pages that should be marked as obsolete and not linked to (other than as 
historical footnotes):
http://chandlerproject.org/Projects/DetailViewProject
http://chandlerproject.org/Projects/SecurityFramework
http://chandlerproject.org/Projects/ICalendarInteroperationProject
http://chandlerproject.org/Projects/WebdavService
http://chandlerproject.org/Projects/EmailService
http://chandlerproject.org/Projects/DomainModelProject
http://chandlerproject.org/Projects/ParcelFramework
http://chandlerproject.org/Projects/RepositoryFramework

If people agree to this proposal (modulo disagreeing with my 
classification of a particular page above), my next actions would be:
- mark certain pages as "historical" or "obsolete"
- update the "desktop team" and "developer area" pages to be consistent 
with the above decisions
- have some space (either on developer area home or linked to from 
there) to link to documentation, proposals, etc.

Cheers,
Katie