search

internet-sicherheit / eco-blockchain-governance

Working repo for the eco Blockchain Governance Framework
Apache License 2.0
5 stars 3 forks source link

Opening repository for easier collaboration #6

Closed kiview closed 4 years ago

kiview commented 4 years ago

When can and should we make this repository public in order to gain visibility and attract collaborators (in addition to sharing of results with existing collaborators easier)?

I personally have no problem to do this as early as possible. We have to however discuss how to handle sharing of documents and information which falls under NDA (obviously those should never touch this repo in this case). So which is the channel we can use for this? Our internal Slack or E-Mail seems reasonable to me.

In addition, one would traditionally add a license for the texts generated in this repo once we make the repo public. Hyperledger Aries uses the Apache2 license for their RFCs, maybe this works fine for us as well. I am very open on this topic and would like to handle without much legal overhead if possible.

kiview commented 4 years ago

In case we base ourselves on Aries, we have to go on using Apache 2 license.

An alternative can be using rust-rfc as a base and leverage their MIT dual licensing. However, they are missing most of the automation (Python scripts and CI pipelines) that Aries already includes.

kiview commented 4 years ago

I also noticed that we are missing some crucial GitHub features as long as we are a private repo, such as draft PRs, merge rules for protected branches, GHA support, etc.

kiview commented 4 years ago

It might be sensible, to also discuss the name of the project if we open it. While we want to have eco branding, it should not look eco proprietary or exclusive.

Just naming it eco Open Blockchain Governance Framework might be enough. Open always works 😉

kiview commented 4 years ago

This is done!