Changes between Version 231 and Version 232 of DevelopersForHire


Ignore:
Timestamp:
08/26/2007 01:56:20 PM (8 years ago)
Author:
vickeybohra@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopersForHire

    v231 v232  
    33''I think it does make sense to put a date. Maybe we could sort this list in alphabetical order, too ?'' -- Etienne Robillard
    44
    5 '' Yes I too agree with Etienne, better to add the names in in alphabetical order. But last updated won't highlight weather the developer is available or not. Better if we can use validity date for the job posted by the Develper. The developer should specify the validity date of the posting, i.e. when he wish to re-update the job posting. This will make it mandatory for a Developer to update the validity before it expires and will help the company to know weather the developer is available or not.
     5'' Yes I too agree with Etienne, better to add the names in in alphabetical order. But last updated won't highlight weather the developer is available or not. Better if we can use validity date for the details posted by the Develper. The developer should specify the validity date of the posting, i.e. when he wish to re-update the posting. This will make it mandatory for a Developer to update the validity before it expires and will help the company to know weather the developer is available or not.
    66
    77''I suggest it can be in the following format:'' 
Back to Top