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 : Artificial Intelligence/ML API #60

Closed stephen-rowan closed 2 years ago

stephen-rowan commented 3 years ago

FeedbackChallenge : Artificial Intelligence/ML API

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, our company build our product around the idea that the community can help to improve it. With that, we release our source code as open source and labelled our robot as an open-source product. This is evident in all our literature from the very beginning.

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

    Yes, the community can put in request and report issues on our GitLab page. The link as follows: https://gitlab.com/thecorpora/QBO

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

    Contributors can access to the latest changes of the code at GitHub. The link as follows:- https://github.com/OpenQbo

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

(to) swhitenstall

Hi Stephen. Our answered to your questions:

1.- Yes, our company build our product around the idea that the community can help to improve it. With that, we release our source code as open source and labelled our robot as an open-source product. This is evident in all our literature from the very beginning.

2.- Yes, the community can put in request and report issues on our GitLab page. The link as follows: https://gitlab.com/thecorpora/QBO

3.- Contributors can access to the latest changes of the code at GitHub. The link as follows:- https://github.com/OpenQbo

stephen-rowan commented 3 years ago

Thank you for your response, Javier Paz (javier.paz) It has helped a lot.

I have captured them at [ https://github.com/Quality-Assurance-DAO/F5-Developer-ecosystem-Proposal/issues/60 ] 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