On 05/28/2015 05:11 AM, Gal Sagie wrote: > Hi Kevin, > > The main idea that i tried to express, is we need a course of action after > the discussions, i understand that we want to discuss high level points > but we still need to decide on a follow up plan, because otherwise this is > all wasted. > > What i was suggesting is that we apply action items in the session and the > moderator of the talk or someone else > try and make sure its being followed.
I have found great success any time I have taken any action in compiling a list of agreed upon items and following up on them. I don't have much networking experience but all the folks I have worked with in Neutron have been happy when I have taken on this task myself. Also it tends to produce results in that the task gets attention and moves forward or if stalled and important enough, moves up and gets more attention. I think anyone who decided to do this work would get support. Thanks, Anita. > > the mailing list suggestion was just that we get some of the points at > least sorted or at least get preliminary feedback > which we can use to focus the agenda more so the meetings themselves will > be more focused > > Gal. > > On Thu, May 28, 2015 at 11:50 AM, Kevin Benton <blak...@gmail.com> wrote: > >> Thanks for the feedback. What to discuss at the summit has always been an >> issue. >> >> The only issue I see with your proposal is that you assume we can agree on >> high-level things on the mailing list. One of the reasons to discuss >> high-level things at the summit is that its a great place to get operators, >> developers, product managers, etc all in the same room to discuss issues. >> If try do decide everything on openstack-dev, we end up operating somewhat >> in a vacuum. >> >> From another angle, what's the point in meeting up at the summit if the >> only point is to look for volunteers to take action items? That could be >> done completely via the mailing list as well. >> >> The summit is our only opportunity for high-bandwidth interaction with >> users and contributors from other projects as well. We need to make sure we >> take advantage of that. >> >> On Thu, May 28, 2015 at 1:12 AM, Gal Sagie <gal.sa...@gmail.com> wrote: >> >>> Hello All, >>> >>> I wanted to very briefly share my thoughts and a suggestion regarding the >>> Neutron design summits (maybe only for the next one, but still..) >>> >>> I would first like to say that i was amazed by the number of people that >>> attended the summit, it was really great to see it and it was very nice >>> meeting most of you and linking the person with the IRC nick. >>> >>> Anyone that knows me, or talked with me in the past knows that i wanted >>> to get involved with Open Source for quite some time and i really feel >>> fortunate to be able to contribute and join OpenStack, and hope to continue >>> with this efforts going forward. >>> >>> I have to share that i was expecting the design summits to be completely >>> different then what went on, and although some issues were interesting i >>> feel they were not use full to go forward but rather were just a stage for >>> people to express opinions/ideas without a distinct decision. >>> >>> Since i am new and never been in one of these i don’t want to judge or >>> declare if that’s good or bad :), i do think that its hard to actually >>> achieve something with so many people but i also understand and appreciate >>> the great interest of so many people with Neutron. >>> >>> A small suggestion i think might improve is if the session moderator will >>> write (or any other volunteer) a follow up email with Action Items that >>> needs to be addressed and people actually taking and volunteering to take >>> some of those action items. >>> This can and should be live in the meeting where anyone requesting or >>> making a suggestion would take it on him/her self to push it forward and >>> report status. >>> (I think every point in the agenda must be converted into an action item) >>> >>> We can also do this before the actual summit on the agenda points and >>> hopefully gets a discussion going before the actual session. >>> >>> I also think we should try to re-write the agenda points into a more >>> lower level points before the summit rather then try to tackle the high >>> level stuff (for example trying to discuss the pro's and con's in the >>> mailing lists/IRC before the summit and have a more concrete discussion in >>> the session it self) >>> >>> >>> I do hope that’s the right place to express this, and again that’s only >>> my impression, i could be completely wrong here as i don’t consider my self >>> experienced enough with the Open Source way of doing things. >>> Would love to help in the future with some of the points i raised here. >>> >>> Thanks >>> Gal. >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> >> -- >> Kevin Benton >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
