rename project?

[millermedeiros]

I kinda feel that the name "amd-utils" is not really good for the long run.

Even tho we write the modules using AMD we convert it to Node.js using nodefy before npm publish. A generic name would be more future-proof in case AMD loses the modules battle and/or Harmony modules becomes a reality.

This project is a collection of modular/functional utilities, the authoring format is just a detail.

The name should be available on popular package managers and not being used by other important JavaScript libraries.

For AMD projects that change wouldn't really affect anything since all modules are unnamed and we can use the packages, map and paths settings and/or place the files wherever we want. Node.js is less flexible and would require users to update their dependencies manually (or we can write a tool to automate the process).

Suggestions/feedback are welcome.

PS: the earlier we change it the better since it will affect less people.

[millermedeiros]

I think we should also use this opportunity to create a GitHub organization and promote some of the contributors to admins. I don't want it to be a one man project.

[millermedeiros]

It's really hard to find a name that is small and available on both github and npm... Favorite names so far:

• mlib: modular library (favorite, available everywhere)
• mfu: modular functional utilities (mfujs on github)
• bag: bag of utilities (bagjs on github)

The advantage of smaller names is that it can be used as "namespace" for each individual package in case we decide to split it (#113) - eg. mlib-array, mlib-object, ... - But we could also use an abbreviation for bigger names if needed, @satazor suggested the name "estagiário" (means intern/trainee in Portuguese) which could become "stgr-array" or "est-array" on the individual packages.

I'm almost going forward with mlib.

/cc @satazor, @conradz

[millermedeiros]

the namespacing could be even simpler, require('m-array/sort'), require('m-math/round') let's reduce verbosity and grab all package names starting with "m-" if we pick mlib or mfu.

[conradz]

I wouldn't be opposed to mlib. mutils to me sounds like a better name, since it can be pronounced one word (e.g. mootils), but might be too close to mootools. One I thought of is fume, (FUnctional ModulEs), but it doesn't exactly encourage nice thoughts about the project :).

[satazor]

when using amd-utils, I find myself naming it utils:

var utils = require('amd-utils');

Having this in mind, I also prefer mutils. Let met think a bit and I might come with some other names.

[marcooliveira]

Haven't put much thought into this, but stdlib could be nice. It is not available on NPM, but the package seems irrelevant, the author might be open to release the name.

Will still think about this a bit further.

[conradz]

stdlib.js is available both on github and NPM. It's kinda redundant to have the .js on NPM, but it would make the package easier to find by googling. I think stdlib.js describes the project pretty well, a base set of utilities for JavaScript. Thoughts?

[millermedeiros]

The ".js" doesn't really go well on npm, it is also longer. There are a few libraries called std/stdlib and searching for standard/std on npm gives a lot of results which I don't think is a good thing.

I'm still favoring short and unique names, keep the ideas coming.

• mout : modular utilities (means "malt" in some languages, available).

[millermedeiros]

I think mout is the best name so far, besides the fact that it is related to modular utilities it also relates to malt which have a pretty good meaning as well:

Malting grains develops the enzymes required to modify the grain's starches into sugars source: http://en.wikipedia.org/wiki/Malt

We are adding sugar methods to JavaScript. Malted barley can also become a nice logo.

I put some thoughts on it and I think this project deserves its own organization, it could potentially become something as big as Dojo/Mootools and it would be nice to have mout-std, mout-dom, mout-ajax as separate projects. So what we currently call amd-utils would become the mout standard library and we would add anything that isn't directly related to a standard library as separate projects - I have no plans to create new projects for now but who knows?

Are you guys OK with it? If so I will create the github organization, the npm package, design a logo and add @satazor @conradz as admins since they been contributing to the project for a long time (if they are ok with it).

[conradz]

I would be OK with that. Like the sugar analogy :smiley:. Would the current amd-utils become just mout, or would it be mout-std?

[millermedeiros]

I created the new organization and project! https://github.com/mout/ you can access the homepage at http://mout.github.com/

will update amd-utils README to point out that the project moved to a different location and delete all files. Will also make sure documentation redirects to new location or at least prompt users telling that project now have a new name.

Will try to be more professional with mout than I was being with amd-utils (proper changelogs, versioning, etc..).