Configure project nodes to be Organic Groups

I think it's easy: turn on OG and configure project node types to act as OGs. I doubt this requires any code at all. If it does, it can live in http://drupal.org/project/og_project.

What is this a duplicate of? You did not specify that, neither you said anything about there being any duplicate issue.

Even if it is easy, it makes sense to track progress of it, right? We'd need pull in this new module in SVN, possibly an update function, etc. Otherwise we'd need this one as a manual step on all test "redesign upgrade" tests.

The question whether we want to have OG on two subsites should also be answered.

Please mark duplicate if there is another issue we can pull into the redesign queue for this which allows tracking the task.

Well, let's have a pushing match about the title of this issue, then. ;)

Next step: read this thread: drupal.org projects as Organic Groups. That's the proposal where MB + Leia got the idea in the first place.

Linking off to a separate site would be a drag and a usability problem IMHO. A big part of the point is that per-project documentation and discussion lives right off the project pages themselves.

Isn't the idea that all this is going to move to "downloads.d.o" or something anyway?

Well, there already are project specific groups on groups.drupal.org. We either migrate them, their posts, etc. to this new project groups site (including whatever features, filters, signups, etc. they used), or we are going to end up with a massive confusion with project groups being at multiple places.

If we migrate the groups anyway, we can now link to the groups group (should somehow be able to provide that group name on drupal.org per project, if exists); and then later we can always migrate.

If we are not going to migrate but have groups, then we are back at having the groups on g.d.o, so same applies.

I have no time or energy to discuss this in the short term (I'll have more next week). I'd suggest that before anyone spends more time on this that we postpone this particular feature of the redesign so that we can a) have a proper discussion about it and b) come to an agreement before anything is actually implemented. Nothing says we have to roll out all the features at once, and this is not the most critical part of the redesign. There are many pros and cons to the various approaches to dealing with this, and I don't want a half solution that's not really decided just come into existence in the name of "we have to get something working now". Thanks.

Where should this be filed? I need to clean out the Redesign issues.

Gerhard's suggestion in #7 sounds good (just a link to the group, if it exists), but I don't think it's worth importing posts from g.d.o. because they are often crossposted from other groups, and will probably be very confusing to visitors.

The other problem is that including this link will encouraging people to create groups based on modules. Is that desirable? Given all the trouble we have recently over where to put support inquiries, I'd be hesitant to scatter information even more.

Reverting this back to the original intent of the issue. This is still desirable, unrelated to the redesign. This has come up a few times in various discussions on g.d.o, but it's nice to have an actual infrastructure issue about it when the time comes to un-postpone this and actually do it.

Closing old issues. Please re-open if needed.