Difference between revisions of "Solum/BreakoutMeetings"

Revision as of 23:38, 13 November 2013

These are special focus meetings to be held for interactive design of key topics. They are conducted by IRC, and with an etherpad tool for interactive editing of work product.

Solum Design Workshop

We encourage all developers working on Solum to attend this event.

Register here for in-person attendance
Date/Time: Tuesday, November 19, 2013 at 9:00 AM - Wednesday, November 20, 2013 at 3:00 PM
Location: Rackspace, 620 Folsom Street, San Francisco, CA 94107
Hotel: A number of us are staying at the Courtyard by Marriott in Downtown Oakland and riding into the city on BART. This is a more cost effective option, as hotels are sold out because of the Salesforce conference happening on the same dates at Moscone Center.
Remote Attendees: We will use #solum, etherpads, and probably Google Hangout (TBD).

Solum API Deep Dive

There will be a series of these meetings to focus on API design concerns. Schedule was selected based on input from contributors. The meeting will be held on freenode IRC in #solum, and will utilize an etherpad for collaborative editing.

PART I: Wednesday 2013-11-13 1:00 PM US/Pacific (2100 UTC, convert to your timezone)
- Agenda
  - Overview of API Related Blueprints: rest-api-base, api
  - Discuss creation of code repository for API spec, as suggested in an ML thread using API-Blueprint format.
  - Current API Spec linked from api blueprint.
    - Overview of proposed API nouns and what the purpose for each.
    - Devdatta Kulkarni: Ground the API discussion using one of the flows outlined in the Git integration blueprint.
- Minutes (text), and Log
  - Summary: Overview of Components, Assemblies, Artifacts, Applications, and Plans. Example use cases for Sensors and Operations.

PART II: Friday 2013-11-15 1:00 PM US/Pacific (2100 UTC, convert to your timezone)
- Agenda
  - Current API Spec linked from api blueprint.
    - Overview of proposed API nouns and what the purpose for each.
    - Devdatta Kulkarni: Ground the API discussion using one of the flows outlined in the Git integration blueprint.

@@ Line 17: / Line 17: @@
 *** Current API Spec linked from [https://blueprints.launchpad.net/solum/+spec/api api] blueprint.
 **** Overview of proposed API nouns and what the purpose for each.
-*** To ground the discussion, I propose we use at least one of the flows outlined in the Git integration blueprint (https://wiki.openstack.org/wiki/Solum/FeatureBlueprints/GitIntegration) for the API discussion (comment added by Devdatta Kulkarni)
+**** Devdatta Kulkarni: Ground the API discussion using one of the flows outlined in the [[Solum/FeatureBlueprints/GitIntegration|Git integration blueprint]].
+** [http://irclogs.solum.io/2013/solum.2013-11-13-21.02.html Minutes] ([http://irclogs.solum.io/2013/solum.2013-11-13-21.02.txt text]), and [http://irclogs.solum.io/2013/solum.2013-11-13-21.02.log.html Log]
+*** Summary: Overview of Components, Assemblies, Artifacts, Applications, and Plans. Example use cases for Sensors and Operations.
 * PART II: Friday 2013-11-15 1:00 PM US/Pacific (2100 UTC, [http://www.worldtimebuddy.com/?qm=1&lid=8,0,4726206&h=8&date=2013-11-15&sln=13-14 convert to your timezone])
+** Agenda
+*** Current API Spec linked from [https://blueprints.launchpad.net/solum/+spec/api api] blueprint.
+**** Overview of proposed API nouns and what the purpose for each.
+**** Devdatta Kulkarni: Ground the API discussion using one of the flows outlined in the [[Solum/FeatureBlueprints/GitIntegration|Git integration blueprint]].