Warm Ashes
Warm Ashes
@jdittrich thank you for re-opening (and clarifying) the case- the wording of this title makes more sense than the other as well. One approach is to have two fields (like...
w00t w00t, great @simonv3 great step and progress 👍 For some reason I had to update the ID in your link to Discourse from 328 to 353, not sure why....
> we can only do it for jobs I think, not for, say, articles Why is this? We can (and should / am working towards) have multiple RSS feeds.
Yah, that sounds like a pretty good idea to me... but maybe some criteria like: 1. must be member of GH Org 2. must on a certain "Website" team or...
Also, using **this** repo's issue tracker, when it comes to design / site improvements to a given repo, I advocate that we use labels for each repo + skill based...
@m1guelpf no and sort of. > So the idea is to build a list of people in OSD using the GitHub API No. What I'm thinking does not require /...
With #137 @simonv3 got a first pass of this implemented. Now we just need to test it a bit with users submitting data 😄
Great job @elioqoshi 👍 > requires now means to filter the list by status tags and paid/gratis flag. Yes @HeikoTietze this is well known and tracked in #70 it's a...
> It’s very text-heavy, and as a design job board I think some kind of visual would be nice. @bnvk I know I mentioned it to you and you weren’t...
Useing a favicon has the following requirements / limitations: 1. That they list a website, otherwise we end up with Github or such 2. We create some parser to find...