Jump to: navigation, search

Difference between revisions of "Watcher Meeting Agenda"

m
Line 10: Line 10:
 
## tpeoples> sballe: if we want to keep 1500 UTC the only day that is available is Friday. There is a slot open for 1400 UTC on Tuesday, Wednesday. Slots open for Wednesday at 1600. i uploaded the ical into google calendar: https://www.google.com/calendar/render?pli=1#main_7%7Cweek-2+23371+23377+23373
 
## tpeoples> sballe: if we want to keep 1500 UTC the only day that is available is Friday. There is a slot open for 1400 UTC on Tuesday, Wednesday. Slots open for Wednesday at 1600. i uploaded the ical into google calendar: https://www.google.com/calendar/render?pli=1#main_7%7Cweek-2+23371+23377+23373
 
# Mailing list creation
 
# Mailing list creation
 +
## Quick comment: OpenStack doesn;t run seperrate mailing lists. We should use the openstack-dev@lists.openstack.org mailing list with "[watcher]" in the subject.
 
# Tokyo summit actions
 
# Tokyo summit actions
  

Revision as of 14:24, 7 October 2015

Weekly Meetings

10/07/2015 Agenda:

  1. review the talk proposal for Tokyo (still in standby mode) https://docs.google.com/presentation/d/1gdb3PcC8KnKvs9PmblludTAqXmBI92t3zxTsX0BmPE0/edit?usp=sharing
  2. Intel & IBM status on resources for Watcher
  3. all blueprints wrote down on launchpad https://launchpad.net/watcher
  4. Watcher wiki update
  5. Weekly IRC meeting
    1. When do we want to have these meetings?
    2. tpeoples> sballe: if we want to keep 1500 UTC the only day that is available is Friday. There is a slot open for 1400 UTC on Tuesday, Wednesday. Slots open for Wednesday at 1600. i uploaded the ical into google calendar: https://www.google.com/calendar/render?pli=1#main_7%7Cweek-2+23371+23377+23373
  6. Mailing list creation
    1. Quick comment: OpenStack doesn;t run seperrate mailing lists. We should use the openstack-dev@lists.openstack.org mailing list with "[watcher]" in the subject.
  7. Tokyo summit actions


09/30/2015 Agenda:

Announcements

  1. Re: OpenStack Watcher repos: The Stackforge in this list: https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement will be moved automatically to OpenStack repos. Watcher is on the list so we do not have to do anything.
    1. These changes are scheduled to occur on October 17, 2015.
  2. review the OpenStack Watcher vision document https://docs.google.com/document/d/1PAEK3eYi9Et2lpc6pT1JU2AoVSaivMmeHmj62qajqm8/edit#
  3. review the current architecture https://docs.google.com/presentation/d/1-AEqDPAOaLva4N9PkBhvQ070SxhSFPiNnLiUFKiSJj0/edit#slide=id.gca3d12c11_2_52
  4. review the actions list from our last workshop https://etherpad.openstack.org/p/watcher-workshop-rennes
    1. [sballe] Setup cadence for weekly meetings - work out an acceptable time for the group
    2. [acabot] Send out email to introducing Watcher to mailing lists (pre-requisites would be to have the wiki upadated, vision doc, etc.)
    3. [acabot] Clean up wiki document, including alignment with the Watcher vision document
    4. [sballe] Set up Git repositories on openstack.org
    5. [JeD56] Transfer code from existing StackForge repositories to Gerrit (after sballe gets the repositories configured)
    6. [jwcroppe] Create initial mission statement and vision doc and send out to team (jwcroppe: done - see "Watcher Vision Doc" in the "Key Links" section)
    7. [dtardivel] Add a link to the API generated doc in Watcher wiki
    8. [all] Write down blueprints in LaunchPad from the use cases list
  1. Tokyo summit actions
    1. [jwcroppe, sballe, acabot] Prepare slides for Watcher talk (still in 'standby' mode)
    2. [sballe] Figure out a place where we can do an ad-hoc talk
    3. Talk to Nova, Ceilometer, etc. PTLs to inform them of the project
    4. [acabot, jwcroppe, sballe] Consider a Nova unconference session to introduce Watcher
    5. [sballe] Setup a meeting with Monty Taylor to introduce him to Watcher
    6. [sballe, acabot, jwcroppe] Evangelize Watcher with other folks (e.g., jaypipes, bauzas, Perry Myers from Red Hat, folks from Rackspace, Julien Danjou from Red Hat)

Brief progress reports

Open Discussion