Handling multiple Group types

Hello.
Am working on a department collaboration site and decided that Commons would be the best fit. And it is good for the most part.

Given that this is a department site, where staff share thoughts but also collaborate on operations (say, a proposal, a Task or a campaign etc), there will be different groups within the department. Each group will have its own custom content types (and a subset or all of Commons group content types such as Posts, Q&A, Documents etc.), its own Group dashboard and reporting screens.

I considered creating different OG types - Commons Group (for those "generic" groups that only need the Commons group content types), and specialized groups (A Proposal Group, A Campaign group etc.).

This approach, I thought, would give me the most flexibility and provide all functionality such as group security/visibility, layout and views, while providing the users options to create different types of groups for different purposes ("Create a Group", "Create a Proposal Group", "Create a Campaign Group" etc.).

But, am not able to create it without causing the Commons_Groups feature to be overridden. And am unable to come up with the best practice to do this on the Commons distribution. Overall, it seems very complex. Looking at the code, am uncertain if Commons is coded to be used with different group types.

Am now considering using Taxonomy to provide different views (using just one Commons Group type), but this does not seem to be as clear-cut as using different group types.

(I did see in one issue that OG Features was used in Commons 2 and that enabled per-group customization. This feature is missing in Commons 3. Am not sure if OG Features will solve this problem or if it planned to be included into Commons 3).

If anyone can shed some light on if and how we can implement different types of groups that would be helpful.

Thank you.