FeedbackChallenge : Workspace for JavaScript Developers

[stephen-rowan]

FeedbackChallenge : Workspace for JavaScript Developers

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 ?

   I don't have an organization (MIT License)

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

   Yes, community contributors can access the Github repository

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

   Yes, the documentation is also on Github, if it gets to a point where a website is needed for the documentation I will use gitbook or some other tool to generate one from the github markdown files

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.
• [ ] Close Issue once proposal submitted and record responses

Report

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

[stephen-rowan]

Ícaro C. Capobianco (icarocapobianco) kudos icon

Idea Submitter

Thank you swhitenstall

This proposal is about a open source project, I just added the MIT license to it. 1 - I don't have an organization 2 - Yes, community contributors can access the Github repository 3 - Yes, the documentation is also on Github, if it gets to a point where a website is needed for the documentation I will use gitbook or some other tool to generate one from the github markdown files

[stephen-rowan]

Thank you for your response, Ícaro C. Capobianco (icarocapobianco) . It has helped a lot.

I have captured them at [ https://github.com//issues/61 ] and moved the status of the Issue to "Done".

Note : The Issue can still be altered and commented upon via GitHub until Fund 5 Proposals are finalized.

As I set out in the "Detailed explanation" section of each Issue : I will collect all data in a report of findings to be published on GitHub with a Creative Commons License after Fund 5 Proposals are finalized.

Good Luck with your proposal.

Stephen Whitenstall QA-DAO