diff --git a/docs/beman_standard.md b/docs/beman_standard.md index db490ab..9d4a2d5 100644 --- a/docs/beman_standard.md +++ b/docs/beman_standard.md @@ -38,7 +38,7 @@ needs. To make changes: 1. Create a [discourse topic](https://discourse.boost.org) detailing the change and how it aligns with the core principles. 2. After some community discussion, create a PR with the actual change on - [GitHub](https://github.com/bemanproject/beman) and apply the **Beman leads** label. + [GitHub](https://github.com/bemanproject/beman) and apply the *Beman leads* label. The PR should also link to the discourse topic. 3. Continue discussions on the PR and discourse topic. 4. Await a leads decision based on the community feedback. @@ -68,7 +68,6 @@ recommendations. 1. [Apache License v2.0 with LLVM Exceptions](https://llvm.org/LICENSE.txt) 2. [Boost Software License 1.0](https://www.boost.org/LICENSE_1_0.txt) -3. [The MIT License](https://opensource.org/license/mit) ### **[license.apache_llvm]** @@ -131,19 +130,18 @@ Here is snapshot of `default branch` settings in `exemplar` repository: **Requirement**: There must be a default `Rulesets` configured for any Beman repository (library, infrastructre, documentation, etc.) Use the following example: - -- Go to your repository's settings - e.g., [exemplar/settings](https://github.com/bemanproject/exemplar/settings/). -- Go to `Code and automation` / `Rules` / `Rulesets` - e.g., [exemplar/settings/rulesets](https://github.com/bemanproject/exemplar/settings/rules/). -- You should have a single ruleset named `Default` - e.g., [exemplar/settings/rulesets/beman](https://github.com/bemanproject/exemplar/settings/rulesets/beman). -- Create (via `New ruleset` button) or update (click on `Default` ruleset) it to include the following rules: - - Rulset Name: `Default` - - Enforcement status: `Active` - - Bypass list: Check `Organization admin` and `Repository admin` - - Target branch: Check `Include default branch` - - Go to `Rules` section - - Check `Restrict deletions` and `Block force pushes` - - Check `Require a pull request before merging` and configure it to have `Required approvals: 1`, `Require review from Code Owners` and `Allowed merge methods: Merge, Squash, Rebase`. -- Click `Create` to save the ruleset. +* Go to your repository's settings - e.g., [exemplar/settings](https://github.com/bemanproject/exemplar/settings/). +* Go to `Code and automation` / `Rules` / `Rulesets` - e.g., [exemplar/settings/rulesets](https://github.com/bemanproject/exemplar/settings/rules/). +* You should have a single ruleset named `Default` - e.g., [exemplar/settings/rulesets/beman](https://github.com/bemanproject/exemplar/settings/rulesets/beman). +* Create (via `New ruleset` button) or update (click on `Default` ruleset) it to include the following rules: + * Rulset Name: `Default` + * Enforcement status: `Active` + * Bypass list: Check `Organization admin` and `Repository admin` + * Target branch: Check `Include default branch` + * Go to `Rules` section + * Check `Restrict deletions` and `Block force pushes` + * Check `Require a pull request before merging` and configure it to have `Required approvals: 1`, `Require review from Code Owners` and `Allowed merge methods: Merge, Squash, Rebase`. +* Click `Create` to save the ruleset. Here is a snapshot of `default branch` settings in `exemplar`: @@ -154,8 +152,7 @@ Here is a snapshot of `default branch` settings in `exemplar`: **Recommendation**: The repository should not use git submodules. Check `cmake.use_find_package` for alternatives. Known exceptions: - -- [mpark/wg21: Framework for Writing C++ Committee Papers](https://github.com/mpark/wg21): A non-C++ submodule designed for drafting ISO C++ papers using LaTeX or Markdown. +* [mpark/wg21: Framework for Writing C++ Committee Papers](https://github.com/mpark/wg21): A non-C++ submodule designed for drafting ISO C++ papers using LaTeX or Markdown. ## Release @@ -182,11 +179,11 @@ Known exceptions: - Build system changes - Documentation updates - 2.4. A "New Contributors" section listing all first-time contributors. + 2.4. A "New Contributors" section listing all first-time contributors. - 2.5. A "Full Changelog" link to the complete list of commits. + 2.5. A "Full Changelog" link to the complete list of commits. - 2.6. A "Contributors" section listing all contributors to this release. Note: This section is autogenerated by GitHub Releases! + 2.6. A "Contributors" section listing all contributors to this release. Note: This section is autogenerated by GitHub Releases! Use the following format: @@ -201,12 +198,13 @@ Use the following format: This release has a status of [Under development and not yet ready for production use.](https://github.com/bemanproject/beman/blob/main/docs/beman_library_maturity_model.md#under-development-and-not-yet-ready-for-production-use). + ## Changelog -- by @${USER} in https://github.com/bemanproject/${REPO}/pull/${PR_ID} -- ... +* by @${USER} in https://github.com/bemanproject/${REPO}/pull/${PR_ID} +* ... **Full Changelog**: https://github.com/bemanproject/${REPO}/compare/${PREV_VERSION}...${CURRENT_VERSION} @@ -214,8 +212,9 @@ This release has a status of [Under development and not yet ready for production -- @${USER} made their first contribution in https://github.com/bemanproject/${REPO}/pull/#${PR_ID} -- ... +* @${USER} made their first contribution in https://github.com/bemanproject/${REPO}/pull/#${PR_ID} +* ... + ``` Complete examples can be found in [https://github.com/bemanproject/exemplar/releases](https://github.com/bemanproject/exemplar/releases). @@ -224,10 +223,12 @@ Here is a snapshot of notes for a particular release in `exemplar`: ![](./images/release.notes-example01.png) + ### **[release.godbolt_trunk_version]** **Recommendation**: A Beman library should have at least a trunk version deployed on godbolt with nightyclone mode activated. Check [tutorial: Compiler Explorer Deployment](https://github.com/bemanproject/beman/blob/main/guidelines/compiler-explorer-deployment.md). + ## Top-level The top-level of a Beman library repository must consist of `CMakeLists.txt`, `LICENSE`, and `README.md` files. @@ -267,7 +268,6 @@ Examples: **Requirement**: Following the title, the `README.md` must have a one-line badge list. Examples: library status (`[readme.library_status]`), CI status, code coverage, Compiler Explorer example. Example: - ```markdown ![Library Status](https://raw.githubusercontent.com/bemanproject/beman/refs/heads/main/images/badges/beman_badge-beman_library_under_development.svg) ![Continuous Integration Tests](https://github.com/bemanproject/exemplar/actions/workflows/ci_tests.yml/badge.svg) ![Lint Check (pre-commit)](https://github.com/bemanproject/exemplar/actions/workflows/pre-commit.yml/badge.svg) [![Compiler Explorer Example](https://img.shields.io/badge/Try%20it%20on%20Compiler%20Explorer-grey?logo=compilerexplorer&logoColor=67c52a)](https://godbolt.org) ``` @@ -325,7 +325,7 @@ If the library has been deployed onto Compiler Explorer, add this badge and repl ```markdown **Implements**: [`std::optional` (P2988R5)](https://wg21.link/P2988R5) and -[Give **std::optional** Range Support (P3168R1)](https://wg21.link/P3168R1). +[Give *std::optional* Range Support (P3168R1)](https://wg21.link/P3168R1). ``` Note that specifying the revision number is optional. @@ -363,7 +363,6 @@ or **Requirement**: Following the library status line and a new line, the `README.md` must have a `LICENSE` section. Use exactly the following format: - ```markdown ## License @@ -420,6 +419,7 @@ find_package( [REQUIRED]) See `[cmake.skip_tests]` in this document for a working example or [exemplar/blob/main/CMakeLists.txt](https://github.com/bemanproject/exemplar/blob/main/CMakeLists.txt). + ### **[cmake.project_name]** **Recommendation**: The CMake project name should be identical to the beman library name. @@ -521,6 +521,7 @@ endif() The `CMakeLists.txt` in the test directory can declare any test-only dependendencies that are required. For instance: + ```CMake # File: /tests/CMakeLists.txt # ... @@ -581,7 +582,7 @@ add_subdirectory(beman) # Don't do this add_subdirectory(optional) # Don't do this ``` -### **[cmake.implicit_defaults]** +### **[cmake.implicit_defaults]** **Recommendation**: Where CMake commands have reasonable default values, and the project does not intend to change those values, the parameters should be left implicitly defaulted rather than enumerated in the command. @@ -798,19 +799,19 @@ first possible line in all files which can contain a comment Examples: -- C++ files shall use the following form: +* C++ files shall use the following form: ```C++ // SPDX-License-Identifier: ``` -- CMake files and scripts shall use the following form: +* CMake files and scripts shall use the following form: ```CMake # SPDX-License-Identifier: ``` -- Markdown files will use a comment following the title: +* Markdown files will use a comment following the title: ```markdown # Title diff --git a/docs/code_of_conduct.md b/docs/code_of_conduct.md index 6e80811..f9b139d 100644 --- a/docs/code_of_conduct.md +++ b/docs/code_of_conduct.md @@ -13,13 +13,13 @@ SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception The Beman Project community works to be welcoming and kind among itself and to others, with a deep commitment to psychological safety, and we want to ensure that doesn’t change as we grow and evolve. To that end, we have a few ground rules that we ask all community members to adhere to: -- be welcoming, -- be friendly and patient, -- be considerate, -- be kind, -- be careful in the words that we choose, -- when we disagree, try to understand the reason -- recognize when progress has stopped, and take a step back. +* be welcoming, +* be friendly and patient, +* be considerate, +* be kind, +* be careful in the words that we choose, +* when we disagree, try to understand the reason +* recognize when progress has stopped, and take a step back. This list isn't exhaustive. Rather, take it in the spirit in which it’s intended -- a guide to make it easier to communicate and participate in the community. @@ -36,73 +36,74 @@ If you believe someone is violating the code of conduct, please report it to the More detailed guidance on how to participate effectively in our community spaces: -- **Be welcoming.** - - We strive to be a community that welcomes and supports - people of all backgrounds and identities. - This includes, but is not limited to, members of any race, ethnicity, culture, national origin, color, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, physical appearance, age, size, family status, relationship status, political belief, religion or lack thereof, and mental and physical ability. - -- **Be friendly and patient.** - - We want to encourage people to participate in our community in a constructive manner, so we can keep a friendly atmosphere. - This is especially important because many of our communication - tools on the Internet are low-fidelity and make it difficult to understand - each other. - Be patient, acknowledge that we are all on a learning journey, and stay supportive so that we can learn how to collaborate effectively as a group. - -- **Be considerate.** - - Your work will be used by other people, and you in turn will depend on the work of others. - Any decision you make will affect users and colleagues, and you should take those consequences into account. - Remember that we’re a world-wide community, so you might not be communicating in someone else’s primary language. - -- **Be kind.** - - Not all of us will agree all the time, but disagreement is no excuse for poor behavior and hurtful words. - We might all experience some frustration now and then, but we cannot allow that frustration to turn into - a personal attack. - It’s important to remember that a community where people feel threatened is not a productive one. - Members of our community should be kind when dealing with other members as well as with people outside the - Beman Project community. - -- **Be careful in the words that we choose and be kind to others.** - - Do not use insults or put downs. - Harassment and other exclusionary behaviors aren’t acceptable. This includes, but is not limited to: - - Violent threats or language directed against another person. - - Discriminatory jokes and language. - - Posting sexually explicit or violent material. - - Posting, or threatening to post, other people’s personally identifying - information without their explicit permission ("doxing"). - - Personal insults, especially those using racist or sexist terms. - - Unwelcome sexual attention. - - Advocating for, or encouraging, any of the above behavior. - - In general, if someone asks you to stop, then stop. Persisting after - being asked to stop is considered harassment. - -- **When we disagree, we try to understand the reason.** - - Disagreements, both social and technical, happen all the time. - It is important that we resolve disagreements and differing views constructively. - Remember that we’re different. - The strength of the project comes from its varied community: people from a wide range of backgrounds. - Different people have different perspectives on issues. - Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. - Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. - Instead, focus on helping to resolve issues and learning from mistakes. - -- **Recognize when progress has stopped, and take a step back.** - - Regardless of whether you're trying to resolve a disagreement or anything else, think - about whether you're making progress. - Sometimes messaging doesn't give time to think about a situation fully, and repeating positions can make people - defensive. - Step back for a few minutes or hours to think through the issue before responding again. - Consider pulling in another community member to give a fresh perspective. - Maybe meet over VC (video call) instead. - Switching approaches can help resume progress. - -No weapons are allowed at Beman Project events. +* **Be welcoming.** + + We strive to be a community that welcomes and supports + people of all backgrounds and identities. + This includes, but is not limited to, members of any race, ethnicity, culture, national origin, color, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, physical appearance, age, size, family status, relationship status, political belief, religion or lack thereof, and mental and physical ability. + +* **Be friendly and patient.** + + We want to encourage people to participate in our community in a constructive manner, so we can keep a friendly atmosphere. + This is especially important because many of our communication + tools on the Internet are low-fidelity and make it difficult to understand + each other. + Be patient, acknowledge that we are all on a learning journey, and stay supportive so that we can learn how to collaborate effectively as a group. + +* **Be considerate.** + + Your work will be used by other people, and you in turn will depend on the work of others. + Any decision you make will affect users and colleagues, and you should take those consequences into account. + Remember that we’re a world-wide community, so you might not be communicating in someone else’s primary language. + +* **Be kind.** + + Not all of us will agree all the time, but disagreement is no excuse for poor behavior and hurtful words. + We might all experience some frustration now and then, but we cannot allow that frustration to turn into + a personal attack. + It’s important to remember that a community where people feel threatened is not a productive one. + Members of our community should be kind when dealing with other members as well as with people outside the + Beman Project community. + +* **Be careful in the words that we choose and be kind to others.** + + Do not use insults or put downs. + Harassment and other exclusionary behaviors aren’t acceptable. This includes, but is not limited to: + + * Violent threats or language directed against another person. + * Discriminatory jokes and language. + * Posting sexually explicit or violent material. + * Posting, or threatening to post, other people’s personally identifying + information without their explicit permission ("doxing"). + * Personal insults, especially those using racist or sexist terms. + * Unwelcome sexual attention. + * Advocating for, or encouraging, any of the above behavior. + * In general, if someone asks you to stop, then stop. Persisting after + being asked to stop is considered harassment. + +* **When we disagree, we try to understand the reason.** + + Disagreements, both social and technical, happen all the time. + It is important that we resolve disagreements and differing views constructively. + Remember that we’re different. + The strength of the project comes from its varied community: people from a wide range of backgrounds. + Different people have different perspectives on issues. + Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. + Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. + Instead, focus on helping to resolve issues and learning from mistakes. + +* **Recognize when progress has stopped, and take a step back.** + + Regardless of whether you're trying to resolve a disagreement or anything else, think + about whether you're making progress. + Sometimes messaging doesn't give time to think about a situation fully, and repeating positions can make people + defensive. + Step back for a few minutes or hours to think through the issue before responding again. + Consider pulling in another community member to give a fresh perspective. + Maybe meet over VC (video call) instead. + Switching approaches can help resume progress. + +No weapons are allowed at Beman Project events. Weapons include, but are not limited to, explosives (including fireworks), guns, and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. @@ -128,33 +129,33 @@ If you believe someone is violating the code of conduct, you can report it to th **All reports will be kept confidential**, and are only used by the conduct team to address conduct issues and keep the Beman Project community safe and inclusive. -Please send reports concerning a member of the conduct team directly to other members of the conduct team. +Please send reports concerning a member of the conduct team directly to other members of the conduct team. This allows discussion of the complaint to more easily exclude the concerned member as a [special case](#special-cases). If you believe anyone is in **physical danger**, please notify appropriate law enforcement first. If you are unsure what law enforcement agency is appropriate, please include this in your report and we will attempt to notify them. -If the violation occurs at an event and requires immediate attention, you can also reach out to any of the event organizers or staff. -Event organizers and staff will be prepared to handle the incident and be able to help. +If the violation occurs at an event and requires immediate attention, you can also reach out to any of the event organizers or staff. +Event organizers and staff will be prepared to handle the incident and be able to help. If you cannot find one of the organizers, the venue staff can locate one for you. Specific event information will include detailed contact information for that event. In person reports will still be kept confidential exactly as above, but also feel free to email the conduct team, anonymously if needed. ### Filing a report -Reports can be as formal or informal as needed for the situation at hand. -If possible, please include as much information as you can. +Reports can be as formal or informal as needed for the situation at hand. +If possible, please include as much information as you can. If you feel comfortable, please consider including: -- Your contact info, so we can get in touch with you if we need to follow up. -- Names -- real, nicknames, or pseudonyms -- of any individuals involved. If - there were other witnesses besides you, please try to include them as well. -- When and where the incident occurred. Please be as specific as possible. -- Your account of what occurred, including any private chat logs or email. -- Links for any public records, including community discussions. -- Any extra context for the incident. -- Whether you believe this incident is ongoing. -- Any other information you believe we should have. +* Your contact info, so we can get in touch with you if we need to follow up. +* Names -- real, nicknames, or pseudonyms -- of any individuals involved. If + there were other witnesses besides you, please try to include them as well. +* When and where the incident occurred. Please be as specific as possible. +* Your account of what occurred, including any private chat logs or email. +* Links for any public records, including community discussions. +* Any extra context for the incident. +* Whether you believe this incident is ongoing. +* Any other information you believe we should have. ### What happens after contacting the conduct team? @@ -163,24 +164,24 @@ business day, and we will aim to respond much quicker than that. The conduct team will review the incident as soon as possible and try to determine: -- What happened and who was involved. -- Whether this event constitutes a code of conduct violation. -- Whether this is an ongoing situation, or if there is a threat to anyone’s - physical safety. +* What happened and who was involved. +* Whether this event constitutes a code of conduct violation. +* Whether this is an ongoing situation, or if there is a threat to anyone’s + physical safety. If this is determined to be an ongoing incident or a threat to physical safety, -the conduct team's immediate priority will be to protect everyone involved. +the conduct team's immediate priority will be to protect everyone involved. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe. The conduct team will try to contact other parties involved or witnessing the event to gain clarity on what happened and understand any different perspectives. -Once the conduct team has a complete account of the events they will make a decision as to how to respond. +Once the conduct team has a complete account of the events they will make a decision as to how to respond. Responses may include: -- Nothing, if no violation occurred or it has already been appropriately resolved. -- One or more [enforcement actions](#enforcement-action-guidelines). -- Involvement of relevant law enforcement if appropriate. +* Nothing, if no violation occurred or it has already been appropriately resolved. +* One or more [enforcement actions](#enforcement-action-guidelines). +* Involvement of relevant law enforcement if appropriate. If the situation is not resolved within one week, we’ll respond to the original reporter with an update and explanation. @@ -189,24 +190,24 @@ Once we’ve determined our response, we will separately contact the original re taking. We will take into account feedback from the individuals involved on the appropriateness of our response, but we don’t guarantee we’ll act on it. -After any incident, the Beman Project leads may choose to make a public statement about the incident. +After any incident, the Beman Project leads may choose to make a public statement about the incident. If that’s the case, the identities of anyone involved will remain confidential unless instructed otherwise by those individuals. ### Appealing -Only permanent resolutions, such as bans, or requests for public actions may be appealed. +Only permanent resolutions, such as bans, or requests for public actions may be appealed. To appeal a decision of the conduct team, contact the [Beman leads](governance.md) with your appeal and they will review the case. In general, it is **not** appropriate to appeal a particular decision in public -areas of GitHub or Discord. -Doing so would involve disclosure of information which should remain confidential. -Disclosing this kind of information publicly may be considered a separate and, potentially, more serious violation of the Code of Conduct. +areas of GitHub or Discord. +Doing so would involve disclosure of information which should remain confidential. +Disclosing this kind of information publicly may be considered a separate and, potentially, more serious violation of the Code of Conduct. This is not meant to limit discussion of the Code of Conduct, the conduct team itself, or the appropriateness of responses in general, but **please** refrain from mentioning specific facts about cases without the explicit permission of all parties involved. ### Special cases If a complaint is raised against a member of the Beman Project leads, they will be excluded from conduct discussion and decisions, including appeals. -They will only be included as needed for an involved party, such as to get their perspective or to notify them of decisions. +They will only be included as needed for an involved party, such as to get their perspective or to notify them of decisions. Such complaints may lead to a member's responsibilities being revoked. ## Enforcement action guidelines @@ -218,30 +219,30 @@ The conduct team may take additional action they deem appropriate for any violat involved: 1. **Correction** - - **Behavior:** Use of inappropriate language or other minor violations of - the code of conduct. - - **Action:** A private, written message providing clarity around the - nature of the violation and an explanation of why the behavior was - inappropriate. - A public apology may be requested. + * **Behavior:** Use of inappropriate language or other minor violations of + the code of conduct. + * **Action:** A private, written message providing clarity around the + nature of the violation and an explanation of why the behavior was + inappropriate. + A public apology may be requested. 1. **Warning** - - **Behavior:** A code of conduct violation through a single moderate - incident, or a series of minor violations. - - **Action:** In addition to the correction action, a temporary - restriction forbidding interaction with the people involved for a - specified period of time, including unsolicited interaction with the - conduct team. - Violating these terms may lead to a ban. + * **Behavior:** A code of conduct violation through a single moderate + incident, or a series of minor violations. + * **Action:** In addition to the correction action, a temporary + restriction forbidding interaction with the people involved for a + specified period of time, including unsolicited interaction with the + conduct team. + Violating these terms may lead to a ban. 1. **Temporary ban** - - **Behavior:** A serious violation of the code of conduct, including - sustained inappropriate behavior. - - **Action:** In addition to the warning action, a temporary ban from use - of Beman Project's community spaces for a specified period of time. External channels, such as social media, should not be used to bypass these restrictions during the temporary ban. - Violating these terms may lead to a permanent ban. + * **Behavior:** A serious violation of the code of conduct, including + sustained inappropriate behavior. + * **Action:** In addition to the warning action, a temporary ban from use + of Beman Project's community spaces for a specified period of time. External channels, such as social media, should not be used to bypass these restrictions during the temporary ban. + Violating these terms may lead to a permanent ban. 1. **Permanent ban** - - **Behavior:** Demonstrating a pattern of violation of the code of - conduct. - - **Action:** A permanent ban from use of Beman Project's community spaces. + * **Behavior:** Demonstrating a pattern of violation of the code of + conduct. + * **Action:** A permanent ban from use of Beman Project's community spaces. ## Acknowledgements diff --git a/docs/governance.md b/docs/governance.md index ec0a644..298ef19 100644 --- a/docs/governance.md +++ b/docs/governance.md @@ -39,7 +39,7 @@ Beman Leads are currently: Jeff Garland, Inbal Levi, and Eddie Nolan. ### 3.1.2 Adding and removing Beman Leads -Any member of Beman Project Leads may step down or be replaced when they are no longer able to contribute effectively. +Any member of Beman Project Leads may step down or be replaced when they are no longer able to contribute effectively. The Beman Project Leads can nominate and decide on adding, removing, or replacing members by a majority decision. ## 3.2 Beman Project Contributors: @@ -48,7 +48,7 @@ The Beman Project Contributors are individuals who help execute the facilities p ### 3.2.3 Adding and removing Beman Project Contributors -The Beman Project Leads may accept new members or remove members to the Beman Project Contributors by majority decision. There is no restriction to the number of Project Contributors. +The Beman Project Leads may accept new members or remove members to the Beman Project Contributors by majority decision. There is no restriction to the number of Project Contributors. ## 3.3 Beman Project Library Authors: @@ -56,7 +56,7 @@ The Beman Project Library Authors are the Library authors who are maintaining an ### 3.3.3 Adding and removing Beman Project Library Authors: -Beman Project Library Authors apply for acceptance into Beman Project when they have reached the point of path toward standardization. +Beman Project Library Authors apply for acceptance into Beman Project when they have reached the point of path toward standardization. This would be the submission of a Paper to the Committee, request to have a library to help write their paper, or a similar path. Removal as a Beman Project Library Author may be done when the library no longer becomes part of the Beman Project. @@ -65,8 +65,8 @@ Removal as a Beman Project Library Author may be done when the library no longer # 4.1 Consensus Decision-Making: -Beman Project strives to make decisions through consensus among the Project Contributors and the Project Leads. -Proposals on the best way to proceed should be discussed in good faith. +Beman Project strives to make decisions through consensus among the Project Contributors and the Project Leads. +Proposals on the best way to proceed should be discussed in good faith. Beman Project Leads ultimately decide the direction of the Project. # 5. Code of Conduct diff --git a/docs/images/release.notes-example01.png b/docs/images/release.notes-example01.png index 895cfdc..d9a7de8 100644 Binary files a/docs/images/release.notes-example01.png and b/docs/images/release.notes-example01.png differ diff --git a/docs/images/repository.default_branch-example01.png b/docs/images/repository.default_branch-example01.png index 723750e..366a787 100644 Binary files a/docs/images/repository.default_branch-example01.png and b/docs/images/repository.default_branch-example01.png differ diff --git a/images/badges/beman_badge-beman_library_production_ready_api_may_undergo_changes.svg b/images/badges/beman_badge-beman_library_production_ready_api_may_undergo_changes.svg index ca49b43..2b0054b 100644 --- a/images/badges/beman_badge-beman_library_production_ready_api_may_undergo_changes.svg +++ b/images/badges/beman_badge-beman_library_production_ready_api_may_undergo_changes.svg @@ -1 +1 @@ -Library status: production ready (api may undergo changes)Library statusproduction ready (api may undergo changes) \ No newline at end of file +Library status: production ready (api may undergo changes)Library statusproduction ready (api may undergo changes) \ No newline at end of file diff --git a/images/badges/beman_badge-beman_library_production_ready_stable_api.svg b/images/badges/beman_badge-beman_library_production_ready_stable_api.svg index f0bab42..eaaa640 100644 --- a/images/badges/beman_badge-beman_library_production_ready_stable_api.svg +++ b/images/badges/beman_badge-beman_library_production_ready_stable_api.svg @@ -1 +1 @@ -Library status: production ready (stable api)Library statusproduction ready (stable api) \ No newline at end of file +Library status: production ready (stable api)Library statusproduction ready (stable api) \ No newline at end of file diff --git a/images/badges/beman_badge-beman_library_retired.svg b/images/badges/beman_badge-beman_library_retired.svg index a9e1afc..eb5dd60 100644 --- a/images/badges/beman_badge-beman_library_retired.svg +++ b/images/badges/beman_badge-beman_library_retired.svg @@ -1 +1 @@ -Library status: retiredLibrary statusretired \ No newline at end of file +Library status: retiredLibrary statusretired \ No newline at end of file diff --git a/images/badges/beman_badge-beman_library_under_development.svg b/images/badges/beman_badge-beman_library_under_development.svg index 2bbf4f6..986a1a6 100644 --- a/images/badges/beman_badge-beman_library_under_development.svg +++ b/images/badges/beman_badge-beman_library_under_development.svg @@ -1 +1 @@ -Library status: under developmentLibrary statusunder development \ No newline at end of file +Library status: under developmentLibrary statusunder development \ No newline at end of file diff --git a/images/badges/cpp26.svg b/images/badges/cpp26.svg index 2d54103..11d3ccd 100644 --- a/images/badges/cpp26.svg +++ b/images/badges/cpp26.svg @@ -1 +1,7 @@ -Standard Target: C++26Standard TargetC++26 \ No newline at end of file + +Standard Target: C++26 + + + Standard Target + C++26 + diff --git a/images/badges/cpp29.svg b/images/badges/cpp29.svg index d1f2545..513e666 100644 --- a/images/badges/cpp29.svg +++ b/images/badges/cpp29.svg @@ -1 +1,7 @@ -Standard Target: C++29Standard TargetC++29 \ No newline at end of file + + Standard Target: C++29 + + + Standard Target + C++29 + diff --git a/images/banners/beman_banner.png b/images/banners/beman_banner.png index 2c1216e..31a72b5 100644 Binary files a/images/banners/beman_banner.png and b/images/banners/beman_banner.png differ diff --git a/images/banners/beman_banner_reversed.png b/images/banners/beman_banner_reversed.png index 3e712bb..1104e4d 100644 Binary files a/images/banners/beman_banner_reversed.png and b/images/banners/beman_banner_reversed.png differ diff --git a/images/beman_flow-beman_library_maturity_model.png b/images/beman_flow-beman_library_maturity_model.png index 61d8533..a71b4b7 100644 Binary files a/images/beman_flow-beman_library_maturity_model.png and b/images/beman_flow-beman_library_maturity_model.png differ diff --git a/images/logos/beman_logo-beman_library_production_ready_api_may_undergo_changes.png b/images/logos/beman_logo-beman_library_production_ready_api_may_undergo_changes.png index 3160224..70f15b1 100644 Binary files a/images/logos/beman_logo-beman_library_production_ready_api_may_undergo_changes.png and b/images/logos/beman_logo-beman_library_production_ready_api_may_undergo_changes.png differ diff --git a/images/logos/beman_logo-beman_library_production_ready_stable_api.png b/images/logos/beman_logo-beman_library_production_ready_stable_api.png index ece8f1d..0938ba7 100644 Binary files a/images/logos/beman_logo-beman_library_production_ready_stable_api.png and b/images/logos/beman_logo-beman_library_production_ready_stable_api.png differ diff --git a/images/logos/beman_logo-beman_library_retired.png b/images/logos/beman_logo-beman_library_retired.png index 8a7bb78..51850d0 100644 Binary files a/images/logos/beman_logo-beman_library_retired.png and b/images/logos/beman_logo-beman_library_retired.png differ diff --git a/images/logos/beman_logo-beman_library_under_development.png b/images/logos/beman_logo-beman_library_under_development.png index 40367b2..4ac28bc 100644 Binary files a/images/logos/beman_logo-beman_library_under_development.png and b/images/logos/beman_logo-beman_library_under_development.png differ diff --git a/images/logos/beman_logo.png b/images/logos/beman_logo.png index 1042e5e..e729f12 100644 Binary files a/images/logos/beman_logo.png and b/images/logos/beman_logo.png differ diff --git a/images/logos/beman_logo_reversed.png b/images/logos/beman_logo_reversed.png index fc338ba..8980e58 100644 Binary files a/images/logos/beman_logo_reversed.png and b/images/logos/beman_logo_reversed.png differ diff --git a/images/qr/beman-qr.png b/images/qr/beman-qr.png index a26305e..15df5f5 100644 Binary files a/images/qr/beman-qr.png and b/images/qr/beman-qr.png differ diff --git a/static/docs/images/release.notes-example01.png b/static/docs/images/release.notes-example01.png index 895cfdc..d9a7de8 100644 Binary files a/static/docs/images/release.notes-example01.png and b/static/docs/images/release.notes-example01.png differ diff --git a/static/docs/images/repository.default_branch-example01.png b/static/docs/images/repository.default_branch-example01.png index 723750e..366a787 100644 Binary files a/static/docs/images/repository.default_branch-example01.png and b/static/docs/images/repository.default_branch-example01.png differ diff --git a/static/images/badges/beman_badge-beman_library_production_ready_api_may_undergo_changes.svg b/static/images/badges/beman_badge-beman_library_production_ready_api_may_undergo_changes.svg index ca49b43..2b0054b 100644 --- a/static/images/badges/beman_badge-beman_library_production_ready_api_may_undergo_changes.svg +++ b/static/images/badges/beman_badge-beman_library_production_ready_api_may_undergo_changes.svg @@ -1 +1 @@ -Library status: production ready (api may undergo changes)Library statusproduction ready (api may undergo changes) \ No newline at end of file +Library status: production ready (api may undergo changes)Library statusproduction ready (api may undergo changes) \ No newline at end of file diff --git a/static/images/badges/beman_badge-beman_library_production_ready_stable_api.svg b/static/images/badges/beman_badge-beman_library_production_ready_stable_api.svg index f0bab42..eaaa640 100644 --- a/static/images/badges/beman_badge-beman_library_production_ready_stable_api.svg +++ b/static/images/badges/beman_badge-beman_library_production_ready_stable_api.svg @@ -1 +1 @@ -Library status: production ready (stable api)Library statusproduction ready (stable api) \ No newline at end of file +Library status: production ready (stable api)Library statusproduction ready (stable api) \ No newline at end of file diff --git a/static/images/badges/beman_badge-beman_library_retired.svg b/static/images/badges/beman_badge-beman_library_retired.svg index a9e1afc..eb5dd60 100644 --- a/static/images/badges/beman_badge-beman_library_retired.svg +++ b/static/images/badges/beman_badge-beman_library_retired.svg @@ -1 +1 @@ -Library status: retiredLibrary statusretired \ No newline at end of file +Library status: retiredLibrary statusretired \ No newline at end of file diff --git a/static/images/badges/beman_badge-beman_library_under_development.svg b/static/images/badges/beman_badge-beman_library_under_development.svg index 2bbf4f6..986a1a6 100644 --- a/static/images/badges/beman_badge-beman_library_under_development.svg +++ b/static/images/badges/beman_badge-beman_library_under_development.svg @@ -1 +1 @@ -Library status: under developmentLibrary statusunder development \ No newline at end of file +Library status: under developmentLibrary statusunder development \ No newline at end of file diff --git a/static/images/badges/cpp26.svg b/static/images/badges/cpp26.svg index 2d54103..11d3ccd 100644 --- a/static/images/badges/cpp26.svg +++ b/static/images/badges/cpp26.svg @@ -1 +1,7 @@ -Standard Target: C++26Standard TargetC++26 \ No newline at end of file + +Standard Target: C++26 + + + Standard Target + C++26 + diff --git a/static/images/badges/cpp29.svg b/static/images/badges/cpp29.svg index d1f2545..513e666 100644 --- a/static/images/badges/cpp29.svg +++ b/static/images/badges/cpp29.svg @@ -1 +1,7 @@ -Standard Target: C++29Standard TargetC++29 \ No newline at end of file + + Standard Target: C++29 + + + Standard Target + C++29 + diff --git a/static/images/banners/beman_banner.png b/static/images/banners/beman_banner.png index 2c1216e..31a72b5 100644 Binary files a/static/images/banners/beman_banner.png and b/static/images/banners/beman_banner.png differ diff --git a/static/images/banners/beman_banner_reversed.png b/static/images/banners/beman_banner_reversed.png index 3e712bb..1104e4d 100644 Binary files a/static/images/banners/beman_banner_reversed.png and b/static/images/banners/beman_banner_reversed.png differ diff --git a/static/images/beman_flow-beman_library_maturity_model.png b/static/images/beman_flow-beman_library_maturity_model.png index 61d8533..a71b4b7 100644 Binary files a/static/images/beman_flow-beman_library_maturity_model.png and b/static/images/beman_flow-beman_library_maturity_model.png differ diff --git a/static/images/logos/beman_logo-beman_library_production_ready_api_may_undergo_changes.png b/static/images/logos/beman_logo-beman_library_production_ready_api_may_undergo_changes.png index 3160224..70f15b1 100644 Binary files a/static/images/logos/beman_logo-beman_library_production_ready_api_may_undergo_changes.png and b/static/images/logos/beman_logo-beman_library_production_ready_api_may_undergo_changes.png differ diff --git a/static/images/logos/beman_logo-beman_library_production_ready_stable_api.png b/static/images/logos/beman_logo-beman_library_production_ready_stable_api.png index ece8f1d..0938ba7 100644 Binary files a/static/images/logos/beman_logo-beman_library_production_ready_stable_api.png and b/static/images/logos/beman_logo-beman_library_production_ready_stable_api.png differ diff --git a/static/images/logos/beman_logo-beman_library_retired.png b/static/images/logos/beman_logo-beman_library_retired.png index 8a7bb78..51850d0 100644 Binary files a/static/images/logos/beman_logo-beman_library_retired.png and b/static/images/logos/beman_logo-beman_library_retired.png differ diff --git a/static/images/logos/beman_logo-beman_library_under_development.png b/static/images/logos/beman_logo-beman_library_under_development.png index 40367b2..4ac28bc 100644 Binary files a/static/images/logos/beman_logo-beman_library_under_development.png and b/static/images/logos/beman_logo-beman_library_under_development.png differ diff --git a/static/images/logos/beman_logo.png b/static/images/logos/beman_logo.png index 1042e5e..e729f12 100644 Binary files a/static/images/logos/beman_logo.png and b/static/images/logos/beman_logo.png differ diff --git a/static/images/logos/beman_logo_reversed.png b/static/images/logos/beman_logo_reversed.png index fc338ba..8980e58 100644 Binary files a/static/images/logos/beman_logo_reversed.png and b/static/images/logos/beman_logo_reversed.png differ diff --git a/static/images/qr/beman-qr.png b/static/images/qr/beman-qr.png index a26305e..15df5f5 100644 Binary files a/static/images/qr/beman-qr.png and b/static/images/qr/beman-qr.png differ