Broken link in newsletter about usrse.github.io

[vsoch]

This is fixed with #129. We will need to be diligent for future Newsletter posts!

[vsoch]

A lot of the job links I’ve seen on here are almost certain to go away - which is why we test the jobs data file and require an expiration date. For Travis, you’re right that the broken link will break testing into the future, so here is my thinking:

• for this and all future site newsletters, maybe mention the job names but then link to the single jobs page for more information.
• Generally don’t hard link jobs anywhere on the site.

Of course direct links are fine in the email newsletter since they will work when it’s sent, and nobody is likely to go back later to retrieve again.

[cferenba]

I think @vsoch's idea makes sense, but one clarification:

Generally don’t hard link jobs anywhere on the site.

That is, except for the jobs page itself, right? Since we have expiration dates attached to the jobs there, the links should get filtered out by the expiration date before they go invalid.

[cosden]

Removing hard links in the website version of the newsletter seems the easiest and most sensible solution. Since it requires a manual (for now) conversion to markdown, it should be easy enough to make standard practice. I'll make the change in the october one.

[vsoch]

I can better clarify - when I say a hard link, I mean writing it directly into the text, like https://hotdogs.are.us. The jobs page itself doesn't have any hard links because they are rendered from the data file _data/jobs.yml that is checked for correctness via the continuous integration. Does that make sense?

[vsoch]

And exactly, the expiration date controls if we render the link or not - once a job link is expired it won't render any longer, and it's okay to just leave in the file, but likely someone will clean it up every once in a while :)

[cferenba]

Ah, okay, I see what you mean now, I wasn't familiar with that terminology. That makes sense.

[vsoch]

For future folks to see - here is what the jobs page looks like:

<ol>{% for job in site.data.jobs %}
{% capture nowunix %}{{'now' | date: '%s'}}{% endcapture %}
{% capture expires %}{{ job.expires | date: '%s'}}{% endcapture %}

{% if expires > nowunix %}
   <li><a href="{{ job.url }}" target="_blank">{{ job.name }}</a>: {{ job.location }}</li>
{% endif %}{% endfor %}</ol>

and the newsletter page (with hard links)

These opportunities were recently posted to the [RSE Careers page](https://us-rse.org/jobs/):  
[Scientific Research Software Developer](https://chm.tbe.taleo.net/chm03/ats/careers/v2/viewRequisition?org=CALTECH&cws=37&rid=4938): Caltech/JPL/Dartmouth  
[Research Software Engineer - FTC](https://careers.peopleclick.com/careerscp/client_arm/external/en_GB/gateway.do?functionName=viewFromLink&localeCode=en-us&jobPostId=43583&source=LinkedIn&sourceType=NETWORKING_SITE): Warwick/UK  
[Research Software Engineer/Senior Research Software Engineer](https://brown.wd5.myworkdayjobs.com/en-US/staff-careers-brown/job/180-George-Street/Research-Software-Engineer-Senior-Research-Software-Engineer_REQ162388): Brown University