GCTools Hackathon

Team PSC Revs and other participants hard at work at the ISED Lab during the 2017 GCTools Hackathon

The second annual GCTools Hackathon was on and at the Innovation, Science and Economic Development Canada (ISED) Service Lab. Participants were invited not only to submit their ideas but were also encouraged to provide the necessary coding for enhancement and fixes by submitting the code on GitHub.

Teams were free to work on any fix or functionality. A list of current issues such as bugs and enhancement requests were available on the GitHub repository of each project. In addition, we identified the following themes and challenges as areas where we want to improve the GCTools:

  • Accessibility
  • Usability and User Experience
  • Collaboration with open source communities

GCTools Hackathon 2017 results

There were 12 teams participating and 68 people who came in person as well as 30 virtual participants from coast to coast to coast - all the way from Whitehorse, to Burnaby to St. John’s.  There was representation from over 20 departments and a total of 25 bug fixes and feature enhancements submitted as a result of the hackathon.  Most participants were Canadian public servants, save a few students and external participants.

Winners were announced April 13th 2017 on GCconnex and GCcollab.

Winning teams

  • IRCC
  • Open Source
  • Access Avengers

Other mentions

Best team spirit – PSC Revs
Best team name – Leeroy Jenkins
Best virtual participation – Go Go Gadget
Most tech problems – Team Three
Most unnoticed – Jets 10

The hackathon let us share our passion and pride, showcase our development process, and welcome a new generation of GCTools collaborators and contributors.

We hope to see everyone again on GitHub and beyond.  Building better open source tools can happen with anyone, anywhere, anytime (not just during the hackathon!).

A big thank you to all participants!  See you next year!

Report a problem or mistake on this page
Please select all that apply:

Thank you for your help!

You will not receive a reply. For enquiries, contact us.

Date modified: