Was just talking to Moshe, drumm, and webchick on IRC, and encouraged to start this issue about moving jobs out of g.d.o. (Also see webchick's comment on http://drupal.org/node/896296#comment-3809784), which was sparked by my noticing how many jobs are being posted on the Drupalchix group despite a "no job postings" disclaimer. (Obviously this is happening on lots of working groups that don't want job postings - location groups tend to be more fond of job postings.)

Pasting notes from IRC:

- jobs.drupal.org or a section of d.o itself
- detailed location-based info
- location based feeds, so eg. the Vancouver group could have a nice sidebar block that's like "Recent job posts in Vancouver" that links to a view that gets things within a 100km radius of whatever the long/lat is of Vancouver. And that data is pulled form jobs.drupal.org, where the 'mother of all jobs site' is. (then people can subscribe to this without needing to post jobs right to g.d.o)
- also, companies could have nodes, and could post jobs (& case studies)

Comments

greggles’s picture

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

This seems a bit drastic to me, though g.d.o/jobs is the most popular page on the site so I can see a justification for creating it's own subsite. If we did that, I'd worry that we'd still be trying to tie things together too much by doing something like the "Recent job posts in Vancouver" that you mention which will be harder if it is a separate site.

Would webchick's idea would help solve your problem sufficiently or you think it's not enough?

What if you (personally) could unsubscribe from e-mails about jobs across the whole site even if they are still posted into groups where you are a member?

arianek’s picture

arianek commented

Hey greggles - most of those notes were actually from webchick (and one or two from drumm), it's not really something that bothered me enough to file the issue for, but since it seemed it was bothering a lot of people, it was suggested I file a starter issue. ;) So just trying to put some ideas down here as a starting point. Of groups I admin, the Vancouver group uses and likes the job postings... but the Drupalchix group has gotten really out of hand, and relative to the amount of other content it's really cumbersome (and Docs doesn't tend to get hardly any).

That said - the thing that bothers me the most is just that the job posts clutter up the main RON view on any given group. I don't mind them going into the RSS feed and such, but yah, the mainpage view and I suppose the g.d.o email notifications are what are my main annoyances.

Webchick's suggestion on the other queue is fine for admins being able to get rid of the posts, but that still means an admin has to spend time weeding, which is really what I would want to avoid.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

For clarification, #896296-3: Improve Content Type Administration by Organic Group so it can be deployed on groups.drupal.org was intended to be a one-time configuration on a per-group basis (or, failing that, a per-group type basis), so there'd be no weeding involved. Just a policy change. Some groups would have a "Create job" link, and others wouldn't.

moshe weitzman’s picture

moshe weitzman commented

In the end, I think it doesn't make sense for the group admin to dictate whether NYC or Boston gets to a job board or not. Inevitably, some folks like it and many don't.

Also, I don't think shutting off notifications for jobs is a sufficient response. RSS and web pages suffer just as much.

Immediate action items:
- remove jobs from the standard river of news View and RSS
- add a tab or block in each group for Jobs
- remove notification by default for jobs.

My .02.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

subscribe

ChrisBryant’s picture

ChrisBryant commented

I was just going to post the exact same suggestions that Moshe posted. If all groups default to not including jobs in the RON, RSS, and notifications and then had a jobs block that showed by default or could be added with OG Panels, then that would cover the major issues people have with jobs on g.d.o.

If that's done then it would be great to have an option at a personal or group level to be able to enable or disable email notifications of the job postings, though if the jobs block/view has RSS also, then that becomes less of an issue.

I feel it's important to have job postings in the community and g.d.o seems like a great place for it. I've personally become less involved in g.d.o due to too many job postings distracting from the conversations, but these changes would be a huge help in that regard.

arianek’s picture

arianek commented

i really think they're more valuable for location based groups than topic based ones, but i would totally +1 moshe's suggestions in comment #4 as a compromise, especially if the notifications are disable-able. ;)

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
commented

at epiqo we develop the eRecruiter drupal 7 distribution for job boards which might be a good starting point. the next release is scheduled for end of april / beginning of may

mgifford’s picture

mgifford
he/him
Primary language English
commented
Issue summary: View changes
Status: Active » Closed (duplicate)

I think this can be closed as it seems to be handled by:
https://association.drupal.org/node/18998

moshe weitzman’s picture

moshe weitzman commented

Does that mean that the Da has decided to move job board off GDO? If they have not, I think this is an open issue still. Thanks for the link, regardless.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Closed (duplicate) » Active

I don't think the outcome is quite clear yet. Let's leave open for a bit longer.

Project: Drupal.org infrastructure » Groups.drupal.org
Component: groups.drupal.org » Other
sreynen’s picture

sreynen commented
Version: » 6.x-1.x-dev
Status: Active » Closed (duplicate)

Let's continue this discussion on #2292881: Remove jobs from groups.drupal.org after jobs.drupal.org has comparable functionality.