...

At this moment GitHub allows for searching a Topic in one organization or all organizations available in GitHub. There's no way to configure a search for a group of organizations. To improve the success in searches we could prepend "slac-" to all our Topics, like slac-timing, slac-atca, slac-llrf, etc. This way we ensure that a broad search in GitHub would bring repositories related only to organizations related to SLAC.

GitHub Issues

Currently we have 2 ticket systems in use for software development/bug tracking: CATER and Jira. GitHub brings its own ticket system called Issues.

CATER won't go away for a long time. So, what do we do regarding Jira and GitHub issues? The use cases could be:

1. CATER is kept as it is used today. No changes.
2. GitHub issues for SLAC maintained repositories that have external collaborators.
3. GitHub issues for tickets clearly related to one single repository.
4. Jira for tickets that cross multiple repositories or that are unrelated to work for any repository. Could GitHub Projects be used for this, instead?

Do we want to keep track of tickets in 3 different tools? 

Licenses

In TID we've been following SLAC's legal request of adding a specific LICENSE file to each repository's top directory, plus a disclamer text in all .c, .cpp., .h, .hpp, .py, .vhd, etc files. There's a Python script that we run that do this automatically: https://github.com/slaclab/surf/blob/pre-release/scripts/apply_slac_license.py. As this comes from SLAC legal, I believe that this would be extended to all code available in SLAC's GitHub organizations.

...

I believe that we need to talk with SLAC legal again to verify more use cases.

Other

...

aspects (should they be standardized among all SLAC?)

Repository Naming

...

Should we standardize for repository naming or keep each team to define them freely? Use cases:

If we have a single organization:

• Keep names identical to upstream software?
• Prefix EPICS modules with epics-?
• Prefix extensions with extension-? or epics-?
• Prefix IOC applications with ioc-?

...

If we have slac_epics or directorate

...

orgs:

• No module prefix
• No extension prefix
• Prefix IOC applications with ioc-?

Standard Rulesets

Should the entire SLAC follow the same workflow, with standard names for branches, and standard rules for using each branch? What if different departments have conflicting requirements? 

Settings > Rules > Rulesets

...