FeedbackChallenge : Glow Formal verification

[stephen-rowan]

FeedbackChallenge : Glow Formal verification

In the spirit of Project Catalyst's #FeedbackChallenge we are assessing to what extent the Catalyst Funding Process and it's Proposals are open source as part of the proposal Quality-Assurance-DAO. Your proposal has been selected because "open source" is mentioned in it's text or comments.

We would appreciate it if you could respond to the following questions (in the reply to my comments below) :

1. Open - Is your Organisation open-source ?

   Yes, triple yes! We believe that Open Source is our moral imperative and intend to produce all our code this way.

2. Accessible - Can community contributors issue pull requests or raise issues on your source code ?

   2. Yes, we value that very much.

3. Transparent - Can community contributors access and propose changes to the source text of your documentation ?

   Yes as well: since we are building a language that aims at helping the whole community grow stronger, we of course value evaluation and modification of our documentation.

To keep the assessment transparent each comment is recorded as a GitHub Issue on Quality-Assurance-DAO's proposal repository (Apache-2.0 License) where a more detailed explanation can be found.

Together we can build a community of open source contributors on the Cardano platform.

Thank You

Stephen Whitenstall, QA-DAO

Detailed explanation

Your Issue reference includes a more detailed explanation of the methodology of this FeedbackChallenge : Open Source. There is also a Open Source Assessment Project Board and a GitHub bot post Issues in my channel #quality-assurance-dao on Project Catalyst's Discord.

We believe this is important because many developers are concerned with the lack of a clear commitment to open source and fear their free contributions will be locked into a proprietary platform.

Open Source Assessment Method

• [x] Draft a basic Open Source Assessment Method. https://github.com/Quality-Assurance-DAO/DAO-Open-Source/tree/main/Documents/Assessments

Basic Open Source Assessment

1. Open - Is your Organisation open-source ?
2. Accessible - Can your users issue pull requests or raise issues on your organisation's source code ?
3. Transparent - Can your users access and propose changes to the source of your organisation's documentation ?

Method

• [x] Do text search of "open source" on Catalyst Projects.
• [x] Post assessment questions in comments of proposal.
• [x] Raise Issue for each proposal's assessment.
• [x] Record response to assessment.
• [x] Close Issue once proposal submitted and record responses

Report

• [ ] Collate and publish report of findings with a Creative Commons License

[stephen-rowan]

Gauthier Lamothe (gauthierlamothe) Team Member

swhitenstall Hello there!

1. Yes, triple yes! We believe that Open Source is our moral imperative and intend to produce all our code this way.
2. Yes, we value that very much.
3. Yes as well: since we are building a language that aims at helping the whole community grow stronger, we of course value evaluation and modification of our documentation.

[stephen-rowan]

Thank you for your response, Gauthier Lamothe (gauthierlamothe), It is very helpful and informative.

I have captured your response at [ https://github.com/Quality-Assurance-DAO/F5-Developer-ecosystem-Proposal/issues/50] and moved the status of the Issue to "Done".

I will collect all data in an informal report to be published on GitHub with a Creative Commons License by 26/05/2021

Good Luck with your proposal. Stephen Whitenstall QA-DAO