Jobs boards down

With Heroku discontinuing their free plan, our jobs board is officially broken :frowning: It is no longer possible to submit a job.

I would like to propose we use some of the funding in Open Collective to hire a developer to find and set up an alternative to Heroku.

Any thoughts?

We should probably also discuss this in the next monthly call.


Why not use just discourse?
*sorry I am newbie in this forum

Don’t apologise: it’s a fair question :slight_smile:

We found that projects sometimes struggled to articulate what they were looking for design-wise. Other times, they simply forgot to add fundamental information like contact details. So a bit of structure helps projects ensure they include all the necessary information and helps them explain what they are looking for in ways designers can understand. Discourse provides a free text field (I believe), so there was no way for us to provide structure. That’s why we created the jobs form

Finally, the jobs board is curated: it is only for design-related contributions to free or open source projects. We occasionally get things that are neither. Although it is possible that curation could be facilitated through Discourse as well: I am not sure.

I hope this explains somehow :slight_smile:

PS: the approved jobs do land on Discourse once they are approved by the curating volunteers

Is this job-form attached to a server-side functionality? I mean you made something like a “bridge” or just store data of sended form and read/post it ourself - this is not automated?

As I see you are review posts before posting, in this case it is possible store job-posts in Firestore for example, or obvious Google Forms( not sure about customizing design and domain, just thoughts) before a posting.

I also got the message from Heroku)

Github now has yaml issue templates that can be used to define form fields ahead of time.

Could also make it so that the new post spawned with some text laying out what people need to enter (similar to what nextcloud help forums do).

Wouldn’t be surprised if there was a form field plugin for discourse either.

1 Like

This is good to know. Thank you for your input! Please keep it coming. Knowing our options will help us make decisions :slight_smile:

1 Like

I could not find a form plugin but there are post templates in discourse since almost 10 years. I wonder if that, together with a moderated topic (topic/settings/“Require moderator approval of all new topics”) might suffice?

1 Like

My only thought is that your current submission form is open to the public, no sign-in required. If it was on GitHub/Discourse that might deter some without credentials?

1 Like

One of the objectives of our OSD jobsboard is 0 friction involved in posting a job. Nothing is required to post a job - no Github account, no Discourse account. Nothing.

Unless the Discourse templates can be completed without the requirement for signing up to our discourse, I completey agree with @Ian.

Requiring some credentials will deter people, for many reasons, the most common being just unnecessary friction.

Our goal here has to be to recreate the jobs board with 0 friction for the poster.

PS: Also nice to see you here again @Ian. :wave:

1 Like

Hello @bazylevnik0 and welcome. No need to apologise for being a newbie. We’re all newbies somewhere. :slight_smile:

1 Like

Hello, I might know someone who can help.
Do we have the current code that used to be in Heroku? Is it in any repository?

Hey @ei8fdb :wave: !

The repo is opensourcedesign/jobs. From my rudimentary knowledge:

  1. The form at Submit a Job fires a request to which is an endpoint provided by a Staticman instance running on Heroku. Now that the Heroku plan has ended presumably this is where things fail.
  2. Staticman has access to the same jobs repo and reads its config from staticman.yml. It simply creates a new PR in the jobs repo I think, with all the submitted data written to a file, e.g. pull #853.
  3. From there a human can vet the PR and if it’s accepted then the static site is rebuilt and deployed, thus the new job appears.

There do seem to be some Heroku alternatives (Render) that still have free tiers so it might be possible to shift staticman to one of those and update the URL on the job form. Or maybe someone else knows a new/simpler way to create a PR in a GitHub repo from a public form…


Thank you so much for all you replies. They are really useful.

I am still keen on fixing the current implementation. It means people don’t need to create a Discourse account to post a job (low friction is good in this case!).

I am also keen on getting someone to do things well, instead of relying on a volunteer contribution. If anyone is interested in sending a quote for the job, please do so. The quote should include documentation and some time for training community members on the technical setup and troubleshooting. We need to be able to maintain this ourselves! :slight_smile:

You can either post your quote here (if you don’t mind it being public), or you can email me on belenbarrospena at gmail dot com if you rather keep it private.

This is just my personal take on things: the community will need to decide on a final course of action. But I hope that gathering some details about potential costs will help decision making.

Thanks again to all those who replied here!

1 Like

I can just copy existing project from heroku to codesandbox(also if it need edit something then edit),it is also going to be as opensource(everyone can see source) in page of project. It can be in any environment(like a in the heroku). But if you have some private information as a app keys, it is not a good solution.
*if it on JS)

A quick update on this.

Someone suggested that we look into upgrading our Heroku account to a paid subscription.

Sadly, it looks like Heroku only takes payments by card, and Open Source Design doesn’t have a card we could use as an organisation. So I guess this means Heroku is jut not a good option for us :confused:

1 Like

As a makeshift solution, here a link we can provide for people to create a post on discourse:

template link

  • It basically mirrors the form
  • has a tag showing that it was created with this link

We could put it at the place of the current post-a-job button (with the disclaimer that it needs a discourse account) until we have a better solution.

(I tried to find the relevant place in our website repo, but could not locate where to do the change if needed)

Two ways:

  1. Direct Job menu entry to a sub-page briefly explaining that it needs a discourse account and links to both the job board and the job-template.
  2. Direct Job menu entry to discourse category directly and explain how to use it in the header text of the category and set a category template (I prefer this, less indirection)

Thanks @jdittrich

This is certainly a possible interim solution. The only thing to iron out would be moderation. I think there is value in looking at the jobs before they are posted to the world.

Is it possible to turn on moderation for new forum posts within a category? If yes, who can be set up as a moderator? Just forum administrators? Everyone?

I’ll do a bit of digging about this, but I still think the priority is to get that form fixed!

Just thoughts after month call:
We can solve a coding problem with no-code way, I tried for example (it is can works with backend API’s but with paid subscription… ).
This way will drop a finding a coder, and we will can make it ourself, it is not really hard.

@belenbarrospena I did a bit of research and found that it’s possible to moderate forum posts within a category - Category Group Review/Moderation - announcements - Discourse Meta

I think the forum admins would suit the job well. If delegated to members outside admins, maybe some criteria would help not just for moderators but for job posters.


Yes, its in forum settings
lable: Moderation Checkbox: Require moderator approval of all new topics