opensourcedesign / opensourcedesign.github.io Goto Github PK

https://fortawesome.github.io/Font-Awesome/icons/ because, icons 😁

As per @evalica comment in opensourcedesign/jobs#91 she asks:

We need filters for active posts, payed/free and specialization required.

Yes. These are the two most needed ones. As I suggested, 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!

The padding and margins on our articles is well, absent, and I think we need to fix that up.

Title just shows Open Source Design. It should probably show the name of the article or event being viewed as well.

As transferred from opensourcedesign/jobs#200

Story: I want to create a job via the 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.

Currently, our About page outlines the things we hope to achieve with OSD. I really like that it is not a manifesto but more of a list of concrete actions or resources

Given the nature of our About page, what if we made each item link to the thing we are working on achieve? Example:

"a job board for designers to find open source projects"

instead becomes

"a job board for designers to find open source projects"

This way, a simple reading over our goals also provides examples of our progress / how to participate in said goal 😄

As per the goal of making it easy for designers who are not comfortable using GitHub to participate in OSD, we should make a nice web form so that people can "Add An Event" without having to create a Github account.

It looks like the notes plugin page is requiring a js file that doesn't exist.

- ./_site/slideshows/free-and-usable/plugin/notes/notes.html
  *  internal script ../../plugin/markdown/marked.js does not exist (line 175)

As we talked about previously and say in point 1 on our About page, we should aggregate UX blogs of open source projects to spread the existing knowledge.

@danilapellicani did you want to work on that?
@bnvk @simonv3 do you know if there is a way to handle RSS stuff with Jekyll?

In opensourcedesign/jobs#202 @jdittrich made some changes 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 opensourcedesign/jobs@62c2532 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 opensourcedesign/jobs#208

Moved from opensourcedesign/jobs#131 by @evalica

While usually we start having 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>

As per the goal of making it easy for designers who are not comfortable using GitHub to participate in OSD, we should make a nice web form to "Add Design Resource" without having to create a Github account. Ideally, we should have a dropdown menu which sorts resources by category. Currently, the following categories exist:

• Tools
• Material / Content
• Images
• Inspiration
• Icons
• Fonts
• CSS Frameworks
• General Design Reads
• Open Source and Design Reads
• Searching The Creative Commons
• Learn to Code
• Learn to Design
• Other nice stuff

The later half of those could be clarified / condensed a bit perhaps.

Given the architecture of the OSD website and it's use of multiple repos (which I am partly to blame for), it might be fortuitous to move towards making many of the repos (jobs, events, organization, slideshows, etc...) submodules. This is the pattern we use at Qubes OS and can be seen via the .gitmodules files.

I think this would make developing a bit more easy!

It would be nice to have a timeline that lists notable milestones in the history and growth of OSD. I'd see this existing on the /about page or such and containing items like:

• 🕙 One thousandth designer added to organization, June 2017... hope 😄
• 🇸🇬 Presented at FOSSASIA, Mar 2016
• ☯️ Code of Conduct published, Jun 2015
• 🎉 Website is collaboratively created and launched, Apr, 2015
• 🗣️ Open Source Design dev room at FOSDEM, Jan 2015
• 🗣️ Conference talks on open source design and sharing resources, Dec 2013

Getting the type of information and tone right will be crucial- just how broad vs. idiosyncratic do we want to be? My thinking is the following:

• Mention notable and big things that shift or change the community
• Highlights efforts at collaboration and growing "community" more so than individuals
• Give credit where credit is due if someone makes a significant and large contribution

So... I was a bit too "repo happy" early on, thus I think merging things where appropriate would be a good idea at this stage of our growth.

I opened an issue in Organization about combing appropriate repos into that one, which I believe should stay separate for now!

However, upon reviewing, I think the following can (and should be) merged to this repo

• foss-contributors-checklist

Aside from the whole "What is design" and "What is user experience design" existential crisis, it would be sort of nice to get a rough outline of how we define design.

Is it visual? Is it aesthetic? Is it user experience?

Sparked by: http://irclogs.jackgrigg.com/irc.freenode.net/openhatch/2015-05-24#i_3636466

At https://botbot.me/freenode/opensourcedesign/msg/39962749/ I mentioned that each article at http://opensourcedesign.net/articles/ should probably show the name of the author.

Here's how I show the author (me) at http://crimsonfu.github.io/2012/07/01/graphs-help-tell-a-war-story.html for example:

• add author: pdurbin to the front matter at https://raw.githubusercontent.com/crimsonfu/crimsonfu.github.com/master/_posts/2012-07-01-graphs-help-tell-a-war-story.md
• add "pdurbin" to https://github.com/crimsonfu/crimsonfu.github.com/blob/master/_config.yml
• add member page per author to link to: https://github.com/crimsonfu/crimsonfu.github.com/tree/master/members/pdurbin
• set up template: https://github.com/crimsonfu/crimsonfu.github.com/blob/master/_layouts/post.html

Of course there are other ways to do it! :)

The README for opensourcedesign/resources points to http://opensourcedesign.net/resources/, which is broken. Where should it point?

This version is more up front, targeted, and almost a marketing site:

One interesting thing to explore here is to maybe include little facts for each section (300 commits, 299 members, 400 tweets, 13 open jobs, etc)

This version is more functional:

Because, our logo 😀

Moved from opensourcedesign/jobs#90 by @simonv3

There should be a method via IFTTT using an "RSS to Twitter recipe"
We should automate this to do multiple RSS feeds:

• https://opensourcedesign.net/articles/feed.xml
• https://opensourcedesign.net/jobs/feed.xml
• 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?

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?

In homepage, users writing 'clever comments' is a fabulous feature. However, I am not able to see the comment. It links to their user profile instead of the comment. Should we add the comment or, at least, the comment link?

Because, security. Because, privacy are good things 😃

I've done this before using CloudFlare + Github page hosted sites. It's relatively easy and i'll look into doing it when I have a few free minutes!

Update: My thinking has changed a bit. FUCK CLOUDFLARE. Me (and every other Tor user) are suffering death by a thousand CAPTCHA's daily because we believe in the right for a free and non-surveiled internet. Thus, OSD seriously needs to consider an alternate approach! Sorry for suggesting CloudFlare and now 180'ing

The results from the survey are in!

TL;DR The new OSD Logo:

osd-responses.csv (edited to remove identifying details)

First Round:

And distributing the votes of non-winning options:

Which makes 7 by @Xaviju a pretty good winner.

I want to address some of the concerns raised in the survey anonymously:

Holy crap that's a lot of choices.

We've got a pretty awesome community :)

Guys, when you let people choose a logo out of a selection you should at least bring them on the same size or at best in one bigger, one smaller one. Otherwise the comparison might easily be misleading.

This is a valid complaint, but judging by how strapped for time the people working on this already are, I think it's an unfair one. I don't think the logos were that different is size on the logos.html page, people could easily click through to see the original size in #18, and I also trust people to make that judgement for themselves. Though resizing help will always be appreciated in the future :)

Interim logo

This depends on whether a group of people step forward and want to work on that. Be the change you want to see. I've reached out to the person in the survey who offered their help, and I'm sure we'll post more updates on that soon.

Current logo preference.

Unfortunately we can't do that. The current logo is a trademark of the Open Source organization. It's not freely available for use.

CC @jancborchardt @GarthDB @una @Xaviju @gillisig @plastelina @MariekevC

Moved from opensourcedesign/jobs#128 by @Miserlou

Currently one has to scroll 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.

In the spirit on making it easier and clearer to contribute and engage with OSD and like our add a job form we should have a form for FOSS projects who are open to having designers join their community.

Ideally, there should be some criteria this form. Please chime in with ideas 😄

For (code) organizational purposes, we should move the code in this repo into either this repo or the jobs repo.

As highlighted in opensourcedesign/jobs#204 there are many cases where people submit 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

Leading up to doing some wireframing leading to a visual style, here's a potential outline of some requirements for the website:

http://piratepad.net/opensourcedesign-website-requirements

Also in Chrome 48, the same thing.

In pull req #11 I have introduced the idea of an activity feed. However, currently it's just the activity feed of this one repo- ideally it will encompass all repos and do some sort of intelligent "filtering" to only show highly understandable items.

The font-size of "Chat With Us" and "Code of Conduct" doesn't match with "opensourcedesign" and "opensrcdesign" in the footer.
Also, the icon is not displayed along with "Chat With Us" and "Code of Conduct".

Currently, the title refreshes to the same page. There should be a link to the open source project which is posting a job. @opensourcedesign/people

Some big problems with the job board at the moment are:

• it’s very static, discussion 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), 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

http://opensourcedesign.net/2015/07/10/this-month-in-open-source-design refers to a blog post by Jan D.:

• http://opensourcedesign.net/2015/05/23/TextbasedToolsForDesigners.html

That's no longer found. I found it captured in the Wayback Machine and re-posted at:

• Why designers need tools beyond text and code – Medium
  

Please consider an edit to /2015/07/10/this-month-in-open-source-design to refer to the Medium address for the post.

Related: https://github.com/opensourcedesign/opensourcedesign.github.io/blob/master/_posts/2015-05-24-TextbasedToolsForDesigners.markdown

As per the goal of making it easy for designers who are not comfortable using GitHub to participate in OSD, as well as #70 goal, we should make a nice web form (using Staticman) like our job form so that people can "Join OSD / Add Your Self" without having to create a Github account.

Hi open source design. I am new to your community. I want to help in small ways but an unsure of best way. I looked at the contributing file but seems not yet done. I know got and github a little but dont know how you suggest developing your site with all the different repos

I think having a page on facebook would be useful to convey news about Open Source Design and help invite more people to Open Source Design.
What do all of you think?

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:

• Main nav:

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

We could have a nice list of the supporters on the frontpage by using this website banner:
https://github.com/OpenCollective/OpenCollective/wiki/Website-banner

Similarly also with the Github banner, but not sure which repo we should add it to (I guess /organization?)
https://github.com/OpenCollective/OpenCollective/wiki/Github-banner

Edit for update 2:

Hey all!

So, that's enough logo options I think. As a group of volunteers, I don't think anyone has a significant amount of time to take a lead on logo design, or taking the time to appoint someone to do so. After talking with some people on the IRC channel I put up a survey asking people to indicate their favorite logo.

You can take the survey here.

You can enter your favorite choice and your second favorite choice. This will be a simplified single transferable vote survey. That means that if your first choice comes last in the first round (so it gets eliminated), your second choice vote will be counted as well, etc until there's a clear winner. The results are stored anonymously, so I'll publish them once they're done (unless people have a major objection?).

If you have a better idea, please tell us. There's a special comment box. It can be anonymous, but I'd prefer for it to be actionable, and that you are willing to take the lead on this. Your idea might be great and the best way to do it, but if no one acts on it than it won't happen. (See: this thread).

I'm going to close this topic to prevent more options from appearing. If you think this is wrong, ping me on IRC or on twitter (@simonv3 on both), or any of the other people who can open it again. Also you can open another issue for discussion purposes specifically.

(The reason this took so long is because I couldn't find a suitable open source survey tool. If you want to help me build this one out more, come check it out ;))

EDIT for update:

Hey all!

Thanks so much for contributing all of your great thoughts, ideas, logos, sketches, etc. This is super awesome, and exactly what I hope for this community. It's great to see you all pitch in, and I'm super appreciative of all of the work you've been doing on this.

However, to prevent this from going on and on with new ideas and concepts, and never end up with a logo, I'm going to suggest that we all agree that a week from today Wednesday the 17th (this gives people a weekend to pitch in ideas as well) we close this topic. If by the end of this week we don't have a clear choice of favorite, we can put things to a vote.

I want everyone's opinions on our logo. Why a particular concept is great, why it fails, etc. I want to make sure that everyone's voice gets a chance to be heard. But I also want a positive conclusion to this conversation.

Let me know if you think this is unfair.

continued from before

Some concepts so far:

1. @MariekevC
2. @jdittrich
3. @plastelina

@plastelina. The logo you referenced is semi-off limits. It's the design open logo, for some more background look here: opensourcedesign/jobs#26.

Link is here: opensourcedesign/organization#29

It currently looks like this and doesn't follow the overall theme the website uses.

It should instead look like this, just like a regular post.

Required class change is : post col-md-8 col-md-offset-2
Fix: layout: page => layout: post

This week I started creating a bunch of repos to power the opensourcedesign.net website. My plan was to use Jekyll to generate the site and various JS libs and Bootsrap on top of that.

I am keenly aware of the pain points @una brings up in her great blog post The Intimidation Barrier and how this affects designers looking to contribute to FOSS projects. Una highlights the current 15 steps it takes to add a simple article to the designopen.org website.

I've crossed out the steps I was hoping to remove with my process

1. Stumble upon this [on a public website] page
2. Open the link to Github
3. Have a Github account
4. Know about Github Contribution workflow
5. Fork the Repo
6. Open terminal
7. Know that one needs to install dependancies
8. Know how to install dependancies
9. Know about how Jekyll works
10. Run Jekyll server
11. Write in markdown or with HTML tags
12. Know about the config file and how to add authors
13. Add changes
14. Commit Changes
15. Submit pull request

How to properly minimize designer intimidation is the tricky part. My approach would remove 6 of 15 steps, as they can simply use the Github web browser editor to write in the Markdown content.

Methinks, the trick with this sort of thing is that it must balance:

• Minimizing complex steps for designers
• Not restricting developers to use tools they don't know / prefer
• Strike the right balance of "openness" as both an organization & codebase
• Keep things small and easy to interact with in a modular way (small different repos)

There's numerous different programming languages, frameworks, and system architectures. I don't know the most ideal approach, but Jeykll (which the @DesignOpen folks are using) feels like a step in the right direction.

I'd argue that designers who want to meaningfully contribute to open source need to learn basic Github flows in order to effectively contribute to projects, Also, a simple tutorial video walking wary designers through the Github workflow and this whole process would be very helpful and achievable, I think!

I'm curious what others think about this approach!

This was reported on IRC by @Xaviju who experienced an issue upon using the nice submission form

[{"code":"INVALID_FIELDS","data":["org_url","rate"]}]

As per @LibreAnne comment in #66 and @evalica bringing up fixing the Job Board board in opensourcedesign/jobs#91

I think we should only use this repo for site design, UI / UX improvements. Whereas the more specific repo's (jobs, events, etc...) should be used in a more task + discussion focused way (e.g. feedback about design jobs like opensourcedesign/jobs#116 as this approach has these advantages:

• Makes "subscribing" simple & granular - for conversation / watching / participatory purposes
• Github as a mailing list - we're effectively using the OSD repos as a mailing list / Slack channels.

Does that sound ok to everyone? If yes, we should add this to the README and Contributing pages and use this issue to track that effot. I think this will help with "contributing" feeling @LibreAnne mentioned.

opensourcedesign/slick#2 stated we should:

A shared vocabulary of terms for all designers/devs/content strategists/etc. to refer to

Across the spectrum: designers ◀️ ▶️ project managers ◀️ ▶️ developers various terms are used which can often lead to confusion and misunderstandings. Here's an example I can think of:

Templates

• Designer - a Photoshop, Illustrator, or SVG file used to to base a new design off
• Project Manager - a Wordpress or Jekyll theme
• Developer - the collection of files that render the view of webpage

Thus, making a glossary of design terms could prove helpful towards aiding collaboration between the spectrum!

At the Berlin meetup, @HeikoTietze brought up that a »Deadline« field would be useful for the job postings. This might be because there’s a release upcoming, but also simply for us to automatically expire old job postings.

The idea we had at the meetup was to simply replace the »Tags« field which kind of duplicates the »Job role / category« anyway with a »Deadline« section:

<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>

What do you think @bnvk @simonv3 @belenbarrospena @evalica?