Skip to content

Commit 64e8ff9

Browse files
FloChehabFloChehab
committed
🎉 init repo with basic files
Init was inspired by files on the meet repo
0 parents  commit 64e8ff9

6 files changed

Lines changed: 269 additions & 0 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# Changelog
2+
3+
All notable changes to this project will be documented in this file.
4+
5+
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0),
6+
and this project adheres to
7+
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
8+

‎CODE_OF_CONDUCT.md‎

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at visio@numerique.gouv.fr. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [PostHog Code of Conduct](https://github.com/PostHog/posthog/blob/master/CODE_OF_CONDUCT.md), inspired from Contributor Covenant version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

‎CONTRIBUTING.md‎

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
# Contributing to the Project
2+
3+
Thank you for taking the time to contribute! Please follow these guidelines to ensure a smooth and productive workflow. 🚀🚀🚀
4+
5+
To get started with the project, please refer to the [README.md](https://github.com/suitenumerique/meet/blob/main/README.md) for detailed instructions.
6+
7+
Please also check out our [dev handbook](https://suitenumerique.gitbook.io/handbook) to learn our best practices.
8+
9+
10+
## Creating an Issue
11+
12+
When creating an issue, please provide the following details:
13+
14+
1. **Title**: A concise and descriptive title for the issue.
15+
2. **Description**: A detailed explanation of the issue, including relevant context or screenshots if applicable.
16+
3. **Steps to Reproduce**: If the issue is a bug, include the steps needed to reproduce the problem.
17+
4. **Expected vs. Actual Behavior**: Describe what you expected to happen and what actually happened.
18+
5. **Labels**: Add appropriate labels to categorize the issue (e.g., bug, feature request, documentation).
19+
20+
21+
## Commit Message Format
22+
23+
All commit messages must adhere to the following format:
24+
25+
`<gitmoji>(type) title description`
26+
27+
* <**gitmoji**>: Use a gitmoji to represent the purpose of the commit. For example, ✨ for adding a new feature or 🔥 for removing something, see the list here: <https://gitmoji.dev/>.
28+
* **(type)**: Describe the type of change. Common types include `backend`, `frontend`, `CI`, `docker` etc...
29+
* **title**: A short, descriptive title for the change, starting with a lowercase character.
30+
* **description**: Include additional details about what was changed and why.
31+
32+
### Example Commit Message
33+
34+
```
35+
✨(frontend) add user authentication logic
36+
37+
Implemented login and signup features, and integrated OAuth2 for social login.
38+
```
39+
40+
## Changelog Update
41+
42+
Please add a line to the changelog describing your development. The changelog entry should include a brief summary of the changes, this helps in tracking changes effectively and keeping everyone informed. We usually include the title of the pull request, followed by the pull request ID to finish the log entry. The changelog line should be less than 80 characters in total.
43+
44+
### Example Changelog Message
45+
```
46+
## [Unreleased]
47+
48+
## Added
49+
50+
- ✨(frontend) add AI to the project #321
51+
```
52+
53+
## Pull Requests
54+
55+
It is nice to add information about the purpose of the pull request to help reviewers understand the context and intent of the changes. If you can, add some pictures or a small video to show the changes.
56+
57+
### Don't forget to:
58+
- check your commits
59+
- check the linting: `make lint && make frontend-lint`
60+
- check the tests: `make test`
61+
- add a changelog entry
62+
63+
Once all the required tests have passed, you can request a review from the project maintainers.
64+
65+
## Code Style
66+
67+
Please maintain consistency in code style. Run any linting tools available to make sure the code is clean and follows the project's conventions.
68+
69+
## Tests
70+
71+
Make sure that all new features or fixes have corresponding tests. Run the test suite before pushing your changes to ensure that nothing is broken.
72+
73+
## Asking for Help
74+
75+
If you need any help while contributing, feel free to open a discussion or ask for guidance in the issue tracker. We are more than happy to assist!
76+
77+
Thank you for your contributions! 👍

‎LICENSE.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2026 DINUM/Etalab
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

‎README.md‎

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
<p align="center">
2+
<a href="https://github.com/suitenumerique/dictaphone/stargazers/">
3+
<img src="https://img.shields.io/github/stars/suitenumerique/dictaphone" alt="">
4+
</a>
5+
<a href='http://makeapullrequest.com'><img alt='PRs Welcome' src='https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=shields'/></a>
6+
<img alt="GitHub commit activity" src="https://img.shields.io/github/commit-activity/m/suitenumerique/dictaphone"/>
7+
<img alt="GitHub closed issues" src="https://img.shields.io/github/issues-closed/suitenumerique/dictaphone"/>
8+
<a href="https://github.com/suitenumerique/dictaphone/blob/main/LICENSE">
9+
<img alt="GitHub closed issues" src="https://img.shields.io/github/license/suitenumerique/dictaphone"/>
10+
</a>
11+
</p>
12+
13+
<p align="center">
14+
<a href="https://github.com/suitenumerique/dictaphone/blob/main/CHANGELOG.md">Changelog</a> - <a href="https://github.com/suitenumerique/dictaphone/issues/new?assignees=&labels=bug&template=Bug_report.md">Bug reports</a>
15+
</p>
16+
17+
## Dictaphone
18+
19+
### Features
20+
21+
## Table of Contents
22+
23+
## Get started
24+
25+
## Docs
26+
27+
## Contributing
28+
29+
We <3 contributions of any kind, big and small:
30+
31+
- Vote on features or get early access to beta functionality in our [roadmap](https://github.com/orgs/suitenumerique/projects/11/views/4)
32+
- Open a PR (see our instructions on [developing La Suite Meet locally](https://github.com/suitenumerique/dictaphone/blob/main/docs/developping_locally.md))
33+
- Submit a [feature request](https://github.com/suitenumerique/dictaphone/issues/new?assignees=&labels=enhancement&template=Feature_request.md) or [bug report](https://github.com/suitenumerique/dictaphone/issues/new?assignees=&labels=bug&template=Bug_report.md)
34+
35+
## Philosophy
36+
37+
We’re relentlessly focused on building the best open-source dictaphone product—La Suite Dictaphone. Growth comes from creating something people truly need, not just from chasing metrics.
38+
39+
Our users come first. We’re committed to making La Suite Dictaphone as accessible and easy to use as proprietary solutions, ensuring it meets the highest standards.
40+
41+
We follow extreme programming practices, favoring pair programming and quick, iterative releases. Challenge our tech and architecture—simplicity is always our top priority.
42+
43+
## Open-source
44+
45+
Gov 🇫🇷 supports open source! This project is available under [MIT license](./LICENSE.md).
46+
47+
To learn more, don't hesitate to [reach out](mailto:visio@numerique.gouv.fr).
48+
49+
### Help us!
50+
51+
## Contributors 🧞
52+
53+
<a href="https://github.com/suitenumerique/dictaphone/graphs/contributors">
54+
<img src="https://contrib.rocks/image?repo=suitenumerique/dictaphone" />
55+
</a>
56+
57+
## Credits
58+
59+
We're also thankful to the teams behind [Django Rest Framework](https://www.django-rest-framework.org/), [Vite.js](https://vite.dev/), and [React Aria](https://github.com/adobe/react-spectrum) — Thanks for your amazing work!
60+
61+
## License
62+
63+
Code in this repository is published under the MIT license by DINUM (Direction interministériel du numérique).
64+
Documentation (in the docs/) directory is released under the [Etalab-2.0 license](https://spdx.org/licenses/etalab-2.0.html).

‎SECURITY.md‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Security Policy
2+
3+
## Reporting a Vulnerability
4+
5+
Security is very important to us.
6+
7+
If you have any issue regarding security, please disclose the information responsibly submiting [this form](https://vdp.numerique.gouv.fr/p/Send-a-report?lang=en) and not by creating an issue on the repository. You can also email us at visio@numerique.gouv.fr
8+
9+
We appreciate your effort to make Visio more secure.
10+
11+
## Vulnerability disclosure policy
12+
13+
Working with security issues in an open source project can be challenging, as we are required to disclose potential problems that could be exploited by attackers. With this in mind, our security fix policy is as follows:
14+
15+
1. The Maintainers team will handle the fix as usual (Pull Request,
16+
release).
17+
2. In the release notes, we will include the identification numbers from the
18+
GitHub Advisory Database (GHSA) and, if applicable, the Common Vulnerabilities
19+
and Exposures (CVE) identifier for the vulnerability.
20+
3. Once this grace period has passed, we will publish the vulnerability.
21+
22+
By adhering to this security policy, we aim to address security concerns
23+
effectively and responsibly in our open source software project.

0 commit comments

Comments
 (0)