COmanage Users List

["Basney, Jim" <>]

Thanks Scott for the notice. This change impacts the CILogon project which 
relies on these Dockerfiles.

My concern is that this change will make it more difficult to contribute to 
this open source project. "Send email to <person> for details on how to 
acquire an account" creates an unacceptable hurdle in my opinion -- the 
difference between "let me just take a few minutes to submit this fix as a 
pull request on github.com" versus "nevermind, it's not worth it."

Sincerely,
Jim
________________________________________
From: Scott Koranda <>
Sent: Tuesday, May 12, 2020 7:41 AM
To: 
Subject: [comanage-users] COmanage Registry Docker repository transition

Hello,

This note is only relevant for COmanage Registry deployers who use a
Docker image to deploy COmanage Registry and who build their own
image(s) using the Dockerfiles from the COmanage Registry project.

If you do not deploy COmanage Registry using Docker or if you use a
pre-built image such as the InCommon Trusted Access Platform (TAP)
image, then you may safely ignore this note.

In the coming days in May the COmanage Registry Docker Git repository
that is currently hosted using "cloud" GitHub at

https://github.com/Internet2/comanage-registry-docker

will transition in two (2) ways:

1) The code will move from being hosted at "cloud" GitHub to the
Internet2 Enterprise GitHub at

https://github.internet2.edu/

The Internet2 Enterprise GitHub is readable by anyone. Cloning and
building COmanage Registry Docker images will not require an account on
the Internet2 Enterprise GitHub.

Contributing to the development of the COmanage Registry Docker
code/files going forward, however, requires an account on the Internet2
Enterprise GitHub. If you plan to contribute and do not already have an
account on the Internet2 Enterprise GitHub please contact Bill Kaufman
() for details on how to acquire an account.

2) The single repository with 14 different directories for the various
Docker images (base, basic authentication, Shibboleth SP authentication,
OIDC authentication, and so on) will be split into 14 individual
repositories to accommodate the InCommon TAP build pipeline.

The overall process for building a COmanage Registry Docker image will
largely remain the same but any automated build scripts will need to be
updated to adapt to the new service location and the new individual
repositories.

After the transition the current repository in the "cloud" GitHub will
remain available for a time but will be configured to no longer accept
pushes and issues and pull requests will not be allowed. All new work
will be done in the new repositories. After some time the "cloud" GitHub
repository will be removed.

Another note will be sent just before the transition begins and then
again when the transition is complete.

Please reply to the list with any questions or concerns.

Thanks,

Scott K for the COmanage Project