Links

• Project Management
  • Basecamp: project management via blog - Useful ideas for project dashboard
• Tools
  • generating python module dependency graphs - Good for deciphering Chandler
  • TWiki vs JotSpot^? - a comparison of TWiki and JotSpot^?
• Repository Performance
  • Comparisons of embedded db's - SQLLite doesn't fare very well, GDBM is the winner
• Related Projects
  • JetBrains Omea - in the same space
• Community Building
  • EPlugin hackfest - We should be thinking about doing this too
  • More on the EPlugin hackfest
  • Ubuntu Linux - a productized Debian. Perhaps we should be looking at this in the future.

Notes

Project management / organization / status

• The Apps group is now using Wiki notebook pages for reporting status and keeping daily work records. I slowed down on my wiki notebook pages because its a pain to create the pages and link them in. I wonder if this usage would be better served by giving each person a blog -- the blog software would take care of linking/archiving/etc. We could use the same software that the ASF is using for PlanetApache^? to display a group blog, which would aggregate all the posts into a single place. It would also have the benefit of providing a full RSS feed, which would make it easier to read all the status, etc.
• The Basecamp link (above) shows come good examples of the kind of functionality that I'd like to see in a project dashboard.

If you name your pages intelligently, you don't need to link them in. See SmallMeetingNotes, for example -- the Community pages are all linked in via a query. One disadvantage of a blog is that it's not as well set up for making changes at a later date. While in theory, the Journal is for things that don't change over time, in reality, many people go back (usually within about a week) and make changes. -- DuckySherwood

0.5 Tasks

• Developer Dogfood
  • help develop plan
  • implement items (unknown)
  • pylucene plan
    • front page, web log, etc.
  • increase use of transparent communication mid-process rather than only at the end
• Performance
  • trace tool
  • co-ordinate with Andi - work on requirements
  • TBD
• Query Language
  • Query Grammar
    • better notation for recursive kind queries
    • better notation for kind queries -- omit WHERE TRUE
    • handle floating point literals
    • bug with spaces in strings
    • clean up parameter syntax
    • clean up handling of path literals? (depends on addressing)
  • allow use of Pythonisms like infix 'is', 'contains'
  • yapps patches to Amit
  • Full Text
    • allow restriction to particular collections/kinds
  • Query semantics
    • queries over stamped (multiple superkinded) items
    • queries vs defaultValue/initialValue
    • allow parameters in paths?
    • orderBy (sorting) support - interaction with ref-collections
    • expand set of functions that can be used in queries
    • interruptible queries (generators vs ??)
    • queries vs item clouds -- do we want a way to preload a cloud using query notation?
  • Documentation
    • Overview
      • link to relevant docs/api docs/specs
    • spec
    • samples
• Query Processor
  • Notification
    • better notification for path queries
    • implement notification using monitors - change in semantics, must co-ordinate with ItemCollection^?
    • implement notification for full text queries
  • Full Text
    • support for full text indexing at the parcel.xml level (co-ordinate with Morgen)
  • Python API
    • factory methods for query creation (eliminate need to pass repository)
    • queries are items and query results are ref-collections
    • change execute method to compile() or prepare()
  • Performance
    • improve query performance by accessing repository internals (XPath?, don't create items)
    • paged result sets - interaction with ref-collections
  • Documentation
    • Overview
      • link to relevant docs/api docs/specs
    • samples
    • epydoc
• Data Model
  • Types
    • date/time types -- needed by Calendar EngineeringIssues
    • easier to use and better documented struct type
    • persistent tuple type * persistent dict (not RefDict^?) type
  • deletion semantics (explicit vs gc) EngineeringIssues
  • addressing mechanism EngineeringIssues
  • relationship kind EngineeringIssues
  • Documentation
    • specification (documentation and feature reduction)
  • non-uniform LOB API's
  • Repository Performance
  • use case walkthroughs
  • generate/replay traces
• Server Plan
  • help define plan
  • facilitate ASF liason if necessary (shouldn't be)
• Switch Version Control Systems
  • look at svn 1.10, svk
  • get opinions from GUI tool users
  • investigate interactions with tinderbox, bonsai, commits

Repository Roadmap

Unscheduled Large grain features

• Migration/Upgrade
  • import / export to neutral format
  • backup / restore
  • schema evolution
• Packaging / Release
  • distutils based build
• Access Control: Principal identification, storing ACLs, implement API
• Sharing/replication: implement private attributes, remote browsing
• Sharing/replication: read-write, two-way replication?

0.5

• Improve performance
• Reduce footprint

0.6

0.7 (Kibble)

-- TedLeung - 21 Oct 2004