-
Notifications
You must be signed in to change notification settings - Fork 0
How to contribute
We have been working out over time how to run our projects on GitHub/ZenHub. One of our early desires was to have a meritocracy based system for allowing access to our projects. Essentially, that means that those with the most involvement and the most investment in our projects will have the most access.
We can break up access levels for contributors into three broad categories.
A CDISC employee or contractor will want to join the CDISC GitHub organization. There are specific workflows an internal developer can take advantage of.
For these people, the repository owner/admin can give them outside collaborator status on the repo. They can then work within the CDISC repo or their own cloned repos, just as a CDISC employee would.
Though not members of CDISC teams, these people will find GitHub issues they want to resolve, or they may have their own ideas they will want to conribute. There are workflows specific to external developers they can use.
We are the GitHub/ZenHub Community of Practice (CoP)
Please feel free to edit documents here. As a member of this CoP your opinion is important to the rest of the community. You can't break anything. Jump in, share your opinions, and let your colleagues know you've added content.
- Why GitHub and ZenHub?
- How To Contribute
- Workflows in GitHub/ZenHub
- Support
- Project Management
- Authentication and Authorization
- Labels or Built In?
- Tips for using ZenHub on a Scrum project.
- Using Kanban with ZenHub.
- Current Open Source Projects
- Projects that are currently being migrated to GitHub and/or ZenHub
Below are some links to information describing the CoP and how we are getting it started.