Wiki Content Issues

• The dev docs area should be reworked (in part to eliminate redundancy with the sidebar links). In particular, DeveloperDocumentation and HackingChandler perhaps could be merged.
• There is some info on what you need to build at BuildingChandlerDesktop#buildRequirements, what platforms it builds on at ChandlerDesktopSource, and a little at GettingChandler. Not sure if that needs to be more prominent.
• The Design group has zillions of pages, and wrestles with finding stuff. See OsafLibraryProject^?.

• There are a bunch of different schedule pages that should be consolidated: ChatSchedule, Bugzilla milestone schedule, OsafPublicEventsSchedule^?. now INCLUDE from ChatSchedule into OsafPublicEventsSchedule^?. Can't do that with milestones and EventsAndMeetings without buy-in from the maintainers of those pages.

• Pages about code/projects that are somewhat separate from core Chandler -- both stuff we imported from the outside world (e.g. wxWidgets) and stuff we are exporting to the outside world (e.g. Projects.PyLucene) -- are poorly organized and hard to find. (Examples: LiasionsToOtherProjects, Projects.PyLucene, PyLuceneGoals, PyEgads, M2Crypto, LicensingTopics, ContributedCode) Created ThirdPartyCode, which has links to info about third-party projects that we use; reworked so that there is only one master table of third-party code; added links to the home page.
• The home page should be reworked to eliminate redundancy with the sidebar links; perhaps more "welcome, here's who we are, here's what this is" text. done
• It would be nice to make PageListByPerson and PageListByPageType more automatically generated, perhaps with bilevel searches, using information from MaintainedBy. (Goal: remove the need for someone to add new people by hand.) Done. I spent a lot of time with formatted searches, trying to make bilevel search work -- and a simple single-level search sufficed.
• We don't have an org chart up. Text version put up at WorkingGroups^?.

-- DuckySherwood - 29 Jun 2004