Now we can start translation meta project on Transifex or similar platform such as translatewiki.net.

You can see instructions at https://docs.transifex.com/integrations/rails/ for transifex.

There are many volunteers who may help us to localize ossfriday site.

@bkeepers, @MikeMcQuaid and I talked this week about having people sign up for an email series, as a way to measure program adoption and success. (Mike pointed out that with ex. a calendar invite, we won't know whether people are actually participating, nor who they are.)

We were thinking of starting with 8 weekly emails that you'd receive when you sign up, containing helpful tips around contributing to open source.

I started drafting ideas for an email campaign here: https://docs.google.com/a/github.com/document/d/1KK1ylt4w_pbN72UfnbUUepBzGz46FifhVEMMY6lfkz8/edit?usp=sharing

The downside, as you can see, is someone doesn't even learn how to contribute until several weeks in. Which is probably bad.

So, we have to make some assumptions here:

• People are experienced contributors, so we should show them interesting tips/quotes/anecdotes to keep them motivated (ex. "Here's how to manage your notifications" or "Did you know...?")
• People are experienced contributors, but aren't contributing during work, so the content is more about how to talk about open source at work, get employers on board, etc.
• People don't know how to contribute, so we should show them little ways to get started and make each week more actionable

I'm leaning towards the first option. I don't think this program is about handholding 100% new contributors, that's why we have the guides. But I don't want to make assumptions.

The downside of the first option also is it's less structured, so we have to make it not feel abrupt when they end after 8 weeks.

@bkeepers @MikeMcQuaid what do you think?

On the profile page here, the company name links to `https://github.com/{company_name}. There are two issues with this:

• All companies don't have a profile on GitHub
• Not every company will have a username which is same as their name.

Getting a 404 telling me that there is no Github pages site when clicking in the description header.

Hello GitHub,

We hope the open source Friday campaign to be useful for everyone.

My plan to improve Open Source Friday in Persian:

• Adding a Persian and open-source font.
• Keep ?locale=** when switch between pages.
• Adding rtl direction and modify CSS styles.
• Adding some words not in locale yml files.

I use here as a share space to work on this subject.

I will inform after any activity at here.

At first, I need permission from administrators.
We can continue? @MikeMcQuaid

Best,
Max Base

The font for the list-items in the Add To Calendar dropdown is "Verdana" - we can change that with some specific selectors:

To fix it, we can add:

.atcb-item-link { font-family: $body-font !important; }

Let me know if y'all want to see a PR 👍

Minimal 🚢 list:

• Login with GitHub (to get weekly reminder emails and track progress)
• Homepage explaining what #ossfriday is and how to get involved
• Dynamic list of issues labeled ossfriday from GitHub
• Documentation for maintainers on how to get involved
• Links to related services and contribution guides/blogposts
• Basic diary functionality for logged in users to say what they did (markdown)
• Social sharing badges
• Meta tags for twitter/facebook shares

These were originally added to ease deployment on Heroku but can easily become out of sync (partial fix in #561).

Instead, it would be preferable to remove node_modules from Git and instead use an additional Heroku build pack to ensure npm install is run before the application is run (e.g. https://stackoverflow.com/a/22850632/5355).

Note if this is done there will need to be some workaround to handle e.g. newer versions of Primer removing CSS rules that are used (e.g. alt-h0).

See #562 for a related PR.

The sorting of my OpenSourceFriday contributions are incorrectly sorted.

See my profile page: https://opensourcefriday.com/users/sumnerevans. Notice that the last two days are in the wrong place.

Filing issues is important too.

When we authorize the user, we're sending the user:email scope.

I expected to get the user's email back if it's public, but for my user I didn't get an email.

/cc @MikeMcQuaid

Re-reading @andrew's issue (#2), he suggests:

Focusing on issues rather than projects - trying to find a project to contribute to and then find something to do on that project is tricky, instead let's get maintainers to label issues that they want to promote to new contributors with ossfriday along with related labels like Your First PR, first-timers-only and help wanted

@MikeMcQuaid any reason we would not want to encourage maintainers to do this? It could be another CTA on the maintainer page.

Pros:

• Helps us track participation
• Helps maintainers flag appropriate issues
• Helps contributors find ways to help

Cons:

• Yet Another Label (as Andrew points out, there are a bunch of others already)
• We've already got a system for tracking participation (OAuth)

I know this got overwhelming for maintainers with Hacktoberfest, but since there's less gamification ("open 4 PRs and get a T-shirt") I don't think there'd be spammy incentives?

We've been brainstorming how to measure participation in Open Source Fridays. Right now, the plan is to have people sign up for a weekly email series.

Seeing as Open Source Fridays is meant to be 52 Pull Requests 😉 I went back to https://24pullrequests.com/ for inspiration. They ask people to "sign up with GitHub", which gives you:

• Quick form to sign up for emails
• Dashboard that tracks how many contributions you've made since signing up

I like the idea of seeing how many contributions you've made; that's a natural motivator. And OAuth app feels more intuitive than email, since it integrates with your GitHub account. It's also something we can build on as the program grows.

I know this isn't a trivial decision, so looking to @MikeMcQuaid @bkeepers for input, as well as @andrew on whether that's been useful for 24PR.

Pedantic i know, but i had something similar on libraries.io:

If you're on macOS and have Homebrew installed to get started just run:

./script/bootstrap
./script/setup
./script/server

results in figaro erroring out on the missing ENV variables. Might be useful to put the section:

You'll need to set at least github_client_id and github_client_secret environment variables. The values can be obtained by registering a new GitHub OAuth application with the Authorization callback URL pointing to your application with /users/auth/github/callback appended.

Ahead of that.

Kicking off a discussion around OSS Friday, a movement, inspired by https://24pullrequests.com, to encourage people to contribute to open source every Friday.

Alternative name: 52 pull requests 🤣

Some of the things that worked well for 24 Pull Request that I'd like replicate:

• opt-in for maintainers - only suggesting projects that maintainers have suggested means we don't send a swarm of extra maintainer work to someone who doesn't want it or can't handle it.
• Wisdom of crowds - if lots of people are doing the same thing at the same time more people will make an effort to join in
• Gamification - a little bit of gamification goes a long way, I'm thinking streaks for having done some kind of contribution every Friday throughout the year
• Automation - many efforts around cultivating open source contributions that require humans tend to fizzle out as the humans involved can't sustain the level of work required to keep it going, 24 Pull Requests pretty much runs itself now which is why it's been so easy to keep it going for 5 years
• Emails - sending out regular reminder emails with suggested contribution content works great to give people a kick to keep them going, optional for people who hate email.

Things I'd like to try:

• Focusing on issues rather than projects - trying to find a project to contribute to and then find something to do on that project is tricky, instead let's get maintainers to label issues that they want to promote to new contributors with ossfriday along with related labels like Your First PR, first-timers-only and help wanted

• not tied to pull requests - there are lots of ways someone can contribute to an open source project that doesn't require opening a PR on GitHub, we should encourage things like documentation, issue triage, stackoverflow answering, support forum helping, event organising, blogging as well as code contributions

I'm planning on getting something basic together (in ruby of course) before 6th January, the first Friday of 2017 and we can iterate from there 🚀

Would love to hear your ideas, thoughts, feedback, contributions, gifs and emoji reactions, Happy Friday 🍻

Is this:

Just place "x" to indicate selection (e.g. "[x]")

• feature
• bug:

Problem

Add to calendar page use UK/London timezone fixed.
It is better to adjust timezone according to a address user lived.

Steps to Reproduce

1. go to user page
2. scroll page to "Set a reminder" section
3. click "Add to Calender"

Related component

Addtocalendar NPM package. https://addtocalendar.com/

I had to type, like, at least 3 commands to get this app running.

This is just a reminder to add a script/bootstrap to make it easier.

Edit: Most of this can be scripted.

I showed the site and talked through some ideas with @amateurhuman and he had some really good feedback.

He said, as a developer, seeing "your business depends on it" as the first headline on the page isn't very inspiring. His thought was "this isn't for me".

• Move business messaging back to its own page
• Keep the homepage really simple with what this thing is and how you can get involved:
  1. contribute to a project
  2. or, improve the onboarding experience of a project you maintainer
  3. or, help your company improve their open source practices/policies/etc.

Thoughts @MikeMcQuaid @nayafia ?

We can have two preferences at least.

1. langauge

2. subscription opt-in/out

Getting 500 error on github oauth callback when trying to sign up.

https://opensourcefriday.com/users/auth/github/callback?browser_session_id=SKIPPED&state=SKIPPED

Currently it only shows the first organization a person's joined which may not be representative of the organizations that they contribute to the most.

Hi there, glad to see your open source Friday guide. It's a topic near to my heart. Wrote about a technique for organizing technical and non-technical contributors that I thought you'd like. Perhaps you can incorporate the BASEDEF idea into your guide.

https://begriffs.com/posts/2016-01-29-making-twenty-percent-time-work.html

Cheers.

I've been working on this for a wee while now and thinking about what makes this different to other projects like e.g. 24 Pull Requests and Hacktoberfest. The thing that's dawned for me is that it's companies/employers encouraging, enabling and supporting open source contributions inside of work hours that are going to make a regular program of contributions like this really succeed. Rather than replicating existing resources like 24 Pull Requests (https://24pullrequests.com) and Libraries.io (https://libraries.io) for finding projects to work on we should link to these resources and make Open Source Fridays primarily an informational program.

As I work for GitHub some of you may ask why I'm doing this and why GitHub cares. Basically, I/we just want more people to contribute more to open source and getting this happening during work hours is going to be more effective for increasing contributions, collaboration and diversity of open source communities. Some of my team at GitHub (@bkeepers, @nayafia, @kytrinyx) will be working on this with me and I'd love you to join us. To be clear, though, we don't see this program as being exclusive to GitHub: contributions will happen on GitLab, BitBucket, SourceForge and friends and that's great too.

Here's our rough roadmap we're thinking so far:

• Get the existing https://github.com/ossfriday/ossfriday repository running on a machine and document how others can do so #8
• Add a static page explaining the what the program is and how it works with stakeholder pages for projects, contributors and companies stating how and why they can benefit from participating #11
• Speak with @andrew privately about project direction
• Add a non-shit design #13 (which is not only non-shit but actually good)
• Publicly document our planned, loose roadmap so others can get involved and know what we're doing and why #21
• Get the site deployed and hosted on Heroku
• Edit/improve company-centric view/pages
• Edit/improve maintainer-centric view/pages
• Edit/improve contributor-centric view/pages
• Figure out how to suggest and find projects e.g. libraries.io, project gem file, GitHub showcase, etc.
• Get named maintainers on board with the program
• Get named companies on board with the program and doing it internally and provide soundbites for that on the site
• Promote the program through blog/Twitter/social media

🚢 Date: June/July 2017

Have any thoughts? Want to help? Think I'm totally wrong? Chime in here!

On my Open Source Friday profile, I have multiple companies @-mentioned.

It shows up as only one link to https://github.com/SummationTech%20@kenzanlabs which is not a valid link. On my GitHub.com profile, these two @-mentions show up as separate links.

Relevant Details

Page: my profile page https://opensourcefriday.com/users/sumnerevans

What I expected to see: two links, one to each company @-mentioned, just like on GitHub.com.

What I saw instead: one link to an invalid page.

The homepage has this footer:

After clicking to the other pages, I kind of expected to see the same footer again. But links to other pages are only in the nav.

Does it make sense to add the footer to the other two audience pages, too?

cc @MikeMcQuaid

Context: https://github.com/github/github/issues/174690

After signing up and clicking on Add to Calendar -> Google Calendar (under Set a reminder), getting the following error -

When I was on the user page, I saw the business and maintainer navigation and wondered where to go to find the contributor page.

It wasn't until later that I realized that the contributor page is on the homepage.

I don't know whether this is a real problem, or just me being confused or dense, but I thought I'd mention it in case anyone has thoughts about mitigating potential confusion.

Howdy! I really love this initiative and wanted to see if I could help out in any way! I was taking a look through your CONTRIBUTING.md section on setup and noticed you link to "Getting Started" on the README.md but it is a dead link because there is no section.

If you don't mind, I would love to help out! I have a general idea of how to do it just given that I had to figure it out myself just a bit ago.

0. (This might not be something everyone knows but could be helpful) Be sure to have a Ruby Version Manager even if it isn't RVM.
1. Get the working version of Ruby installed (2.4.0) (I believe)
   a. Switch over to the version of ruby
2. Install the necessary gems: bundle install
3. Make sure to have your ossfriday Postgres database
4. Migrations: rails db:migrate
5. Spin up the server: rails s or rails server

I know in the file, it talks about in-depth and I would love any feedback about what we should/shouldn't include. However, I think it would be great to involve this now versus taking it on later and forgetting and excluding assistance from the community 😄

on running the command "./script/setup". The following error trace is printed in the console

== Preparing database ==
rails aborted!
NoMethodError: undefined method `reject' for #<String:0x007fa27e910f00>
/Users/bimarian/projects/github/ossfriday/config/application.rb:14:in `<module:Ossfriday>'
/Users/bimarian/projects/github/ossfriday/config/application.rb:13:in `<top (required)>'
/Users/bimarian/projects/github/ossfriday/Rakefile:4:in `require_relative'
/Users/bimarian/projects/github/ossfriday/Rakefile:4:in `<top (required)>'
/Users/bimarian/projects/github/ossfriday/bin/rails:9:in `require'
/Users/bimarian/projects/github/ossfriday/bin/rails:9:in `<top (required)>'
/Users/bimarian/projects/github/ossfriday/bin/spring:14:in `<top (required)>'
bin/rails:3:in `load'
bin/rails:3:in `<main>'
(See full trace by running task with --trace)

== Command ["bin/rails db:setup"] failed ==

Help me to resolve the issue

Thanks & regards
Bhanu

Just signed up with github and noticed a missing space in the header for my friday contribution stats:

I can't seem to find any documentation on what this software does and what the long term goals are.

Adding such to the readme would most definately increase engagement.

The project (Your First PR) has been inactive for a while now, so perhaps it would be better to remove it?

Their Tweet Regarding Activity:

Filing that we'll need to do a bit of work in order to merge #778

Essentially, that PR bumps the version of Rubocop, but the new rubocop gem then detects some issues with some of our code. The test failure in that PR has more details, but this should be an extremely teeny amount of work!

Why should you be restricted to helping on fridays only? Why not everyday! ;)

Hello!

I work at Skylight. We are launching a program to offer free Skylight accounts to open source apps (similar to Github and Travis), so I am reaching out to see if this is something you would be interested in.

If you’re not already familiar with Skylight, it is a smart profiler for Rails apps. Skylight makes it easy to pinpoint performance issues in Rails applications.

We work on a lot of open source projects ourselves, and in our experience it can be pretty hard to get contributors to work on application performance issues. Few contributors consider working on performance problems, and the ones that might be interested may not even know where to start. By making performance information more accessible, we hope to inspire potential contributors to tackle slow parts of your app, and have a good way to see if their contributions helped.

Integrating Skylight to a Rails application is very easy. All you have to do is add the gem to your Gemfile and set an environment variable with your authentication token. (We are happy to send a pull request.) If you’re interested in setting this up or if you have any questions, you can reach us here or at [email protected].

We'd also love to feature you on our website as one of the first open source organizations using Skylight. We hope you’ll join us in helping to make performance an accessible way to contribute to an open source project!

This will allow us to do a few things:

• Use newly refactored container styles (so there are less flexbox bugs)
• Use new gutter styles

I've tried to create a PR to fix it, but I didn't find where the content was.

The appsec team has determined that CVE-2015-9284 is high risk and this repository is vulnerable. Please remediate this issue by updating your omniauth package.

More information is provided in the master tracking issue 👇 Please feel free to drop a comment there if you need assistance.

Building off of #40, a few more things to build out the user page:

• How do people sign up for emails? Do we automatically add them to Mailchimp when they sign in, or should they manually opt in on the dashboard? (Side note: I'm not totally convinced we should still do emails, let's chat when you're back @MikeMcQuaid)

• On the homepage, "Sign up with GitHub" should be a front and center button in at least two places:

and

For the maintainer page, I'd similarly put it: 1) on the hero and 2) below the Get ready for Open Source Friday heading/subtext.

It would be a good thing accessibility-wise for those with vestibular disorders https://www.deque.com/blog/current-design-trends-affect-web-accessibility/

is it possible?

I've got no knowledge of ruby/rails/devise :/

From my profile while logged in:

If user is current, this should say in your last 1,000 events. If logged out, their.

Or just edit to neutral copy, like in the last 1,000 events 😉

Hey y'all, apologies for weird format but figured this was the best way to do it.

@stephbwills @yourfrienderin We did a first pass at copy on https://open-source-friday.githubapp.com/. Can you review?

Comments on here are fine, or you can start a PR.

NOTE:

• CTAs will change (we'll ask ppl to sign up for emails or connect GitHub acct)
• Images of the Guides are mostly placeholders for now
• We're gonna make the homepage point to contributors, not companies (#33), so think of the pages as standalone

(For others following along: meet @stephbwills, who does brand editorial, and @yourfrienderin, who does business marketing, at GitHub! I've asked them to provide feedback as they're both editorial super-:star:s.)

Hello..

I have tried to visit the OssFriday Website and return 404 error from GitHub Pages..

I would like somehow to see the project and participate.

Are there any predictions of when the site might be online?

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "orm_adapter":
  In Gemfile:
    devise was resolved to 4.5.0, which depends on
      orm_adapter (~> 0.1)

Could not find gem 'orm_adapter (~> 0.1)', which is required by gem 'devise', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

My thoughts so far:

• Contributors: sign up for email list
• Maintainers: improve their project
• Corporate decision makers: encourage employees to contribute

How do we track the success of the 2nd two CTAs? Do we need to?

For maintainers, I could see us making a separate email list, but I also don't want to get too bogged down in lists (especially as we don't really have capacity to maintain them).

For corporate, we could measure by number of official partnerships, or if we offer special content (ex. policy kit), number of downloads.

I'm also inclined to just focus on messaging and reaching contributors to start, as that seems to be the main point of this program.

@MikeMcQuaid @bkeepers

createuser: error: could not connect to database postgres: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
##[error]Process completed with exit code 1.

Please check it.

This is more of a UI alignment nitpick.
Currently, the text has default alignment with the top, while the right side navbar is centered.

Suggestion: add align-items: center to the h1 parent div, and remove the 4px top margin from the h1 to result in: