operations

"the Contact tab over at GDO seems to be broken "

see: http://drupal.org/node/280597

Would it be possible to turn on revision histories for all logged in users? In particular this would be really helpful for Wiki pages to be able to see where (and why) things were edited so one doesn't make the same mistake again later.

Another g.d.o member tried posting updates to Contributed modules status - version 6.x and, when he encountered some spam filter, was not able to post his updates. He stated that he tried for over an hour.

He emailed me for help, I attempted posting the updates, and was unable to do so because of the following error message:

i have upgraded OG today. There were some major under the hood changes, so please watch out for bugs.

As part of the new features, I disabled email notifications for job posts. This is based on feedback that they were "taking over my group.". If a group admin wants to deemphasize them in the web presentation, she may do so using the new group Pages feature. I will be adding the ability for a group admin to remove arbitrary content types from the list of 'Create' links in the group block. That would effectively remove 'job' or other content types from the group.

apache is now compressing javascript, css, and html files for groups.drupal.org. please report back any problems. especially watch for older browsers, anon users, and other edge cases.

I enabled javascript_aggregator module in an attempt to improve our YSlow score here. Please report any js related issues here.

I've installed a new spam module and removed CAPTCHA.module. The new module analyzes the contents of comments and node submissions and assigns a spam score. If the module is unsure, the user may see a CAPTCHA. But usually, the module just allows the right stuff proceed without challenge.

Please let me know if you see spam or if you hear of authors getting stopped incorrectly.

Update: The new spam module is in alpha testing right now, and I'm not able to discuss its particulars.

The post http://groups.drupal.org/node/8328 was unpublished due to violating gdo policy on posting jobs. A warning was sent via contact form. This is the text of the warning I sent. If this person violates the rules again, please block the user. Thanks.

I committed new code to OG today and rolled it to this site. We are now capable of completely private groups. Although we always have supported private content in a group, the group homepage has always been public. Thats not so anymore. A group can choose to be private now. I don't expect much use for that here, except for private planning groups like Drupalcon, Google Summer of code mentors, and so on.

Please let me know if you see funny behavior related to posting content or creating groups.

We need to do this prior to Drupal6 installation on Drupal.org right? Which will probably happen in the not-too-distant future given our tendency to install an RC on Drupal.org.

If so, we should probably make some front page posts and perhaps create a way to email all of the groups.drupal.org users who are using @drupal.org usernames

Or will their g.d.o logins still work after disabling them?