universe-projects-talk.md

Intro

Slide: Projects // Pat Nakajima & Ayman Nadeem

[Transition from Connor's talk] P: Hey guys, my name is Pat.

A: And I’m Ayman. We’re here to talk to you about some developments we’ve made in the project management space. Today, we’re launching Projects: a new way to organize and prioritize your work on GitHub.

Project Management: what GitHub aims to do broadly

Slide: What does Project Management mean on GitHub?

At GitHub, we think of project management as a way to make developers’ lives easier.

To us, Project management is about easily finding and organizing information to do work.

For a user, that means knowing exactly what needs to be done, when it needs to be done, and what they need to be aware of when doing it.

Problem

Currently on GitHub, developers contribute to a repository by writing and commenting on Issues, opening pull requests and giving one another feedback along the process of building together—but with so many moving parts, it can be difficult to understand how all these pieces relate and connect one another as part of something cohesive.

Solution

To address this, Projects allow you to organize your work in GitHub. At a high-level, clicking on the Projects tab takes you to where you can create a project. Once you have a project, you’re able to create columns that represent categories or contexts that matter to you and add cards to these columns. Cards are the atomic unit of a project: a card can be an issue, pull request, or a note.

P: To show you what it looks like, let’s go through the flow of creating and using a GitHub Project.

Things to demo: (wrap this up into a walkthrough that feels smoooooth)

• Project index page: list of all the projects you’ve ever created.
• Create a new project
• Project show page: Clicking any of these projects brings you to your project page where you can define columns...
• Contribute to an existing project (example Project)
• Searching for issues/PRs
• Communicate that a repo can have multiple projects
• Adding cards
• Visual separation of closed and open issues
• Number of cards in any given issue
• Labels
• Convert to issue

A: What’s next

• Orgs, Personal (in addition to repo scoping)
• Integrators (we want the community to build)
• More specific functionality (do we want to say this?)
• Reminders
• Archiving
• What else do we want to share here?

The work we've shared on project management and code review is part of a broader set of improvements along the goal of improving developer workflow at large. We know how audacious this goal is, so [ask PR how to communicate pragmatic humility and end off on a cool swaggalicious note].