I completely agree with everyone regarding 1.0 and I really think we should
make a clear list of issues for this (just saying API is pretty vague).
However there is life after the 1.0, and I think Andy's message was more
about that kind of long-term decisions.
We should avoid getting features that aren't used by users, and equally
well features that aren't of interest to active developers. I don't feel
like scikit-learn is at risk at the moment, but we must avoid ending up
with (more?) semi-orphaned modules that most developers are afraid to touch
in case an issue is reported.
Vlad
On Thu, Jan 10, 2013 at 11:29 PM, Robert Layton <robertlay...@gmail.com>wrote:
> On 11 January 2013 10:21, Lars Buitinck <l.j.buiti...@uva.nl> wrote:
>
>> 2013/1/10 Andreas Mueller <amuel...@ais.uni-bonn.de>:
>> > I wanted to ask: should we try to make plans? We get a lot of PRs and
>> > have more and more contributors and I think it might be nice
>> > if we had some form of road map to give everything a bit more direction.
>> >
>> > I know that people mostly contribute algorithms they are using in
>> research,
>> > and that is great, because that makes for high-quality code.
>> > I am not sure, though, for how long the "hey look, I coded this cool
>> > estimator which I used in my latest paper" strategy is feasible.
>>
>> What we could do is determine a focus for the next release other than
>> "add more features", like:
>> * implement Python 3 support
>> * fix outstanding API issues, like sparse matrix support for some
>> estimators.
>>
>> That would be a step towards a 1.0.
>>
>> --
>> Lars Buitinck
>> Scientific programmer, ILPS
>> University of Amsterdam
>>
>>
>> ------------------------------------------------------------------------------
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
>> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
>> MVPs and experts. ON SALE this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122712
>> _______________________________________________
>> Scikit-learn-general mailing list
>> Scikit-learn-general@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
>>
>
>
> I would say to not worry about the addition of algorithms, and have 1.0 as
> being a API/python3/sparse release as Lars said.
> I don't think that holding off a big release because it doesn't contain
> algorithm X is a good idea, as there are plenty of algorithms we don't have
> yet, even important ones (depending on your definition of important).
>
> - Robert
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122712
> _______________________________________________
> Scikit-learn-general mailing list
> Scikit-learn-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
>
>
------------------------------------------------------------------------------
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
_______________________________________________
Scikit-learn-general mailing list
Scikit-learn-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
