If you have a sense that the issue is urgent in some way, then give it up
quickly if you've said you'd do it.

Otherwise, it's okay to take a few weeks. Yes, it would be kind, if it
looks like you won't be able to do it, to say you can't.

Sorry there are no hard rules, but thanks for trying to clarify

On 11 October 2016 at 16:49, Jaques Grobler <jaquesgrob...@gmail.com> wrote:

> 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 <siddharthgupta...@gmail.com>
> wrote:
>> 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>
> _______________________________________________
> scikit-learn mailing list
> scikit-learn@python.org
> https://mail.python.org/mailman/listinfo/scikit-learn
scikit-learn mailing list

Reply via email to