[Here's a roughed in agenda for the three days. Please edit away.]
Roles:
- We have two facilitators and five documenters (or else three and four). At any given time one person is facilitating, one documenting. We rotate these roles so everyone gets a chance to participate fully.
Day 1. Broad vision plus introductory discussion of fields in core.
Select roles. Review and refine agenda.
-
Introductions. A bit about ourselves. [all]
-
Lightning talks (five minutes). [all]
-
Broad spec of unified set of data APIs. What, not how. [all]
-
CCK fields: Current status [Karen and Yves]
-
CCK fields: What new features will the CCK fields implementation need? Example: Fields can be associated with all object types (user, file, etc.), not only nodes.
-
Having achieved the minimum, what might next steps be? Example: All object properties or relationships are handled as fields. A simple example would be user created date. A complex example might be node taxonomy.
Day 2: Detailed planning of fields in core
Taking our new features tasks as identified in Day 1, discuss each in detail plus add new ones as needed. What do these solutions look like?
Day 3: Concrete tasks and teams
Break the work into concrete tasks with timelines and proposed implementation teams, including leaders and initial proposed membership.
Review broad spec as identified on day 1. To what extent do the concrete tasks fulfill this vision?
Review process of design sprint. What worked, what didn't, lessons?
Assign short term work in preparation for DrupalCon presentation.