Ability to manually assign jobs to a foundation/project after submission

[iamweswilson]

Some companies submitting roles to GitJobs aren't selecting "OpenInfra" as the project, which means their posts don't appear in the OpenInfra Foundation's bucket. I suspect the "project" terminology is causing confusion, submitters may be thinking of it as the specific upstream project rather than the foundation umbrella.

This week we had 3 companies submit roles where this happened. One example:
https://gitjobs.dev/?job_id=a33c9906-aec4-4d7b-91b8-c41d783b8f5e

I'm unclear whether they missed something when adding the job or if there is a bug here. Either way, is there a way for foundation admins to manually update existing job posts to assign them to the correct project/foundation bucket after submission? This would let us pull in roles that should have been associated with OpenInfra but weren't tagged correctly at submission time.

It might also be worth looking at the submission UX around the "project" field, clarifying the distinction between foundation and project (or letting submitters select both) could reduce these mis-assignments going forward.

Happy to discuss further or provide additional examples if useful.

[tegioz]

Hi @iamweswilson 👋

submitters may be thinking of it as the specific upstream project rather than the foundation umbrella.

That's correct actually: when submitting a job, it's possible to specify the projects the candidate would work on (a project like Kubernetes, or Helm, for example, that belongs to the selected foundation). We did it this way because each job posting may have a different list of projects, so they need to be selected at submission time. GitJobs collects those projects from the corresponding foundation landscape and makes them available to submitters.

The Cloud & Heat case you shared is a bit different. They're members of the OpenInfra foundation, and I understand you'd like to see their job postings properly linked to OpenInfra.

In the employer profile, companies can select the foundations they are members of. They can select multiple if they wish. In this case, Cloud & Heat should update their profile and indicate their membership to OpenInfra (please see screenshot below). That way, all their postings going forward will be automatically linked to OpenInfra, without any further action needed at submission time.

Hope this helps 🙂

[jimmytipit]

A few questions on this:

• Is there a way for us to do that manually if we see one of our member companies submitted?
• Why wouldn’t choosing “OPENINFRA” as the foundation/project create the same effect of having them show up on our page?
• What about a company like Graphcore that posted a job intended for our audience, but they’re not yet a member of our Foundation?
• Coulld the member landscape be used to automatically tagging orgs that submit a job to the jobs board without the company having to do it manually?

Thank you for your time!

[tegioz]

• Is there a way for us to do that manually if we see one of our member companies submitted?

No, only employers can manage their own profile, you'd need to ask them to do it.

• Why wouldn’t choosing “OPENINFRA” as the foundation/project create the same effect of having them show up on our page?

It would, but OpenInfra doesn't have projects, only members (as per its landscape). When you see that selector in the job posting form, it's to select a project using the search bar next to it, on the right. You can try how it works by selecting the CNCF one, that has multiple projects.

• What about a company like Graphcore that posted a job intended for our audience, but they’re not yet a member of our Foundation?

This use case is not supported at the moment.

• Coulld the member landscape be used to automatically tagging orgs that submit a job to the jobs board without the company having to do it manually?

Exact names do not match often, or there are multiple employer accounts for the same member, so it wouldn't be reliable. It's something that can be easily set during the employer setup, often just a one-time thing. Maybe we could highlight that section in the profile form, to grab their attention and encourage them to use it.

Thank you for your time!

No worries! 🙂