Date: Thu, 18 Dec 2003 14:31:31 -0500 (EST)
From: Francisco Reyes <lists@natserv.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-www@postgresql.org
Subject: Re: Requirements feedback for jobs.postgresql.org.
In-Reply-To: <200312160853.10380.josh@agliodbs.com>
Message-ID: <20031218142507.S27657@zoraida.natserv.net>
References: <1070400141.25244.8915.camel@camel>
	<200312120908.47640.josh@agliodbs.com>
	<20031215211038.Q1205@zoraida.natserv.net>
	<200312160853.10380.josh@agliodbs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 16 Dec 2003, Josh Berkus wrote:

> But you've missed two important points I addressed in my earlier e-mails:
>
> 1) We (my team) does not want to code that functionality.

Ok so do what you can and then others, including myself, could later on
decide if they want to pickup the ball and add the extra functionality.

> >If you EVER send attachments to
> > prospective employers what will happen if someone fakes an email as coming
> > from you and sends a trojan or a virus?
>
> Mmmm... yeah, we'd better put in a filter to limit the MIME encoding and
> extensions of resume attachements to DOC, PDF, WPD, TXT & SXW.

I believe DOC files can have viruses in them.
As long as we allow attachments this will be an issue. I am not saying you
should not continue with the exact same plans you have, just that we
should consider what we want to do for the long term.

> Maybe.  I can see adding a couple new categories after the system is launched
> and we get feedback from the users.   Otherwise, I think the categories
> should be rather inflexible; otherwise we risk ending up with 80 categories,
> 50% of which have only one job in them.

Although I think it's great you are thinking ahead I don't think we will
be flooded with postings that categories will be a problem. Of all the
problems this project could possibly have I really wish someday too many
postings will be one. I just don't think it will happen any time soon. I
wish/hope I am wrong on that though. :-)

> > So people are going to attach or cut/paste their resumes?
> > Sounds cumbersome.
>
> Well, if you don't like it, you're welcome to ready your PHP skills.  After
> you draft a spec to deal with the security issues raised by online storage of
> resumes ....

Go ahead and do the system as you planned. We can then decide what's next
after we have something in place. I think you and your team are doing
probably the most difficult part. Getting the project off the ground. I
don't think we should do anything to slow you down or distract you othen
that just give feedback when you request it.