<commit_before># Contributing

Welcome! We're super excited that you are interested in contributing to Braid.

There are a lot of ways you can be involved - not just coding - and all are valuable.


## Say Hello

If you'd like to contribute, jump into the [Braid group on Braid](https://braid.chat/braid) and say hello. We can help match you with a good task, point you to resources and help you if you run into any problems.

@jamesnvc and @rafd have a standing offer to remotely pair with anyone on Braid (via [Screenhero](https://screenhero.com/) or [Teamviewer](https://www.teamviewer.com/)). Send a message on Braid chat if you'd like to take us up on it.

We want to make contributing to Braid as painless as possible (and, ideally, gratifying). Please let us know how we can improve.


## Giving Feedback

We want Braid to be useful to you, so we highly value your feedback.

Right now, we're especially looking for feedback on:

  - the first-time user experience
  - the first-time contributor experience
  - the first-time developer experience

You can give us feedback [Braid](https://braid.chat/braid) or via [Github Issues](https://github.com/braidchat/planning/issues).


### Reporting Issues

Found a bug or some other issue? Let us know on [Braid](https://braid.chat/braid) or create a [Github Issue](https://github.com/braidchat/planning/issues).

If it's a security issue, please do not post it publicly, and instead, report it to us via email (see our [Responsible Disclosure Policy](./responsible-disclosure-policy.md).

When reporting an issue, the following information helps us track it down and fix it faster:

  - steps to reproduce the issue
  - expected vs observed behaviour
  - relevant error messages and/or screenshots
  - possible fixes


### Contributing Feature Ideas

If you have an idea for a new feature or change to Braid, we'd love to hear it. Let us know on [Braid](https://braid.chat/braid) or create a [Github Issue](https://github.com/braidchat/planning/issues).


### Feedback and Voting on Planned Features

There are a lot of ideas in the [Braid Planning Repo](https://github.com/braidchat/planning/issues), and your feedback can help us prioritize which ones to address. Give the existing ideas a look, and feel free to leave a comment or a :+1:.


### Triaging and Organizing Issues

The [Braid Planning Repo](https://github.com/braidchat/planning/issues) needs help staying organized (tagging issues, removing duplicates, removing stales issues, etc.) and if that sounds interesting to you, let us know.


## Writing

### Improving Documentation for Developers

### Improving Guides for Users

### Translating Braid to Other Languages


## Sharing


## Sponsoring

### Paid Hosting

### Gratipay

### Bountysource



## Coding

(./contributing/coding.md)


### Adressing "Help Wanted" Issues

We've been tagging issues that are ideal for first-time committers with the [`help wanted`](https://github.com/braidchat/planning/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22help%20wanted%22) tag on Braid Meta. Most of these issues can be addressed with minor code changes that don't require knowledge of the full system.


### Contributing to Braid Core


### Writing End-to-End Tests


### Developing Integrations


<commit_msg>Remove broken link to non-existent file<commit_after># Contributing

Welcome! We're super excited that you are interested in contributing to Braid.

There are a lot of ways you can be involved - not just coding - and all are valuable.


## Say Hello

If you'd like to contribute, jump into the [Braid group on Braid](https://braid.chat/braid) and say hello. We can help match you with a good task, point you to resources and help you if you run into any problems.

@jamesnvc and @rafd have a standing offer to remotely pair with anyone on Braid (via [Screenhero](https://screenhero.com/) or [Teamviewer](https://www.teamviewer.com/)). Send a message on Braid chat if you'd like to take us up on it.

We want to make contributing to Braid as painless as possible (and, ideally, gratifying). Please let us know how we can improve.


## Giving Feedback

We want Braid to be useful to you, so we highly value your feedback.

Right now, we're especially looking for feedback on:

  - the first-time user experience
  - the first-time contributor experience
  - the first-time developer experience

You can give us feedback [Braid](https://braid.chat/braid) or via [Github Issues](https://github.com/braidchat/planning/issues).


### Reporting Issues

Found a bug or some other issue? Let us know on [Braid](https://braid.chat/braid) or create a [Github Issue](https://github.com/braidchat/planning/issues).

If it's a security issue, please do not post it publicly, and instead, report it to us via email (see our [Responsible Disclosure Policy](./responsible-disclosure-policy.md).

When reporting an issue, the following information helps us track it down and fix it faster:

  - steps to reproduce the issue
  - expected vs observed behaviour
  - relevant error messages and/or screenshots
  - possible fixes


### Contributing Feature Ideas

If you have an idea for a new feature or change to Braid, we'd love to hear it. Let us know on [Braid](https://braid.chat/braid) or create a [Github Issue](https://github.com/braidchat/planning/issues).


### Feedback and Voting on Planned Features

There are a lot of ideas in the [Braid Planning Repo](https://github.com/braidchat/planning/issues), and your feedback can help us prioritize which ones to address. Give the existing ideas a look, and feel free to leave a comment or a :+1:.


### Triaging and Organizing Issues

The [Braid Planning Repo](https://github.com/braidchat/planning/issues) needs help staying organized (tagging issues, removing duplicates, removing stales issues, etc.) and if that sounds interesting to you, let us know.


## Writing

### Improving Documentation for Developers

### Improving Guides for Users

### Translating Braid to Other Languages


## Sharing


## Sponsoring

### Paid Hosting

### Gratipay

### Bountysource


## Coding

### Adressing "Help Wanted" Issues

We've been tagging issues that are ideal for first-time committers with the [`help wanted`](https://github.com/braidchat/planning/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22help%20wanted%22) tag on Braid Meta. Most of these issues can be addressed with minor code changes that don't require knowledge of the full system.


### Contributing to Braid Core


### Writing End-to-End Tests


### Developing Integrations



{'fraction_non_alphanumeric': 0.087492391965916, 'fraction_numerical': 0.005782105903834449, 'mean_word_length': 4.245810055865922, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 24, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2444099', 'n_tokens_mistral': 1944, 'n_tokens_neox': 1834, 'n_words': 850}