[scikit-learn] Doubt regarding issue timeline

Jaques Grobler jaquesgrobler at gmail.com
Tue Oct 11 01:49:30 EDT 2016

I'd say a 'standup'-ish approach could work with this - everyday or three,
if you find yourself getting pulled off the issue by other work, life,
etc. perhaps take a moment to at a set time to , if needed, post on the
progress/blocking factors -- even if it's 'can't work in this today' - yes,
this could potentially get spammy, but it gives nice transparency and if
it's urgent to finish the issue soon, like before a release, the community
can know wether or not it needs to be handed over - or if you believe
you'll have time still --
This doesn't have to be a rule- but more of a guide line - the community
will always have a fairly recent status update, even if the person can't
touch the issue for weeks.

Just my thoughts on it :)

On Tuesday, 11 October 2016, Siddharth Gupta <siddharthgupta234 at gmail.com>

> Hello fellas,
> I have a doubt. Suppose I ask to volunteer in working on an issue but due
> to some unavoidable scenario I fail to work on it for sometime, when should
> I let the community know about the same. I guess it depends on the
> issue/bug, but on an average how much time should one take to resolve an
> issue.
> Regards Siddharth Gupta,
> Ph: 9871012292
> Linkedin <https://www.linkedin.com/in/sidgupta234/> | Github
> <https://github.com/sidgupta234> | Codechef
> <https://www.codechef.com/users/sidgupta234> | Twitter
> <https://twitter.com/SidGupta234> | Facebook
> <https://www.facebook.com/profile.php?id=1483695876>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scikit-learn/attachments/20161011/fb5780c7/attachment.html>

More information about the scikit-learn mailing list