Jump to: navigation, search

Difference between revisions of "Meetings/MuranoAgenda"

(Next meetings)
Line 3: Line 3:
== Next meetings ==
== Next meetings ==
* Mar 18, 2014, 17:00 UTC
* Mar 25, 2014, 17:00 UTC
=== Agenda ===
=== Agenda ===
* Action Items Review
* Action Items Review
* Repo-reorganization progress
* API versioning
* Vote on getting rid of murano-common
* MuranoPl package name
  [ruhe] I will not be able to attend the meeting, so I'll put my thoughts on this topic here:
  There are two options now:
  1. Unbind murano-common releases from murano releases
  a. We will use pypi package instead of url to tarballs.o.o
  b. No need to copy-paste code (compared to option #2)
  a. For a proper release tracking we will need another Launchpad project
  b. Maintanance overhead (compared to option #2) - releasing, Launchpad management, packaging
  c. Another dependency not listed in global-requirements
  2. Copy murano-common code to modules which use it (murano-api and murano-agent)
  a. -1 dependency not listed in global-requirements
  b. Less maintenance overhead - no need to release another library, no need to create another Launchpad project
  c. No need to update murano-api/requirements.txt after we release new version of murano-common
  a. We will need to maintain two copies of the same code.
    Which I personally think is ok - there are just 20 commits in a 9 months history of this project
* ApplicationCatalog API
* UI for the Application Catalog
* Open discussion
* Open discussion

Revision as of 17:01, 25 March 2014

We have meetings in #openstack-meeting-alt weekly on Tuesdays at 17:00 UTC.

Next meetings

  • Mar 25, 2014, 17:00 UTC


  • Action Items Review
  • API versioning
  • MuranoPl package name
  • Open discussion

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.

Previous meetings