diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS deleted file mode 100644 index f3206485..00000000 --- a/.github/CODEOWNERS +++ /dev/null @@ -1,6 +0,0 @@ -# These are the default owners for everything in -# webpack-contrib -@webpack-contrib/org-maintainers - -# Add repository specific users / groups -# below here for libs that are not maintained by the org. diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md deleted file mode 100644 index bda82616..00000000 --- a/.github/CONTRIBUTING.md +++ /dev/null @@ -1,156 +0,0 @@ -# Contributing in @webpack-contrib - -We'd always love contributions to further improve the webpack / webpack-contrib ecosystem! -Here are the guidelines we'd like you to follow: - -- [Questions and Problems](#question) -- [Issues and Bugs](#issue) -- [Feature Requests](#feature) -- [Pull Request Submission Guidelines](#submit-pr) -- [Commit Message Conventions](#commit) - -## Got a Question or Problem? - -Please submit support requests and questions to StackOverflow using the tag [[webpack]](http://stackoverflow.com/tags/webpack). -StackOverflow is better suited for this kind of support though you may also inquire in [Webpack Gitter](https://gitter.im/webpack/webpack). -The issue tracker is for bug reports and feature discussions. - -## Found an Issue or Bug? - -Before you submit an issue, please search the issue tracker, an issue for your problem may already exist, and the discussion might inform you of workarounds readily available. - -We want to fix all the issues as soon as possible, but before fixing a bug, we need to reproduce and confirm it. In order to reproduce bugs, we ask that you provide a minimal reproduction scenario (GitHub repo or failing test case). Having a live, reproducible scenario gives us a wealth of important information without going back & forth to you with additional questions like: - -- version of Webpack used -- version of the loader / plugin you are creating a bug report for -- the use-case that fails - -A minimal reproduce scenario allows us to quickly confirm a bug (or point out config problems) as well as confirm that we are fixing the right problem. - -We will be insisting on a minimal reproduction scenario in order to save the maintainers' time and ultimately be able to fix more bugs. We understand that sometimes it might be hard to extract essential bits of code from a larger codebase, but we really need to isolate the problem before we can fix it. - -Unfortunately, we are unable to investigate or fix bugs without a minimal reproduction, so if we don't hear back from you, we may have to close an issue that doesn't have enough info to be reproduced. - -## Feature Requests? - -You can _request_ a new feature by creating an issue on GitHub. - -If you would like to _implement_ a new feature yourself, please **first submit an issue** with a proposal to ensure the idea aligns with the goals of the project. - -## Pull Request Submission Guidelines - -Before you submit your Pull Request (PR) consider the following guidelines: - -- Search GitHub for an open or closed PR related to your submission to avoid duplicating effort. -- Commit your changes using a descriptive commit message that follows our [commit message conventions](#commit). This is important because release notes are automatically generated from these messages. -- Complete the `Pull Request Template`. Pull requests that ignore the template will not be reviewed. -- Please sign the `Contributor License Agreement (CLA)` when you open your pull request. We cannot accept your contribution without it. Be sure to sign using the primary email address associated with your local and GitHub account. - -## Webpack Contrib Commit Conventions - -Each commit message consists of a **header**, a **body** and a **footer**. The header has a special -format that includes a **type**, a **scope** and a **subject**: - -``` -(): - - - -