Re: [scikit-learn] Monthly meetings between core developers
I don't think it's worthwhile to worry too much about Beijing time if I'm the only person in Beijing. I'm happy to get up early once a month to learn from the great team! Hanmin Qin ----- Original Message ----- From: Alexandre Gramfort <alexandre.gramfort@inria.fr> To: Scikit-learn mailing list <scikit-learn@python.org> Subject: Re: [scikit-learn] Monthly meetings between core developers Date: 2019-07-18 17:16 hi, I kind of like the project boards we used for sprints: https://github.com/scikit-learn/scikit-learn/projects/11 the outcome of the core devs meeting could be to agree what should be listed on such a priority board. my 2c Alex On Thu, Jul 18, 2019 at 10:59 AM Olivier Grisel <olivier.grisel@ensta.org> wrote:
I just found this planner to give it a try:
(Berlin and Paris are on the same timezone so I did not put only Berlin).
It's going to be challenging to find a timeslot for every body. The least extreme timeslot for everybody to attend at the same time would be:
We could also arrange for a second timeslot later (that would be Tuesday morning in Australia and China):
I wouldn't mind doing a meeting around 11pm on Monday evening from time to time but it would still be very early for Beijing.
Just to let you know, I will be off from next Saturday till Monday August 19 (big summer break :) so don't count on my for the first meeting if you start the meetings in the mean time.
Le jeu. 18 juil. 2019 à 00:15, Andreas Mueller <t3kcit@gmail.com> a écrit :
On 7/17/19 2:17 PM, Guillaume Lemaître wrote:
I am +1. This is a great initiative.
IMO, we could make it really regular (i.e., a specific week-day of a specific week in a month), with a rolling time (for the time-zone issue). In this matter, we could maybe clear more in advance our agenda instead of trying to find a date which accommodates everyone.
I agree, we could do something like the last Monday every month and alternate between two (or three) different time zones. We have CET (UTC+1), EST (UTC-5), CT (UTC+08), AEDT (USC+11) so that seems super easy, right? (TIL CST can stand for "Central"/US, China, and Cuba! not confusing at all)
I agree that we should be as inclusive as possible, but I also don't want to create the expectation that some people (not thinking of any Australian in particular) who already sacrifice a lot of their free time have to invest even more time to keep up with the rest.
I think the idea of posting write-ups will help being more inclusive in that regard. _______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
-- Olivier http://twitter.com/ogrisel - http://github.com/ogrisel _______________________________________________ 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
I'm away on a holiday at the moment (in case you hadn't identified my silence). I'd be keen to join in but might not be able to move schedules around it. I like the idea of prioritising together, though I'm not sure how to keep the meetings clipped. I'm also going to be quite lost on the issue tracker when I return to civilisation next week... (Are we still on for two patch releases?) J
Dear list, I'm Chiara, in September I will start to work full time for the Scikit-Learn Consortium at INRIA (France). My background is in Astronomy and Planetary Science: I've worked there as a Research Engineer for around 15 years, writing code, mining data and managing some project. One of my task at the Consortium will be to take care of our connection with the developer community, so let me know if I can help in managing those monthly meetings in some way. In the meanwhile, may I suggest to create a github team for core developers in the scikit-learn organization? As Alexandre said, team specific projects and discussions on github could be a way to efficiently prepare meetings and prioritize issues. Thanks for listening, have a nice day. Chiara
Awesome, excited to have your help around :) We already have the @core-devs team on github, we can use it more often/more organized. On Fri, Jul 19, 2019 at 2:48 PM Chiara Marmo <marmochiaskl@gmail.com> wrote:
Dear list,
I'm Chiara, in September I will start to work full time for the Scikit-Learn Consortium at INRIA (France). My background is in Astronomy and Planetary Science: I've worked there as a Research Engineer for around 15 years, writing code, mining data and managing some project.
One of my task at the Consortium will be to take care of our connection with the developer community, so let me know if I can help in managing those monthly meetings in some way. In the meanwhile, may I suggest to create a github team for core developers in the scikit-learn organization? As Alexandre said, team specific projects and discussions on github could be a way to efficiently prepare meetings and prioritize issues.
Thanks for listening, have a nice day. Chiara _______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
On 7/22/19 9:22 AM, Adrin wrote:
Awesome, excited to have your help around :)
We already have the @core-devs team on github, we can use it more often/more organized.hi
Why wouldn't we just use the scikit-learn repo projects?
On Fri, Jul 19, 2019 at 2:48 PM Chiara Marmo <marmochiaskl@gmail.com <mailto:marmochiaskl@gmail.com>> wrote:
Dear list,
I'm Chiara, in September I will start to work full time for the Scikit-Learn Consortium at INRIA (France). My background is in Astronomy and Planetary Science: I've worked there as a Research Engineer for around 15 years, writing code, mining data and managing some project.
One of my task at the Consortium will be to take care of our connection with the developer community, so let me know if I can help in managing those monthly meetings in some way. In the meanwhile, may I suggest to create a github team for core developers in the scikit-learn organization? As Alexandre said, team specific projects and discussions on github could be a way to efficiently prepare meetings and prioritize issues.
Thanks for listening, have a nice day. Chiara _______________________________________________ scikit-learn mailing list scikit-learn@python.org <mailto: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
That's kinda what I meant. I didn't mean to limit the access to the project to @core-devs, I meant they can be pinged. On Mon, Jul 22, 2019 at 3:56 PM Andreas Mueller <t3kcit@gmail.com> wrote:
On 7/22/19 9:22 AM, Adrin wrote:
Awesome, excited to have your help around :)
We already have the @core-devs team on github, we can use it more often/more organized.hi
Why wouldn't we just use the scikit-learn repo projects?
On Fri, Jul 19, 2019 at 2:48 PM Chiara Marmo <marmochiaskl@gmail.com> wrote:
Dear list,
I'm Chiara, in September I will start to work full time for the Scikit-Learn Consortium at INRIA (France). My background is in Astronomy and Planetary Science: I've worked there as a Research Engineer for around 15 years, writing code, mining data and managing some project.
One of my task at the Consortium will be to take care of our connection with the developer community, so let me know if I can help in managing those monthly meetings in some way. In the meanwhile, may I suggest to create a github team for core developers in the scikit-learn organization? As Alexandre said, team specific projects and discussions on github could be a way to efficiently prepare meetings and prioritize issues.
Thanks for listening, have a nice day. Chiara _______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________ scikit-learn mailing listscikit-learn@python.orghttps://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
Thanks everyone for your feedback! Let's try to have a meeting on Monday 5th August, and then have meetings on the last Monday of the month? Next meeting would be on August 26th. For the time: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=8&day=5&hour=13&min=0&sec=0&p1=240&p2=33&p3=37&p4=179. This one is convenient for NY and Europe, less so for Sydney / Beijing . We can have the next meeting accommodate for Joel / Hanmin. We can use Andy's appear.in : https://appear.in/amueller. I'm happy to (try to) "lead" the discussion this first time? For logistics: I created a new project board https://github.com/scikit-learn/scikit-learn/projects/15 I was thinking of having one column per meeting. A few days before the meeting, people can write down what they plan to discuss (one note per core-dev), so others can prepare. In particular, people that are not able to attend can leave details here (let us know in the notes!). One advantage of these boards is that they're searchable, we have a clear history of meetings, and it's easy to reference PRs/issues. This is of course only a proposal, we can try it and see whether it works out ;) @Chiara Welcome!! Thanks for offering to help! It didn't take long so I took care of creating the board (also I would have felt bad for making you work while you only start in Sep). Thanks, Nicolas On 7/22/19 9:57 AM, Adrin wrote:
That's kinda what I meant. I didn't mean to limit the access to the project to @core-devs, I meant they can be pinged.
On Mon, Jul 22, 2019 at 3:56 PM Andreas Mueller <t3kcit@gmail.com <mailto:t3kcit@gmail.com>> wrote:
On 7/22/19 9:22 AM, Adrin wrote:
Awesome, excited to have your help around :)
We already have the @core-devs team on github, we can use it more often/more organized.hi
Why wouldn't we just use the scikit-learn repo projects?
On Fri, Jul 19, 2019 at 2:48 PM Chiara Marmo <marmochiaskl@gmail.com <mailto:marmochiaskl@gmail.com>> wrote:
Dear list,
I'm Chiara, in September I will start to work full time for the Scikit-Learn Consortium at INRIA (France). My background is in Astronomy and Planetary Science: I've worked there as a Research Engineer for around 15 years, writing code, mining data and managing some project.
One of my task at the Consortium will be to take care of our connection with the developer community, so let me know if I can help in managing those monthly meetings in some way. In the meanwhile, may I suggest to create a github team for core developers in the scikit-learn organization? As Alexandre said, team specific projects and discussions on github could be a way to efficiently prepare meetings and prioritize issues.
Thanks for listening, have a nice day. Chiara _______________________________________________ scikit-learn mailing list scikit-learn@python.org <mailto:scikit-learn@python.org> https://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________ scikit-learn mailing list scikit-learn@python.org <mailto:scikit-learn@python.org> https://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________ scikit-learn mailing list scikit-learn@python.org <mailto: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
Hi everyone, Since the meeting is at 9am Monday for NYC, it'd be nice to have all cards up to date by tomorrow, so we can do our homework on Friday (and not on the week end ;) ) Please don't forget to add links to specific PR/issues so others can take a look prior to the meeting. Thanks! Nicolas project board: https://github.com/scikit-learn/scikit-learn/projects/15 Meeting link: https://appear.in/amueller. On 7/26/19 2:08 PM, Nicolas Hug wrote:
Thanks everyone for your feedback!
Let's try to have a meeting on Monday 5th August, and then have meetings on the last Monday of the month? Next meeting would be on August 26th.
For the time: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=8&day=5&hour=13&min=0&sec=0&p1=240&p2=33&p3=37&p4=179. This one is convenient for NY and Europe, less so for Sydney / Beijing . We can have the next meeting accommodate for Joel / Hanmin.
We can use Andy's appear.in : https://appear.in/amueller. I'm happy to (try to) "lead" the discussion this first time?
For logistics: I created a new project board https://github.com/scikit-learn/scikit-learn/projects/15
I was thinking of having one column per meeting. A few days before the meeting, people can write down what they plan to discuss (one note per core-dev), so others can prepare. In particular, people that are not able to attend can leave details here (let us know in the notes!).
One advantage of these boards is that they're searchable, we have a clear history of meetings, and it's easy to reference PRs/issues. This is of course only a proposal, we can try it and see whether it works out ;)
@Chiara Welcome!! Thanks for offering to help! It didn't take long so I took care of creating the board (also I would have felt bad for making you work while you only start in Sep).
Thanks,
Nicolas
On 7/22/19 9:57 AM, Adrin wrote:
That's kinda what I meant. I didn't mean to limit the access to the project to @core-devs, I meant they can be pinged.
On Mon, Jul 22, 2019 at 3:56 PM Andreas Mueller <t3kcit@gmail.com <mailto:t3kcit@gmail.com>> wrote:
On 7/22/19 9:22 AM, Adrin wrote:
Awesome, excited to have your help around :)
We already have the @core-devs team on github, we can use it more often/more organized.hi
Why wouldn't we just use the scikit-learn repo projects?
On Fri, Jul 19, 2019 at 2:48 PM Chiara Marmo <marmochiaskl@gmail.com <mailto:marmochiaskl@gmail.com>> wrote:
Dear list,
I'm Chiara, in September I will start to work full time for the Scikit-Learn Consortium at INRIA (France). My background is in Astronomy and Planetary Science: I've worked there as a Research Engineer for around 15 years, writing code, mining data and managing some project.
One of my task at the Consortium will be to take care of our connection with the developer community, so let me know if I can help in managing those monthly meetings in some way. In the meanwhile, may I suggest to create a github team for core developers in the scikit-learn organization? As Alexandre said, team specific projects and discussions on github could be a way to efficiently prepare meetings and prioritize issues.
Thanks for listening, have a nice day. Chiara _______________________________________________ scikit-learn mailing list scikit-learn@python.org <mailto:scikit-learn@python.org> https://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________ scikit-learn mailing list scikit-learn@python.org <mailto:scikit-learn@python.org> https://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________ scikit-learn mailing list scikit-learn@python.org <mailto: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
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!
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
Yay for technology! Awesome to see you all and have some matters clarified. Adrin is right that the issue tracker is increasingly overwhelming (because there are more awesome people hired to work on the project, more frequent sprints, etc). This meeting is a useful summary. The meeting mostly focussed on big features. We should be careful to not leave behind important bugs fixes and work originating outside the core devs. Despite that: Some of Guillaume's activities got cut off. I think it would be great to progress both on stacking and resampling before the next release. I also think these meetings should, as a standing item, note the estimated upcoming release schedule, to help us remain aware of that cadence. Good night! J
As usual, I agree ;) I think it would be good to call out particularly important bugfixes so they get reviews. We might also want to think about how we can organize the issue tracker better. Having more full-time people on the project certainly means more activity but ideally we can use some of that time to make the issue tracker more organized. On 8/5/19 9:21 AM, Joel Nothman wrote:
Yay for technology! Awesome to see you all and have some matters clarified.
Adrin is right that the issue tracker is increasingly overwhelming (because there are more awesome people hired to work on the project, more frequent sprints, etc). This meeting is a useful summary.
The meeting mostly focussed on big features. We should be careful to not leave behind important bugs fixes and work originating outside the core devs.
Despite that: Some of Guillaume's activities got cut off. I think it would be great to progress both on stacking and resampling before the next release.
I also think these meetings should, as a standing item, note the estimated upcoming release schedule, to help us remain aware of that cadence.
Good night!
J
_______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
Hi How to acquire the probability in the cross_validate function? Thanks Rujing -- 发自我的网易邮箱手机智能版 在 2019-08-05 22:31:38，"Andreas Mueller" <t3kcit@gmail.com> 写道： As usual, I agree ;) I think it would be good to call out particularly important bugfixes so they get reviews. We might also want to think about how we can organize the issue tracker better. Having more full-time people on the project certainly means more activity but ideally we can use some of that time to make the issue tracker more organized. On 8/5/19 9:21 AM, Joel Nothman wrote: Yay for technology! Awesome to see you all and have some matters clarified. Adrin is right that the issue tracker is increasingly overwhelming (because there are more awesome people hired to work on the project, more frequent sprints, etc). This meeting is a useful summary. The meeting mostly focussed on big features. We should be careful to not leave behind important bugs fixes and work originating outside the core devs. Despite that: Some of Guillaume's activities got cut off. I think it would be great to progress both on stacking and resampling before the next release. I also think these meetings should, as a standing item, note the estimated upcoming release schedule, to help us remain aware of that cadence. Good night! J _______________________________________________ scikit-learn mailing list scikit-learn@python.orghttps://mail.python.org/mailman/listinfo/scikit-learn
cross_validate should not be used to make predictions but to evaluate the performance, the parameter, etc of models. You probably want to check cross_val_predict to get the prediction. However, be aware of what it involves: https://scikit-learn.org/stable/modules/cross_validation.html#obtaining-pred... On Mon, 5 Aug 2019 at 16:57, Rujing Zha <charujing123@163.com> wrote:
Hi How to acquire the probability in the cross_validate function? Thanks Rujing
-- 发自我的网易邮箱手机智能版
在 2019-08-05 22:31:38，"Andreas Mueller" <t3kcit@gmail.com> 写道：
As usual, I agree ;) I think it would be good to call out particularly important bugfixes so they get reviews. We might also want to think about how we can organize the issue tracker better.
Having more full-time people on the project certainly means more activity but ideally we can use some of that time to make the issue tracker more organized.
On 8/5/19 9:21 AM, Joel Nothman wrote:
Yay for technology! Awesome to see you all and have some matters clarified.
Adrin is right that the issue tracker is increasingly overwhelming (because there are more awesome people hired to work on the project, more frequent sprints, etc). This meeting is a useful summary.
The meeting mostly focussed on big features. We should be careful to not leave behind important bugs fixes and work originating outside the core devs.
Despite that: Some of Guillaume's activities got cut off. I think it would be great to progress both on stacking and resampling before the next release.
I also think these meetings should, as a standing item, note the estimated upcoming release schedule, to help us remain aware of that cadence.
Good night!
J
_______________________________________________ scikit-learn mailing listscikit-learn@python.orghttps://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
-- Guillaume Lemaitre INRIA Saclay - Parietal team Center for Data Science Paris-Saclay https://glemaitre.github.io/
hi this function is exactly what i wanted. However, the description of this function contained this: Passing these predictions into an evaluation metric may not be a valid way to measure generalization performance. Could i use this prediction to calculate the accuracy? I am not sure after seeing this sentence. Thanks. 2019-08-13 charujing123 发件人：Guillaume Lemaître <g.lemaitre58@gmail.com> 发送时间：2019-08-12 23:16 主题：Re: [scikit-learn] Predictive probability from cross_validate 收件人："Scikit-learn mailing list"<scikit-learn@python.org> 抄送： cross_validate should not be used to make predictions but to evaluate the performance, the parameter, etc of models. You probably want to check cross_val_predict to get the prediction. However, be aware of what it involves: https://scikit-learn.org/stable/modules/cross_validation.html#obtaining-pred... On Mon, 5 Aug 2019 at 16:57, Rujing Zha <charujing123@163.com> wrote: Hi How to acquire the probability in the cross_validate function? Thanks Rujing -- 发自我的网易邮箱手机智能版 在 2019-08-05 22:31:38，"Andreas Mueller" <t3kcit@gmail.com> 写道： As usual, I agree ;) I think it would be good to call out particularly important bugfixes so they get reviews. We might also want to think about how we can organize the issue tracker better. Having more full-time people on the project certainly means more activity but ideally we can use some of that time to make the issue tracker more organized. On 8/5/19 9:21 AM, Joel Nothman wrote: Yay for technology! Awesome to see you all and have some matters clarified. Adrin is right that the issue tracker is increasingly overwhelming (because there are more awesome people hired to work on the project, more frequent sprints, etc). This meeting is a useful summary. The meeting mostly focussed on big features. We should be careful to not leave behind important bugs fixes and work originating outside the core devs. Despite that: Some of Guillaume's activities got cut off. I think it would be great to progress both on stacking and resampling before the next release. I also think these meetings should, as a standing item, note the estimated upcoming release schedule, to help us remain aware of that cadence. Good night! J _______________________________________________ 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 -- Guillaume Lemaitre INRIA Saclay - Parietal team Center for Data Science Paris-Saclay https://glemaitre.github.io/
As the note is saying, you should not use this approach to evaluate your model. You should use cross_val_score instead. On Tue, 13 Aug 2019 at 04:30, charujing123 <charujing123@163.com> wrote:
hi this function is exactly what i wanted. However, the description of this function contained this: Passing these predictions into an evaluation metric may not be a valid way to measure generalization performance. Could i use this prediction to calculate the accuracy? I am not sure after seeing this sentence. Thanks.
2019-08-13 ------------------------------ charujing123 ------------------------------
*发件人：*Guillaume Lemaître <g.lemaitre58@gmail.com> *发送时间：*2019-08-12 23:16 *主题：*Re: [scikit-learn] Predictive probability from cross_validate *收件人：*"Scikit-learn mailing list"<scikit-learn@python.org> *抄送：*
cross_validate should not be used to make predictions but to evaluate the performance, the parameter, etc of models. You probably want to check cross_val_predict to get the prediction. However, be aware of what it involves:
https://scikit-learn.org/stable/modules/cross_validation.html#obtaining-pred...
On Mon, 5 Aug 2019 at 16:57, Rujing Zha <charujing123@163.com> wrote:
Hi How to acquire the probability in the cross_validate function? Thanks Rujing
-- 发自我的网易邮箱手机智能版
在 2019-08-05 22:31:38，"Andreas Mueller" <t3kcit@gmail.com> 写道：
As usual, I agree ;) I think it would be good to call out particularly important bugfixes so they get reviews. We might also want to think about how we can organize the issue tracker better.
Having more full-time people on the project certainly means more activity but ideally we can use some of that time to make the issue tracker more organized.
On 8/5/19 9:21 AM, Joel Nothman wrote:
Yay for technology! Awesome to see you all and have some matters clarified.
Adrin is right that the issue tracker is increasingly overwhelming (because there are more awesome people hired to work on the project, more frequent sprints, etc). This meeting is a useful summary.
The meeting mostly focussed on big features. We should be careful to not leave behind important bugs fixes and work originating outside the core devs.
Despite that: Some of Guillaume's activities got cut off. I think it would be great to progress both on stacking and resampling before the next release.
I also think these meetings should, as a standing item, note the estimated upcoming release schedule, to help us remain aware of that cadence.
Good night!
J
_______________________________________________ scikit-learn mailing listscikit-learn@python.orghttps://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
-- Guillaume Lemaitre INRIA Saclay - Parietal team Center for Data Science Paris-Saclay https://glemaitre.github.io/
_______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
-- Guillaume Lemaitre INRIA Saclay - Parietal team Center for Data Science Paris-Saclay https://glemaitre.github.io/
Thanks everyone for joining, There's definitely room from improvement but this was still very productive I think :) The meeting notes are on the project board. I sent a google calendar invite to everyone for the next meeting: Monday 26th August, same time. If I missed you or if you want me to use another address, let me know. Anybody interested in moderating the next one? Nicolas On 8/5/19 10:31 AM, Andreas Mueller wrote:
As usual, I agree ;) I think it would be good to call out particularly important bugfixes so they get reviews. We might also want to think about how we can organize the issue tracker better.
Having more full-time people on the project certainly means more activity but ideally we can use some of that time to make the issue tracker more organized.
On 8/5/19 9:21 AM, Joel Nothman wrote:
Yay for technology! Awesome to see you all and have some matters clarified.
Adrin is right that the issue tracker is increasingly overwhelming (because there are more awesome people hired to work on the project, more frequent sprints, etc). This meeting is a useful summary.
The meeting mostly focussed on big features. We should be careful to not leave behind important bugs fixes and work originating outside the core devs.
Despite that: Some of Guillaume's activities got cut off. I think it would be great to progress both on stacking and resampling before the next release.
I also think these meetings should, as a standing item, note the estimated upcoming release schedule, to help us remain aware of that cadence.
Good night!
J
_______________________________________________ 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
Hi Everyone, Quick reminder that the next meeting is on Monday! *Please update your cards on the project board* so we can all have a look before the week-end. We decided to go for a "scrum-like" approach this time: quickly go through everyone's notes first, then discuss main issues. Anyone interested in hosting? I think we should have a new person each time, or you'll soon be fed up with me. If nobody speaks up I'll np.random.choice someone on Monday ;) ---- Time and date: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=8&day=26&hour=13&min=0&sec=0&p1=240&p2=33&p3=37&p4=179 Project board: https://github.com/scikit-learn/scikit-learn/projects/15 <https://www.google.com/url?q=https://github.com/scikit-learn/scikit-learn/projects/15&sa=D&ust=1566914386036000&usg=AOvVaw15duAHoylKYpdBsYgogoOQ> Meeting link: https://appear.in/amueller <https://www.google.com/url?q=https://appear.in/amueller&sa=D&ust=1566914386036000&usg=AOvVaw2rS1k5NlK35I-_dSoJLgt2> See you on Monday! Nicolas On 8/5/19 10:31 AM, Andreas Mueller wrote:
As usual, I agree ;) I think it would be good to call out particularly important bugfixes so they get reviews. We might also want to think about how we can organize the issue tracker better.
Having more full-time people on the project certainly means more activity but ideally we can use some of that time to make the issue tracker more organized.
On 8/5/19 9:21 AM, Joel Nothman wrote:
Yay for technology! Awesome to see you all and have some matters clarified.
Adrin is right that the issue tracker is increasingly overwhelming (because there are more awesome people hired to work on the project, more frequent sprints, etc). This meeting is a useful summary.
The meeting mostly focussed on big features. We should be careful to not leave behind important bugs fixes and work originating outside the core devs.
Despite that: Some of Guillaume's activities got cut off. I think it would be great to progress both on stacking and resampling before the next release.
I also think these meetings should, as a standing item, note the estimated upcoming release schedule, to help us remain aware of that cadence.
Good night!
J
_______________________________________________ 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
Meeting is in 5 minutes everyone! Prepare to be np.random.choice'd :) https://appear.in/amueller <https://www.google.com/url?q=https://appear.in/amueller&sa=D&ust=1566914386036000&usg=AOvVaw2rS1k5NlK35I-_dSoJLgt2> On 8/22/19 10:11 AM, Nicolas Hug wrote:
Hi Everyone,
Quick reminder that the next meeting is on Monday! *Please update your cards on the project board* so we can all have a look before the week-end.
We decided to go for a "scrum-like" approach this time: quickly go through everyone's notes first, then discuss main issues.
Anyone interested in hosting? I think we should have a new person each time, or you'll soon be fed up with me. If nobody speaks up I'll np.random.choice someone on Monday ;)
----
Time and date: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=8&day=26&hour=13&min=0&sec=0&p1=240&p2=33&p3=37&p4=179
Project board: https://github.com/scikit-learn/scikit-learn/projects/15 <https://www.google.com/url?q=https://github.com/scikit-learn/scikit-learn/projects/15&sa=D&ust=1566914386036000&usg=AOvVaw15duAHoylKYpdBsYgogoOQ>
Meeting link: https://appear.in/amueller <https://www.google.com/url?q=https://appear.in/amueller&sa=D&ust=1566914386036000&usg=AOvVaw2rS1k5NlK35I-_dSoJLgt2>
See you on Monday!
Nicolas
On 8/5/19 10:31 AM, Andreas Mueller wrote:
As usual, I agree ;) I think it would be good to call out particularly important bugfixes so they get reviews. We might also want to think about how we can organize the issue tracker better.
Having more full-time people on the project certainly means more activity but ideally we can use some of that time to make the issue tracker more organized.
On 8/5/19 9:21 AM, Joel Nothman wrote:
Yay for technology! Awesome to see you all and have some matters clarified.
Adrin is right that the issue tracker is increasingly overwhelming (because there are more awesome people hired to work on the project, more frequent sprints, etc). This meeting is a useful summary.
The meeting mostly focussed on big features. We should be careful to not leave behind important bugs fixes and work originating outside the core devs.
Despite that: Some of Guillaume's activities got cut off. I think it would be great to progress both on stacking and resampling before the next release.
I also think these meetings should, as a standing item, note the estimated upcoming release schedule, to help us remain aware of that cadence.
Good night!
J
_______________________________________________ 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
Hi everyone, Remainder that the next monthly meeting is on Monday! Please update your project notes *before Friday* so we don't have extra work on the WE :) https://github.com/scikit-learn/scikit-learn/projects/15 <https://www.google.com/url?q=https://github.com/scikit-learn/scikit-learn/projects/15&sa=D&ust=1569248921932000&usg=AOvVaw0mv4SPS00zPOz2HIzLKy1o> https://appear.in/amueller <https://www.google.com/url?q=https://appear.in/amueller&sa=D&ust=1569248921932000&usg=AOvVaw2YzZNavzQWVTX9wXs586Hw> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=9&day=23&hour=13&min=0&sec=0&p1=240&p2=33&p3=37&p4=179 Cheers, Nicolas
participants (9)
-
Adrin -
Andreas Mueller -
charujing123 -
Chiara Marmo -
Guillaume Lemaître -
Hanmin Qin -
Joel Nothman -
Nicolas Hug -
Rujing Zha