Add 'temp-packages/' from commit '39314f7068fb1ac5f7206ef01b0cf561b30…

…bfe90'

git-subtree-dir: temp-packages
git-subtree-mainline: 04c0ea2
git-subtree-split: 39314f7

temp-packages/.editorconfig

@@ -0,0 +1,21 @@
+# This file is for unifying the coding style for different editors and IDEs
+# editorconfig.org
+
+# WordPress Coding Standards
+# https://make.wordpress.org/core/handbook/coding-standards/
+
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = tab
+
+[*.yml]
+indent_style = space
+indent_size = 2
+
+[*.md]
+trim_trailing_whitespace = false

temp-packages/.gitignore

@@ -0,0 +1,9 @@
+node_modules/
+
+/packages/*/build/
+/packages/*/build-module/
+/packages/*/build-browser/
+
+coverage/
+
+package-lock.json

temp-packages/.npmrc

@@ -0,0 +1 @@
+package-lock=false

temp-packages/.nvmrc

@@ -0,0 +1 @@
+v8

temp-packages/.travis.yml

@@ -0,0 +1,16 @@
+sudo: false
+language: node_js
+node_js:
+ - '8'
+
+script:
+ - npm run test:coverage-ci
+
+notifications:
+ slack:
+ rooms:
+ secure: p6bTA+Tfevko/4mdKjSB1xv8cCKJbMut6o6J49X2nXecNdiZ3tseA0ctbXsMgsQgXoU74imLtNOqC5ufs83TLy4D+J4vnfJ8XPCAecTZtq3qFl/8/QFB4ozxyVfVIaxhIVDJGcrQOWARB/NLk7v1arCHjyD3eVabAPGfwhtRxOhoD2c7B3mhQq0qNh1q7MHhWPWG8bmpbZeZfjvheRjpj6uNh7unxg3sY3AiMyg//W0vgub/LfZwhpS1YCbUmKhmmmdT3wqBH4+Q3LMcNN2tcVfBI/ajhR9akpuhxRorO9/a49WQ5HeHEPAbAC4bjk0/V9XiFaiKYk+vJowEX8i1mladvBiYQcLfUPl2tg2zxgAs9aXigMLd+6F9rm2tx039wKp7zKAcNioR5IcJcLrmOarsJivVyiO/DBC0IsJ9GPCk5Me6GV5dIOOCG/IywW3sF5FMbcBGZaJEf2AV+m2eETbXXcJyOyci5OCVr2oaAdaphf+kzesSt5Ir05I6kxDBh6czRHkBJ+KoLtGpnO+4YrMEuPPpZSqe5BCKzrLixggcGfk3OLUek1+DVTfdGDwUZf8p7kmXYm9IWqJ36kdg1vI9B5aZh6+ZW0RXqZeAImhn5mkkQTmyoTmX0uo8HvrBtAOQI9Gss9UkP5BYwpmxTBGvgCqwwCRyDKZAF2GFGBU=
+ on_start: never
+ on_success: change
+ on_failure: always
+ on_pull_requests: false

temp-packages/CONTRIBUTING.md

@@ -0,0 +1,83 @@
+# Contributing
+
+## Workflow
+
+A good workflow is to work directly in this repo, branch off `master`, and submit your changes as a pull request.
+
+Ideally name your branches with prefixes and descriptions, like this: `[type]/[change]`. A good prefix would be:
+
+- `add/` = add a new feature
+- `try/` = experimental feature, "tentatively add"
+- `update/` = update an existing feature
+
+For example, `add/foo-module` means you're working on adding a new foo module.
+
+You can pick among all the <a href="https://github.com/WordPress/packages/issues">issues</a>, or some of the ones labelled <a href="https://github.com/WordPress/packages/labels/Good%20First%20Issue">Good First Issue</a>.
+
+## Developing
+
+Be sure to have [Node.js](https://nodejs.org/en/) installed first. You should be running a Node.js version matching the [current active LTS release](https://github.com/nodejs/Release#release-schedule) or newer. You can check this with `node -v`.
+
+Make sure that npm is installed with version >= `5.0.0` using `npm -v`.
+
+### Setup
+
+```sh
+$ git clone https://github.com/WordPress/packages.git
+$ cd packages
+$ npm install
+```
+
+### Testing
+
+In order to run the tests:
+
+```sh
+$ npm test
+
+# If you want to watch for changes
+$ npm run test:watch
+
+# If you want to check code coverage
+$ npm run test:coverage
+```
+
+## Releasing
+
+This repository uses [lerna](https://lernajs.io) to manage and release the packages. Lerna automatically releases all the outdated packages. To check which packages are outdated and will be released, type `npm run publish:check`.
+
+If you have the ability to publish packages, you _must_ have [2FA enabled](https://docs.npmjs.com/getting-started/using-two-factor-authentication) on your npmjs.com account.
+
+### Before releasing
+
+Confirm that you're logged into npm, by running `npm whoami`. If you're not logged in, run `npm adduser` to login.
+
+If you're publishing a new package, ensure that its `package.json` file contains the correct `publishConfig` settings:
+
+```json
+ "publishConfig": {
+ "access": "public"
+ }
+```
+
+### Development release
+
+Run the following command to release a dev version of the outdated packages, replacing "123456" with your 2FA code. Make sure you're using a freshly generated 2FA code, rather than one that's about to timeout. This is a little cumbersome, but helps to prevent the release process from dying mid-deploy.
+
+```bash
+NPM_CONFIG_OTP=123456 npm run publish:dev
+```
+
+Lerna will ask you which version number you want to choose for each package. For a `dev` release, you'll more likely want to choose the "prerelease" option. Repeat the same for all the outdated packages and confirm your version updates.
+
+Lerna will then publish to `npm`, commit the `package.json` changes and create the git tags.
+
+### Production release
+
+To release a production version for the outdated packages, run the following command, replacing "123456" with your (freshly generated, as above) 2FA code:
+
+```bash
+NPM_CONFIG_OTP=123456 npm run publish:prod
+```
+
+Choose the correct version (minor, major or patch) and confirm your choices and let Lerna do its magic.