|
Size: 890
Comment:
|
Size: 1949
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| - Documentation | * Documentation * Adding interfaces (what exactly are the public APIs? it's become muddy) * Bug fixes * Code cleanup * Saner tests * Multi-database support, http://zope.org/Wikis/ZODB/MultiDatabases * Savepoints * Getting rid of versions * Database iteration (e.g., iterate over all the objects of class Foo; there's no efficient way to do this now, especially when using ZEO) * Conflict resolution redesign. Possiblities: make it optional, make it pluggable, use a registry of class->resolution code instead of methods, get it off the ZEO server? |
| Line 13: | Line 22: |
| - Adding interfaces (what exactly are the public APIs? it's become muddy) | Note that to be able to make code contributions, you must be a Zope contributor: http://dev.zope.org/Subversion Note that you don't have to be a Zope user to be a Zope contributor. :) You don't have to be a Zope contributor either to participate in working out (and writing up) proposals for things ZODB could/should be doing better. |
| Line 15: | Line 27: |
| - Bug fixes | If you plan to participate, please put your name below, and, if you won't be there all 4 days, indicate which days you plan to be there. |
| Line 17: | Line 31: |
| - Code cleanup | Participants: * Tim Peters (Sat, Sun, Mon, Tue) * Christian Theune (All days) |
| Line 19: | Line 35: |
| - Saner tests | If you don't sign up, you can still come and participate. The sign up is to give us an idea who will be there. |
| Line 21: | Line 38: |
| - Multi-database support, http://zope.org/Wikis/ZODB/MultiDatabases | ChrisMcDonough says ---- Other minor things: |
| Line 23: | Line 42: |
| - Savepoints | - Make ZEO server write a pidfile so we can rotate its logs by sending an appropriate signal. |
| Line 25: | Line 45: |
| - Getting rid of versions | - Come up with a Wiki page somewhere that details how to check stuff into ZODB without making Tim's life a nightmare. |
| Line 27: | Line 48: |
| - Database iteration (e.g., iterate over all the objects of class Foo; there's no efficient way to do this now, especially when using ZEO) |
- Allow ZEO clients to query the active ZEO server for its system clock value (useful for synchronization). |
| Line 30: | Line 51: |
| Note that to be able to make contributions, you must be a Zope contributor: http://dev.zope.org/Subversion (Note that you don't have to be a Zope user to be a Zope contributor. :) |
Let's work on making ZODB better!
Leader: Tim Peters
Jim Fulton will present the ZODB architecture as a basis for work. This will be a good opportunity to learn about many of the nitty-gritty details of ZODB.
There are many things we could work on, including:
- Documentation
- Adding interfaces (what exactly are the public APIs? it's become muddy)
- Bug fixes
- Code cleanup
- Saner tests
Multi-database support, http://zope.org/Wikis/ZODB/MultiDatabases
- Savepoints
- Getting rid of versions
- Database iteration (e.g., iterate over all the objects of class Foo; there's no efficient way to do this now, especially when using ZEO)
Conflict resolution redesign. Possiblities: make it optional, make it pluggable, use a registry of class->resolution code instead of methods, get it off the ZEO server?
Note that to be able to make code contributions, you must be a Zope contributor: http://dev.zope.org/Subversion Note that you don't have to be a Zope user to be a Zope contributor. 
You don't have to be a Zope contributor either to participate in working out (and writing up) proposals for things ZODB could/should be doing better.
If you plan to participate, please put your name below, and, if you won't be there all 4 days, indicate which days you plan to be there.
Participants:
- Tim Peters (Sat, Sun, Mon, Tue)
- Christian Theune (All days)
If you don't sign up, you can still come and participate. The sign up is to give us an idea who will be there.
ChrisMcDonough says
Other minor things:
- - Make ZEO server write a pidfile so we can rotate its logs by sending an appropriate
- signal.
- making Tim's life a nightmare.
- (useful for synchronization).