Version 0.2.0 (#169)

Version 0.2.0 (#169)
Release of version 0.2.0
See below the full CHANGELOG details.

Added:
- [DemoApp][Library] Create component - `Checkbox` (#47)
- [DemoApp][Library] RTL : activation of RTL mode / manage arabic language (#134)
- [DemoApp] Tokens: screen opacity (#123)
- [DemoApp] Migration of PNG Illustrations to SVG (#143)
- [DemoApp] Tokens: screen color (#124)
- [Library] `RadioButton` component (tokens library v0.11.0) (#145)
- [Library] `ControlItem` component (tokens library v0.11.0) (#132)
- [DemoApp] Tokens: screen elevation (#84)
- [Library] `Chekbox` component (tokens library v0.8.0) (#120)

Changed:
- [Library] Update of tokens (library version 0.11.0) (#126)
- Add @nouha06 and @AhmedAmineZr as new contributor in project (#127)
- [Library] Update of tokens (library version 0.10.0) (#125)
- [Library] Update of tokens (library version 0.9.0) (#121)

Fixed:
- [DemoApp] Limited `bottomsheet` height to half screen (#89)
- [DemoApp] A11y improvements for `bottomsheet` component (#89)
- [DemoApp] Update dart-define env to retrieve flavor (#110)
- [DemoApp] Icon system not adapting to light/dark mode (#112)

---------

Signed-off-by: Tayeb Sedraia <[email protected]>
Signed-off-by: Nouha Hammami < [email protected] >
Signed-off-by: Ahmed Amine Zribi <ahmedamine.zribi@sofrecom>
Co-authored-by: Benoit SUZANNE <[email protected]>
Co-authored-by: Florent Maitre <[email protected]>
Co-authored-by: OUDS Bot [bot] <[email protected]>
Co-authored-by: boosted-bot <[email protected]>
Co-authored-by: Mateo M. <[email protected]>
Co-authored-by: Mateo MARTINEZ <[email protected]>
Co-authored-by: Ahmed Amine Zribi <ahmedamine.zribi@sofrecom>
Co-authored-by: Nouha Hammami <[email protected]>

Author: 8 people

.github/AUTHORS.txt

@@ -0,0 +1,13 @@
+# This is the official list of ouds-ios authors for copyright purposes.
+# This file is distinct from the CONTRIBUTORS files.
+# See the latter for an explanation.
+
+# Names should be added to this file as one of
+#     Organization's name
+#     Individual's name <submission email address>
+#     Individual's name <submission email address> <email2> <emailN>
+# See CONTRIBUTORS for the meaning of multiple email addresses.
+
+# Please keep the list sorted.
+
+Orange SA

CODE_OF_CONDUCT.md .github/CODE_OF_CONDUCT.mdCODE_OF_CONDUCT.md renamed to .github/CODE_OF_CONDUCT.md

@@ -119,6 +119,39 @@ Adhering to the following process is the best way to get your work included in t
 
 Format your code before committing to ensure your changes follow our coding standards.
 
+## Review workflow
+
+Because we want to define and provide an amazing design system for developers, we want to onboard for any evolutions the Q/A team for tests and also the design ans accessibiltiy (a11y) teams so as to check the fixes, patches or evolutions have been well implemented and tested.
+
+The following chart explain how the review is done with also the intermediate alpha builds.
+In few words, alpha builds are made for reviewers, and the merge is processed if and only if any review have been done.
+
+```mermaid
+flowchart TD
+    A[New evolution needed, feature or bug fix] --> |Define needs and acceptance criteria| B(Create issue on GitHub)
+    B --> C(Implementation or refactoring in GitHub branch)
+    C --> |Code review| D{Code review OK?}
+    D --> |No| C
+    D --> |Yes| E(Build alpha version on TestFlight ‘ios‘ and Firebase ‘android‘)
+    E --> F(Update GitHub PR with details of alpha build)
+    F --> G{Feature ready for review}
+    G --> |Test of feature| H{Tests OK?}
+    H --> |No| C
+    G -->|Design review| I{Design review OK?}
+    I --> |No| C
+    G -->|A11Y review| J{A11Y review OK?}
+    J --> |No| C
+    H --> |Yes| K
+    I --> |Yes| K
+    J --> |Yes| K
+    K[Merge in develop branch] --> |Nightly build| L(Beta build on TestFlight ‘ios‘ and Firebase ‘android‘)
+    L --> M(Update GitHub issue with details of beta build)
+```
+
+Pull requests will be merged if no conditions / prerequisites / checks are red (except DCO which is not - yet - mandatory, but we must at least outside contributors to apply it). Some _GitHub Actions_ workflows are defined:
+- [task-list-completed GitHub app](https://github.com/apps/task-list-completed) prevents pull requests to be merged if some mandatory / not optional prerequisites are not filled ;
+- another [workflow YAML](https://github.com/Orange-OpenSource/ouds-ios/blob/develop/.github/workflows/build.yml) building and testing the app / lib;
+
 ## License
 
 By contributing your code, you agree to license your contribution under the [MIT License](LICENSE).

CONTRIBUTING.md .github/CONTRIBUTING.mdCONTRIBUTING.md renamed to .github/CONTRIBUTING.md

@@ -0,0 +1,26 @@
+# This is the official list of people have contributed code to the
+# ouds-flutter repository.
+#
+# The AUTHORS file lists the copyright holders; this file
+# lists people.  For example, Orange employees are listed here
+# but not in AUTHORS, because Orange holds the copyright.
+#
+# When adding J Random Contributor's name to this file,
+# either J's name or J's organization's name should be
+# added to the AUTHORS file, depending on who holds the copyright.
+#
+# Names should be added to this file like so:
+#     Individual's name <submission email address>
+#     Individual's name <submission email address> <email2> <emailN>
+#
+# An entry with multiple email addresses specifies that the
+# first address should be used in the submit logs and
+# that the other addresses should be recognized as the
+# same person.
+
+# Please keep the list sorted.
+
+Julien DERAMOND <[email protected]>
+Tayeb SEDRAIA <[email protected]>
+Ahmed Amine ZRIBI <[email protected]>
+HAMMAMI Nouha <[email protected]>

.github/CONTRIBUTORS.txt

@@ -0,0 +1,92 @@
+# Developer Guide
+
+- [Technical Preconditions](#technical-preconditions)
+  * [Dependency Management](#dependency-management)
+  * [Generation of Localization Files in the app and ouds_core Folders](#generation-of-localization-files-in-the-app-and-ouds_core-folders)
+- [Commits, Changelog, Release Notes, Versioning](#commits-changelog-release-notes-versioning)
+  * [Commit Guidelines](#commit-guidelines)
+  * [Release Notes and Changelog](#release-notes-and-changelog)
+- [Documentation](#documentation)
+- [Installation](#installation)
+  * [Generating Docs](#generating-docs)
+
+## Technical Preconditions
+
+You can refer to the **THIRD_PARTY.md** file, which lists the dependencies and tools we use at different levels (SDK, design system toolbox app, and projects).
+Check the lock files (*pubspec* and *pubspec.lock*) to see which versions are being used.
+
+### Dependency Management
+
+The project uses **Pub Workspace** via [Pub Workspaces](https://dart.dev/tools/pub/workspaces).
+
+The `pubspec.yaml` file at the root of the project manages all dependencies, so please use the following commands at the root to clean up the dependencies:
+
+```bash
+flutter clean
+flutter pub get
+```
+
+### Generation of Localization Files in the `app` and `ouds_core` Folders
+To generate the localization files for the project, use the `flutter gen-l10n` command for each folder (`app` and `ouds_core`).
+
+You need to run this command because it generates the necessary localization files for your project, which helps Flutter manage translations for multiple languages. These files are crucial for the app to properly support localization and internationalization.
+
+```bash
+flutter gen-l10n
+```
+
+## Commits, Changelog, Release Notes, Versioning
+
+### Commit Guidelines
+
+#### Conventional Commit Rules
+
+Please make every effort to follow [conventional commit rules](https://www.conventionalcommits.org/en/v1.0.0/). 
+Ensure that your commits are properly prefixed and include the issue number in parentheses at the end. If applicable, also include the pull request issue number.
+If your commit includes contributions from others, don't forget to [add them as co-authors](https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors).
+All contributors should also comply with the DCO.
+
+Your commit messages should be prefixed with the following keywords (as specified in the [commit specification](https://www.conventionalcommits.org/en/v1.0.0/#specification)):
+- `fix:`
+- `feat:`
+- `build:`
+- `chore:`
+- `ci:`
+- `docs:`
+- `style:`
+- `refactor:`
+- `perf:`
+- `test:`
+
+You can also add `!` after the keyword to indicate a breaking change, and include a scope in parentheses like:
+- `feat!:` breaking change because...
+- `feat(API)!:` breaking change in the API because...
+- `feat:` adding a new feature to the API...
+
+#### Chain of Responsibility
+
+We can include metadata from [this guideline](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n525) in the commit messages.
+This is not mandatory (yet), but it's a good practice to indicate who reviewed and validated each commit.
+You must mention *co-authors* (using `Co-authored-by`), and you should include who are the code reviewers (`Reviewed-by`), testers (`Tested-by`), and if needed, ackers (`Acked-by`).
+
+### Release Notes and Changelog
+
+We also aim to [keep a changelog](https://keepachangelog.com/en/1.0.0/) and apply [semantic versioning](https://semver.org/spec/v2.0.0.html) along with [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/).
+
+## Documentation
+
+OUDS Flutter documentation is generated using the [Dart documentation generator](https://pub.dev/packages/dartdoc).
+Open the `ouds-flutter/library/doc/api` directory.
+
+More technical information about Dart documentation generation is available [here](https://pub.dev/packages/dartdoc).
+
+## Installation
+
+The `dart` tool, with the `dart doc` command, is part of the Dart SDK.
+
+### Generating Docs
+
+Run `dart doc .` from the `library/doc/api` directory of the package. You must first run `dart pub get` or `flutter pub get`, and your package must analyze without errors using `dart analyze` or `flutter analyze` as appropriate. Here's an example of `dartdoc` documenting itself:
+
+```bash
+$ dart doc .

.github/DEVELOP.md

@@ -2,7 +2,7 @@ name: Report a bug
 description: Tell us about a bug or issue you may have identified in OUDS Flutter.
 title: "[Bug]: Bug Summary"
 labels: ["🐞 bug", "🔍 triage"]
-assignees: ["Tayebsed93"]
+assignees: ["Tayebsed93", "nouha06", "AhmedAmineZr"]
 body:
   - type: checkboxes
     attributes:

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -2,7 +2,7 @@ name: Documentation Update
 description: Describe this issue found in the documentation
 title: "[Doc]: "
 labels: ["📖 documentation", "🔍 triage"]
-assignees: ["Tayebsed93"]
+assignees: ["Tayebsed93", "nouha06", "AhmedAmineZr"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/documentation-update.yml

@@ -2,7 +2,7 @@ name: Feature Request
 description: Suggest a new Epic to be added to the backlog.
 title: "[feature]: "
 labels: ["🗳️ feature", "🔍 triage"]
-assignees: ["Tayebsed93"]
+assignees: ["Tayebsed93", "nouha06", "AhmedAmineZr"]
 body:
   - type: checkboxes
     attributes:

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,25 @@
+- [Overview](#overview)
+- [Current Maintainers](#current-maintainers)
+<!-- - [Emeritus](#emeritus) -->
+
+## Overview
+
+This document contains a list of maintainers in this repo. If you're interested in contributing, and becoming a maintainer, see [CONTRIBUTING](https://github.com/Orange-OpenSource/ouds-flutter/blob/develop/.github/CONTRIBUTING.md).
+
+## Current Maintainers
+
+<!-- Sort by alphabetic order, last name in upper case -->
+
+| Maintainer           | GitHub ID    | Email                                | Affiliation    |
+| -------------------- | -----------  | ------------------------------------ | -------------- |
+| Tayeb SEDRAIA        | Tayebsed93   | [email protected]             | OAB SA         |
+| Ahmed Amine ZRIBI    | AhmedAmineZr | [email protected]        | SOFRECOM       |
+| HAMMAMI Nouha        | nouha06      | [email protected]           | SOFRECOM       |
+
+<!--
+## Emeritus
+
+| Maintainer           | GitHub ID    | Affiliation    |
+| -------------------- | -----------  | -------------- |
+-->
+

.github/MAINTAINERS.md

@@ -0,0 +1,10 @@
+# Security Policy
+
+# Reporting Security Issues
+
+We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
+Send an e-mail to [[email protected]](mailto:[email protected]) to report a vulnerability and contact all people in CONTRIBUTORS and MAINTAINERS including the word "SECURITY" in the subject line.
+
+Please allow our team sufficient time to resolve the vulnerability before disclosing it ; we'll remain in contact about the fix and may ask for your assistance to verify it is resolved.
+
+We will endeavor to respond quickly, and will keep you updated throughout the process.