-
Notifications
You must be signed in to change notification settings - Fork 1
Organization-wide code of conduct and contributing files #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
8fb1dd5
e7821d5
c9d93f6
c13e767
359b1ca
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,132 @@ | ||||||
| # Contributor Covenant Code of Conduct | ||||||
|
|
||||||
| ## Our Pledge | ||||||
|
|
||||||
| We as members, contributors, and leaders pledge to make participation in our | ||||||
| community a harassment-free experience for everyone, regardless of age, body | ||||||
| size, visible or invisible disability, ethnicity, sex characteristics, gender | ||||||
| identity and expression, level of experience, education, socio-economic status, | ||||||
| nationality, personal appearance, race, caste, color, religion, or sexual | ||||||
| identity and orientation. | ||||||
|
|
||||||
| We pledge to act and interact in ways that contribute to an open, welcoming, | ||||||
| diverse, inclusive, and healthy community. | ||||||
|
|
||||||
| ## Our Standards | ||||||
|
|
||||||
| Examples of behavior that contributes to a positive environment for our | ||||||
| community include: | ||||||
|
|
||||||
| * Demonstrating empathy and kindness toward other people | ||||||
| * Being respectful of differing opinions, viewpoints, and experiences | ||||||
| * Giving and gracefully accepting constructive feedback | ||||||
| * Accepting responsibility and apologizing to those affected by our mistakes, | ||||||
| and learning from the experience | ||||||
| * Focusing on what is best not just for us as individuals, but for the overall | ||||||
| community | ||||||
|
|
||||||
| Examples of unacceptable behavior include: | ||||||
|
|
||||||
| * The use of sexualized language or imagery, and sexual attention or advances of | ||||||
| any kind | ||||||
| * Trolling, insulting or derogatory comments, and personal or political attacks | ||||||
| * Public or private harassment | ||||||
| * Publishing others' private information, such as a physical or email address, | ||||||
| without their explicit permission | ||||||
| * Other conduct which could reasonably be considered inappropriate in a | ||||||
| professional setting | ||||||
|
|
||||||
| ## Enforcement Responsibilities | ||||||
|
|
||||||
| Community leaders are responsible for clarifying and enforcing our standards of | ||||||
| acceptable behavior and will take appropriate and fair corrective action in | ||||||
| response to any behavior that they deem inappropriate, threatening, offensive, | ||||||
| or harmful. | ||||||
|
|
||||||
| Community leaders have the right and responsibility to remove, edit, or reject | ||||||
| comments, commits, code, wiki edits, issues, and other contributions that are | ||||||
| not aligned to this Code of Conduct, and will communicate reasons for moderation | ||||||
| decisions when appropriate. | ||||||
|
|
||||||
| ## Scope | ||||||
|
|
||||||
| This Code of Conduct applies within all community spaces, and also applies when | ||||||
| an individual is officially representing the community in public spaces. | ||||||
| Examples of representing our community include using an official email address, | ||||||
| posting via an official social media account, or acting as an appointed | ||||||
| representative at an online or offline event. | ||||||
|
|
||||||
| ## Enforcement | ||||||
|
|
||||||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||||||
| reported to the community leaders responsible for enforcement: | ||||||
| `tangi.migot@gmail.com` and `dominique.orban@gmail.com`. | ||||||
|
||||||
| `tangi.migot@gmail.com` and `dominique.orban@gmail.com`. | |
| `code-of-conduct@project.org` (or via the repository's contact links on GitHub). |
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,21 @@ | ||||||
| # Contributing to JuliaSmoothOptimizers | ||||||
|
|
||||||
| We welcome contributions, which can come in many forms: | ||||||
|
|
||||||
| ## Bug reports and discussions | ||||||
|
|
||||||
| If you think you found a bug in any of our packages, feel free to open an issue at the specific GitHub repo. | ||||||
| For our packages, it should be a link like `https://github.com/JuliaSmoothOptimizers/PACKAGE.jl`. | ||||||
| For our tutorials, you can open an issue here or in <https://github.com/JuliaSmoothOptimizers/JSOTutorials.jl>. | ||||||
|
|
||||||
| Focused suggestion and requests can also be opened as issues. | ||||||
|
||||||
| Focused suggestion and requests can also be opened as issues. | |
| Focused suggestions and requests can also be opened as issues. |
Copilot
AI
Mar 28, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The discussion link points to a specific repo path (JuliaSmoothOptimizers/Organization/discussions). If the intent is to use organization-level Discussions, the canonical URL is https://github.com/orgs/JuliaSmoothOptimizers/discussions (also used elsewhere in this repo). Using the wrong URL will 404 or send users to the wrong place.
| If you want to ask a question that is not suited for a bug report, feel free to start a discussion [here](https://github.com/JuliaSmoothOptimizers/Organization/discussions). | |
| If you want to ask a question that is not suited for a bug report, feel free to start a discussion [here](https://github.com/orgs/JuliaSmoothOptimizers/discussions). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The email addresses are wrapped in inline code formatting, which prevents GitHub from auto-linking them. Consider using plain text or a mailto link so reporters can click/tap to contact the enforcement team more easily.