- CC-X (describe in comments)
We have pushed the idea that e-Infrastructure (ie, the networks, compute and data facilities, as well as the user-facing services) can be expressed as code. Yes, you need the actual hardware, that goes without saying. But a large part of the value of e-Infrastructure comes from how you put it together. The knowledge and skill required to orchestrate and configure services so that they work is what e-Infrastructure developers have.
As a members of this community, we have the luxury most times to be able to develop our services in development and testing environments, by writing the code which - when executed - composes the services in the way that we want. When this code is applied to relevant hardware, you get production services which users can use.
Since we're talking about code here, we can apply "good code stuff" to it : peer review, test-driven development, continuous integration, etc. In other words, we can adopt a DevOps paradigm to design and develop infrastructure, and then smoothly put it into operation.
Tools and platforms are rapidly changing before our eyes. The capability to use them to our advantage implies the capability to specialise and share know-how efficiently too. I believe that the ability to test, reproduce and share this code is really important in reaching some form of sustainability, and in developing the commons which we all rely on. Since we're talking about many different institutes and contributors here (hopefully !) we need to choose a license that satisfies the legal issues in all of these institutes.
Typically, most of the work done in @AAROC has been licensed to the CSIR under the Apache-2.0 license. However, what would happen if someone from say UFS wanted to contribute ? We want to make it not just easy, but attractive to contribute code to the e-Infrastructure commons.
Which license do you currently use ?
What is the policy of the department where you work regarding open source development ?