I interpreted the deafening silence to mean "I'm focused on my bugs,
whatever, just go make the wiki better."
Outline of what we have now below (though we could still use wiki
gardening to move additional useful links to the right place, and some
not-so-useful-links to history/archive):
*Home page for developers*
http://chandlerproject.org/Developers/WebHome
- "Development tools" section has information immediately useful for
building/testing/localizations/etc.
- "Reference materials" and "Tutorials" contain all wiki pages I found
with documentation that was at least sort of up-to-date (or a good
foundation for editing to be up to date).
*Desktop team page*
http://chandlerproject.org/Teams/DesktopTeam
- Meeting notes. Any future team meeting notes should be linked from here.
- People
- Team related resources that span releases like "self assigned projects".
*Desktop release team page*
http://chandlerproject.org/Teams/DesktopReleaseTeam
- Meeting notes for "release team" of QA/PPD/Build/Devs. All future
meeting notes should be linked from here.
- Release related resources that span releases (how to use bugzilla)
- Release history
*Desktop release dashboard*
http://chandlerproject.org/Developers/DesktopZeroDotSevenRelease
- Bugzilla queries we use for bug councils
- Philippe's graphs
- 0.7 plan tables (developer work plans)
- 0.7 specific documentation
*Old team pages*
http://chandlerproject.org/Projects/DeveloperPlatformProject
http://chandlerproject.org/Teams/ApplicationProject
- linked from new team page
- repository of out of date project and documentation pages
- links to old meeting notes, etc.
The new pages should outright *replace*:
http://chandlerproject.org/bin/view/Projects/DevelopmentHome
Cheers,
Katie
Katie Capps Parlante wrote:
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.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
