should use correct grouping of commerce modules

I've posted a comment to the post you mentioned above. And I'll not change the info file until we have a final guideline for how to grouping payment modules.

Reopening this as I was just playing around with it. We actually went for the distinction because of user expectations - one group is modules that are part of the core Commerce package, one is everything else. We actually wanted to avoid excessive subdividing. It sounds nice from a categorization standpoint when you're talking about dozens of modules, but most sites will just have a handful of contributed modules, not overwhelming a single "Commerce (contrib)" package. This is what all the other contribs are using, and this one should be updated to use it, too. (I only found it in the main package on a whim.)

Ryan, Commerce Paypal has package = Commerce (PayPal) and it's essentially the same size as Commerce MoIP. Don't you think it makes sense having those two modules in a "Commerce Payments" package?

Maybe payments modules are something sites usually will have many, so deserves it's own package? Other modules such as Commerce Stock would initially be in "Commerce Contrib"?

It's just a suggestion. We're better moving any discussion to #844014: Implement a single way for grouping Commerce modules.

Nah, the thing is most sites will only have a single payment method module, so it doesn't make sense to have a whole package for it. Also, Commerce PayPal is one of the edge cases I mention... it only has 2 now, but it's also going to have PayPal WPS, PayPal EC, and potentially PayPal Recurring. Basically one module per service. Even then, I may just move these into Commerce (Contrib).

Fair enough. Moved to Commerce (contrib) package.