This is a snapshot of the CurrentCombinedStatus as of Mon Sep 27 09:01:59 2004

Current Combined Status

This page consolidates the status of all the different projects.

---

Apps (from ApplicationProject)

Plans for 0.3.25 Feature Freeze

• WxPythonProject: wxWidgets transition (David) plan to bring into main branch wed
• WxPythonProject: 100% CPU bug/native flicker fix (David)
• SharingUIProject^?: testing, bug fixing, overall sharing and email stability (Morgen, Donn) ongoing
• DetailViewProject: proposal and fix for stamping/attribute indirection problems (Donn) proposal sent out
• CpiaFramework: Mac toolbar fixes in build (Jed and David) waiting on wx252
• CpiaFramework: wx.Grid fixes in build (Jed and David) waiting on wx252
• SummaryTableViewProject: get columns to spec (Jed) all logged as visual bugs, many bugs fixed
• ApplicationChromeProject: combining views with tab (Jed) not done -- move to .5
• ApplicationChromeProject: delete (John)
• CpiaFramework: image in header (Jed)
• CpiaFramework: attribute editor validation (John) not done -- move to .5
• CpiaFramework: Kind filtering (John) bugs remain, but feature is in
• CpiaFramework: STRETCH -- sorting, multiple selection (John) not done -- move to .5
• CalendarBlocksProject: bug fixing (including visual bugs) (Katie) ongoing
• reviews: Morgen's sharing ui code done
• reviews: Katie's calendar/collection canvas not done
• reviews: Donn's notification to main view done
• issues: follow up meeting on sharing done
• issues: clarity on bugzilla fields used in release process done
• issues: item collection fixes accepted or not done: accepted
• issues: short term owner for mail bugs: Morgen and Heikki

Plans for 0.3.26 Code Freeze

• CalendarBlocksProject: testing and bug fixing (Katie)
• SharingUIProject^?: testing and bug fixing (Morgen, Donn)
• CpiaFramework: testing and bug fixing (Jed, John)
• ApplicationChromeProject: testing and bug fixing (Jed, John)
• SummaryTableViewProject: testing and bug fixing (Jed, John)
• DetailViewProject: testing and bug fixing (Donn)
• reviews: Katie's calendar/collection canvas
• reviews: Jed's layout selector and John's kind filter

Not done, out of .4

• ApplicationChromeProject: sorting, multiple selection
• CpiaFramework: attribute editor validation
• ApplicationChromeProject: combining views with tab

Issues

• team wants to allocate time in 0.5 for developer productivity tasks
  • generic item viewer/editor, improvements to repository viewer, etc.
• many instances of "notification" code: unify more in notification manager?
• a few fixes to 2.5.2.9 may show up (final version) -- do we pull these into the release?
• colored buttons for the toolbar to make chandler look spiffier in .4?
• are there showstoppers to linux fc 2 development? is it reasonable for john to move to fc2 for day to day development?

---

Services (from ServicesWorkingGroup)

Plan for milestone 0.3.25

• Build: Milestone build next week will be delayed from Sept 21 to Sept 22 or 23.
• Build: wxWidgets version upgrade is on a separate branch to minimize effect on other stuff
• Build: Heikki plans to fix Linux launcher bug and a similar bug for Windows that has a nasty workaround.
• QA: Aparna to work on script for demos as well as regular bug finding and resolution.
• Stuart: Fix a couple bugs, improve sharing unit tests
• Stuart: Code review already done
• Brian: code reviews when he gets back

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

• Services group Bugzilla status

---

Repository (from RepositoryFramework)

Plan for (3.25) [9/21]

• Persistence: Version Merging (started)
• Queries: evaluation engine [done] in bug fix mode

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