I think that how Docs handles these changes depends largely on whether
or not we're given a track. I'm aware that we didn't get one in Paris,
and as a consequence a lot of my team felt it was difficult to get any
real work done.
Like Sean, I appreciate that it's a difficult decision, but am
On 09/01/15 15:50 +0100, Thierry Carrez wrote:
[huge snip]
What do you think ? Could that work ? If not, do you have alternate
suggestions ?
Love it! Thanks for the thoughtful and detailed email.
Flavio
--
@flaper87
Flavio Percoco
pgp2LB9GMnSpn.pgp
Description: PGP signature
Tim Bell wrote:
Let's ask the operators opinions too on openstack-operators mailing list.
Sure, that's my next step. I first wanted to check that this change was
fine for historic Design Summit participants. I'll follow up with
operators and also discuss it at the Ops meetup.
FWIW, the
On Fri, Jan 9, 2015 at 8:50 AM, Thierry Carrez thie...@openstack.org
wrote:
Hi everyone,
The OpenStack Foundation staff is considering a number of changes to the
Design Summit format for Vancouver, changes on which we'd very much like
to hear your feedback.
The problems we are trying to
On 10/01/15 03:26, Michael Dorman wrote:
(X-posted to -operators.)
Any thoughts on how the ops track spaces would be requested, since there
is not a real ‘operators project’, PTL, etc.?
Based on our past events and summit survey feedback from Paris, I've
mentioned to Thierry that we
On 15:50 Fri 09 Jan , Thierry Carrez wrote:
Hi everyone,
The OpenStack Foundation staff is considering a number of changes to the
Design Summit format for Vancouver, changes on which we'd very much like
to hear your feedback.
The problems we are trying to solve are the following:
-
On 01/09/2015 09:50 AM, Thierry Carrez wrote:
What do you think ? Could that work ? If not, do you have alternate
suggestions ?
This seems incorporate more of what people have found incredibly useful
(work sessions) and organizes things in a way to accommodate the
anticipated growth in projects
Let's ask the operators opinions too on openstack-operators mailing list. There
was some duplication during the summit between the tracks but there is also a
significant operator need outside the pure code area which comes along with the
big tent tagging for projects. We need to make sure that
Inline
~sean
On Jan 9, 2015, at 9:30 AM, Thierry Carrez thie...@openstack.org wrote:
sean roberts wrote:
I like it. Thank you for coming up with improvements to the
summit planning. One caveat on the definition of project for summit
space. Which projects get considered for space is always
(X-posted to -operators.)
Any thoughts on how the ops track spaces would be requested, since there
is not a real ‘operators project’, PTL, etc.?
I assume this would come from the operators group as a whole, so probably
something we should put on the agenda at the ops meet up in March. (I’ve
sean roberts wrote:
I like it. Thank you for coming up with improvements to the
summit planning. One caveat on the definition of project for summit
space. Which projects get considered for space is always difficult. Who
is going to fill the rooms they request or are they going to have them
Huge +1 from me. Thank you, Thierry.
-jay
On 01/09/2015 09:50 AM, Thierry Carrez wrote:
Hi everyone,
The OpenStack Foundation staff is considering a number of changes to the
Design Summit format for Vancouver, changes on which we'd very much like
to hear your feedback.
The problems we are
12 matches
Mail list logo
