Currently groups.drupal.org has a "Job" content type available for content creators to use.
Due to the number of organizations looking to do hiring, the availability of this content type has resulted in an increasing number of Job content type nodes being posted into groups here where job postings reduce the effectiveness / usefulness of the group. Frequently (almost always?) the job postings are for positions that have very little to do with the subject matter of the group.
Group admins must figure out how to handle these in a sane way. I certainly have this as a common problem in http://groups.drupal.org/web-experience-management . For example, today http://groups.drupal.org/node/206868 was created in this group; this posting is for a "Data Base Analyst I" at Duke University. This has nothing to do with Web Experience Management. Since I would like to keep the signal-to-noise ratio in my group very high, I want to get rid of this type of posting in my group.
I have often edited job postings in my group and moved the Audience to more relevant-sounding groups. But often, I'm making a pretty arbitrary decisions about what other groups to foist these postings into.
I would like to propose changing g.d.o to implement one of several solutions:
- Get rid of the Jobs content type. Jobs are already one of the functions of the d.o forums (at http://drupal.org/paid-services ), so we could get rid of the Jobs content type here. The downside of this: There _may_, in fact, be times when a job posting here at d.o is actually relevant to the topic of a group. I think I'd rather NOT have such postings in a group, but I can see a case for it.
- Create a "Job postings" group. The Consulting and business group often has job postings in it, but job postings seem outside of the stated mission of that group. (There's currently a discussion going on in there about this same issue.) Group managers can edit/change the audience of an unrelated job posting over to that group.
The downside of this: There's already a page at g.d.o/jobs; presumably this is just a view, and it's still useful to have that view. So we'd have to fit that view with the normal group home page (either as a special tab within the group, or something...).
- Enable admins to disable content types per-group using OG Features. We created this capability for the Commons distribution and it's really useful. This would give group admins the option to turn off the Job content type for their groups if desired. (Note: This does not require use of the Features module; "Feature" is a bit of a namespace collision....)
Frankly, IMHO, I would do both 2 and 3, because it seems impossible to respond to every job posting & tell the poster to move the listing to d.o. (I've tried; nobody ever does.) So let's just funnel the job postings that show up on on g.d.o into a sane place.