X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 83D51D1B4A1 for ; Fri, 12 Dec 2003 19:04:32 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 76993-03 for ; Fri, 12 Dec 2003 15:04:02 -0400 (AST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id 73267D1DF64 for ; Fri, 12 Dec 2003 15:04:00 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id 62A7D379C1; Fri, 12 Dec 2003 15:01:59 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 4DC913796C; Fri, 12 Dec 2003 15:01:59 -0400 (AST) Date: Fri, 12 Dec 2003 15:01:59 -0400 (AST) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Josh Berkus Cc: francisco@natserv.net, pgsql-www@postgresql.org Subject: Re: Requirements feedback for jobs.postgresql.org. In-Reply-To: <200312120908.47640.josh@agliodbs.com> Message-ID: <20031212145510.Q17041@ganymede.hub.org> References: <1070400141.25244.8915.camel@camel> <200312091630.02129.josh@agliodbs.com> <20031211154707.X3018@zoraida.natserv.net> <200312120908.47640.josh@agliodbs.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/64 X-Sequence-Number: 3124 On Fri, 12 Dec 2003, Josh Berkus wrote: > > On the first page I would like to better understand what you mean by > > "Applications will be received by the jobs... and forwarded > > on to a specified email... to prevent email spiders? I wasn't clear after > > that what will be emailed to users? The contact info? > > In other words: > Employers will enter jobs and their contact info. The jobs but *not* > the contact info will be made public. Applicants will fill out a form, > and the system will e-mail its contents (and any attached resume) to the > employer. > > There are a few reasons for doing things this way rather than simply posting > the employer's contact info and letting people contact them on their own. > These include: > -- Protection for employers from being bombarded with spam every time they > post an ad; > -- Protection for our job listings from being "mined" by an agency or online > job web site; > -- Preserving the possibility of eventually turing jobs.postgresql.org into a > revenue stream to support postgresql. Altho I agree with all three reasons, in this day and age of heavy spam, I think 1 is definitely the big one ... but ... What information is provided about the "employer"? I take it company name and such is still provided? > Certainly we want to stick to a small number of easy-to-understand > categories. For example, I was thinking of: Database Administrator > (DBA), Software Development, Performance Tuning, PostgreSQL Support, > General System Administrator, Training, and Other. Will cross-categories be permitted? Maybe a max of 2 or 3 per job description, but would provide a bit better coverage where some overlap may be appropriate? > > From company to company, local to local, country to country views on a set > > of job duties may vary and type may just be a point of confusion. > > Or may not. Look, from my perspective, I don't want to even see jobs in the > "General System Administrator" category; they don't apply to me. Other > applicants may *only* be qualified for training. They should be allowed to > filter by this, just like applicants will filter by Full-Time, Part-Time, or > Consultant to match their availability. Point: there is nothing that stops an applicant from searching other categories ... if they can't find something under "DBA", but are wondering if something is available under GSA, they can still go check it out ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664