Background:
I have been watching the OG developments since Drupal 4.x and I have _never_ got more than just close to consider (and re-consider) using it, always because of the problematic combination of unfixed serious security issues and constantly shifting perspectives. New developments branching into such complex and new directions before current branch is stable, with the guarantee to significantly break things and complicate upgrades to the degree that it simply is not an economical option.

For the first time in OG's now fairly long history, I was just about to decide to start relying on it for production sites, as a strategic component. This important shift was made possible by the positive developments in OG7, partly also by security and architectural fixes and improvements to Drupal core in both D6 and D7, and now finally with the very convincing developments of the crucial moderation module suite, WorkBench, which is an entirely different and separate area of itself, but crucial elements of the type of modern community web sites I am planning.

Notice that when I use the term "stable", I do not only refer to "bug free" and security-wise, but a situation where all the security related things actually are working well together in a way and structure that will stay so for long enough time to deserve to be referred to as "stable"... The emphasis is on the perspectives, not only on the security and bugs. This includes the economics of upgrades, the timing aspect (now we are in an early new core phase (D7), which will last LONG before we "need" or even wish to upgrade to D8). This timing aspect is important, too. RIGHT NOW is a very crucial moment for setting perspectives straight.

To the point:
Well, it seemed that we were just so close now (a month or two ago), and then it sadly looks like the perspectives might again be distorted and forgotten, possibly to pave way for new exciting developments, I understand that part of course, just at the very moment many of us for the first time dare consider it for production sites. (and where there are solid modules providing compatible moderation features as well for the first time ever).

This is caused by the recent discussions about Roles as Entities ( #1261376: Entity-ify Roles ) and Deprecating the OG group entity ( #1342632: Deprecate OG group entity ).

You can already see several comments coming in from various people wanting to adjust their perspectives and getting stressed about these new plans. My experience with OG is that it takes a LOT longer to get into a new situation where things are - well, any point in repeating this word? - stable... - than what anyone dares suggest without risking being ridiculed by excited others.

As a side note:
I suspect that the majority of the people for whom this module will or should be used on important production sites (and thus of strategic importance) are willing to actualy financially support the developments if they get a perspective that eases their decisions (and their sleep), and that those people are not necessarily the same ones as those that are most excited about bleeding-edge developments. Remember that entities are still in its relatively early stage.

I am just one example, but for what its worth; If I will never get to the point where I actually make the decision to trust that the development perspectives of this module are sufficient to actually start relying on, then I will not get to the point where I can start contributing economically either. But I can ensure you that I am more than willing to contribute once we see that this is the way to go (and the moment to do so).

I wish (begging, actually) that such architectual changes should be developed for D8, as they very well may trigger incompatibilities with other modules that will serve as showstoppers if OG does not work well with them.

As those discussions (which are nevertheless important) moves on, I would like to see that:

  • A) the new, separate branch for those bleeding-edge changes will not be affecting the bugfixing and developments of the current 7.x version for still a year or so,

    and
  • B) the new development branch will not be promoted as the recommended version until 2013 (that turn is roughly just a year from now, folks...), to really prove that we have a solution we have reason to start relying on.

    and - crucially (my main aim with this post, actually)
  • C) a documentation of such a strategic perspective on the OG front page and in the handbook, possibly as its own, separate page for "perspectives" and strategic confirmations.

Call me naive, if you want, for I am possibly just dreaming.

Comments

bonobo’s picture

Category: task » feature
Priority: Critical » Normal

Some quick thoughts here.

One person's "new exciting developments" are another person's natural evolution.

*All* code gets refactored, and of the many modules on d.o, OG has received some high quality thought and input from a large number of community members over the years. There are a lot of discussions/issues related to the suggestion in #1342632: Deprecate OG group entity - these discussions go into the issues that will be solved by #1342632: Deprecate OG group entity.

RE: "I suspect that the majority of the people for whom this module will or should be used on important production sites (and thus of strategic importance) are willing to actualy financially support the developments if they get a perspective that eases their decisions (and their sleep), and that those people are not necessarily the same ones as those that are most excited about bleeding-edge developments."

A couple things here: historically, shops within the Drupal community have been hesitant to sponsor individual developers to do development on a module that someone else maintains, unless it's been a feature for a specific project. Speaking from my perspective as a decision-maker at a shop that *has* put a lot of time/effort into OG, dating back to 4.7, I am willing to sponsor the work in #1342632: Deprecate OG group entity because it will help us make better sites for the entire D7 lifecycle. Really, it's a no brainer. As to the "bleeding edge" nature of this, that definition doesn't fit here. Entities are part of core. Not using them to our full advantage doesn't make sense.

It sounds like what you are asking for is maintenance, for the foreseeable future, the the 1.x branch of OG in 7. If that's important to you and your work, funding that, or taking on that workload, is entirely up to you.

RE: "just at the very moment many of us for the first time dare consider it for production sites"

According to the homepage, the community has a little over 718,000 members. It's a pretty safe bet that a good percentage of us work in web development, and people who work in web development are in the business of launching production sites. In other words, at any given point, people are *always* about to launch a production site. So, any refactoring/rework of any module is bound to inconvenience someone. It's part of what site architects need to consider when timing a launch, and part of what needs to get communicated to clients: no site is future proof.

Changing the category to a feature request, and the priority to normal.

bonobo’s picture

Status: Active » Closed (won't fix)

The 7.x-2.x branch has been awesome for a while now, and development there has been steady and ongoing.

Closing this out.