Slide 1
Slide 1 text
How to find "Good First Issues"
How to find "Good First Issues"
part II
part II
Quipper Limited
at Roppongi.js#5
@ohbarye
Slide 2
Slide 2 text
If you:
If you:
want to contribute OSS
are struggling to nd a repository or an issue to
contribute
(would rather you preferred major OSS)
This talk would be helpful to you.
Slide 3
Slide 3 text
Agenda
Agenda
1. Story so far
2. Current status
3. What's next?
Slide 4
Slide 4 text
Story so far
Story so far
Slide 5
Slide 5 text
Problem to solve is...
Problem to solve is...
Slide 6
Slide 6 text
Contribution Accessibility
Contribution Accessibility
Slide 7
Slide 7 text
Ideal world
Ideal world
Slide 8
Slide 8 text
Story so far
Story so far
At the previous Roppongi.js. I've shared a simple script
to fetch "good rst issues" from GitHub.
Slide 9
Slide 9 text
what is "good first issue"?
what is "good first issue"?
Slide 10
Slide 10 text
Apply the "help wanted" and "good rst issue" labels
to issues in your repository to highlight opportunities
for people to contribute to your project.
https://help.github.com/articles/helping-new-
contributors- nd-your-project-with-labels/
Slide 11
Slide 11 text
Previous output
Previous output
I could make Good rst issue list. But not cool. I felt I
should implement GUI for better usability.
Slide 12
Slide 12 text
Response
Response
Slide 13
Slide 13 text
Current status
Current status
Slide 14
Slide 14 text
No content
Slide 15
Slide 15 text
Features
Features
List up repos and issues ltered by language
Single Page Application built with React
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
What I did
What I did
Implemented frontend and backend
React, Material UI, TypeScript
Node.js, Express, GraphQL
Slide 18
Slide 18 text
monorepo
monorepo
Use Docker Compose on development
Deployed to Heroku and Netlify respectively
I wrote articles on how to deploy sub-directory
https://ohbarye.hatenablog.jp/archive/category/mon
Slide 19
Slide 19 text
Interested?
Interested?
See:
App
Implementation
https://goo .netlify.com/
https://github.com/ohbarye/goo
Slide 20
Slide 20 text
What's next?
What's next?
Slide 21
Slide 21 text
Current issues
Current issues
The current goo has 2 major issues.
Performance
It queries against GitHub for every request
No cache
Rate limit
GitHub's constraint: 5,000 requests/day
Slide 22
Slide 22 text
Solution
Solution
Next.js, SSR, PWA, server side cache
They come from
Aim to get perfect score of Lighthouse
https://github.com/hanford/trends
Slide 23
Slide 23 text
No content
Slide 24
Slide 24 text
Let's find your "good first issues"
Let's find your "good first issues"
with "goofi" and contribute!
with "goofi" and contribute!
Go https://goo .netlify.com/
Slide 25
Slide 25 text
Who?
Who?
@ohbarye
Web Developer / Engineering Manager
Working for
http://ohbarye.me/
Quipper