Initial commit of wp-calypso

Props to the following people whose hard work has gotten us here.

@aduth
@mtias
@scruffian
@timmyc
@rads
@rralian
@drewblaisdell
@blowery
@stephanethomas
@ebinnion
@gcorne
@lezama
@bluefuton
@retrofox
@ehg
@dzver
@isaackeyet
@enej
@kellychoffman
@johnHackworth
@jonathansadowski
@shaunandrews
@apeatling
@ockham
@breezyskies
@sirbrillig
@mcsf
@gziolo
@seear
@adambbecker
@fabianapsimoes
@roccotripaldi
@melchoyce
@beaulebens
@jancavan
@rase-
@umurkontaci
@mattsherman
@mattm
@jkudish
@dmsnell
@folletto
@yoavf
@johngodley
@janm6k
@jblz
@nb
@fredrocious
@dllh
@omarjackman
@mjangda
@deBhal
@nprasath002
@matthusby
@allendav
@rodrigoi
@akirk
@rickybanister
@kwight
@justinkropp
@mattwiebe
@gravityrail
@drw158
@hewsut
@codebykat
@kateray
@alternatekev
@klimeryk
@jasmussen
@hafizrahman
@TooTallNate
@justinshreve
@lucasartoni
@spncrb
@lancewillett
@peterbutler
@skeltoac
@dbspringer
@mikeshelton1503
@zinigor
@Tsarp
@artpi
@mdawaffe
@scottsweb
@michaeldcain
@gwwar
@jenial
@Tug
@jeremylduvall
@jeffstieler
@hugobaeta
@xyu
@bikedorkjon
@beaucollins
@danhauk
@koke
@bazza
@wahjava

.dockerignore

@@ -0,0 +1,2 @@
+.git
+node_modules

.editorconfig

@@ -0,0 +1,12 @@
+# http://editorconfig.org
+root = true
+
+[*]
+indent_style = tab
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

.esformatter

@@ -0,0 +1,76 @@
+{
+ "root": true,
+
+ "preset": "default",
+ "indent": {
+ "value": "\t",
+ "IfStatementConditional": 2,
+ "SwitchStatement": 1,
+ "TopLevelFunctionBlock": 1
+ },
+ "lineBreak": {
+ "before": {
+ "VariableDeclarationWithoutInit": 0,
+ "ArrayExpressionClosing": 1
+ },
+ "after": {
+ "AssignmentOperator": -1,
+ "ArrayExpressionOpening": 1,
+ "ArrayExpressionComma": 1
+ }
+ },
+ "whiteSpace": {
+ "before": {
+ "ArgumentList": 1,
+ "ArgumentListArrayExpression": 1,
+ "ArgumentListFunctionExpression": 1,
+ "ArgumentListObjectExpression": 1,
+ "ArrayExpressionClosing": 1,
+ "ExpressionClosingParentheses": 1,
+ "ForInStatementExpressionClosing": 1,
+ "ForStatementExpressionClosing": 1,
+ "IfStatementConditionalClosing": 1,
+ "MemberExpressionClosing": 1,
+ "ParameterList": 1,
+ "SwitchDiscriminantClosing": 1,
+ "WhileStatementConditionalClosing": 1,
+ "CallExpression": -1
+ },
+ "after": {
+ "ArgumentList": 1,
+ "ArgumentListArrayExpression": 1,
+ "ArgumentListFunctionExpression": 1,
+ "ArgumentListObjectExpression": 1,
+ "ArrayExpressionOpening": 1,
+ "ExpressionOpeningParentheses": 1,
+ "ForInStatementExpressionOpening": 1,
+ "ForStatementExpressionOpening": 1,
+ "IfStatementConditionalOpening": 1,
+ "MemberExpressionOpening": 1,
+ "ParameterList": 1,
+ "SwitchDiscriminantOpening": 1,
+ "WhileStatementConditionalOpening": 1,
+ "CallExpression": 0
+ }
+ },
+ "collapseObjects": {
+ "ObjectExpression": {
+ "maxLineLength": 120,
+ "maxKeys": 1,
+ "forbidden": [ "FunctionExpression" ]
+ },
+ "ArrayExpression": {
+ "maxLineLength": 120,
+ "maxKeys": 10,
+ "forbidden": [ "FunctionExpression" ]
+ }
+ },
+ "plugins": [
+ "esformatter-quotes",
+ "esformatter-semicolons",
+ "esformatter-braces",
+ "esformatter-dot-notation",
+ "esformatter-special-bangs",
+ "esformatter-collapse-objects-a8c"
+ ]
+}

.eslintignore

@@ -0,0 +1,2 @@
+server/devdocs/search-index.js
+client/components/tinymce/plugins/wptextpattern/plugin.js

.eslintrc

@@ -0,0 +1,83 @@
+{
+ "parser": "babel-eslint",
+ "env": {
+ "browser": true,
+ "es6": true,
+ "mocha": true,
+ "node": true
+ },
+ "ecmaFeatures": {
+ "jsx": true,
+ "modules": true
+ },
+ "plugins": [
+ "eslint-plugin-react"
+ ],
+ "rules": {
+ "brace-style": [ 1, "1tbs" ],
+ // REST API objects include underscores
+ "camelcase": 0,
+ "comma-dangle": 0,
+ "comma-spacing": 1,
+ // Allows returning early as undefined
+ "consistent-return": 0,
+ "dot-notation": 1,
+ "eqeqeq": [ 2, "allow-null" ],
+ "eol-last": 1,
+ "indent": [ 1, "tab", { "SwitchCase": 1 } ],
+ "key-spacing": 1,
+ // Most common is "Emitter", should be improved
+ "new-cap": 1,
+ "no-cond-assign": 2,
+ "no-else-return": 1,
+ "no-empty": 1,
+ // Flux stores use switch case fallthrough
+ "no-fallthrough": 0,
+ "no-lonely-if": 1,
+ "no-mixed-requires": 0,
+ "no-mixed-spaces-and-tabs": 1,
+ "no-multiple-empty-lines": [ 1, { max: 1 } ],
+ "no-multi-spaces": 1,
+ "no-nested-ternary": 1,
+ "no-new": 1,
+ "no-process-exit": 1,
+ "no-shadow": 1,
+ "no-spaced-func": 1,
+ "no-trailing-spaces": 1,
+ "no-undef": 1,
+ "no-underscore-dangle": 0,
+ // Allows Chai `expect` expressions
+ "no-unused-expressions": 0,
+ "no-unused-vars": 1,
+ // Teach eslint about React+JSX
+ "react/jsx-uses-react": 1,
+ "react/jsx-uses-vars": 1,
+ // Allows function use before declaration
+ "no-use-before-define": [ 2, "nofunc" ],
+ // We split external, internal, module variables
+ "one-var": 0,
+ "operator-linebreak": [ 1, "after", { "overrides": {
+ "?": "before",
+ ":": "before"
+ } } ],
+ "padded-blocks": [ 1, "never" ],
+ "quote-props": [ 1, "as-needed" ],
+ "quotes": [ 1, "single", "avoid-escape" ],
+ "semi-spacing": 1,
+ "space-after-keywords": [ 1, "always" ],
+ "space-before-blocks": [ 1, "always" ],
+ "space-before-function-paren": [ 1, "never" ],
+ // Our array literal index exception violates this rule
+ "space-in-brackets": 0,
+ "space-in-parens": [ 1, "always" ],
+ "space-infix-ops": [ 1, { "int32Hint": false } ],
+ // Ideal for "!" but not for "++"
+ "space-unary-ops": 0,
+ // Assumed by default with Babel
+ "strict": [ 2, "never" ],
+ "valid-jsdoc": [ 1, { "requireReturn": false } ],
+ // Common top-of-file requires, expressions between external, interal
+ "vars-on-top": 1,
+ "yoda": 0
+ }
+}

.gitignore

@@ -0,0 +1,35 @@
+.sass-cache
+.vagrant
+.unison
+.env
+.DS_Store
+.idea
+*.iml
+*.iws
+tags
+node_modules
+/npm-debug.log*
+*.sw?
+!*.swf
+
+# script used during docker build that is specific to the environment
+env-config.sh
+
+# added during build
+/config/secrets.json
+
+/build
+
+/public/*.js
+/public/style*.css
+/public/style*.css.map
+/public/editor*.css
+/server/devdocs/search-index.js
+/server/bundler/assets-*.json
+
+*.rdb
+*.db
+
+/calypso-strings.php
+cover.html
+.test.log

.jsfmtrc

@@ -0,0 +1,75 @@
+{
+ "preset": "default",
+ "indent": {
+ "value": "\t",
+ "IfStatementConditional": 2,
+ "SwitchStatement": 1,
+ "TopLevelFunctionBlock": 1
+ },
+ "lineBreak": {
+ "before": {
+ "VariableDeclarationWithoutInit": 0,
+ "ArrayExpressionClosing": 1
+ },
+ "after": {
+ "AssignmentOperator": -1,
+ "ArrayExpressionOpening": 1,
+ "ArrayExpressionComma": 1
+ }
+ },
+ "whiteSpace": {
+ "before": {
+ "ArgumentList": 1,
+ "ArgumentListArrayExpression": 1,
+ "ArgumentListFunctionExpression": 1,
+ "ArgumentListObjectExpression": 1,
+ "ArrayExpressionClosing": 1,
+ "ExpressionClosingParentheses": 1,
+ "ForInStatementExpressionClosing": 1,
+ "ForStatementExpressionClosing": 1,
+ "IfStatementConditionalClosing": 1,
+ "MemberExpressionClosing": 1,
+ "ParameterList": 1,
+ "SwitchDiscriminantClosing": 1,
+ "WhileStatementConditionalClosing": 1,
+ "CallExpression": -1
+ },
+ "after": {
+ "ArgumentList": 1,
+ "ArgumentListArrayExpression": 1,
+ "ArgumentListFunctionExpression": 1,
+ "ArgumentListObjectExpression": 1,
+ "ArrayExpressionOpening": 1,
+ "ExpressionOpeningParentheses": 1,
+ "ForInStatementExpressionOpening": 1,
+ "ForStatementExpressionOpening": 1,
+ "IfStatementConditionalOpening": 1,
+ "MemberExpressionOpening": 1,
+ "ParameterList": 1,
+ "SwitchDiscriminantOpening": 1,
+ "WhileStatementConditionalOpening": 1,
+ "CallExpression": 0
+ }
+ },
+ "collapseObjects": {
+ "ObjectExpression": {
+ "maxLineLength": 120,
+ "maxKeys": 1,
+ "forbidden": [ "FunctionExpression" ]
+ },
+ "ArrayExpression": {
+ "maxLineLength": 120,
+ "maxKeys": 10,
+ "forbidden": [ "FunctionExpression" ]
+ }
+ },
+ "plugins": [
+ "esformatter-quotes",
+ "esformatter-semicolons",
+ "esformatter-braces",
+ "esformatter-dot-notation",
+ "esformatter-special-bangs",
+ "esformatter-jsx-ignore",
+ "esformatter-collapse-objects-a8c"
+ ]
+}

.npmrc

@@ -0,0 +1,2 @@
+save-exact = true
+

.rtlcssrc

@@ -0,0 +1,10 @@
+{
+ "options": {
+ "preserveComments": true,
+ "preserveDirectives": false,
+ "swapLeftRightInUrl": true,
+ "swapLtrRtlInUrl": true,
+ "swapWestEastInUrl": false,
+ "autoRename": false
+ }
+}

CONTRIBUTING.md

@@ -0,0 +1,70 @@
+Contributing to Calypso
+=======================
+
+Calypso is Open Source software licensed under [GNU General Public License v2 (or later)](./LICENSE.md).
+
+--------
+
+We want to help you start off on the right foot when working with Calypso, reading this is a great first step.
+
+**The most important things to know when starting out are:**
+
+1. All code written for Calypso goes through a peer code review process before it is merged to master.
+2. The workflows for Calypso are different than what you're used to at Automattic, it will take time to adjust.
+3. We are all in this together, building a great WordPress powered experience. We're here to help you along the way.
+4. Good judgement trumps all.
+
+If you can keep those in mind during your first couple of months working with Calypso, you're going to do great. Don't stop reading here though, there's some more important details for each of the above points.
+
+The peer code review process
+----------------------------
+
+Code reviews are an important part of the Calypso workflow. They help to keep code quality consistent, and they help every person working on Calypso improve over time. We want to make you the best Calypso contributor you can be.
+
+Every PR should be reviewed and approved by someone other than the author. Fresh eyes can find problems that can hide in the open if you've been working on the code for a while.
+
+This is one of the primary reasons PRs should be kept small and pushed often (more about that below). We can help you with decisions, make suggestions, and help guide your feature *as you're building it.*
+
+*Everyone* is encouraged to review PRs and add feedback and ask questions, even people who are new to calypso. Also, don't just review PRs from your own team. Reading other people's code is a great way to learn new techniques, and seeing code outside of your own feature helps you to see patterns across the project. It's also helpful to see the feedback other contributors are getting on their PRs. 
+
+The final thumbs-up and **<span class="label status-ready-to-merge">[Status] Ready to Merge</span>** should come from a Calypso contributor that has authored and reviewed a number of merged PRs if the change is substantial.
+
+[A positive mindset towards code reviews](https://medium.com/medium-eng/the-code-review-mindset-3280a4af0a89) is really important. We're building something together that is greater than the sum of its parts, everyone should feel ownership of code going into Calypso and want to make it the best it can be.
+
+If you feel yourself waiting for someone to review a PR, don't hesitate to ask for someone to review on Slack or to ping someone directly via a Github mention. _The PR author is responsible for pushing the change through._
+
+The Calypso Workflow
+--------------------
+
+When you're first starting out, your natural instinct when creating a new feature will be to create a local feature branch, and start building away. If you start doing this, *stop*, take your hands off the keyboard, grab a coffee and read on. :)
+
+**It's important to break your feature down into small pieces first**, each piece should become its own pull request. Even if after finishing the first piece your feature isn't functional, that is okay, we love merging unfinished code early and often. You can place your feature behind a [feature-check](config/README.md#feature-flags) to make sure it's not exposed until all pieces are completed. It's also a good idea to read up on [the CSS/SASS coding guidelines](docs/coding-guidelines/css.md), to ensure form and syntax is consistent.
+
+Once you know what the first small piece of your feature will be, follow this general process while working:
+
+1. Create a new branch, use the [proper naming](docs/git-workflow.md#branch-naming-scheme), _e.g._ `add/video-preview` or `fix/1337-language-too-geeky`
+2. Make your first commit: any will do even if empty or trivial, but we need something in order to create the initial pull request. Create the pull request and prefix the name with the section of the product, _e.g._ _Posts: Prepare store for desktop app_.
+ - Write a detailed description of the problem you are solving, the part of Calypso it affects, and how you plan on going about solving it.
+ - Add the **<span class="label status-in-progress">[Status] In Progress</span>** label. This indicates that the pull request isn't ready for final review and may still be incomplete. On the other hand, it welcomes early feedback and encourages collaboration during the development process.
+3. Start developing and pushing out commits to your new branch.
+ - Push your changes out frequently and try to avoid getting yourself stuck in a long-running branch or a merge nightmare. When your local work diverges enough from the master branch it can be hard to review and hard to reconcile conflicts.
+ - Follow the [merge checklist](docs/merge-checklist.md) before pushing. This ensures that your code follows the style guidelines and doesn't accidentally introduce any errors or regressions.
+ - Note that you can automate some of these tasks by setting up [githooks](docs/coding-guidelines/javascript.md#setting-up-githooks) and they will run whenever you `git commit`.
+ - Don’t be afraid to change, [squash](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html), and rearrange commits or to force push - `git push -f origin fix/something-broken`. Keep in mind, however, that if other people are working on the same branch then you can mess up their history. You are perfectly safe if you are the only one pushing commits to that branch.
+ - Do proactively squash minor commits such as typo fixes or [fixes to previous commits](http://fle.github.io/git-tip-keep-your-branch-clean-with-fixup-and-autosquash.html) in the pull request.
+4. If you end up needing more than a few commits, consider splitting the pull request into separate components. Discuss in the new pull request and in the comments why the branch was broken apart and any changes that may have taken place that necessitated the split. Our goal is to catch early in the review process those pull requests that attempt to do too much.
+5. When you feel that you are ready for a formal review or for merging into `master` make sure you check this list and our [merge checklist](docs/merge-checklist.md).
+ - Make sure your branch merges cleanly and consider rebasing against `master` to keep the branch history short and clean.
+ - If there are visual changes, add before and after screenshots in the pull request comments.
+ - Add unit tests, or at a minimum, provide helpful instructions for the reviewer so he or she can test your changes. This will help speed up the review process.
+ - Ensure that your commit messages are [meaningful](http://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message).
+6. Remove the **<span class="label status-in-progress">[Status] In Progress</span>** label from the pull request and add the **<span class="label status-needs-review">[Status] Needs Review</span>** label - someone will provide feedback on the latest unreviewed changes. The reviewer will also mark the pull request as **<span class="label status-awaiting-fixes">[Status] Awaiting Fixes</span>** if he or she thinks changes are needed.
+7. If you get a <img src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f44d.png" class="emoji" />, <img src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f4a5.png" class="emoji" />, <img src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f6a2.png" class="emoji" />, <img src="https://assets-cdn.github.com/images/icons/emoji/shipit.png" class="emoji" />, or a LGTM and the status has been changed to **<span class="label status-ready-to-merge">[Status] Ready to Merge</span>**, merge the changes into `master`.
+
+> Reviewing can be a time-consuming process if only handled by a few developers. Why not skim the list of open pull requests while waiting and review someone else's work in the meantime? Everyone is welcome to add comments at any level, from basic programming style to advanced Calypso ways and means. You may not feel comfortable signing off on someone else's work, but they reviewing you are more-fully joining the project and helping to share the load. **We're all in this together**.
+
+
+We're here to help along the way
+--------------------------------
+
+Don't be afraid to ask for help at any point. We want your first experience with Calypso to be a good one, so don't be shy. If you're wondering why something is the way it is, or how a decision was made, you can tag issues with **<span class="label type-question">[Type] Question</span>**.