This is a snapshot of the CurrentCombinedStatus as of Mon Nov 1 07:00:20 2004

Current Combined Status

This page consolidates the status of all the different projects.

---

Apps (from ApplicationProject)

• Working on tech documentation (tracked in bugzilla, docs on wiki)
• Planning .5 tasks (bottom up list and estimates)
  • wxPythonProject: WxPythonProjectZeroPointFivePlanning^? (David and Jed)
  • CpiaFramework: cpia list (John and Donn)
  • developer dogfood (Katie, Ted and Morgen)
  • EngineeringIssues: general list of miscellaneous engineering issues (Katie)
  • calendar and other ZeroPointFivePlanning apps requirements (whole team)
• Working on .5 bugs that were punted from .4

---

Services (from ServicesWorkingGroup)

Plan for milestone 0.4.01 (Nov 9)

• Brian: Adding SMTP type to exceptions in Twisted
• Brian: Fix Timeout logic in Twisted
• Brian: Clean code based on code review
• Brian: Determine if a way to automate deferred callback and views
• Brian: Continue working with Barry Warsaw to get a standard email address validator in to standard dist of Python
• Brian: Refactor mail code to get API logic out of Mail Content Model and CPIA callbacks out of Mail Service.
• Heikki: M2Crypto + Twisted integration

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/19]

• Documentation

---

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