<div dir="ltr">+1 <div>I think the best use of our time is to discuss <span style="font-family:arial,sans-serif;font-size:13px">new features and functions that may have a api or functional impact for ironic or projects that depend on ironic.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Chris Krelle</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 13, 2014 at 8:22 AM, Ghe Rivero <span dir="ltr"><<a href="mailto:ghe@debian.org" target="_blank">ghe@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">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)</p>
<p dir="ltr"> 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.</p><span class="HOEnZb"><font color="#888888">
<p dir="ltr">Ghe Rivero</p></font></span><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Nov 13, 2014 5:08 PM, "Peeyush Gupta" <<a href="mailto:gpeeyush@linux.vnet.ibm.com" target="_blank">gpeeyush@linux.vnet.ibm.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1<br>
<br>
I agree with Lucas. Sounds like a good idea. I guess if we could spare<br>
more time for discussing new features and requirements rather than<br>
asking for status, that would be helpful for everyone.<br>
<br>
On 11/13/2014 05:45 PM, Lucas Alvares Gomes wrote:<br>
> This was discussed in the Contributor Meetup on Friday at the Summit<br>
> but I think it's important to share on the mail list too so we can get<br>
> more opnions/suggestions/comments about it.<br>
><br>
> In the Ironic weekly meeting we dedicate a good time of the meeting to<br>
> do some announcements, reporting bug status, CI status, oslo status,<br>
> specific drivers status, etc... It's all good information, but I<br>
> believe that the mail list would be a better place to report it and<br>
> then we can free some time from our meeting to actually discuss<br>
> things.<br>
><br>
> Are you guys in favor of it?<br>
><br>
> If so I'd like to propose a new format based on the discussions we had<br>
> in Paris. For the people doing the status report on the meeting, they<br>
> would start adding the status to an etherpad and then we would have a<br>
> responsible person to get this information and send it to the mail<br>
> list once a week.<br>
><br>
> For the meeting itself we have a wiki page with an agenda[1] which<br>
> everyone can edit to put the topic they want to discuss in the meeting<br>
> there, I think that's fine and works. The only change about it would<br>
> be that we may want freeze the agenda 2 days before the meeting so<br>
> people can take a look at the topics that will be discussed and<br>
> prepare for it; With that we can move forward quicker with the<br>
> discussions because people will be familiar with the topics already.<br>
><br>
> Let me know what you guys think.<br>
><br>
> [1] <a href="https://wiki.openstack.org/wiki/Meetings/Ironic" target="_blank">https://wiki.openstack.org/wiki/Meetings/Ironic</a><br>
><br>
> Lucas<br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
--<br>
Peeyush Gupta<br>
<a href="mailto:gpeeyush@linux.vnet.ibm.com" target="_blank">gpeeyush@linux.vnet.ibm.com</a><br>
<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>