/wiki/Schulze_method#Use_of_the_Schulze_method
[2] http://www.cs.cornell.edu/w8/~andru/civs/proportional.html
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc
.
Thoughts ?
[1] http://wiki.openstack.org/Governance/Foundation/TechnicalCommittee
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc@lists.launchpad.net
Unsubscribe
is discussed. Whether their influence also counts as a formal vote
in the final TC tally is a bit of a separate question... which I'd
rather let the foundation technical members decide.
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list
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
is a bit more tricky here since most names are a bit overloaded. Maybe
OpenStack recommended project/plugin...
Regards,
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack
Joshua McKenty wrote:
We need to meet. I'm nominating RIGHT NOW, at the bar, in the Hyatt Lobby.
Alternatively, lunch tomorrow?
I can do lunch (in one hour!). Anyone else ?
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list
Jay Pipes wrote:
On the questions at hand, here are my thoughts:
1) satellite.openstack.org - we talked about setting something similar
up a long time ago around Related Projects but never had the
bandwidth. I think if we can get user curation tools in there so
there's some form distributed
Jonathan Bryce wrote:
We have 2 requests to use openstack.org for community-related technical
projects: one for satellite projects and one as the package name for a java
library. Would you all prefer to discuss tomorrow at 3:00 PM CDT/20:00 UTC or
over email?
Either.
Can't hurt to meet,
** Changed in: nova
Milestone: essex-3 = 2012.1
--
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/915039
Title:
flags.FLAGS( crashes bpython
Status in OpenStack Compute
** Changed in: nova
Milestone: essex-rc1 = 2012.1
--
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/954488
Title:
nova/openstack/common/cfg.py:
** Changed in: nova
Status: Fix Committed = Fix Released
** Changed in: nova
Milestone: None = essex-rc1
--
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/954488
(announced during the projectrelease meeting). Like for Boston,
sessions will be proposed on the site and reviewed by track leads.
We are still looking for a volunteer to organize/promote/handle the
lightning talks (after lunch every day).
Let me know if you have more questions,
--
Thierry Carrez (ttx
. Results from the elections are available online if you haven't
seen them: http://etherpad.openstack.org/xSWPqf6DWE
Should we now add DanW (as Quantum PTL) as well ?
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list: https
** Changed in: nova
Status: Fix Committed = Fix Released
** Changed in: nova
Milestone: None = essex-4
--
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/930270
) made some decisions...
There is definitely room for improvement here, and I'm very open to
suggestions -- though most of this should get overhauled anyway once the
foundation is set up.
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list
this in more detail
tomorrow at the PPB meeting.
Won't be around for the meeting today. FWIW, as far as release
management is concerned, Quantum did the best job for a project in
incubation so far in tracking features and aligning with release
policies ahead of time.
Cheers,
--
Thierry Carrez (ttx
John Dickinson wrote:
On Nov 8, 2011, at 10:54 AM, Thierry Carrez wrote:
With solution (2), if you look at the issue from Gerrit, GitHub,
Launchpad or Jenkins, those will be separate projects though. The fact
that they share the same PTL is not enough to make them one. For
example
if there is
disagreement. This is a duty, not a set of rights.
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-poc
consensus on the ML before deciding, but not giving the community a
chance to raise concerns about a given proposal is unfair (and in some
cases unproductive).
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list: https://launchpad.net
, on the other, security@ is common
practice... Would it just be autoforwarded to private list ?
vulnerability discussion classification (MSA/CVE)
MSA are Mozilla Security Advisories, I doubt we would issue those :)
Maybe OSA ?
Cheers,
--
Thierry Carrez (ttx)
Release Manager, OpenStack
4-week time-based plan option and grant Swift
an exception retrospectively if they have a reason to differ. There is
value in coordinating milestone dates, from an integrated product
testing standpoint.
--
Thierry Carrez (ttx)
Release Manager, OpenStack
this ?
Vish: what are your thoughts on the matter ?
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
, it could be added to the same page.
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-poc
More help
23 matches
Mail list logo