The Open Ethics Initiative is a global movement focused on promoting transparency, ethical design, and responsible deployment of artificial intelligence (AI) solutions. Let me break down what it’s all about:
The Open Ethics Initiative aims to engage various stakeholders, including citizens, legislators, engineers, and subject-matter experts. Its core mission is to foster a transparent approach to designing and deploying AI-powered solutions that positively impact society.
Inclusive Dialog: The initiative encourages open conversations between experts and citizens. Inclusive dialogues lead to better collaboration and understanding, ensuring that humans and AI can work together effectively.
Disclosure and Transparency Protocol: This bottom-up approach encourages providers of AI systems to disclose their modes of operation in a standardized, user-friendly, and explicit manner. Think of it as a starting point for machines to explain themselves.
Open Ethics Maturity Model: Organizations can use this framework to become more transparent and ethically consistent. It outlines steps for critical self-examination of practices.
- Join us using this link https://openethics.ai/join/
- Explore Discord conversations https://openethics.ai/discord/
- Participate in meetups, write content or code, browse through open issues and pick the one that makes sense
We have a project management tool in the form of the task board called the Impact Hub. You'll get your invite as soon as you Join. Code, research and content-related tasks are added there.
If you have an idea, pick up someone from the community to chat about it first. The best place to start is Discord. Once the idea gets crystalized, add it in the Impact Hub project in this repository and attempt to describe the features and scenarios of your idea as detailed as you can.
In the most cases Open Ethics Initiative is asking all contributors to sign a contributor license agreement (CLA). By signing the CLA you grant the license to Open Ethics to use your contribution but it does not change Your rights to use Your own contributions for any other purpose.
We use the Gherkin syntax to formalize requirements. The Gherkin language is easy to read and used for writing test cases, particularly in the context of Behavior-Driven Development (BDD). Gherkin connects the human concept of cause and effect to the software concept of input/process and output.
The complex scenario could be described as follows using simple vocabulary of keywords:
Feature, Background, Scenario, Given, When, Then, And, But
