Ubuntu Rally in NYC

Alan Pope

on 1 September 2017

The Ubuntu Rally, taking place in New York City September 25th-29th, is a forward-thinking five day software hackathon attended by major software vendors, Ubuntu developers working at every level of the stack, and community contributors.

There are a limited number of non-sponsored slots remaining. If you’re local to New York or can arrange for your own travel and accommodation, send us a mail to snap-advocacy@canonical.com briefly outlining what you’d like to work on during the sprint.

Some examples:

  • Language ecosystem developers who want to support outputting Snaps
  • Application developers who want to publish in the Snap Store and share feedback
  • Linux distribution maintainers who want to add Snap support to their storefront
  • GNOME developers who want to help improve the Ubuntu Desktop
  • IoT device manufacturers who want to enable their hardware with Ubuntu Core
  • PC OEMs who want to to help set the direction of Ubuntu or enable Ubuntu on their hardware
  • Active & passionate community contributors

Proposals will be reviewed and invites sent on Sept 13th.

Talk to us today

Interested in running Ubuntu in your organisation?

Newsletter signup

Get the latest Ubuntu news and updates in your inbox.

By submitting this form, I confirm that I have read and agree to Canonical's Privacy Policy.

Related posts

Building an open source chain of trust: new research uncovers key blockers and ways forward

Canonical is pleased to share its latest research report, “The open source chain of trust.” Based on a survey of 500 DevOps professionals, the report...

Beyond safety and security: Why automotive open source demands dependability 

In the traditional automotive world, teams often work in silos: the cybersecurity experts lock down the ports, the quality assurance teams hunt for bugs, and...

DirtyClone Linux kernel local privilege escalation vulnerability fixes available

On June 25, 2026, JFrog published their research into CVE-2026-43503, referring to the vulnerability as DirtyClone. The vulnerability had previously been...