What we want from our Jobs page - An issue to collect our wants

Erioldoesdesign · May 5, 2021, 6:28pm

I created a GitHub epic for what we as a community want to improve for our jobs page:

github.com/opensourcedesign/opensourcedesign.github.io

Improving the Jobs page: Improvements to the way the jobs page works

opened 06:25PM - 05 May 21 UTC

Epic

In the community meeting held on May 5th 2021 we talked about what we want from …our jobs section and form. The jobs section of opensourcedesign.net can be improved in multiple ways. This is now an Epic issue that will collect all issues about the '[Jobs](https://opensourcedesign.net/jobs/)' page underneath it. ------------ What community members suggested for the Jobs page in terms of improvements: * Better structure for the form for jobs 'original posters'. * Clearer in form support for the jobs 'original posters' as they fill in the form. * Clear and accurate form validation for job 'original posters' * Ability to have more than one contact method * 'Contributors' have a clear set of steps to contact the 'original poster' of the job that is clear and easy to follow for any designer regardless of proficiency with OSS and comms platforms. * Keep the feature where a new job is automatically cross-posted to the discourse forum. * An easy way to see the status of a job for both the 'original poster' of the job and any potential 'contributors' to the job. * Easy way to update the job that doesn't include editing the .md file in the[ jobs repository](https://github.com/opensourcedesign/jobs/tree/master/jobs). * Review stage for the job so that abuse of 'contributors' or 'original posters' is avoided. * Include a notice that states that jobs that are open and unchanged/not commented on in a time frame (agreed by OSD community, suggest 6 months - 1 year) then the job post will be automatically closed. We welcome further comments on improvements to the job page as we grow this epic.

Designs are WIP in Figma at the moment:https://www.figma.com/file/Epo7gdfwJCDAVknWnpvfn1/Open-Source-Design?node-id=107%3A263

Erioldoesdesign · June 22, 2021, 10:39pm

From the last community call I had this action above

I changed the issue above into an ‘Epic’ on our repo (I use Zenhub chrome browser extension to create and view epics) and the issue that is an epic is here: Improving the Jobs page: Improvements to the way the jobs page works · Issue #323 · opensourcedesign/opensourcedesign.github.io · GitHub however, I know not everyone uses Zenhub so I’ll link all the associated job issues in a comment on that issue.

The Issues that were already in our repo related to the jobs page are:

github.com/opensourcedesign/opensourcedesign.github.io

Add filtering to Job Board

opened 12:17PM - 06 Jan 17 UTC

bnvk

enhancement CSS JS design jekyll Jobs

As per @evalica comment in opensourcedesign/jobs#91 she asks: > We need filte…rs for active posts, payed/free and specialization required. Yes. These are the two most needed ones. As [I suggested](https://github.com/opensourcedesign/jobs/issues/91#issuecomment-261949075), here **Status** ``` - Searching - Negotiating - Started - Complete - Rejected ``` **Specialization** ``` - Unsure / General Help ------------------------------------- - Font Design - Logo Design - Icon Design - Styleguide - Website Design - App Interface Design - User Experience Design - Usability Testing - Wireframe Prototyping - Data Visualization - Information Architecture - Product Design - Print Design - Packaging Design -------------------------------------- - Other ``` **Payment** ``` - Gratis - Negotiable / Trade - $500 or less - $1000 or less - $5000 or less - Greater than $5000 - Part Time Position - Full Time Position ``` One we agree those are the default "allowed" entries for those fields, @evalica if you want to go through and standardize the items, that would help me doing my next step!

github.com/opensourcedesign/opensourcedesign.github.io

Display Jobs by payment type (gratis vs. paid)

opened 01:10PM - 21 Mar 17 UTC

bnvk

enhancement CSS JS jekyll Jobs

*Moved from opensourcedesign/jobs#128 by* @Miserlou Currently one has to scro…ll through all to see which are paid opportunities. As @evalica pointed out Some more ideas about filtering (although this issue was perfect since it was specific, I still want to make this comments in order for the implementation to be extendible): - There is no way to see the resolved jobs (in order to determine the board's success) - The filtering is by date of posting, but this is not obvious. Apparently there is no order in the listing. Having that said it's hard to know which entries are still relevant/recent. We should have a rule to deprecate/close older than x entries.

github.com/opensourcedesign/opensourcedesign.github.io

Add concept of "Expiration" to jobs

opened 01:14PM - 21 Mar 17 UTC

bnvk

enhancement CSS JS design jekyll Jobs

*Moved from opensourcedesign/jobs#131 by* @evalica While usually we start ha…ving the need for this kind of functionality when we are flooded with posts (not quite yet, although we have 56 entries, from which 39 are searching), the problem we have is that: - we don't know if the job post is still active - people from our organization might forget to mark a post as "closed" - people that initially added the post might forget to close it in our repo. A solution would be to: - [ ] allow people to add in the job template the expiration date; - [ ] have a filter on the website and just display not expired job posts; - [ ] have a listener and automatically change the status to "expired" if the date passed (although I don't think this is possible on the platform used). - [ ] notify poster of job that it has "expired" The first two tasks can be done with Jekyll, but the later two will require some sort of server daemon / service that checks and monitors things! --- Added an implementation suggestion from #101 ``` <div class="form-group"> <label for="deadline"> Deadline <small>(optional)</small> </label> <p class="help-block">If you need the work done until a specific date.</p> <input class="form-control" id="deadline" placeholder="3 months from job posting date" name="fields[deadline]" /> </div> ```

github.com/opensourcedesign/opensourcedesign.github.io

Add RSS auto-posting to social media

opened 01:28PM - 21 Mar 17 UTC

bnvk

enhancement design jekyll Jobs

*Moved from opensourcedesign/jobs#90 by* @simonv3 There should be a method v…ia [IFTTT](https://ifttt.com) using an "RSS to Twitter recipe" We should automate this to do multiple RSS feeds: - [x] https://opensourcedesign.net/articles/feed.xml - [ ] https://opensourcedesign.net/jobs/feed.xml - [x] https://opensourcedesign.net/events/feed.xml - [ ] https://opensourcedesign.net/resources/feed.xml Additionally, we should add all of these RSS feeds in the `<meta>` tags of the global site templates so as to be semantic and robust. @jancborchardt do you know who has access to the IFTTT account?

github.com/opensourcedesign/opensourcedesign.github.io

Move content of jobs repo to this repo.

opened 03:05PM - 21 Mar 17 UTC

simonv3

servers

To make life easier, does it make sense to move the contents of the /jobs/ repo …to this repository? Why are we keeping it all separate? I feel like it just introduces a lot of complexities that we could easily avoid. Benefits to moving things here: * One site to rule them all * Can switch to using netlify, which actually lets us use a bunch more things as far as gems goes in jekyll, and also is easy to use letsencrypt, and would let use use test and staging branches (:O) * Clear where to file issues for a website thing * Don't have to do weird things to keep the CSS and layouts the same across pages. Down sides: * everything is in one repository I think the benefits outweigh the downsides, just for sake of simplicity and cost of maintenance. Thoughts?

github.com/opensourcedesign/opensourcedesign.github.io

jobs/css/bootstrap.min.css values conflict with css/main.css

opened 06:53AM - 02 Apr 17 UTC

evalica

bug CSS

The job form uses a full bootstrap.min.css that has different defaults than main….css. Some example: - .navbar-nav>li>a: padding from 20px to 15px - .navbar-nav>li>a: font-size from 16px to 14px - etc. This is visible here for example: - Job Form nav: <img width="500" alt="jobform" src="https://cloud.githubusercontent.com/assets/629552/24585053/cc16fa8e-1789-11e7-95f5-ee0fcbbb65ef.png"> - Main nav: <img width="500" alt="main" src="https://cloud.githubusercontent.com/assets/629552/24585057/d957dd26-1789-11e7-87ee-0ef541b75e8d.png"> I'm sure other values also conflict. Solutions: 1. see if jobs/css/bootstrap.min.css can be removed or what it brings in addition. those values can be added in main.css 2. use the same Bootstrap values in jobs/css/bootstrap.min.css as main.css

github.com/opensourcedesign/opensourcedesign.github.io

Make non-markdown formatted URLs auto link-ify

opened 10:07AM - 21 Apr 17 UTC

bnvk

enhancement JS design jekyll Jobs

As highlighted in opensourcedesign/jobs#204 there are many cases where people su…bmit content (especially Jobs) with URLs in non-markdown format. These should be automatically turned into links across the site. - Using a Javascript plugin - Using a Jekyll plugin (not sure if Github Pages supports this) - Using a bot that crawls repos / that uses a webhook to look for these

github.com/opensourcedesign/opensourcedesign.github.io

Conditional form fields: Only show payment amount information if "we can pay" is choosen

opened 10:47AM - 21 Apr 17 UTC

jdittrich

design Jobs

As transferred from https://github.com/opensourcedesign/jobs/issues/200 **Sto…ry:** I want to create a [job via the form](http://opensourcedesign.net/jobs/job-form/). I don't want to be distracted by fields I don't need, for example the " How much can you pay? (optional)" in case I chose "I can’t pay" before. **Solution:** Only show payment information if "we can pay" is chosen.

github.com/opensourcedesign/opensourcedesign.github.io

It should be possible to interact/comment on each job

opened 11:25AM - 21 Apr 17 UTC

jancborchardt

enhancement design Jobs

Some big problems with the job board at the moment are: - it’s very static, d…iscussion is difficult to start - you don’t know the state of it, if it’s taken already - we don’t know if it’s done As far as I know it’s possible to embed Discourse thread replies in a website. We could have a category in the Discourse called »Jobs« (you can’t create posts but will be led to the [job submission form](http://opensourcedesign.net/jobs/job-form/)), and one thread per job. Then on every job there’s the discussion thread below. @erlend-sh could you point us how to do that maybe? :) We do have to require that the people have to register at Discourse though and be subscribed to the issue. But maybe that can be automated and will lead to growth. cc @jdittrich @simonv3 @belenbarrospena @janushead @guiguru @HeikoTietze @bnvk @evalica

github.com/opensourcedesign/opensourcedesign.github.io

Preview <> Jobs Board, Changes after Merge

opened 11:55AM - 21 Apr 17 UTC

HeikoTietze

design content Jobs

In https://github.com/opensourcedesign/jobs/pull/202 @jdittrich made some change…s and me too later. Reason was basically that my lists starting with * were not recognized as such. But in particular I messed up later with links like `<a href="">Foo</a>` that are shown as expected in the github preview but not when the job is posted on the board. After merging it I've seen the problem but being not able to fix it. My try to change the file https://github.com/opensourcedesign/jobs/commit/62c25327909f96d98e591c9a4d7e9e39370739fb directly failed, likely because of missing access right, but that's a guess. In the end I have no idea what happens to the job since the text is kind of scrambled on the board. It starts with pieces from the end, has varying fonts, and the links are not interactive. So besides the failed experiments to solve it myself the post needs some rework. *Originally opened at https://github.com/opensourcedesign/jobs/issues/208*

github.com/opensourcedesign/opensourcedesign.github.io

Branching to specific forms for Hiring, specific Tasks, general interest

opened 05:07PM - 22 Apr 17 UTC

jdittrich

enhancement new page content Jobs waiting on reviewers

We currently have only "Jobs". When @jancborchardt, @HeikoTietze and me tried t…o come up with a better text for the Jobs form, we noted that it is not easy, partly because there are different requirements for * Showing general openness to design contributors (e.g. No payment, no definition of done, emphasis on the feeling in the community) * Hiring and paying people to work part/fulltime at your org (e.g. Payment, hours and employment info relevant, possibly no definition of done (if employed)) * Having a specific task to be done at your projects (Task definition, trust, mode of decision for solutions very relevant) **Possible Solution:** We should have different forms so we can ask for meaningful information.

github.com/opensourcedesign/opensourcedesign.github.io

Line break in YAML-MD

opened 08:05PM - 09 May 17 UTC

Crissov

Jobs

There seems to be something gone wrong in https://github.com/opensourcedesign/jo…bs/pull/214: The two URL entries in `how_to_apply` are separated by `\r\n` which does not seem to translate well, see the [generated page](http://opensourcedesign.net/jobs/jobs/2017-05-09-design-new-emojis). Also, the email address inside angle brackets has been stripped. ```` how_to_apply: - 'Christoph Päper: <emoji@crissov.de>, Github @crissov or Twitter @informoji' - "https://github.com/EmojiTwo/emojitwo/issues/\r\nhttps://github.com/EmojiTwo/emojitwo/blob/master/CONTRIBUTING.md" ```` > **How to apply:** Christoph Päper: , Github @crissov or Twitter @informojihttps://github.com/EmojiTwo/emojitwo/issues/ > https://github.com/EmojiTwo/emojitwo/blob/master/CONTRIBUTING.md

github.com/opensourcedesign/opensourcedesign.github.io

Job Board Redesign

opened 03:20PM - 16 Oct 17 UTC

elioqoshi

enhancement design Jobs

Hey folks, I sat down today with @bnvk and worked on redesigning the job boar…d. This is what we have right now: ![5](https://user-images.githubusercontent.com/5436686/31619567-31b269ae-b295-11e7-8371-a575b01d7403.png) - added Tags depending on the type of job listed - changed the header color to the blue we use on the website to see how that would look like without black everywhere - added PAID and GRATIS filters - added status tags - added post a job button What do you think of the changes? P.S: Source file here: https://github.com/opensourcedesign/organization/blob/master/specifications/Job%20Board%20Redesign%20v5.svg You need the Montserrat Fonts.

github.com/opensourcedesign/opensourcedesign.github.io

Icons for our Job Board

opened 04:50PM - 04 Nov 17 UTC

simonv3

enhancement design content Jobs good first issue

As recommended in #140 it'd be great if we could get some icons for specific job…s that people can choose from. Suggested categories: * Mobile App * Website * Hardware * Desktop App We _could_ use something like font awesome in the mean time, but if we want to release our own icon set this might be a neat place to start.

mantas · September 2, 2021, 7:07pm

I thought it would be good to add another item in this list - slack notification about new job posting. What do you think?

I can contribute by providing github action, but slack app needed to be created if there is none yet.

Topic		Replies	Views
Improving OSD's Job Page Open Source Design meta	11	1055	April 19, 2021
What's up with Job Postings? Open Source Design meta	23	1551	March 19, 2021
Job posting timing? Open Source Design meta	1	689	March 27, 2019
OpenSourceDesign Jobs process Communication and collaboration	6	995	August 21, 2017
Improve the text on our jobs page Design Lounge	0	508	February 14, 2021

Related topics