Difference between revisions of "Meetings/MuranoAgenda"
< Meetings
(→Agenda) |
m |
||
| Line 3: | Line 3: | ||
== Next meetings == | == Next meetings == | ||
| − | *July | + | *July 22, 2014, 17:00 UTC (chaired by katyafervent) |
=== Agenda === | === Agenda === | ||
| Line 14: | Line 14: | ||
** [https://review.openstack.org/#/q/murano+AND+status:+open,n,z Reviews] we should prioritize for juno-2 | ** [https://review.openstack.org/#/q/murano+AND+status:+open,n,z Reviews] we should prioritize for juno-2 | ||
** [https://bugs.launchpad.net/murano/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search Important bugs] we need to fix | ** [https://bugs.launchpad.net/murano/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search Important bugs] we need to fix | ||
| + | * [sjmc7] - Image tagging (http://lists.openstack.org/pipermail/openstack-dev/2014-July/040673.html) - whether there's anything we can do short term to make this more flexible | ||
* Open discussion | * Open discussion | ||
** [ruhe] reviewers, please make sure linked blueprints are approved and have all the required fields filled before you set +1/+2/approved on a patch. I found multiple instances of almost empty blueprints with merged patches. That doesn't help to track changes we have in the project. | ** [ruhe] reviewers, please make sure linked blueprints are approved and have all the required fields filled before you set +1/+2/approved on a patch. I found multiple instances of almost empty blueprints with merged patches. That doesn't help to track changes we have in the project. | ||
Revision as of 15:51, 22 July 2014
We have meetings in #openstack-meeting-alt weekly on Tuesdays at 17:00 UTC.
Next meetings
- July 22, 2014, 17:00 UTC (chaired by katyafervent)
Agenda
- Action Items Review
- [katyafervent & tsufiev] Provide an update on horizon/dashboard/selenium tests research
- Discuss approval of https://blueprints.launchpad.net/murano/+spec/support-keystone-v3
- [sjmc7] Update on (can be skipped, if there are no updates) trusts
- Discuss https://blueprints.launchpad.net/murano/+spec/application-license-tab
- Juno-2 release - July 24
- Reviews we should prioritize for juno-2
- Important bugs we need to fix
- [sjmc7] - Image tagging (http://lists.openstack.org/pipermail/openstack-dev/2014-July/040673.html) - whether there's anything we can do short term to make this more flexible
- Open discussion
- [ruhe] reviewers, please make sure linked blueprints are approved and have all the required fields filled before you set +1/+2/approved on a patch. I found multiple instances of almost empty blueprints with merged patches. That doesn't help to track changes we have in the project.
Checklist for the meeting organizer
- Publish the agenda 24h in advance.
- 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.
- Record decisions and commitments; review in the next meeting.
