Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🥅 Initiative: Grey Software Report Card #53

Open
ArsalaBangash opened this issue Oct 18, 2020 · 0 comments
Open

🥅 Initiative: Grey Software Report Card #53

ArsalaBangash opened this issue Oct 18, 2020 · 0 comments
Labels
Domain: User Experience This issue pertains to a developer's emotions and attitudes when building Grey Software. Role: Maintainer Manages the repository by organizing issues, milestones, projects and new contributors. Role: Product Owner Uses PM tools to execute the vision they co-create with the Designers, Engineers, and Users.

Comments

@ArsalaBangash
Copy link
Member

Motivation 🏁

Students need to show employers real-world software experience in order to stand
out.

A report card that outlines a student's open-source experience at Grey Software
can allow them to stand apart from the competition.

Initiative Overview 👁️‍🗨️

Every contributor to Grey Software will be able to generate an authentic report
card by entering their username into grey.software/report-card

Contributors will be able to share a PDF of this report on websites like
LinkedIn.

A link-able version of their report card will also be available at
grey.software/report-card/GITHUB_USERNAME if they choose to.

Implementation Details 🛠️

We'll add a page to our website under /report-card that will have an input box
for Github usernames.

Once users enter their usernames and click "Generate", our backend will scrape
Github and query its API to generate a PDF of their report card.

If they choose to (via a checkbox), they can host their report card publicly on
our website.

Additional Notes:

  • Students will have to authenticate with Guthub in order to generate a verified
    report card for their username
  • A user's insights for a repo will have to be scraped

Impact 💥

Students struggling to demonstrate real-world software experience will now be
able to show their open-source work in a professional manner.

Describe alternatives you've considered 🔍

Students could link their contributor cards from the Github insights page for
every repo they have contributed to.

Additional details ℹ️

N/A

@ArsalaBangash ArsalaBangash added Domain: User Experience This issue pertains to a developer's emotions and attitudes when building Grey Software. Role: Product Owner Uses PM tools to execute the vision they co-create with the Designers, Engineers, and Users. Role: Maintainer Manages the repository by organizing issues, milestones, projects and new contributors. labels Oct 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Domain: User Experience This issue pertains to a developer's emotions and attitudes when building Grey Software. Role: Maintainer Manages the repository by organizing issues, milestones, projects and new contributors. Role: Product Owner Uses PM tools to execute the vision they co-create with the Designers, Engineers, and Users.
Projects
None yet
Development

No branches or pull requests

1 participant