Tentative Agenda

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
webchick's picture

Re-posting this as its own thing, per Barry. Admins, feel free to edit the crap out of this. ;)

Jan 17 - Jan 20
We get our collective stuff together internally... figure out a rough agenda, logistics about where/when we're meeting, compile resources, etc.

Jan 21
This group becomes the "Data API" group and is opened to the public.

We simultaneously make an announcement to the broader development community on the devel list/Drupal Planet (maybe front page d.o too?) that talks about what we're doing and invites interested members to join the Data API group (this one) and submit feedback on the agenda items.

Specific things to note in this announcement:
- The attendance list is basically final; we've all worked with each other before and think we could hammer through this faster in a small, closely knit group. We also found the money for it ourselves.
- The goal is for these developers with demonstrated contributions to Data API to have concentrated, uninterrupted face-to-face time to hash out strategies and such much faster than can happen online. It is NOT to have anything close to working code.
- We welcome feedback on the posted agenda, additional resources people have, etc. All feedback will be considered, but due to time it may not all be incorporated.

Jan 22 - Feb 1
Let the community/data API meeting team members comment on goals/agenda/etc. Incorporate/change things up as makes sense.

Feb. 2
Post final agenda.

Feb. 3
Announce over the previous channels that the Data API meetup starts tomorrow. Encourage people to watch the group for updates from the team throughout the next 3 days. Create a wiki page for session notes and point the people interested in commenting on the process there.

Feb 4 - Feb 7
Someone (wish it were me :) should create a wiki page on the group and take real-time notes as major decisions/milestones/summaries of discussions/etc. are reached.

Don't concern yourself with community feedback throughout the day: just get your talks complete and do what you have to do (but please please take notes and post them throughout the day). About a half hour before you're ready to wrap up at the end of the day, sift through the comments made (if any) and see if any have merit. Add them to the agenda for the next day. Do a similar quick check in the morning as well.

Feb 8+
Someone writes up a final "whitepaper" discussing what conclusions were reached during the meeting, and submits that to the devel list/Drupal Planet/d.o front page, etc. I'd also love if this was accompanied by some "lessons learned/best practices" from this experience, for anyone else who wanted to try/fund a similar thing.

This allows the best of all worlds:
- Small, tight, focused group to get this done
- Ability for community to get involved in the process without hindering it.

Comments

After-session

Crell's picture

Just a reminder that chx, nedjo, and I will still be here for a few days, and chx for another 2 weeks or so. Originally we were going to try and get code out of it, but now I guess we'll figure out what we're going to do after this session. We may try to code stuff, we may not.

This is the meetup planning group

bjaspan's picture

One note: This is the meetup planning & logistics group. It is for the attendees to plan what we will discuss and work on. The required reading post, for example, is necessary so that everyone knows what everyone else is talking about when we arrive; otherwise, we're wasting our time.

We'll make it public shortly because the community can clearly help us focus our thinking and point us to related issues we need to be away of. But we do not want to make this the "Data API" group because then the "meetup planning" signal to noise ratio will plummet.

There clearly should be a Data API group (isn't there already?). Just not this one.

Database Schema API

Crell's picture

The Schema API group is where the discussion seems to be so far. I don't know if usurping that is appropriate or if we want to start a new one. As you run the Schema API group, I'll let you make that call. :-)

Fields in Core

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: