[Openstack-poc] Fwd: 3rd Party APIs

FYI. Here is a message that was sent to the list but was refused as non-member post. I think it brings some perspective on how the ecosystem is organizing about 3rd party APIs support, so I forward it on this thread. Message original Sujet: 3rd Party APIs Date : Thu, 3 May

[Openstack-poc] [Bug 946573] Re: 404 handler for doc sites

** Project changed: openstack-common = openstack-ci -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/946573 Title: 404 handler for doc sites Status in OpenStack Core

[Openstack-poc] [Bug 927650] Re: cfg: unneeded multiple inheritance

** Changed in: openstack-common Milestone: None = 2012.1 ** Changed in: openstack-common Importance: Undecided = Low ** Changed in: openstack-common Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of OpenStack Common Drivers,

[Openstack-poc] [Bug 925775] Re: utils.import_object sometimes masks the failed import

Think this is fixed by: https://review.openstack.org/#/c/6906/ ** Changed in: openstack-common Milestone: None = folsom-1 ** Changed in: openstack-common Assignee: (unassigned) = Russell Bryant (russellb) ** Changed in: openstack-common Importance: Undecided = Medium ** Changed in:

[Openstack-poc] [Bug 915039] Re: flags.FLAGS( crashes bpython

** Changed in: openstack-common Status: Fix Committed = Fix Released ** Changed in: openstack-common Milestone: None = 2012.1 -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common.

[Openstack-poc] [Bug 627792] Re: Support getting a logger

Moving to Opinion, no progress in 18+ months and a blueprint would be better ** Changed in: openstack-common Status: New = Opinion -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common.

[Openstack-poc] [Bug 930625] Re: PEP8 cleanup (openstack-common)

** Changed in: openstack-common Milestone: None = 2012.1 ** Changed in: openstack-common Status: Fix Committed = Fix Released ** Changed in: openstack-common Importance: Undecided = Low -- You received this bug notification because you are a member of OpenStack Common Drivers,

[Openstack-poc] [Bug 930270] Re: flagfile interpolation breaks instance_name_template

** Changed in: openstack-common Status: Fix Committed = Fix Released ** Changed in: openstack-common Milestone: None = 2012.1 ** Changed in: openstack-common Importance: Undecided = High -- You received this bug notification because you are a member of OpenStack Common Drivers,

[Openstack-poc] [Bug 963509] Re: update.py doesn't handle dependencies of configured modules

** Changed in: openstack-common Status: New = Confirmed ** Changed in: openstack-common Importance: Undecided = Wishlist -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common.

[Openstack-poc] [Bug 960487] Re: Request deserializer does not pass an empty body

Ok, based on Brian Waldon's comment in the review I'm going to close this ** Changed in: openstack-common Status: In Progress = Invalid ** Changed in: openstack-common Importance: Undecided = Wishlist -- You received this bug notification because you are a member of OpenStack Common

[Openstack-poc] [Bug 976267] Re: auto generate AUTHORS for packaging

** Changed in: openstack-common Status: New = Fix Committed ** Changed in: openstack-common Importance: Undecided = Medium ** Changed in: openstack-common Milestone: None = folsom-1 -- You received this bug notification because you are a member of OpenStack Common Drivers, which

[Openstack-poc] [Bug 967400] Re: iniparser needs absolute import

** Changed in: openstack-common Status: Fix Committed = Fix Released ** Changed in: openstack-common Importance: Undecided = Medium ** Changed in: openstack-common Milestone: None = 2012.1 -- You received this bug notification because you are a member of OpenStack Common Drivers,

[Openstack-poc] [Bug 965563] Re: Usability issue: is_public=yes sets Public: No

openstack-common fix: https://review.openstack.org/#/c/5712/ ** Changed in: openstack-common Status: New = Fix Released ** Changed in: openstack-common Importance: Undecided = Medium ** Changed in: openstack-common Assignee: (unassigned) = Sean Dague (sdague-b) ** Changed in:

[Openstack-poc] [Bug 976267] Re: auto generate AUTHORS for packaging

** Changed in: openstack-common Status: In Progress = Fix Committed ** Also affects: nova Importance: Undecided Status: New ** Also affects: swift Importance: Undecided Status: New ** Also affects: horizon Importance: Undecided Status: New -- You received

[Openstack-poc] [Bug 943336] Re: New requirements never get written out

Could do with more details here, I'm not sure I follow what the issue is ** Changed in: openstack-common Assignee: (unassigned) = Jason Kölker (jason-koelker) ** Changed in: openstack-common Importance: Undecided = Low ** Changed in: openstack-common Milestone: None = folsom-1 --

[Openstack-poc] [Bug 976267] Re: auto generate AUTHORS for packaging

Mark, ?? Can you please explain why you set it as Fix committed even though the patch should go in few more projects? ** Changed in: nova Assignee: (unassigned) = Bhuvaneswaran A (bhuvan) -- You received this bug notification because you are a member of OpenStack Common Drivers, which is

[Openstack-poc] [Bug 976267] Re: auto generate AUTHORS for packaging

Mark, nevermind. I got it. -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/976267 Title: auto generate AUTHORS for packaging Status in OpenStack Dashboard (Horizon):

Re: [Openstack-poc] [Bug 943336] Re: New requirements never get written out

Honestly, I think we might want to delete write_requirements() altogether. I don't think it's beneficial... asign this to me and I'll get it fixed up. On 05/04/2012 11:30 AM, Mark McLoughlin wrote: Could do with more details here, I'm not sure I follow what the issue is ** Changed in: