Also, the naming discussion here is not *only* on naming; it's also on the possibility of including *more things *in the package. I would be all for having a package like Palettes.jl, which would include both NoveltyColors.jl and other palettes, but that's not in conflict with the current package - it's an extension, that might happen tomorrow, in a year, or never at all, depending on whether someone actually finds it useful enough to implement it.
// T On Tuesday, December 1, 2015 at 4:34:08 PM UTC+1, Randy Zwitch wrote: > > Here's my PR, I'm not the one who merged it. However, between November 24 > and yesterday seems quite long enough for naming; I mean, no one else was > really thinking of using NoveltyColors as a name, were they? Naming > discussions to me only seem necessary when it's a common name so that > someone doesn't squat on a name that's obvious and should be reserved. > > https://github.com/JuliaLang/METADATA.jl/pull/4120 > > Ultimately, I just wanted to add these color palettes to Vega.jl, > ColorBrewer.jl already shows that we're willing to have small color > packages on METADATA, and I figured other people might want to use these > palettes. Moving them inside of Vega.jl would take 30 seconds, so it > doesn't really matter to me. Just trying to modularize for the benefit of > the community. > > On Tuesday, December 1, 2015 at 9:56:41 AM UTC-5, Andreas Lobinger wrote: >> >> >> >> On Tuesday, December 1, 2015 at 3:32:19 PM UTC+1, Randy Zwitch wrote: >>> >>> +1 Tom. >>> >>> It's on METADATA now, so only focus now is to improve the package, the >>> name isn't going to change. >>> >> >> I can not track it down right now (i think it was on the Color/Colors,jl >> discussion) but wasn't there something like a holding time for METADATA.jl? >> Like 48 hours? I cannot really understand, how a package like this with a >> special interest flavour and somehow limited code makes it an official >> package in a few hours? Without any naming discussion. >> >
