Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A Top Level OOD Github Organization #36

Open
marpierc opened this issue Apr 5, 2018 · 6 comments

Comments

Projects
None yet
5 participants
@marpierc
Copy link

commented Apr 5, 2018

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.

@ericfranz

This comment has been minimized.

Copy link
Contributor

commented Apr 5, 2018

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

This comment has been minimized.

Copy link
Contributor

commented Apr 6, 2018

@dhudak-osc

This comment has been minimized.

Copy link

commented Apr 6, 2018

@nickjer

This comment has been minimized.

Copy link
Contributor

commented Apr 6, 2018

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

This comment has been minimized.

Copy link
Contributor

commented Apr 6, 2018

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

This comment has been minimized.

Copy link
Contributor

commented May 10, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.