Sam Vilain wrote:
I was catching up on the mailing list yesterday, and while I was not
surprised by the comment that the MooseX:: namespace should only be for
modules that extend Moose, I was surprised that MooseX::DataMapper -
despite being an extension specific to Moose classes, and despite being
a primarily trait-based API - did not meet the criteria.
Perhaps someone has some thoughts on where the line should be drawn; for
the above I would have thought it was a Moose extension.
Maybe a general criteria is that MooseX:: could be for modules whose
functionality might have reasonably been built-in to Moose itself, but that
weren't in the interest of keeping Moose from bloating or because the
functionality is experimental etc.
In contrast, something that depends on Moose but wouldn't reasonably be built-in
to Moose under normal circumstances would be a candidate for not being a
MooseX::. For example, the functionality of KiokuDB is best not in a Moose:: or
MooseX:: namespace, and indeed it isn't.
-- Darren Duncan
