A Top Level OOD Github Organization

[marpierc]

Have you considered putting OOD in its own organization rather than having it part of the OSC GitHub organization? This may help streamline some issues, such as versioning.

┆Issue is synchronized with this Asana task by Unito

[ericfranz]

I've seen both examples in the wild. For example, Open XDMoD is under Buffalo's organization on GitHub. On the other hand, Foreman server management tool has its own organization.

I'm ambivalent to whether it is under the osc organization or a dedicated ood organization though I can see the value of knowing the full list of repos all relate to OOD. I'll let my colleagues voice their own response. @dpjohnson @treydock @dhudak-osc @nickjer @achalker any thoughts?

[achalker]

I don’t feel strongly about it, but would probably vote for doing this under OSC

---

Alan Chalker, Ph.D. [email protected]mailto:[email protected] 614-247-8672

From: Eric Franz [email protected] Sent: Thursday, April 5, 2018 5:09 PM To: OSC/Open-OnDemand [email protected] Cc: achalker [email protected]; Mention [email protected] Subject: Re: [OSC/Open-OnDemand] A Top Level OOD Github Organization (#36)

I've seen both examples in the wild. For example, Open XDMoDhttp://open.xdmod.org/7.5/index.html is under Buffalo's organization on GitHubhttps://github.com/ubccr/xdmod. On the other hand, Foremanhttps://theforeman.org/ server management tool has its own organizationhttps://github.com/theforeman/foreman.

I'm ambivalent to whether it is under the osc organization or a dedicated ood organization though I can see the value of knowing the full list of repos all relate to OOD. I'll let my colleagues voice their own response. @dpjohnsonhttps://github.com/dpjohnson @treydockhttps://github.com/treydock @dhudak-oschttps://github.com/dhudak-osc @nickjerhttps://github.com/nickjer @achalkerhttps://github.com/achalker any thoughts?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/OSC/Open-OnDemand/issues/36#issuecomment-379077626, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGe2cr-QN1nMCKIg4sEhcpzTogZG7O58ks5tlogEgaJpZM4TJFDd.

[dhudak-osc]

Will moving the repo streamline versioning?

Thanks, Dave

On Apr 5, 2018, at 8:08 PM, achalker [email protected] wrote:

I don’t feel strongly about it, but would probably vote for doing this under OSC

---

Alan Chalker, Ph.D. [email protected]mailto:[email protected] 614-247-8672

From: Eric Franz [email protected] Sent: Thursday, April 5, 2018 5:09 PM To: OSC/Open-OnDemand [email protected] Cc: achalker [email protected]; Mention [email protected] Subject: Re: [OSC/Open-OnDemand] A Top Level OOD Github Organization (#36)

I've seen both examples in the wild. For example, Open XDMoDhttp://open.xdmod.org/7.5/index.html is under Buffalo's organization on GitHubhttps://github.com/ubccr/xdmod. On the other hand, Foremanhttps://theforeman.org/ server management tool has its own organizationhttps://github.com/theforeman/foreman.

I'm ambivalent to whether it is under the osc organization or a dedicated ood organization though I can see the value of knowing the full list of repos all relate to OOD. I'll let my colleagues voice their own response. @dpjohnsonhttps://github.com/dpjohnson @treydockhttps://github.com/treydock @dhudak-oschttps://github.com/dhudak-osc @nickjerhttps://github.com/nickjer @achalkerhttps://github.com/achalker any thoughts?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/OSC/Open-OnDemand/issues/36#issuecomment-379077626, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGe2cr-QN1nMCKIg4sEhcpzTogZG7O58ks5tlogEgaJpZM4TJFDd. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

-- David E. Hudak, Ph.D. Interim Executive Director and Director of Supercomputer Services Ohio Supercomputer Center (OSC) A member of the Ohio Technology Consortium 1224 Kinnear Road, Columbus, Ohio 43212 Office: (614) 247-8670 • Fax: (614) 292-7168 [email protected]

Learn more about OSC at https://osc.edu

[nickjer]

Hosting the OnDemand tools under an Open OnDemand organization in GitHub can provide some benefits:

• as @ericfranz mentioned an outsider can get an overhead view of all the OnDemand-specific repos and it can make contributions easier
• can add external partners as administrators
• can create teams with external partners and not have them clutter OSC organization teams
• can keep OSC-specific OnDemand apps separate from Open OnDemand so as not to confuse people (also won't need to keep adding prefixes to these projects, e.g., bc_osc_...., osc-systemstatus, osc-ood-conf, ...)
• you can also make an organization website on GitHub so it appears like https://ondemand.github.io instead of https://osc.github.io/ondemand

[ericfranz]

outsider can get an overhead view of all the OnDemand-specific repos

We could use "pinned" repositories to highlight the OOD repos. This would work better if there were fewer of them. Still we need a better place on the website to provide links to all the repos for components, third party, apps, etc. so this isn't a big selling point for me.

you can also make an organization website on GitHub so it appears like https://ondemand.github.io instead of https://osc.github.io/ondemand

I think just using a custom domain name for the main OnDemand repo would be a better approach. But we have go.osu.edu/ood which is sufficient for this.

The other benefits are valid but I don't think its worth moving to a separate org yet. Maybe if OOD expands to become a multi-institution project next year we will know better the collaboration requirements.

[ericfranz]

Now that we are using http://openondemand.org/ domain name, it will at least be a little easier to consider moving to an OOD specific organization if/when the time comes.

[johrstrom]

I'm going to close this ticket as, it may be done at some point (and I'm not necessarily against it) it's unlikely that this ticket specifically will be the driving factor.

That is, we have this conversation from time to time, but always forget this ticket exists. In any case, while yes we may do this someday, it's not really imaginable to me that we'll actually remember that this ticket exists.