├── README.md ├── .github └── FUNDING.yml ├── SECURITY.md └── CODE_OF_CONDUCT.md /README.md: -------------------------------------------------------------------------------- 1 | # Organisation wide GitHub configuration files 2 | 3 | Pushed to: 4 | - https://github.com/gleam-experiments/.github 5 | - https://github.com/gleam-lang/.github 6 | 7 | ```sh 8 | git remote set-url --add --push origin git@github.com:gleam-experiments/.github.git 9 | git remote set-url --add --push origin git@github.com:gleam-lang/.github.git 10 | ``` 11 | -------------------------------------------------------------------------------- /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | github: [lpil, giacomocavalieri, GearsDatapacks] 4 | liberapay: gleam 5 | # patreon: # Replace with a single Patreon username 6 | # open_collective: # Replace with a single Open Collective username 7 | # ko_fi: # Replace with a single Ko-fi username 8 | # tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel 9 | # community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry 10 | # liberapay: # Replace with a single Liberapay username 11 | # issuehunt: # Replace with a single IssueHunt username 12 | # otechie: # Replace with a single Otechie username 13 | # custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2'] 14 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | [![OpenSSF Vulnerability Disclosure](https://img.shields.io/badge/OpenSSF-Vulnerability_Disclosure-green)][openssf-cvd-finders-guide] 4 | [![GitHub Report](https://img.shields.io/badge/GitHub-Security_Advisories-blue)][github-private-vulnerability-reporting] 5 | [![Email Report](https://img.shields.io/badge/Email-security%40gleam.run-blue)][email] 6 | 7 | We take the security of this software seriously and are committed to ensuring 8 | that any vulnerabilities are addressed promptly and effectively. 9 | 10 | This repository follows the OpenSSF 11 | [Vulnerability Disclosure guide][openssf-cvd-guide]. 12 | You can learn more about it in the [Finders Guide][openssf-cvd-finders-guide]. 13 | 14 | ## Reporting Security Issues 15 | 16 | If you believe you have found a security vulnerability in this repository, 17 | please report it via [GitHub Security Vulnerability Reporting][github-private-vulnerability-reporting] 18 | or via email to [`security@gleam.run`][email] if that is more suitable for you. 19 | 20 | **Please do not report vulnerabilities through public channels** such as GitHub 21 | issues, discussions, or pull requests, to avoid exposing the details of the 22 | issue before it has been properly addressed. 23 | 24 | We don't implement a bug bounty program or bounty rewards, but will work with 25 | you to ensure that your findings get the appropriate handling. 26 | 27 | When reporting a vulnerability, please include as much detail as possible to 28 | help us triage and resolve the issue efficiently. Information that will be 29 | specially helpful includes: 30 | 31 | - The type of issue (e.g., buffer overflow, SQL injection, cross-site scripting, etc.) 32 | - Full paths of source file(s) related to the issue 33 | - The location of the affected source code (e.g., tag, branch, commit, or direct URL) 34 | - Any special configuration required to reproduce the issue 35 | - Step-by-step instructions to reproduce the issue 36 | - Proof-of-concept or exploit code (if available) 37 | - The potential impact, including how the issue might be exploited by an attacker 38 | 39 | Our vulnerability management team will respond within 3 working days of your 40 | report. If the issue is confirmed as a vulnerability, we will open a Security 41 | Advisory. This project follows a 90-day disclosure timeline. 42 | 43 | If you have any questions about reporting security issues, please contact our 44 | vulnerability management team at [`security@gleam.run`][email]. 45 | 46 | [openssf-cvd-guide]: https://github.com/ossf/oss-vulnerability-guide/tree/main 47 | [openssf-cvd-finders-guide]: https://github.com/ossf/oss-vulnerability-guide/blob/main/finder-guide.md 48 | [github-private-vulnerability-reporting]: https://github.com/gleam-lang/gleam/security/advisories/new 49 | [email]: mailto:security@gleam.run 50 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 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 louis at lpil.uk. 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 [Contributor Covenant][homepage], 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 | --------------------------------------------------------------------------------