1.0.0 (v2!)

[MikeMcQuaid]

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:

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

:ship: Date: June/July 2017

---

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

[BenJam]

Up with this sort of thing.

It would be good to get a better view on what this needs form Libraries.io. We've been thinking about building this type of functionality into Libraries.io but it's just as valid for us to do so through another platform using our data/service.

Feel free to hammer a review of our API and ticket any further requirements so we can scope and include in our roadmap.

[MikeMcQuaid]

It would be good to get a better view on what this needs form Libraries.io. We've been thinking about building this type of functionality into Libraries.io but it's just as valid for us to do so through another platform using our data/service.

I think what would be awesome is basically (and this may already exist): tell me the dependencies of all the repos I have access to/are mine/are part of this github organisation and higher rank the ones that are duplicated across multiple. Basically an easy way for an individual or company to figure out what projects they are already using and which ones are most in need of help so they can direct contributions accordingly.

[andrew]

@MikeMcQuaid most of that already exists as part of Libraries.io 🎉

[BenJam]

It's also key part of the workflow for dependencyci.com — the commercial service that we hope can sustain libraries.io.

[MikeMcQuaid]

@andrew @BenJam Hooray! Totally happy to point to the commercial service where it solves these type of problems 👍

[bkeepers]

• [ ] Get the site deployed and hosted on Heroku

Do you imagine this will be publicly available at this point? Mostly just curious because once this project is on a webpage and not just on GitHub, it will be "launched" and it'll start to get attention of non-developer types.

[BenJam]

it'll start to get attention of non-developer types.

cough I'm not a developer cough ;)

[bkeepers]

cough I'm not a developer cough ;)

@BenJam Yes you are according to the definition in #16:

Audience: "developers", meaning anyone who has skills that are relevant to software development, that might be looking for ways to use those skills on an open source project.

Your GitHub Profile gives you away.

[BenJam]

Fair point.

[MikeMcQuaid]

Do you imagine this will be publicly available at this point? Mostly just curious because once this project is on a webpage and not just on GitHub, it will be "launched" and it'll start to get attention of non-developer types.

@bkeepers I have no strong opinions either way. Even if it's hosted on Heroku but not linked to anywhere and robots.txtd out of existence that may be sufficient.

[nayafia]

If this is meant to be a chronological timeline I'd suggest keeping it robots.txtd until all the other things are done.

[m1guelpf]

Where can I find a live preview of this?

[nayafia]

@m1guelpf you can view locally by following these instructions: https://github.com/ossfriday/ossfriday#development

Or view here: https://open-source-friday.githubapp.com/

[MikeMcQuaid]

🚢d at https://opensourcefriday.com 🎉

[MikeMcQuaid]

Thank you @andrew, @Charlotteis, @maxcell, @benpolinsky and @stevelacy for helping us build this project!

[stephenlacy]

Not sure if an asset file was not parsed correctly when the prod vs dev build was published

https://opensource.guide/how-to-contribute/#finding-a-project-to-contribute-to

[MikeMcQuaid]

@stevelacy Weird, I'm not seeing that in Safari. Might need a refresh?

[stephenlacy]

I did a cache clean refresh (I always have cache off in chrome), still get the error.

Edit: firefox works perfectly