Skip to content

Latest commit

 

History

History
35 lines (25 loc) · 1.77 KB

CONTRIBUTING.md

File metadata and controls

35 lines (25 loc) · 1.77 KB

Contributing to testingconferences.org

First off, thank you for considering contributing! It’s people like you who keep this list accurate and useful for the testing community.

How Can I Contribute?

1. Adding a New Conference

The most common way to help is by adding a conference that isn't on the list yet or updating one that is.

  • Search the current list to make sure it isn't already there.
  • Open a Pull Request (PR) adding the conference to the relevant data file.
  • Ensure you follow our data schema (see the README.md for field requirements).

2. Reporting an Issue

If you find a broken link, an incorrect date, or a bug on the site:

  • Check the Footer: Find the Site Version in the footer of the website.
  • Open an Issue: Include the version number and a description of the error.

3. Improving the Site (DX/Quality)

We are currently working through our ROADMAP.md to improve site quality and developer experience. If you want to help with Lighthouse scores, build scripts, or automation, please check the roadmap for "Open" tasks.

Pull Request Guidelines

To help us review your changes quickly, please follow these steps:

  1. Fork the repo and create your branch from main.
  2. Test your changes locally to ensure the build passes.
  3. Reference Issues: If your PR fixes a bug, include Closes #123 in the description.
  4. Style: Please ensure your code/data follows the project's formatting (Prettier/ESLint).

Code of Conduct

By participating in this project, you agree to abide by our Code of Conduct [link to file or text]. We strive to maintain a welcoming and inclusive environment.

Need help? If you have questions about how to contribute, feel free to open a "Question" issue and we'll help you get started!