Merging Islandora dev-ops with the main Islandora Organization

[kstapelfeldt]

To streamline administration and increase the transparency of the Islandora code-base, I propose we start the process of transferring Islandora Dev-ops repositories to the main Islandora Organization Repository, and move to a Github Team-based permissions model for access to the repositories the main Islandora repository. This should allow for more granular assigning of permissions in the Github Organization. If the repositories are transferred correctly, it shouldn't break anything people are currently using.

[DonRichards]

There is 1 main issue I can see. Mainly with merge rules. In the "dev-ops" side it's expected to move quickly and with little feedback from the bulk of the community. This also means vendors and organizations can make large swift changes to some codebase without the same code review restrictions we have on the main "core" Islandora codebase.

This is absolutely needed in the "dev-ops" code because this is the implementation of the software but not the actual software. Anything that is truly "Islandora" should be reviewed by the community and should not be allowed to make changes to the core islandora codebase without community feedback.

This distinction was intended to keep the "rules" easier to follow and kept expectations clear to all parties.