Difference between revisions of "Meetings/Zaqar"
< Meetings
(Meeting 2 notes) |
|||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | = Weekly Marconi ( | + | = Weekly Marconi (queuing) meeting = |
The [https://launchpad.net/marconi Marconi] project team holds a meeting in <code><nowiki>#openstack-meeting-alt</nowiki></code>: | The [https://launchpad.net/marconi Marconi] project team holds a meeting in <code><nowiki>#openstack-meeting-alt</nowiki></code>: | ||
| − | * Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 1900 UTC] | + | * 1st and 3rd Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 1900 UTC] |
Everyone is welcome. | Everyone is welcome. | ||
| Line 11: | Line 11: | ||
== Next meeting == | == Next meeting == | ||
| − | * | + | * 7 Feb 2013 |
==== Agenda ==== | ==== Agenda ==== | ||
* Review last week's actions | * Review last week's actions | ||
| − | * | + | * Confirm: API will NOT be split into two namespaces, one for work queuing and one for eventing. |
* Finalize locking semantics | * Finalize locking semantics | ||
* Decide whether client state should be based on timestamps or markers (or make one optional) | * Decide whether client state should be based on timestamps or markers (or make one optional) | ||
Revision as of 16:32, 31 January 2013
Weekly Marconi (queuing) meeting
The Marconi project team holds a meeting in #openstack-meeting-alt:
- 1st and 3rd Thursdays at 1900 UTC
Everyone is welcome.
The blueprints that are used as a basis for the Marconi project can be found at https://blueprints.launchpad.net/marconi
Next meeting
- 7 Feb 2013
Agenda
- Review last week's actions
- Confirm: API will NOT be split into two namespaces, one for work queuing and one for eventing.
- Finalize locking semantics
- Decide whether client state should be based on timestamps or markers (or make one optional)
- Open discussion
Backlog
Stuff we want to talk about in a future meeting:
- Talk about the state of XML support in OpenStack and decide where we stand on the issue.
- Discuss items from the API blueprint decisions list
- Supporting mobile devices, doing so securely (allowing mobile posts to a queue)
- Authorization based on an API key generated for a specific app and a specific queue
- Authentication in general
- Max payload size - give people what they need but also want to encourage appropriate usage of the service
- Audit river - should we do it, and if so, should it be an optional or mandatory part of the spec?
Previous meetings
- meeting 2 | Concrete queues, no tags, locking semantics, unified queue types or ? | 24 Jan 2013 | log | summary
- meeting 1 | Kickoff |17 Jan 2013 | log | summary
Meeting organizers
- Publish the agenda 24h in advance
- Mail the agenda to the list and invite participants
- Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
- Use http://meetbot.debian.net/Manual.html to get an automatic summary
- Prepare an outline for the meeting to speed things up (see http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html for an actual example)
- Record decisions and commitments; review in the next meeting
