The following is a set of guidelines for contributing to Textile-related projects, which are hosted in the Textile organization. These are just guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
Note that Textile is an evolving project, so expect things to change over time as the team learns, listens and refines how we work with the community.
What should I know before I get started?
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
Generally, Textile projects can be initialized with something like:
Step 1: git clone this repo:
Step 2: cd to the cloned repo:
Step 3: Install the Application with yarn or npm i
See each indiviual project's README for details.
This section guides you through submitting a bug report for any Textile repo. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
Before creating bug reports, please check this list as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible.
Perform a cursory search to see if the problem has already been reported. If it does exist, add a 👍 to the issue to indicate this is also an issue for you, and add a comment to the existing issue if there is extra information you can contribute.
Bugs are tracked as GitHub issues.
Simply create an issue on the Textile issue tracker.
The information we are interested in includes:
- details about your environment - which build, which operating system
- details about reproducing the issue - what steps to take, what happens, how often it happens
- other relevant information - log files, screenshots, etc.
This section guides you through submitting an enhancement suggestion for this project, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion 📝 and find related suggestions 🔎.
Before creating enhancement suggestions, please check this list as you might find out that you don't need to create one. When you are creating an enhancement suggestion, please include as many details as possible. Include the steps that you imagine you would take if the feature you're requesting existed.
Perform a cursory search to see if the enhancement has already been suggested. If it has, add a :thumbsup: to indicate your interest in it, or comment if there is additional information you would like to add.
Enhancement suggestions are tracked as GitHub issues.
Simply create an issue on the Textile issue tracker and provide the following information:
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as much detail as possible. This additional context helps the maintainers to understand the enhancement from your perspective
- Explain why this enhancement would be useful to Textile users.
- Include screenshots and animated GIFs if relevant to help you demonstrate the steps or point out the part of Textile which the suggestion is related to.
- List some other applications where this enhancement exists, if applicable.
More to be added