Based someone on this questions here: #1979800: Join forces with COD, how about separating the cod_support modules into separate projects? Unfortunately the bottled-up nature of this project's features makes it hard to move forward right now. I'm currently working to get conference / event type stuff working with Panopoly and I've opened up a couple individual project that aim at specific aspects.

My thought is that we shouldn't just focus on a distribution but provide features that allow and help users get conference/event type stuff up and running on an existing site.

Thoughts?

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Makes sense to me.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

I should say: makes *some* sense to me ;)

I think the most important thing is that they are more loosely coupled. Whether they are separate projects on d.o or not...seems less important to me.

markwk’s picture

markwk commented

I agree with you about part about loosely coupled. My feeling though is that as it stands COD has drifted towards being COD for Drupal and not just conferences in general. I think we see more work / activity in separate project spaces... though that's just a hunch.

kclarkson’s picture

kclarkson commented

I hate to ask this question.

Does it make sense to rip everything down and rebuild from the ground up using Panopoly and the Apps model ?

This would make COD the solo solution for conferences but also allow the end user to select what type of functionality is needed similar to how Commerce Kickstart works.

japerry’s picture

japerry
Location KOMK
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Commons started out as a bunch of different repos, which became a royal PITA to manage. We also noticed that the usage numbers corresponded pretty closely to those downloading the distro. In the end, we decided to go full tilt the other way, not only getting rid of separate projects, but putting them all under the commons project. (no commons_support separate project)

As for COD, there is quite a bit of use of the module suite outside of the distribution. It also makes it a bit easier to install on custom drupal instances, so I don't think pulling the cod modules into the distro would be a good idea.

On the other-hand, the commons issues still stand, and with the amount of interdependency the cod_support modules have, I think we'll keep it this way.