Needs to be public

[andyleejordan]

Tracking here so the issue doesn't get lost.

@agup006 Last I heard this was being discussed with legal. Has there been any movement?

While OMI is "open-source" the only release is through The Open Group, and so our real repository is private.

This causes a lot of pain with our other internal project which takes a dependency on OMI, as every user needs to get authenticated in both GitHub organizations.

[andyleejordan]

Following up on this, it appears that Microsoft organization membership is not enough to access OMI, which is causing everyone on the PowerShell teams headaches. @jeffaco can you follow up on this? At the least, we need OMI to be accessible to anyone in the Microsoft org (i.e. internally readable); it's that, or we give you a new (giant) list of users to add to whatever team controls permissions to this every week (believe me, you don't want this; it's everyone in multiple PowerShell teams).

/cc @paulcallen

[andyleejordan]

/cc @KrisBash

[andyleejordan]

I can think of at least two alternatives:

1. Remove OMI as a submodule from PowerShell (several PS team members have already expressed interest in this, since PS does not require OMI to build, they don't need to be coupled).

2. Fork OMI to the PowerShell org to have centralized permissions; I don't like this because it'll be (slightly) more difficult to contribute back to this repo, but it's a viable option.

[jeffaco]

There's nothing I can do. Opening up OMI is something I want too.

This is for @KrisBash to solve.

I'm pretty sure that everyone in the Microsoft group can read OMI. Do you have examples of folks that belong to the Microsoft group that do NOT have access to the repo? If so, we might want to follow up with people that administer the Microsoft group ...

[andyleejordan]

There were several people at the last PowerShell/GitHub hackathon that had trouble accessing OMI. A possible explanation was it not being readable internally, but I just tested with someone whose GitHub account is linked to the Microsoft organization, but definitely not a member of any of the SCX/OSTC teams, and they had access. Thus I believe those who had trouble just hadn't linked with the Microsoft GitHub org, despite that being a recorded requirement :/.

Opening it up is still the goal, but not as pressing as it seemed earlier.

[agup006]

This can finally be closed :)