I don't think this would be the place for long technical discussions.
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.
But yeah, this is a first for everyone so we'll have to make adjustments!
Nicolas
On 8/2/19 1:56 AM, Joel Nothman wrote:
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?
Should the objective of the meeting be firstly to prioritise or assign
work, and secondarily to discuss issues?
To avoid open-ended discussion, we could put topics in an order with
time limits.
Or we can just see how it goes.
I think we also need to make it clear that non-core contributors are
welcome to these meetings too!
_______________________________________________
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn
