Hacker News Reader

Comment by laumars | Hacker News Reader

The first link I clicked on (the UK section[1]) was listed entire with jobs dated 2015. Even assuming some of those companies still have openings, seeing results that old immediately discourages me from investigating further on your resource. So it might be worth hiding expired positions from a UX perspective.

[1] https://www.fossjobs.net/jobs-in/United-Kingdom/

edit: The 2nd link I click on had jobs ranging from 2014 to 2012. I respect the effort you're putting into this curated list but displaying jobs that old is a little silly.

View on HN

Indeed. I clicked the US link and the newest post is from August 2016. And that's the only one from 2016. The next newest is from August 2015 and they quickly get much older than that as you move down the list.

I guess the one benefit is seeing a list of potential employers of FOSS developers even if it means researching current possibilities elsewhere...

As I write your post is 7 hours old. I saw 4 posted in the US for 2017 so perhaps being on HN is getting them some attention. But yes, there were things from 2012.

That's great! As mentioned my initial take away was at least it was a good place to start researching companies that actually have FOSS positions available whose focus is on contributions and not just using/understanding FOSS.

After my comment I read more and it looks like they want more contributions and, I agree, being on HN probably helped!

An issue requesting automatic expiry was created a bit before you commented: https://github.com/fossjobs/fossjobs/issues/14

If you’re up for contributing a simple timeout or something like that I guess the developers would appreciate that a lot :) https://github.com/fossjobs/fossjobs/

I don't think so, somewhere else in this thread the developer of this job board says that his intention is to keep all listings forever, as this would prove that paid FOSS jobs exists in abundance. IMO a debatable approach.

https://news.ycombinator.com/item?id=13920594

No. I want to keep them around, sure, but of course they can be styled differently.

I don't know what makes everyone so upset at old listings. They are listed chronologically, there is an RSS feed to follow for fresh things. It's not like it's thousands of mixed jobs where you have to hunt for the recent postings? I definitely don't object to someone adding an archive/expiry functionality that does not completely delete old job listings. If you look at the referenced ticket on github, I created it.

Nobody is suggesting old jobs should be deleted from your database (I doubt any job listing website would do this). Just that the old jobs are too irrelevant to display by default as visitors are generally only interested in current vacancies.

Keeping the old jobs as a separate search option (eg "[ ] include historic items") de-clutters the primary purpose of the site. That matters when you consider that few people enjoy the process of job hunting so will quickly abandon any platform with a poor signal to noise ratio.

So, where's the patch?

I spend some of my free time to collect and post open source jobs someplace. That's my goal.

I think that's silly. There could have been hundreds of well-paid FOSS jobs in 2013. That doesn't matter at all if there are none in 2017. It doesn't even prove anyone was ever hired for that job, only that it was posted.

There's certainly analytical value in having every FOSS job you could have ever seen, but none for the end user.

It certainly matters to a lot of people around me, and in conversations I have. It may not matter to some random people on Hacker News.

Reply on news.ycombinator.com