Identify if there exist repositories which should not be included in our DCO policy

[msdisme]

We have decided in #598 to adopt a developer certificate-of-origin requirement for all contributions to MOC repositories. There are currently around 200 repositories in the CCI-MOC GitHub organization. Will all of these repositories be covered by the new policy (and the repository updates described in #598)?

This task is to identify any public repositories that should not be covered by the DCO policy.

[joachimweyl]

List to review. Repos that have a current license or have potential upstream Licenses	Repo	Current License	Possible Upstream
python-esiclient	Apache-2.0	No
xdmod-cntr	none	LGPL-3.0
openshift-acct-mgt	none	Apache-2.0
netbox-sync	none	Apache-2.0
esi-leap	Apache-2.0	No
python-esileapclient	Apache-2.0	No
moc-ansible-netbox	Apache-2.0	Apache-2.0
netbox-topology	none	Apache-2.0
netbox-docker-plugins	Apache-2.0	Apache-2.0
documentation	Apache-2.0	No
lsvd-rbd	GPL-2.0	No
sso	Apache-2.0	No
coldfront-plugin-allocation-api	GPL-3.0	GPL-3.0
onboarding-tools	Apache-2.0	Apache-2.0
horizon-onboarding	Apache-2.0	Apache-2.0
adjutant-moc	Apache-2.0	Apache-2.0
flocx-ui	Apache-2.0	No
adjutant-ui	Apache-2.0	Apache-2.0
adjutant	Apache-2.0	Apache-2.0
hil	Apache-2.0	No
admin-tools	Apache-2.0	No
zabbix-libvirt	Apache-2.0	GPL-2.0
zabbix-config	Apache-2.0	GPL-2.0
openstack-quota-migration	none	Apache-2.0
ovirt-scripts	Apache-2.0	No
zabbix-ceph	Apache-2.0	GPL-2.0
horizon	Apache-2.0	Apache-2.0
esi-common	Apache-2.0	No
moc-forms	Apache-2.0	No
ABMI	Apache-2.0	No
obmd	Apache-2.0	No
hil-vpn	Apache-2.0	No
distro-packages	Apache-2.0	No
Account-Request	Apache-2.0	No
ORE	Apache-2.0	No
ksproj	Apache-2.0	No
MOCOSPpuppet	Apache-2.0	No
setpass	Apache-2.0	No
moc-pyslurm	GPL-2.0	GPL-2.0
osprofiler	Apache-2.0	Apache-2.0
GUI-Backend	Apache-2.0	No
GUI-Frontend	Apache-2.0	No
ui	Apache-2.0	No
k2k-proxy	Apache-2.0	No
nova	Apache-2.0	Apache-2.0
python-openstackclient	Apache-2.0	Apache-2.0
service-directory	Apache-2.0	No
puppetlabs-openstack	Apache-2.0	Apache-2.0
old-UI	Apache-2.0	No

[msdisme]

I may have missed some, but I think the list we need to check is smaller:	Repo	Current License	Possible Upstream
xdmod-cntr	none	LGPL-3.0
lsvd-rbd	GPL-2.0	No
coldfront-plugin-allocation-api	GPL-3.0	GPL-3.0
zabbix-libvirt	Apache-2.0	No
zabbix-config	Apache-2.0	No
zabbix-ceph	Apache-2.0	No
moc-pyslurm	GPL-2.0	GPL-2.0

My thinking is :

• we used Apache 2.0 and the upstream is fine, then we are fine.
• we used Apache 2.0 and upstream is something different we need to look
• we used a GPL flavor we need to see why and change it if we can - recognizing we will need to modify repository with a "this license till this date/version, this license after this date/version."

[joachimweyl]

@knikolla - "at least for the coldfront-plugin-allocation-api, we can delete the repo. We're not using it."