One of the things that has come up at each of the sites we have visited is the possibility of shared development of the HERON source code. We set up an AWS instance that hosts the code, and we're working out a MultiSiteDev<http://informatics.gpcnetwork.org/trac/Project/wiki/MultiSiteDev> process for interested developers to participate:
The KUMC dev team<http://informatics.gpcnetwork.org/trac/Project/wiki/DevTeams#KUMC> publishes heron_load<https://informatics.kumc.edu/work/browser/heron_load>, which is a delayed snapshot of most of the ETL code for HERON<https://informatics.kumc.edu/work/wiki/HERON>. But it's not the actual version control system used for development. The following process is emerging to facilitate more direct collaboration among GPC sites: 1. The HERON integrators are currently Dan Connolly, Matt Hoag, and Nathan Graham (see DevTeams#KUMC<http://informatics.gpcnetwork.org/trac/Project/wiki/DevTeams#KUMC> for contact info); they manageelephant.gpcnetwork.org (as in "elephant never forgets".) 2. To participate in shared development UsingSecureShell<https://informatics.kumc.edu/work/wiki/UsingSecureShell>, a GPC developer creates a public key, if necessary, and sends it to one of the HERON integrators, who will set up an account on elephant and associate the key and provide details on how to clone the heron repository. 3. GPC peers should start development on a branch, with a corresponding GPC ticket. 4. The branch can be submitted for review by assigning the ticket to one of the HERON integrators * The heron repository on elephant uses the acl extension<http://mercurial.selenic.com/wiki/AclExtension> to prevent pushes to default except by @heron-integrators. -- Dan
