Log the display names which are classified as male vs female vs other.

Only present aggregated 'gender gap' statistics on the website, at the bottom, and indicating how many display names it was based upon.
See http://gendergapgrader.com/toolkit/ and https://blog.namsor.com/api/

If #32 doesnt land first, skip any display name which contains numerals and doesnt contain an uppercase letter.

The valid-github-usernames package will only return valid usernames, so there's no point in rechecking that. This can be safely removed as it's not doing anything right now:

diff --git a/lib/scrape.js b/lib/scrape.js
index 9542abc..3d2b346 100644
--- a/lib/scrape.js
+++ b/lib/scrape.js
@@ -173,11 +173,6 @@ async function findGitHubUser({ display_name }, org) {
   const username = await findGitHubUserInOrg(display_name, org)
   if (username) return username
 
-  const displayNamePattern = /^[a-zA-Z0-9-]{1,39}$/
-
-  const displayNameMatches = displayNamePattern.exec(shortName)
-  if (!displayNameMatches) return
-
   const user = await getGitHubUser(shortName)
   if (!user) return

This probably comes from trying to place a chat link, even though Catrobat doesn't have one.

Google publishes how many tasks students have completed for each org.
Scrape this number for each org, and use it to order the orgs.

On a Netlify Deploy Preview, such as https://deploy-preview-84--gci-leaders.netlify.com/ , add a banner at the top which indicates it is not the production website, link back to the GitHub Pull Request, and link to the production website.

Ideally create a package to encapsulate the Netlify information, such as https://github.com/jayvdb/jekyll-netlify .

As the contents of the page include a static snapshot of org activity , it is important to know when it was last generated in UTC, and show how long ago it was generated , aware that the readers timezone is likely not UTC.

The current design with multiple columns looks really cramped.

@synicalsyntax Proposed to make a single column instead.

If possible, use and modify the current grid styling.

The new design should look neat and tidy on large (larger than body width), medium (lower than body width) screen and mobile.

And it's allowed to add css for other elements, such as a or li.

Display the logos of each org, obtained from the GCI website dynamically.
i.e. do not store the logos in this repository.

Each org lists a URL to their chat system. Some are direct links, such as https://coala.zulipchat.org or https://gitter.im/scorelab/scorelab or http://systers.io/slack-systers-opensource/ , but others are using that field to store a http page where more information can be found, such as https://github.com/MovingBlocks/Terasology/wiki/Using-IRC .

This task is to add a clickable chat logo beside the github logo.

For this task, find/create a npm package which interrogates a URL to return metadata about the chat system. It should return at least a short name for the type of chat system, such as 'irc', 'gitter', 'zulip', 'slack' and a consistent logo URL for that chat system.

That package can then be used when building this page.

Extra points for extracting direct chat links from the http page some orgs are using instead of direct links into their chat system.

It appears there is no raw data, so it will need to be scraped from the website.

Present on a separate page, either as one page , or a page per year.

#21 should be done first.

The data feed has a blog_url for many of the orgs:

• coala
• drupal
• FOSSASIA
• HaikuOS
• JBoss
• Liquid Galaxylab
• mifos
• musicbrainz
• OpenMRS
• osgeo
• systers
• ubuntu
• Wikimedia
• XWiki
• Zulip

Exclude URLs which do not have a properly declared RSS/ATOM alternative, e.g. BRL-CAD's FB url (https://fb.me/brlcad) and http://forum.terasology.org/ and http://www.scorelab.org/blog/index.html

Split off from #8 , lets get the easy case done sooner than later.

In the initial GitHub org detection (78d0eaa), the following orgs were resolved using a GitHub search, as is recorded in the build log.

Could not find GitHub org for Apertium. Resorting to GitHub API hit.
Could not find GitHub org for BRL-CAD. Resorting to GitHub API hit.
Could not find GitHub org for Catrobat. Resorting to GitHub API hit.
Could not find GitHub org for CCExtractor Development. Resorting to GitHub API hit.
Could not find GitHub org for Drupal. Resorting to GitHub API hit.
Could not find GitHub org for Haiku. Resorting to GitHub API hit.
Could not find GitHub org for LibreHealth. Resorting to GitHub API hit.
Could not find GitHub org for MetaBrainz Foundation. Resorting to GitHub API hit.
Could not find GitHub org for OpenMRS. Resorting to GitHub API hit.
Could not find GitHub org for OpenWISP. Resorting to GitHub API hit.
Could not find GitHub org for OSGeo. Resorting to GitHub API hit.
Could not find GitHub org for Sugar Labs. Resorting to GitHub API hit.
Could not find GitHub org for Ubuntu. Resorting to GitHub API hit.
Could not find GitHub org for Wikimedia. Resorting to GitHub API hit.
Could not find GitHub org for XWiki. Resorting to GitHub API hit.

This task is for you to find alternative approaches to identity the GitHub org, in order to avoid using a GitHub API hit for these org.

Your build must be rebased and have at least one less API hit than master.

Link to the GitLab org for each Google Code-in organisation, wherever possible, ensuring that only highly probable links are made.

Use a GitLab logo for the link.

https://github.com/ebidel/lighthouse-ci

The padding should be around 2-3em. Find what's the most comfortable.

The padding should be applied once in between every column.

Vertical and horizontal padding should be consistent.

Also we don't need that centered column at the bottom.

Lighthouse analyzes web apps and web pages, collecting modern performance metrics and insights on developer best practices.

https://github.com/GoogleChrome/lighthouse

This is our current Lighthouse audit result: https://u.teknik.io/4SV0f.html

This task is for increasing our Lighthouse score, multiple students can take this task.

For now, don't worry about service worker / offline support, I think we will have another task for that.

Your build must be rebased and have at least one more audit passed than master.

Link to the GitHub user for the leaders, ensuring that only highly probable links are made.

At least confirm that a username is a member of the relevant GitHub organisation before linking to it.

This is a repeatable GCI task.

Use "Related to https://github.com/coala/gci-leaders/issues/8" at the bottom of your commit message, so it doesnt close this issue.

https://gci-leaders.netlify.com/images/GCI-logo.jpg = 404

Also, consider replacing it with slightly bigger one + padding on the sides for better look on share card such as Facebook.

Minimum Image Size
The minimum image size is 200 x 200 pixels. If you try to use an image smaller than this you will see an error in the Sharing Debugger.
https://developers.facebook.com/docs/sharing/best-practices/

Make https://github.com/coala/gci-leaders/blob/gh-pages/data.json readible , and so the history of the file is usable.
Probably also good to emit yaml; which will be more vcs friendly.
Create a separate minified version if required.

The website title is "GCI Current Leaders".

For participants & mentors, we know what it means, but nobody else does, and a google search for "GCI" will not help them.

The only way to find out is to click on an org to go to the codein website.

Improve the title & heading of the website so that the reader knows it is about Google Code-in 2017.

Task completed and github logo should go outside the h3 tag.

A few of the orgs have Google Groups listed, usually as their 'mailing list'.

We should identify them separately, as a Google group has a forum web-interface as well as a traditional mailing list, and a consistent archive browsing mechanism that makes it easy to get involved, without needing to use 'subscribe' type emails, or browse pipermail.

The website title is "GCI Current Leaders".

For participants & mentors, we know what it means, but nobody else does, and a google search for "GCI" will not help them.

The only way to find out is to click on an org to go to the codein website.

Improve the title & heading of the website by expanding it to "Google Code-in 2017" so that the reader knows what's it all about.

The GCI logo should be there also.

Make sure the logo placement is appropriate based on the Google media rules.

https://developers.google.com/open-source/gci/resources/media

We need to make sure that the logo and the title appears correctly in social media share.

Put some Open Graph <meta> tag. We need atleast og:title, og:description, and og:image.

http://ogp.me/

The orgs without any leaders are visually unappealing amongst the other orgs.

They should be a separate list, at the bottom of the page, ordered by number of tasks completed.

#20 only adds prettier which focuses on formatting rules.

eslint:recommended adds some real linter rules. e.g. unused variable.
prettier rules is used to remove any formatting rules that conflicts with prettier.

This was discussed briefly in #78, but I'll use this issue as a way to better express my ideas around the bigger problem here. Our data.(js|min.js|yml) files are going to be changing quite often while this site is in development, not just in their values but also in their keys.

For example, if we were to make some large changes to the data file. Let's say, for example, the desired effect of our change is to move the wikidata link of an organization to a new key:

- "wikidata_url": "//www.wikidata.org/wiki/Q170855"
+ "wikidata_link": "//www.wikidata.org/wiki/Q170855"

When we deploy the code, it will still expect a "wikidata_url" key to exist, despite the name being changed to "wikidata_link". On top of that, the caching code will use the existing organization's object instead of making another API request to GCI (because we don't expect their returned data to change) so the "wikidata_url" will stick around along with the new "wikidata_link" leading to some very cluttered data.

So how do we fix this?

Pretty straight-forward. Adding a CACHE_VERSION or DATA_VERSION constant in our code and putting that value in our data.(js|min.js|yml) files will allow us to check if our data format is up to date. We would increment this version every time a breaking change is made to the data format (be it adding or removing a key, or updating the name of an existing key). If the DATA_VERSION we expect and the DATA_VERSION of the data file we're reading from don't match up, we ignore it and re-fetch all the data.

The new README should explain the

• basic objects of the projects, and
• the technologies used,
• how developers can build it

This website should mention that it has been built by the coala team.

This is a design task; do just add "built by coala".

Do searches on Wikidata, either using the wbsearchentities API (used by https://www.npmjs.com/package/wikidata-search) , or using WDQS (sparql)

The caching of previous wiki values has meant that the old null are stuck in the system.
The reason is https://github.com/coala/gci-leaders/blob/master/lib/scrape.js#L283 .wiki is always a dict, with two keys that are null.

There is homepage, G+ and twitter urls in https://codein.withgoogle.com/api/program/2017/organization/?status=2

Add them as links for each org with appropriate logos.

Some orgs are drowning out everyone else on the feed, and many orgs are too busy to tweet. Best remove them all and let the individuals voices be heard.

Link to the GitHub org for each Google Code-in organisation, wherever possible, ensuring that only highly probable links are made.

Use a GitHub logo for the link.

for Travis.

Use the participants display name to determine nationality.

Discard data which is unsuitable or confidence level is low, but clearly display what percentage of the participants display names were unsuitable or was unusable for the statistics.

wrt unsuitable data, if #32 doesnt land first, skip any display name which contains numerals and doesnt contain an uppercase letter.

To warm you up a bit, see here

Come onto the coala Zulip to discuss how to solve this.

Move the 2 .js file into lib folder for better organization.

Also, rename scrap.js to scrape.js @synicalsyntax told me that it's a typo oops.

This repo uses MIT license

The org name should be a link to the corresponding GCI organization page e.g. https://codein.withgoogle.com/organizations/coala/

There's slug key in the generated data.json.

A lot of research backs up that the ballot order has an impact on the voting patterns.

Likewise a stable alpha ordering of the participants may cause some unintentional bias towards the participants at the top of that ordering.

This task is to introduce client side randomisation of the participants.

.travis.yml , and likely soon .eslintrc

#4 only sorted. The number of tasks completed should be shown.

The data can be scraped on build, from
https://codein.withgoogle.com/api/program/current/

Include at least a few i18n strings, but this task is not about doing translations.

Seems to only happen when the screen is over 720p wide (thus probably being css).
Screenshot from firefox 57.0.1 on linux 64bit, 1080 screen width

e.g. https://github.com/blog/273-github-ribbons

It should check for the file types already in the repository.
Exclude package*.json file and out folder.

Ideally we should use prettier.io to format, because initially I used that.
But PrettierBear doesn't exists yet.

So, use ESLintBear and https://github.com/prettier/eslint-plugin-prettier instead.

The settings should be:

• no semicolon
• es5 trailing commas
• single quote