Jump to: navigation, search

Difference between revisions of "Meetings/PythonOpenStackSDK"

(Weekly Python-OpenStackSDK Team Meeting)
Line 2: Line 2:
  
 
If you're interested in [[PythonOpenStackSDK]], we will be holding public meetings weekly in on freenode in #openstack-meeting-3 at 19:00 UTC on Tuesdays. Please feel free to add items to the agenda below with your name and we'll cover them. The meeting will last 1 hour.
 
If you're interested in [[PythonOpenStackSDK]], we will be holding public meetings weekly in on freenode in #openstack-meeting-3 at 19:00 UTC on Tuesdays. Please feel free to add items to the agenda below with your name and we'll cover them. The meeting will last 1 hour.
 +
 +
== Agenda for 2014-05-05 1900 UTC ==
 +
* Roll Call
 +
* https://review.openstack.org/#/c/90301/ -- Resource Properties
 +
** Has two +1s but one minor issue, has a suggestion to address it.
 +
* https://review.openstack.org/#/c/91448/ -- Example code for presentation
 +
** Test failure in dependent change, but it seems pretty straightforward.
 +
* https://review.openstack.org/#/c/90538/ -- Add presentation layer
 +
** Was changed around from initial comments by Jamie. Last patch set has a comment that will make tests pass all around.
 +
* https://review.openstack.org/#/c/91889/ -- Authentication from keystoneclient
 +
* C&P from keystoneclient, needs to take out some deprecated or no longer useful things that came along with it
  
 
== Agenda for 2014-04-29 1900 UTC ==
 
== Agenda for 2014-04-29 1900 UTC ==

Revision as of 18:37, 6 May 2014

Weekly Python-OpenStackSDK Team Meeting

If you're interested in PythonOpenStackSDK, we will be holding public meetings weekly in on freenode in #openstack-meeting-3 at 19:00 UTC on Tuesdays. Please feel free to add items to the agenda below with your name and we'll cover them. The meeting will last 1 hour.

Agenda for 2014-05-05 1900 UTC

Agenda for 2014-04-29 1900 UTC

  • Roll Call
  • Open discussion? Anything on your minds?

Agenda for 2014-04-22 1900 UTC

  • Roll Call
  • Outline a plan to move forward, ideally with rough timelines. If we can pull it together, it would be nice to head into the OpenStack Summit with a minimum viable demo of the project.
    • Class design decision between the proposals
      • What is outstanding?
      • What do we need to do to reach consensus?
      • When can we build on top of the winner?
    • When can we implement the minimally needed Keystone bits to build out a service?
    • When can we implement the first service?
  • Discuss open reviews

Agenda for 2014-04-15 1900 UTC

Agenda for 2014-04-08 1900 UTC

  • Roll Call (many parties in transit to PyCon)
  • Discussion of base code for class design commit: https://review.openstack.org/#/c/85720/
    • Limit discussion to design approach, and not specific code concerns
    • There is one other proposed entry, but no code yet. Any others we should consider?
    • Timeline for selecting a design and moving forward with it
  • Discussion of any other in-progress reviews
  • Possible BoF at PyCon if enough people attending

Agenda for 2014-04-01 1900 UTC

Agenda for 2014-03-25 1900 UTC

Agenda for 2014-03-18 1900 UTC

Agenda for 2014-03-11 1900 UTC

Agenda for 2014-03-04 1900 UTC

  • Roll Call
  • Feedback on the wiki / current state (open discussion)
  • Discuss extension models for third-party vendors
  • API strawman status

Agenda for 2014-02-19 1900 UTC

  • Roll Call
  • Feedback on the wiki / current state (open discussion)
  • Current public API designs & interfaces
  • Internal HTTP client architecture
  • State of blueprints
  • PTL

Previous Meetings