On Thu, May 4, 2017 at 3:49 AM, Thierry Carrez <thie...@openstack.org> wrote: > Jeremy Stanley wrote: >> On 2017-05-03 14:04:40 -0400 (-0400), Doug Hellmann wrote: >>> Excerpts from Sean Dague's message of 2017-05-03 13:23:11 -0400: >>>> On 05/03/2017 01:02 PM, Doug Hellmann wrote: >>>>> Excerpts from Thierry Carrez's message of 2017-05-03 18:16:29 +0200: >> [...] >>>>> Knowing what will be discussed in advanced also helps everyone >>>>> collect their thoughts and be ready to contribute. >>>> >>>> What about ensuring that every agenda topic is more than a line, >>>> but includes a full paragraph about what the agenda topic >>>> proposer expects it will cover. A lot of times the agenda items >>>> are cryptic enough unless you are knee deep in things. >>>> >>>> That would help people collect their thoughts even more and >>>> break away from the few minutes of delay in introducing the >>>> subject (the introduction of the subject would be in the >>>> agenda). >>> >>> If the goal is to move most of the discussion onto the mailing >>> list, we could link to the thread(s) there, too. >> >> This seems like a great idea to me. Granted in many cases we already >> have a change proposed in Gerrit containing a (potentially) lengthy >> explanation, but duplicating some of that on the agenda can't hurt. > > I like the idea. One issue is the timing. > > I prepare and post the meeting agenda on the Monday (in time for > everyone to read it and decide if they want to attend). However I > prepare the "introduction of the subject" shortly before the meeting on > Tuesday, so that it takes into account the recent changes and is up to > date with the status of the review. Some people post reviews/comments 10 > minutes before meeting, so it will be very hard to account for those > comments or objections in the "introduction" posted the day before...
Right Thierry, we all have to adjust the way we work somewhat. > -- > Thierry Carrez (ttx) > > > __________________________________________________________________________ > 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 > -- Davanum Srinivas :: https://twitter.com/dims __________________________________________________________________________ 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
