Skip to content

Why we use GitHub and ZenHub

Drew Mills edited this page Jul 9, 2024 · 13 revisions

Administration (or a lack thereof)

One of the mightiest qualities of GitHub/ZenHub is that administration is almost zero. Involvement in a project essentially requires only three steps:

  • A user goes to GitHub and creates an account (GitHub handles that administration).
  • If the user wants to use ZenHub, they will create that account on ZenHub and link their GitHub account to it.
  • GitHub accounts for CDISC employees and contractors are added to the CDISC GitHub organization by submitting a support request to IT.
  • Those who are not part of the CDISC organization can be added by a repository owner as an outside collaborator.

And that is it.

Free access to ZenHub

We (CDISC) have an unlimited access to ZenHub licenses. Due to our commitment to open projects and our non-profit status, we have an arrangement with ZenHub that allows us to add and remove users as needed in ZenHub.

Rapid onboarding onto Scrum Teams

Because it is both free and simple to administer, onboarding new users is quick and easy.

Global participation

The world goes to GitHub for open source projects. By participating there, CDISC eases the path for those who want to participate with us. Anyone who knows how to use Git and GitHub will understand how to participate in our Open Source projects.

This is the most compelling reason why we want to be on GitHub rather than any other platform. Yes, you can do open source on other platforms. But GitHub makes it so much easier for the world to work with us, and vice versa.

Organic traffic

With GitHub and open repositories we have the option for completely free organic traffic discovering our open source projects.

Rapid results

Minimal configuration is needed to get a new ZenHub or GitHub project underway. If someone wanted to they could accept all defaults and just start building the project. Changes to any process are easily rolled in over the lifetime of a project as a team decides they want to do things differently.

Customization

Because configuration is so simple, each team has an opportunity to work in the manner that fits them best. The CORE team uses ZenHub builtin capabilities like Sprints, Epics, etc. The DDF team uses Feature labels and Sprint labels, basically labels everywhere (they LOVE labels). Both teams are right.

Using GitHub and ZenHub

The GitHub and ZenHub Community of Practice (CoP)

Training options for GitHub and ZenHub

Tips from the CoP

Open Source Projects at CDISC

Onboarding Questions

Product Owner Experience


Building the CoP from Scratch

Below are some links to information describing the CoP and how we are getting it started.

Clone this wiki locally