Oh and for "how long can you take to fix a bug":
Usually you can take a couple of weeks if you like. If you stop
responding to comments for like a week or two, someone else might take
up the issue
where you left off.
But there is really no requirement on speed.
On 11/04/2015 07:41 AM, Amandeep Gautam wrote:
Hi Andreas,
I am Amandeep Gautam, a master's student at University of
Minnesota. I want to start contributing to scikit-learn. I hope this
direct email does not violate the general norms of open source
community communication. In case it does, please let me
Since I am new, so I started looking at the bugs under the easy
section on Github as suggested here
<http://scikit-learn.org/stable/developers/>.
Following are the two things I need advice about:
1. The stuff get fixed/assigned pretty quickly so getting bugs
assigned is difficult unless you are highly active. The reason it
takes me some time to respond on a bug report is that I try to
look at the code before commenting. By the time I am done with
this exercise, either the bug has already being fixed or assigned.
What would you suggest I do in this case.
2. Bugs are fixed pretty quickly as I see on the issue tracker. I do
not think I can fix a bug that fast. What is expected out of a new
person in this case? Is it okay if it takes longer? What is the
expectation of the community in such a case.
Thanks for you time.
Regards,
Aman
------------------------------------------------------------------------------
_______________________________________________
Scikit-learn-general mailing list
Scikit-learn-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
