I feel that maintaining package infrastructure is quite some work, if
you want to have online documentation and continuous integration.
It took me a day to build the pystruct docs after I tried to update the
gallery from sklearn master.
I guess that having an example repo that has a build, travi
>
> On Dec 4, 2014, at 2:00 AM, Sturla Molden wrote:
>
> Tom Fawcett wrote:
>
>> Wow, I had not seen this FAQ. "As a rule we only add well-established
>> algorithms. A rule of thumb is at least 3 years since publications, 1000+
>> cites and wide use and usefullness.”
>
> A dumping ground fo
Tom Fawcett wrote:
> Wow, I had not seen this FAQ. "As a rule we only add well-established
> algorithms. A rule of thumb is at least 3 years since publications, 1000+
> cites and wide use and usefullness.”
A dumping ground for any kind of algorithm that "someone has found useful"
is not a good
Chiming in as a user who never contributed but who uses sklearn a lot
(yeah, I know, I need to find the time to help a a little), I tend to agree
with this.
I know a couple successful projects that have stand alone plugins,
withwithv standardized names and interface and a easy to find curated list
2014-12-04 0:55 GMT+01:00 Joel Nothman :
> For example, let's say someone has implemented an algorithm (Affinity
> Propagation is what triggered this discussion so you might consider that).
> Someone else wants to come and add features to it, or even just clean the
> code, but by this time the orig
