├── .github └── ISSUE_TEMPLATE │ ├── question.md │ ├── config.yml │ ├── project_lead.md │ ├── pypi_release.md │ ├── website.md │ └── proposal.md ├── .pre-commit-config.yaml ├── README.md └── CODE_OF_CONDUCT.md /.github/ISSUE_TEMPLATE/question.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Question 3 | about: Anything else. 4 | title: '' 5 | labels: question 6 | assignees: '' 7 | 8 | --- 9 | 10 | 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false 2 | contact_links: 3 | - name: Security Issues 4 | url: https://jazzband.co/security 5 | about: Please report security vulnerabilities here. 6 | -------------------------------------------------------------------------------- /.pre-commit-config.yaml: -------------------------------------------------------------------------------- 1 | repos: 2 | - repo: https://github.com/pre-commit/pre-commit-hooks 3 | rev: v4.4.0 4 | hooks: 5 | - id: check-merge-conflict 6 | - id: check-yaml 7 | 8 | ci: 9 | autoupdate_schedule: quarterly 10 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Roadies 2 | 3 | This is just a placeholder repo for some of the [Jazzband's roadies](https://jazzband.co/roadies): 4 | 5 | - [Issues tracker](https://github.com/jazzband/help/issues) ([New issue](https://github.com/jazzband/help/issues/new)) 6 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/project_lead.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Project lead 3 | about: Request to be a project lead of an existing Jazzband project. 4 | title: 'Project Lead: ' 5 | labels: lead 6 | assignees: '' 7 | 8 | --- 9 | 10 | # Project lead request 11 | 12 | Please explain why you'd fit the role of project lead for this project. Explain any prior involvement in the project. If there are existing project leads, they should also agree to this change. 13 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/pypi_release.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: PyPI Release 3 | about: Request a new release of a project to PyPI. 4 | title: 'PyPI Release: ' 5 | labels: pypi 6 | assignees: '' 7 | 8 | --- 9 | 10 | # PyPI Release 11 | Please read the information about [releases](https://jazzband.co/about/releases) on the website before submitting an issue. In particular, if a project already has project leads assigned, then you'd be better off creating an issue in the individual project, and asking the leads to do a release. 12 | 13 | In the event there are no project leads, you're in the right place! Please link the project for which you'd like to create a release. 14 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/website.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Website 3 | about: Report a bug on the website 4 | title: Bug found on website 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Browser [e.g. chrome, safari] 29 | - Version [e.g. 22] 30 | 31 | **Smartphone (please complete the following information):** 32 | - Device: [e.g. iPhone6] 33 | - OS: [e.g. iOS8.1] 34 | - Browser [e.g. stock browser, safari] 35 | - Version [e.g. 22] 36 | 37 | **Additional context** 38 | Add any other context about the problem here. 39 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/proposal.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Proposal 3 | about: Create a proposal to move your package to Jazzband. 4 | title: 'Proposal: ' 5 | labels: proposal 6 | assignees: '' 7 | 8 | --- 9 | 10 | # Project Proposal 11 | 12 | Please fill in the details below to confirm you adhere to the [Jazzband Guidelines](https://jazzband.co/about/guidelines), and also add the package name to the issue title. 13 | 14 | ## Project Details 15 | Enter your project name here. 16 | 17 | ## Project Description 18 | Briefly describe your project, and your reasons for requesting a transfer here. 19 | 20 | ## Project Leads 21 | Please list anyone who you would like to be made a project lead. 22 | 23 | ## Confirmation of Guidelines 24 | 25 | Please confirm the following: 26 | 27 | - [ ] I am the project owner, or have permission from the project owner, to request a transfer. 28 | 29 | - [ ] This project is a [viable candidate](https://jazzband.co/about/guidelines#viability) for Jazzband. 30 | 31 | - [ ] This project fulfills the [documentation requirements](https://jazzband.co/about/guidelines#documentation). 32 | 33 | - [ ] This project is [tested](https://jazzband.co/about/guidelines#tests). 34 | 35 | - [ ] I am happy to adopt Jazzband's [code of conduct](https://jazzband.co/about/guidelines#conduct) in this project. 36 | 37 | - [ ] I am happy to include Jazzband's [contributing guidelines](https://jazzband.co/about/guidelines#contributing-guidelines) in this project. 38 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | As contributors and maintainers of the Jazzband projects, and in the interest of 4 | fostering an open and welcoming community, we pledge to respect all people who 5 | contribute through reporting issues, posting feature requests, updating documentation, 6 | submitting pull requests or patches, and other activities. 7 | 8 | We are committed to making participation in the Jazzband a harassment-free experience 9 | for everyone, regardless of the level of experience, gender, gender identity and 10 | expression, sexual orientation, disability, personal appearance, body size, race, 11 | ethnicity, age, religion, or nationality. 12 | 13 | Examples of unacceptable behavior by participants include: 14 | 15 | - The use of sexualized language or imagery 16 | - Personal attacks 17 | - Trolling or insulting/derogatory comments 18 | - Public or private harassment 19 | - Publishing other's private information, such as physical or electronic addresses, 20 | without explicit permission 21 | - Other unethical or unprofessional conduct 22 | 23 | The Jazzband roadies have the right and responsibility to remove, edit, or reject 24 | comments, commits, code, wiki edits, issues, and other contributions that are not 25 | aligned to this Code of Conduct, or to ban temporarily or permanently any contributor 26 | for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 27 | 28 | By adopting this Code of Conduct, the roadies commit themselves to fairly and 29 | consistently applying these principles to every aspect of managing the jazzband 30 | projects. Roadies who do not follow or enforce the Code of Conduct may be permanently 31 | removed from the Jazzband roadies. 32 | 33 | This code of conduct applies both within project spaces and in public spaces when an 34 | individual is representing the project or its community. 35 | 36 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by 37 | contacting the roadies at `roadies@jazzband.co`. All complaints will be reviewed and 38 | investigated and will result in a response that is deemed necessary and appropriate to 39 | the circumstances. Roadies are obligated to maintain confidentiality with regard to the 40 | reporter of an incident. 41 | 42 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 43 | 1.3.0, available at [https://contributor-covenant.org/version/1/3/0/][version] 44 | 45 | [homepage]: https://contributor-covenant.org 46 | [version]: https://contributor-covenant.org/version/1/3/0/ 47 | --------------------------------------------------------------------------------