Be inclusive of outside communities

[gwaybio]

@allaway suggested this rule in #6

I think this rule is a bit different than open science in the context of direct collaborations. But if we need to squeeze rules together, this and #6 will be one of the first.

Essentially, the way I think about this rule is that different people and different communities will find their own ways to use your data and software. Often times these are ways in which you as the content creator could not imagine. A closed science paradigm would either have not have permitted these ideas or the ideas would have been spawned from a different context. Waiting to release software or data until after publication delays others from using data and software in innovative ways.

I remember hearing a sentiment (that is actually probably pretty common) about data creators (the hosts of research parasites) desiring to release data only until all information is squeezed out. This is fundamentally impossible! If the data can be combined with other data to reveal something novel that could not have been discovered in either dataset alone then all information cannot be squeezed. This is one way we can tie in #6 if we decide to merge.

[gwaybio]

Inclusivity here could also be applied in the context of others actually directly contributing to your project. This is made possible in an open science framework and is welcomed. As the project creator and maintainer it is important to define contribution guidelines (maybe this could be a separate rule 🤔 )