<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I don't think this would be the place for long technical
discussions.</p>
<p>I was picturing something like "IHere's what I'm working on,
here's the current status, and here's what needs to be decided".
Then depending on the complexity, things can be briefly discussed,
or we can just prioritize and assign work. In any case the
moderator is in charge of keeping the meeting < 1h.<br>
</p>
<p>But yeah, this is a first for everyone so we'll have to make
adjustments!</p>
<p>Nicolas<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 8/2/19 1:56 AM, Joel Nothman wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAkaFLU3GUhRyBAc2r=UBAUM0atft2zBE1bJNSw9ybn9Cb+udA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr"><br>
Such meetings could go quite long. (Think those sprint meetings
in Paris...) How do we time box discussions, or ensure that the
most important/urgent/low-hanging things are covered?
<div><br>
</div>
<div>Should the objective of the meeting be firstly to
prioritise or assign work, and secondarily to discuss issues?</div>
<div><br>
</div>
<div>To avoid open-ended discussion, we could put topics in an
order with time limits.</div>
<div><br>
</div>
<div>Or we can just see how it goes.</div>
<div><br>
</div>
<div>I think we also need to make it clear that non-core
contributors are welcome to these meetings too!</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
scikit-learn mailing list
<a class="moz-txt-link-abbreviated" href="mailto:scikit-learn@python.org">scikit-learn@python.org</a>
<a class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/scikit-learn">https://mail.python.org/mailman/listinfo/scikit-learn</a>
</pre>
</blockquote>
</body>
</html>