Great, thanks Oliver!
I'll have a look around and I'll try to analyse what I've already used in
my past projects. I mainly asked to know if that was something important in
particular that you'd like people to focus on, given that there is going to
be a 1.0 release pretty soon.
Looking forward to c
2013/11/4 Nantas Nardelli
> Thank you, Andy!
> I've opened a pull request for the README bit. I think I'll have to look
> to the untagged issues, as the majority of the easy open issues have either
> already some pull request open or are really old and irrelevant (although I
> may find something
Thank you, Andy!
I've opened a pull request for the README bit. I think I'll have to look to
the untagged issues, as the majority of the easy open issues have either
already some pull request open or are really old and irrelevant (although I
may find something interesting to dive in).
Cheers,
Nant
Hi Natas and welcome :)
Thanks for wanting to contribute. I am a bit out of touch with the
current issues, but I think the easy ones are still a good way to start.
I like the idea of having a link to the contributing page in the
README.rst, maybe either under "development" or under "important li
Hi all,
I've started looking at some easy issues to solve to get accustomed with
sklearn code, as I really like the work you are doing and I'd like to start
contributing regularly. Is there anything easy (bugs, documentation, etc)
in particular that you'd like to have fixed?
I looked at the easy t
