[petsc-dev] Job openings

[Barry Smith]

  PETSc announce has more people than petsc-users but it is not clear that everyone on petsc-users is on petsc-announce. Everyone should join petsc-announce but they may not. 

  We could send them to both with the same label but then many people will get two emails which is annoying. 

  Maybe use the labels   [PETSc Job opening] and [PETSc Release] to give people an easier filter. 


   An approach which is probably not simple is that anything sent to petsc-announce is also sent to everyone on petsc-users who IS NOT on petsc-announce so everyone gets only exactly one copy regardless of whether they are on both or either. 

   1)  Maybe we could just manually remove everyone from announce who is in users and make sure that anything sent to announce also gets sent to users.
    2)  Or whenever anyone joins users we sign them up for announce automatically and then only send such message to announce (the webpage could indicate you will 
          automatically also be added to announce. This seems the least painful, but then someone now needs to add to announce everyone who is on users but not
          on announce.

   People could get fancy with filters to get only one copy but that is obnoxious to expect them to do that. 

   Barry



> On Nov 20, 2020, at 1:27 PM, Junchao Zhang <junchao.zhang at gmail.com> wrote:
> 
> The usefulness depends on how many users subscribe to petsc-announce.
> 
> Since there are not many such emails, I think it is fine to send to petsc-users. And in these emails, we can always add a link to a job section on the petsc website.  Once petsc users get used to this, they may go to the website later when they are finding jobs.
> 
> --Junchao Zhang
> 
> 
> On Fri, Nov 20, 2020 at 1:04 PM Matthew Knepley <knepley at gmail.com <mailto:knepley at gmail.com>> wrote:
> That is a good idea. Anyone against this?
> 
>   Thanks,
> 
>     Matt
> 
> On Fri, Nov 20, 2020 at 1:26 PM Barry Smith <bsmith at petsc.dev <mailto:bsmith at petsc.dev>> wrote:
> 
>   Maybe something as simple for petsc-announce
> 
>  Subject:    [Release]     ....
>  Subject:    [Job opening] ....
> 
>    Then when you send out the most recent job opening you can include in the message something like 
> 
>     "The PETSc announce mailing list will continue to be low volume. We will now tag each message in the subject line with [Release], [Job opening],  or possibly other tags so you can have your mail program filter out messages you are not interested in.
> 
>     Thanks for your continued support,"
> 
>        
> 
>> On Nov 20, 2020, at 9:45 AM, Matthew Knepley <knepley at gmail.com <mailto:knepley at gmail.com>> wrote:
>> 
>> I got the second email in less than one month about sending a job opening to the PETSc list.
>> 
>> 1) Should we have some policy about this?
>> 
>> I think we should encourage it, but in a way that does not produce noise for people. I think there are no other good outlets for computational jobs.
>> 
>> 2) Should we have a section of the website for this?
>> 
>> I would like something that just selected some petsc-users mail from the archive with a query in the URL.
>> 
>> 3) If we encourage it, should we have a special header for job posts in the mailing list?
>> 
>> This would facilitate 2).
>> 
>>   Thanks,
>> 
>>      Matt
>> 
>> -- 
>> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
>> -- Norbert Wiener
>> 
>> https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
> 
> 
> 
> -- 
> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
> -- Norbert Wiener
> 
> https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20201120/be5650b0/attachment.html>