Hey Mathieu. I agree that it is a bit awkward at the moment. I remember that when we wanted to get the sklearn freenode channel, people asked "so is this an organization? and why are they called differently?". As scikits-image already went through a rename, I'm not sure we should do it again. I remember there was some discussion back then and I think the outcome was "well sklearn decided for scikit and skimage for scikits, that's unfortunate but so be it". Btw sorry for the "scikits-image core developer" on the bio. I think that is a bit exaggerated given what others did in the last release. I wrote that after Stephan gave me commit rights and I was psyched ;) Cheers, Andy Am 01.10.2012 08:56, schrieb Mathieu Blondel:

Hello,

I could not help but notice that you guys were using scikits-image as project name, rather than scikit-image (without the "s" at the end of "scikit").

In scikit-learn, after a passionate discussion on the mailing-list, "scikit-learn" as project and "sklearn" as package ("import sklearn") emerged as the most popular naming convention.

This may not seem like big deal but I think a little consistency would be beneficial to both scikit-learn and scikit-image (have a look at Andreas' bio at the end of this blog post http://blog.kaggle.com/2012/09/26/impermium-andreas-blog/ ).

So here it is: woud you be willing to transition to scikit-image? (change the logo, buy the domain name, ...)

Since scikit-learn and scikit-image are the two most popular scikits, hopefully this would set the example and new scikits would follow the same naming convention in the future.

For scikit-learn, the transition went rather smoothly and now, most people correctly call it "scikit-learn" (rather than scikits-learn or scikits.learn).

Thanks, Mathieu