search

Quality-Assurance-DAO / F5-Developer-ecosystem-Proposal

A deconstructed, dissected and resurrected Project Catalyst, Fund 5 Developer Ecosystem Proposal.
Apache License 2.0
1 stars 1 forks source link

FeedbackChallenge : Liqwid Protocol Security Audit #68

Closed stephen-rowan closed 3 years ago

stephen-rowan commented 3 years ago

FeedbackChallenge : Liqwid Protocol Security Audit

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 ?
  1. Yes our protocol codebase will be made open source under Apache 2.0 with the 1st components being made open source as early as our testnet app launch end of April/early May.
  1. Accessible - Can community contributors issue pull requests or raise issues on your source code ?
  1. Currently as our team is building Plutus contracts on a rapidly updating codebase we have made our repos private so they are not currently accessible to the community. Our developers are working with Haskell experts at Well-Typed and the protocol will be audited by Tweag in July, as mentioned above the first Plutus contracts released in the testnet app will be made open source and our team will gradually open up more of the codebase leading up to Plutus mainnet launch.
  1. Transparent - Can community contributors access and propose changes to the source text of your documentation ?
  1. We can include the WP document on our GitHub to allow for community feedback yes.

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

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

Report

stephen-rowan commented 3 years ago

Liqwid Labs Idea Submitter

swhitenstall Hey Stephen great questions:

  1. Yes our protocol codebase will be made open source under Apache 2.0 with the 1st components being made open source as early as our testnet app launch end of April/early May.
  2. Currently as our team is building Plutus contracts on a rapidly updating codebase we have made our repos private so they are not currently accessible to the community. Our developers are working with Haskell experts at Well-Typed and the protocol will be audited by Tweag in July, as mentioned above the first Plutus contracts released in the testnet app will be made open source and our team will gradually open up more of the codebase leading up to Plutus mainnet launch.
  3. We can include the WP document on our GitHub to allow for community feedback yes.
stephen-rowan commented 3 years ago

Hi Liqwid Labs,

Apologies for the delay in responding.

Thank you for your input. It is has been very helpful. I am sending this message by PM because comments are now closed. I have captured your response at : https://github.com/Quality-Assurance-DAO/F5-Developer-ecosystem-Proposal/issues/68

And moved the Issue to "Done". I will close the Open-Source Assessment next Wednesday (27th).

Then I will draft a report and send it to all the commenters for you to review before publishing under Creative Commons.

Hopefully this will provide a useful overview for the Catalyst open-source community.

Good Luck with your proposal.