Re: [openstack-dev] [Ironic] Changing our weekly meeting format

2014-11-18 Thread Lucas Alvares Gomes
On Mon, Nov 17, 2014 at 8:58 PM, Devananda van der Veen
devananda@gmail.com wrote:
 Lucas, Thanks for bringing this up (both in Paris and here). I'm strongly in
 favor of these changes as well. We discussed this during the meeting today
 [1], to which I offer the following summary:

 - move the status reporting to the etherpad [2]
 -- take one (1) minute at the start of the meeting for folks to look at the
 'pad and raise any concerns. discuss concerns but cap at ten (10) minutes

We might not want to cap at fixed time like 10 minutes, if there's
something to discuss we can go ahead and discuss it. I like the way
you put on the wiki: Review subteam status reports (capped at one
minute, unless concerns are raised)

 -- at the end of the meeting, an email will be sent out containing the
 status report from the 'pad, plus discussion notes (if needed)
 - meeting agenda to be frozen two (2) days before the meeting. This also
 gives time for others to review/research the topic ahead of time. Anyone who
 has something on the planned agenda should prepare some notes to introduce
 the topic (or type fast enough that we don't notice that you didn't prepare)
 so we aren't all waiting on IRC.

 I'll update the meeting wiki accordingly.

Ta much for that, looks great!

Lucas


 -Deva

 [1]
 http://eavesdrop.openstack.org/meetings/ironic/2014/ironic.2014-11-17-19.00.log.html
 [2] https://etherpad.openstack.org/IronicWhiteBoard


 On Thu Nov 13 2014 at 8:58:18 AM Chris K nobody...@gmail.com wrote:

 +1
 I think the best use of our time is to discuss new features and functions
 that may have a api or functional impact for ironic or projects that depend
 on ironic.

 Chris Krelle

 On Thu, Nov 13, 2014 at 8:22 AM, Ghe Rivero g...@debian.org wrote:

 I agree that a lot of time is missed with the announcement and status
 reports, but mostly because irc is a slow bandwidth communication channel
 (like waiting several minutes for a 3 lines announcement to be written)

 I propose that any announcement and project status must be written in
 advanced to an etherpad, and during the irc meeting just have a slot for
 people to discuss anything that need further explanation, only mentioning
 the topic but not  the content.

 Ghe Rivero

 On Nov 13, 2014 5:08 PM, Peeyush Gupta gpeey...@linux.vnet.ibm.com
 wrote:

 +1

 I agree with Lucas. Sounds like a good idea. I guess if we could spare
 more time for discussing new features and requirements rather than
 asking for status, that would be helpful for everyone.

 On 11/13/2014 05:45 PM, Lucas Alvares Gomes wrote:
  This was discussed in the Contributor Meetup on Friday at the Summit
  but I think it's important to share on the mail list too so we can get
  more opnions/suggestions/comments about it.
 
  In the Ironic weekly meeting we dedicate a good time of the meeting to
  do some announcements, reporting bug status, CI status, oslo status,
  specific drivers status, etc... It's all good information, but I
  believe that the mail list would be a better place to report it and
  then we can free some time from our meeting to actually discuss
  things.
 
  Are you guys in favor of it?
 
  If so I'd like to propose a new format based on the discussions we had
  in Paris. For the people doing the status report on the meeting, they
  would start adding the status to an etherpad and then we would have a
  responsible person to get this information and send it to the mail
  list once a week.
 
  For the meeting itself we have a wiki page with an agenda[1] which
  everyone can edit to put the topic they want to discuss in the meeting
  there, I think that's fine and works. The only change about it would
  be that we may want freeze the agenda 2 days before the meeting so
  people can take a look at the topics that will be discussed and
  prepare for it; With that we can move forward quicker with the
  discussions because people will be familiar with the topics already.
 
  Let me know what you guys think.
 
  [1] https://wiki.openstack.org/wiki/Meetings/Ironic
 
  Lucas
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 

 --
 Peeyush Gupta
 gpeey...@linux.vnet.ibm.com



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 

Re: [openstack-dev] [Ironic] Changing our weekly meeting format

2014-11-17 Thread Devananda van der Veen
Lucas, Thanks for bringing this up (both in Paris and here). I'm strongly
in favor of these changes as well. We discussed this during the meeting
today [1], to which I offer the following summary:

- move the status reporting to the etherpad [2]
-- take one (1) minute at the start of the meeting for folks to look at the
'pad and raise any concerns. discuss concerns but cap at ten (10) minutes
-- at the end of the meeting, an email will be sent out containing the
status report from the 'pad, plus discussion notes (if needed)
- meeting agenda to be frozen two (2) days before the meeting. This also
gives time for others to review/research the topic ahead of time. Anyone
who has something on the planned agenda should prepare some notes to
introduce the topic (or type fast enough that we don't notice that you
didn't prepare) so we aren't all waiting on IRC.

I'll update the meeting wiki accordingly.

-Deva

[1]
http://eavesdrop.openstack.org/meetings/ironic/2014/ironic.2014-11-17-19.00.log.html
[2] https://etherpad.openstack.org/IronicWhiteBoard


On Thu Nov 13 2014 at 8:58:18 AM Chris K nobody...@gmail.com wrote:

 +1
 I think the best use of our time is to discuss new features and functions
 that may have a api or functional impact for ironic or projects that depend
 on ironic.

 Chris Krelle

 On Thu, Nov 13, 2014 at 8:22 AM, Ghe Rivero g...@debian.org wrote:

 I agree that a lot of time is missed with the announcement and status
 reports, but mostly because irc is a slow bandwidth communication channel
 (like waiting several minutes for a 3 lines announcement to be written)

 I propose that any announcement and project status must be written in
 advanced to an etherpad, and during the irc meeting just have a slot for
 people to discuss anything that need further explanation, only mentioning
 the topic but not  the content.

 Ghe Rivero
 On Nov 13, 2014 5:08 PM, Peeyush Gupta gpeey...@linux.vnet.ibm.com
 wrote:

 +1

 I agree with Lucas. Sounds like a good idea. I guess if we could spare
 more time for discussing new features and requirements rather than
 asking for status, that would be helpful for everyone.

 On 11/13/2014 05:45 PM, Lucas Alvares Gomes wrote:
  This was discussed in the Contributor Meetup on Friday at the Summit
  but I think it's important to share on the mail list too so we can get
  more opnions/suggestions/comments about it.
 
  In the Ironic weekly meeting we dedicate a good time of the meeting to
  do some announcements, reporting bug status, CI status, oslo status,
  specific drivers status, etc... It's all good information, but I
  believe that the mail list would be a better place to report it and
  then we can free some time from our meeting to actually discuss
  things.
 
  Are you guys in favor of it?
 
  If so I'd like to propose a new format based on the discussions we had
  in Paris. For the people doing the status report on the meeting, they
  would start adding the status to an etherpad and then we would have a
  responsible person to get this information and send it to the mail
  list once a week.
 
  For the meeting itself we have a wiki page with an agenda[1] which
  everyone can edit to put the topic they want to discuss in the meeting
  there, I think that's fine and works. The only change about it would
  be that we may want freeze the agenda 2 days before the meeting so
  people can take a look at the topics that will be discussed and
  prepare for it; With that we can move forward quicker with the
  discussions because people will be familiar with the topics already.
 
  Let me know what you guys think.
 
  [1] https://wiki.openstack.org/wiki/Meetings/Ironic
 
  Lucas
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 

 --
 Peeyush Gupta
 gpeey...@linux.vnet.ibm.com



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Ironic] Changing our weekly meeting format

2014-11-13 Thread Dmitry Tantsur

On 11/13/2014 01:15 PM, Lucas Alvares Gomes wrote:

This was discussed in the Contributor Meetup on Friday at the Summit
but I think it's important to share on the mail list too so we can get
more opnions/suggestions/comments about it.

In the Ironic weekly meeting we dedicate a good time of the meeting to
do some announcements, reporting bug status, CI status, oslo status,
specific drivers status, etc... It's all good information, but I
believe that the mail list would be a better place to report it and
then we can free some time from our meeting to actually discuss
things.

Are you guys in favor of it?

If so I'd like to propose a new format based on the discussions we had
in Paris. For the people doing the status report on the meeting, they
would start adding the status to an etherpad and then we would have a
responsible person to get this information and send it to the mail
list once a week.

For the meeting itself we have a wiki page with an agenda[1] which
everyone can edit to put the topic they want to discuss in the meeting
there, I think that's fine and works. The only change about it would
be that we may want freeze the agenda 2 days before the meeting so
people can take a look at the topics that will be discussed and
prepare for it; With that we can move forward quicker with the
discussions because people will be familiar with the topics already.

Let me know what you guys think.
I'm not really fond of it (like every process complication) but it looks 
inevitable, so +1.




[1] https://wiki.openstack.org/wiki/Meetings/Ironic

Lucas

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Ironic] Changing our weekly meeting format

2014-11-13 Thread Peeyush Gupta
+1

I agree with Lucas. Sounds like a good idea. I guess if we could spare
more time for discussing new features and requirements rather than
asking for status, that would be helpful for everyone.

On 11/13/2014 05:45 PM, Lucas Alvares Gomes wrote:
 This was discussed in the Contributor Meetup on Friday at the Summit
 but I think it's important to share on the mail list too so we can get
 more opnions/suggestions/comments about it.

 In the Ironic weekly meeting we dedicate a good time of the meeting to
 do some announcements, reporting bug status, CI status, oslo status,
 specific drivers status, etc... It's all good information, but I
 believe that the mail list would be a better place to report it and
 then we can free some time from our meeting to actually discuss
 things.

 Are you guys in favor of it?

 If so I'd like to propose a new format based on the discussions we had
 in Paris. For the people doing the status report on the meeting, they
 would start adding the status to an etherpad and then we would have a
 responsible person to get this information and send it to the mail
 list once a week.

 For the meeting itself we have a wiki page with an agenda[1] which
 everyone can edit to put the topic they want to discuss in the meeting
 there, I think that's fine and works. The only change about it would
 be that we may want freeze the agenda 2 days before the meeting so
 people can take a look at the topics that will be discussed and
 prepare for it; With that we can move forward quicker with the
 discussions because people will be familiar with the topics already.

 Let me know what you guys think.

 [1] https://wiki.openstack.org/wiki/Meetings/Ironic

 Lucas

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-- 
Peeyush Gupta
gpeey...@linux.vnet.ibm.com



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Ironic] Changing our weekly meeting format

2014-11-13 Thread Ghe Rivero
I agree that a lot of time is missed with the announcement and status
reports, but mostly because irc is a slow bandwidth communication channel
(like waiting several minutes for a 3 lines announcement to be written)

I propose that any announcement and project status must be written in
advanced to an etherpad, and during the irc meeting just have a slot for
people to discuss anything that need further explanation, only mentioning
the topic but not  the content.

Ghe Rivero
On Nov 13, 2014 5:08 PM, Peeyush Gupta gpeey...@linux.vnet.ibm.com
wrote:

 +1

 I agree with Lucas. Sounds like a good idea. I guess if we could spare
 more time for discussing new features and requirements rather than
 asking for status, that would be helpful for everyone.

 On 11/13/2014 05:45 PM, Lucas Alvares Gomes wrote:
  This was discussed in the Contributor Meetup on Friday at the Summit
  but I think it's important to share on the mail list too so we can get
  more opnions/suggestions/comments about it.
 
  In the Ironic weekly meeting we dedicate a good time of the meeting to
  do some announcements, reporting bug status, CI status, oslo status,
  specific drivers status, etc... It's all good information, but I
  believe that the mail list would be a better place to report it and
  then we can free some time from our meeting to actually discuss
  things.
 
  Are you guys in favor of it?
 
  If so I'd like to propose a new format based on the discussions we had
  in Paris. For the people doing the status report on the meeting, they
  would start adding the status to an etherpad and then we would have a
  responsible person to get this information and send it to the mail
  list once a week.
 
  For the meeting itself we have a wiki page with an agenda[1] which
  everyone can edit to put the topic they want to discuss in the meeting
  there, I think that's fine and works. The only change about it would
  be that we may want freeze the agenda 2 days before the meeting so
  people can take a look at the topics that will be discussed and
  prepare for it; With that we can move forward quicker with the
  discussions because people will be familiar with the topics already.
 
  Let me know what you guys think.
 
  [1] https://wiki.openstack.org/wiki/Meetings/Ironic
 
  Lucas
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 

 --
 Peeyush Gupta
 gpeey...@linux.vnet.ibm.com



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Ironic] Changing our weekly meeting format

2014-11-13 Thread Chris K
+1
I think the best use of our time is to discuss new features and functions
that may have a api or functional impact for ironic or projects that depend
on ironic.

Chris Krelle

On Thu, Nov 13, 2014 at 8:22 AM, Ghe Rivero g...@debian.org wrote:

 I agree that a lot of time is missed with the announcement and status
 reports, but mostly because irc is a slow bandwidth communication channel
 (like waiting several minutes for a 3 lines announcement to be written)

 I propose that any announcement and project status must be written in
 advanced to an etherpad, and during the irc meeting just have a slot for
 people to discuss anything that need further explanation, only mentioning
 the topic but not  the content.

 Ghe Rivero
 On Nov 13, 2014 5:08 PM, Peeyush Gupta gpeey...@linux.vnet.ibm.com
 wrote:

 +1

 I agree with Lucas. Sounds like a good idea. I guess if we could spare
 more time for discussing new features and requirements rather than
 asking for status, that would be helpful for everyone.

 On 11/13/2014 05:45 PM, Lucas Alvares Gomes wrote:
  This was discussed in the Contributor Meetup on Friday at the Summit
  but I think it's important to share on the mail list too so we can get
  more opnions/suggestions/comments about it.
 
  In the Ironic weekly meeting we dedicate a good time of the meeting to
  do some announcements, reporting bug status, CI status, oslo status,
  specific drivers status, etc... It's all good information, but I
  believe that the mail list would be a better place to report it and
  then we can free some time from our meeting to actually discuss
  things.
 
  Are you guys in favor of it?
 
  If so I'd like to propose a new format based on the discussions we had
  in Paris. For the people doing the status report on the meeting, they
  would start adding the status to an etherpad and then we would have a
  responsible person to get this information and send it to the mail
  list once a week.
 
  For the meeting itself we have a wiki page with an agenda[1] which
  everyone can edit to put the topic they want to discuss in the meeting
  there, I think that's fine and works. The only change about it would
  be that we may want freeze the agenda 2 days before the meeting so
  people can take a look at the topics that will be discussed and
  prepare for it; With that we can move forward quicker with the
  discussions because people will be familiar with the topics already.
 
  Let me know what you guys think.
 
  [1] https://wiki.openstack.org/wiki/Meetings/Ironic
 
  Lucas
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 

 --
 Peeyush Gupta
 gpeey...@linux.vnet.ibm.com



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev