Jump to: navigation, search

Difference between revisions of "Meetings/Ceilometer"

Line 20: Line 20:
 
** nijaba to resfresh http://wiki.openstack.org/Governance/Proposed/Ceilometer before sending email to the tc
 
** nijaba to resfresh http://wiki.openstack.org/Governance/Proposed/Ceilometer before sending email to the tc
 
* Release status
 
* Release status
 +
* Naming convention for Meters
 
* Open discussion
 
* Open discussion
  

Revision as of 06:33, 10 October 2012

Weekly Metering meeting

The ceilometer metering project team holds a meeting in #openstack-meeting:

  • Even weeks on Thursdays at 1500 UTC.
  • Odd weeks on Wednesdays at 2100 UTC /!\ on hold until after Grizzly summit, all weeks are even until then!

Everyone is welcome.

The blueprint that is used as a basis for the ceilometer project can be found at EfficientMetering

Next meeting

 Thursday Oct 11 at 1500 UTC

Agenda

  • Review last week's actions
    • jd to create a stable branch on monday
    • nijaba to prime release notes in the docs
    • nijaba to find a way to give admin right to jd__ and dhellmann for github
    • jd to check if infrateam can generate a tarball for us
    • nijaba to resfresh http://wiki.openstack.org/Governance/Proposed/Ceilometer before sending email to the tc
  • Release status
  • Naming convention for Meters
  • Open discussion

Apologies for absence

Previous meetings

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
#startmeeting
#chair <white space separated list of chairs>
#link <thread announcing the meeting>
#topic actions from previous meetings
<all #actions from people responsible for actions from the previous meetings>
   
  • Update Previous meetings
  • Update == Agenda for next meeting ==
  • Mail the automatic summary as a reply to the invitation