On Sep 13, 2016, at 10:42 AM, Terry Wilson wrote:
> All performance matters. All
> memory consumption matters. Being wasteful over a purely aesthetic few
> extra characters of code is silly.
import this
--
topics. If you have some ideas, please add them to
the agenda at https://wiki.openstack.org/wiki/Meetings/NovaScheduler
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
would like to discuss to the agenda.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
n Profile: http://www.openstack.org/community/members/profile/280
Freenode: edleafe
Website: https://blog.leafe.com
Twitter: @edleafe
[0] https://en.wiktionary.org/wiki/moon_shot (definition 3)
-- Ed Leafe
__
OpenStack Deve
you’d like to discuss to the agenda before the meeting.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
s a bit self-serving, especially to an outsider who might not
know me very well. But I’m sure that Thierry and Doug and others, who have
known me for many years, understand my intent: to keep improving OpenStack.
-- Ed Leafe
___
re elected do the actual work. If the
conversations aren’t happening when the people who are voting are most likely
to be paying attention, then it’s just a small group talking amongst
themselves. And those elected may not represent the voters
items you’d like to discuss to the agenda before the meeting.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
a brief period between
> nomination deadline, and poll creation, maybe 1 week, to spark this
> debate and get the community engaged with the candidates. This goes for
> all of the elections.
Exactly. Most people vote when they get their email ballo
nute of the nomination
window, and ballots go out immediately after that, and voting starts. There
really needs to be a period when a) we know who all the candidates are, and b)
voting has not yet begun. I would like to see that period be created so that
the kind of question/answer/clarify process yo
think that this is a great idea, and would be willing to help in the effort
to make that happen again.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
ection, and
close it a week before. Or open it for two days, and close it a week before. I
don’t understand why, other than procrastination, we need such a long period.
If you’re serious about serving, throw you hat into
at recent
summits. It was the answers I got to these questions that made me start
thinking about how to improve the process.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
to have those discussions in person at the
summit. But if people are interested...
As always, the agenda is here:
https://wiki.openstack.org/wiki/Meetings/NovaScheduler
Please add any items you’d like to discuss to the agenda before the meeting.
-- Ed Leafe
://blog.leafe.com/virtual-bike-sheds/
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
> On Oct 17, 2016, at 8:45 PM, Jay Pipes wrote:
>
> On 10/17/2016 11:14 PM, Ed Leafe wrote:
>> Now that we’re starting to model some more complex resources, it seems that
>> some of the original design decisions may have been mistaken. One approach
>> to work around
roversions after that, 404 is the correct response. For all
other methods, the latest version should not have a maximum specified.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
ng to drive off those who want to work with the
coolest and latest stuff. This isn’t “exciting” work in that sense of the word.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
U
items you’d like to discuss to the agenda before the meeting.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
onally, I prefer ‘nin’, but I’ll
defer to others on that.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://
That said, what about something like
>
> state=!in:x,y,z
>
> This just makes me nervous that we're beginning to define our own query
> language.
Ugh - let’s not do that!
-- Ed Leafe
__
OpenStack
da for the API working group’s meeting tomorrow (Thursday) at
1600 UTC in #openstack-meeting-3
(http://www.timeanddate.com/worldclock/fixedtime.html?iso=20161117T16)
Please join the meeting tomorrow if you are able
301 - 322 of 322 matches
Mail list logo
