Change the module package to Commerce (contrib) - Do Not Capitalize Letters In Module's Name

Fixed in the repository.

While at it, it should be "Commerce (bulk product creation)" instead of "Commerce (Bulk Product Creation)", in order to comply to drupal coding standards (only the first letter of the first word allowed to be capitalized). More info here: #1103208: Projects' names should be checked in .info files for correct capitalization.

+ proper tags too ;)

Thanks for catching this!

Fixed. Dropped the parens, too, as that seems to make sense.

...sorry to activate again, but you missed the parentheses there: "Commerce bulk product creation" should be "Commerce (bulk product creation)" because according to commerce contrib "satellite" modules naming suggestion - it should be in the form of Commerce (contrib module name).

PS: sorry if I am busting b@@ls here with my perfectionism.

Changed it back. And no apologies---that is what coding standards are for, after all.

I wonder though ... where do I find this recommendation? It's not at http://www.drupalcommerce.org/development/standards ...

...sure it's there: http://www.drupalcommerce.org/development/standards#packages

Actually I went through that article just now and located the specific paragraph. I think that I originally heard about it in a video from a drupalcon though. You'll see that exact naming being used in a bunch of other Commerce related projects out there ;)

If I may nitpick myself ;):

What is talked about there is only the _package_ name (emphasis mine):

Commerce (_____) - projects with dependencies between the various modules in the package may consider their own package name using the same format but should otherwise default to Commerce (contrib)

And the following example makes that clear:

As an example exception, Commerce PayPal uses the Commerce (PayPal) package name, because each PayPal payment method is represented by a separate module that depends on a core PayPal module for IPN processing. It is helpful to the user to group these 4+ modules together with their dependency.

Note that the module name in this example is "Commerce PayPal" (no parens), while the suggested package name is "Commerce (PayPal)"---because PayPal may have multiple dependent modules that are usefully grouped together.

(I do believe that what you say is (at least a de facto) standard, but it does not say so in the coding/dev standards. If it is indeed the recommended package name, it should be clarified there.)

...that's right. I believe it was Ryan mentioning it in this video (also linked in Commerce project's page too) from DrupalCon Copenhagen.

Ah, thanx for taking the time to clarify all this Ryan! All this time I was reading "package" and my mind was interpreting this to "project" somehow. Silly me ;)

...though the module names you suggest conflict with drupal naming/coding standards - but I understand you only mean to make a point. Actually, I think "Commerce BPC" is ok though (acronyms are an exception to the capitalization rule).

Hm, I think I'll leave it as is for now. "Commerce BPC" is not a good choice, as it really is not descriptive.

See #1346158: Decide on coding standard for capitalization of module names [policy, no patch] and #1430452: Use Proper Name Case for core modules for current information on this policy.

...yep, the standard has changed and it now allows (more likely suggests) Proper Name Case instead of the Sentence case for module/theme names. The Sentence case policy remains for UI text like widget labels for example.