This is a snapshot of the CurrentCombinedStatus as of Mon Oct 11 07:00:17 2004

Current Combined Status

This page consolidates the status of all the different projects.

---

Apps (from ApplicationProject)

Plans for 0.3.26 Code Freeze

• CpiaFramework: Mac toolbar fixes in build (Jed and David) done
• CpiaFramework: wx.Grid fixes in build (Jed and David) done
• testing and bug fixing: everyone
• reviews: Katie's calendar/collection canvas not done
• reviews: Jed's layout selector and John's kind filter done

---

Services (from ServicesWorkingGroup)

Plan for milestone 0.3.27

• Major goal: converge/maintain zero bugs
• Brian: Code reviews
• Stuart: Fix bugs (count: 5) including possibly performance and unit tests
• Brian: Upgrade to latest Twisted with Brian's IMAP patch
• Brian: Document email model (bug #?)
• Aparna: continued testing

Results for milestone 0.3.26 (code freeze)

• Build: Heikki: Linux launcher bug, take 3
• Build: Get Jurgen to install some packages related to CVS
• 0.5 Planning, Heikki: Investigate Projects.WebDAV ACL support
• Release: Get more bug reports/charts working (Heikki)
• Stuart: Fix bugs (count: 10), improve unit tests, try not to break things Now 5 bugs
• Brian: Fix bugs (count: 4) Done: down to zero bugs
• Brian: Code reviews Planned Thurs Oct 7
• Brian: Fix a bunch of bugs in Twisted library

Bugzilla status by person (shows only tasks that have been entered in Bugzilla):

• Services group Bugzilla status

---

Repository (from RepositoryFramework)

Plan for (3.26) [10/5]

• Bug fixing

0.4 Community Goals

• One or two people helping with QA for the repository -- confirming bugs, reducing test cases, etc.
• One or two people working on the repository.
• Not originally a goal, but spin out pylucene project and add contributers

---

Design (from DesignGroupMilestones)

By Integration Point "B"

• Complete first draft of production projects for following:
  • Rule builder
  • Dashboard view
  • Universal text entry box
• Brainstorm and scope search
• Conduct lightweight (concept and paper prototype) usability tests

---

Build (from BuildProject^?)

0.4 (ZeroPointFour^?) Goals

• wxWidgets 2.5 migration - completed
• Dependencies don't work in all cases; fix them: (30 Apr) Medium
• Investigate switching away from CVS (Subversion, Perforce, ...): (21 May) Medium/Large
  • Would obviously affect Bonsai, LXR, maybe other webtools
• Keep up to date with latest releases of 3rd party libraries: ongoing
• Try to reduce Chandler's dependancy of slightly modified 3rd party libs - try to get Chandler use the standard libs: (21 May) Medium/Large
• Automate more of the build and release process
  • Smarter Tinderbox (performance reporting, separate release and debug builds, Bonsai links, ...): (28 May) Medium/Large
  • Automatic checksums on download packages: - completed
• Keep Tinderbox in green - goal is to have outages last less than 6 hours at a time.
• And in general managing build & release bug list
• See also ReleaseEngineeringGoals20040309^? meeting notes.

#Projects.ReleaseCommunityGoals

• Community-related goals:
  • one or two more ports.
    • Rationale: this helps verify we're not doing things that make porting hard. It also allows developers using othe distributions to participate.
    • Steps to encourage: Have a list of past and existing ports. Have easy to find info on wht to do if one needs help.
  • volunteers setting up more tinderboxes running on their machines that would report to our tinderbox which would display the results along with our tinderboxes.
    • Rationale: This allows us to see run thorough build cycles with more options -- release and debug builds, some different options on each, and for each platform.
    • Steps to encourage: get our infrastucture ready to accept data from other tinderboxes, and hopefully make it easy to add tinderboxes. Create a good set of information about why this is valuable, how to set up a tinderbox, how to send the data to us.
  • evaluate build-related feedback from Projects.PyCon^? and determine if there are easier or standardized ways that we should incorporate.
  • find one or two people with lots of python build experience to make suggestions about build improvements

---

Community (from CommunityHome)

• We're gathering data on community invovlement in the 0.3 timeframe.
• We have started developing goals for the 0.4 release.
• We continue to work on developing a CommunityPlan addressing community involvement through the 1.0 timeframe
• CommunityWorkingGroupMilestones^?
• CommunityRelatedOpenIssues^?

Plans for 0.4 Integration Point A

Goal	Status
Prepare presentation and demo for OSCON 2004	done

Plans for Milestone 0.3.21

Goal	Status
Change copyright notice on wiki and web to Creative Commons	80% done
Create consolidated status report wiki page	done
Improve wiki fonts, borders	done

Plans for 0.4 Integration Point B

Goal	Status

Plans for 0.4 Release

Goal	Status
Prepare presentation and demo for Web 2 conference	not started
Prepare presentation and demo for EDUCAUSE 2004	not started

---

Cross-project status

EngineeringIssues doesn't yet have status by milestones, but might someday.

We don't have a good status page for IT, but see EngineeringRequestsForIT^?.

-- DuckySherwood^? - 06 Jul 2004