2013/11/4 Nantas Nardelli <nantas.narde...@gmail.com>
> 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).
>
I think the best way to get started is to actually use scikit-learn
yourself, either on your own work / research or as on fun problems such as
a kaggle.com challence. Then if you hit bugs or under performing bits try
to work on fixing them and submit a PR.
Also, reviewing the PRs that are related to your area of expertise will
help:
- pull the PR branch and run the tests on your box and report failures
- review the code, examples and documentation, make sure it follows
http://scikit-learn.org/stable/developers/#contributing-code
- profile the code to identifiy the performance bottlenecks (see
http://scikit-learn.org/stable/developers/performance.html )
Finally, browsing the examples and running then is a good way to get to
know the project. If examples lack documentation or could be simplified or
improved to make them clearer to new-comers, you can also write a PR to
improve them. Here is an example of such a PR:
https://github.com/scikit-learn/scikit-learn/pull/2556
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Scikit-learn-general mailing list
Scikit-learn-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
