Dear core-devs, First let me wish a Happy New Year to you all!
There will be two scikit-learn sprints in January to start this 2020 in a busy way: one in Berlin [1] (Jan 25) and one in Paris [2] (Jan 28-31). I feel like we could benefit of some coordination in selecting the issues for those two events. Reshama Shaikh and I, we are already in touch. I've opened two projects [3][4] to follow-up the issue selection for the sprints. I will check for previous "Sprint" labels in the skl issues and maybe ask for clarification on some of them... please, be patient. The goal is to prepare the two sprints in order to make the review process as efficient as possible: we don't want to waste the reviewer time and we hope to make the PR experience a learning opportunity on both sides. In particular, I would like to ask a favour to all of you: I don't know if this is even always possible, but, IMO, it would be really useful to have a list of two/three reviewers available to check on a specific issue. I am, personally, a bit uncomfortable in pinging core-devs randomly, under the impression of crying wolf lacking for attention... If people in charge are defined in advance this could, I think, smooth the review process. What do you think? Please, let us know if you have any suggestion or recommendation to improve the Sprint organization. Thanks for listening, Best, Chiara [1] https://github.com/WiMLDS/berlin-2020-scikit-sprint [2] https://github.com/scikit-learn/scikit-learn/wiki/Paris-scikit-learn-Sprint-of-the-Decade [3] https://github.com/WiMLDS/berlin-2020-scikit-sprint/projects/1 [4] https://github.com/scikit-learn-fondation/ParisSprintJanuary2020/projects/1
_______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
