build the servo script crate from 20170228

servo-script-20170228/.gitignore

@@ -0,0 +1,10 @@
+*.pyc
+*.orig
+.cargo
+.servo
+target
+*~
+components/servo/WD
+python/_virtualenv
+python/tidy/servo_tidy.egg-info
+

servo-script-20170228/.servobuild

@@ -0,0 +1,66 @@
+# Copy this file to .servobuild in the Servo root directory
+# Be sure to set the cache-dir correctly, otherwise extra
+# copies of the Rust compiler may get downloaded
+
+# Paths starting with "./" are relative to the repo root
+
+# Tool options
+[tools]
+# Where Rust compiler and other downloads will be stored.  Can be
+# shared by multiple Servo repositories.  Defaults to <servo-repo>/.servo
+cache-dir = "./.servo"
+
+# Where Cargo stores all of its clones  Defaults to <servo-repo>/.cargo
+cargo-home-dir = "./.cargo"
+
+# If system-rust is true, will use rustc/rustdoc from the path, or if
+# rust-root is specified, will make sure that rust-root is in the path
+# when building. Similarly for Cargo. This takes care of PATH as well as
+# [DY]LD_LIBRARY_PATH.
+# rust-root and cargo-root default to <servo-repo>/
+system-rust = true
+#rust-root = "/path/to/rust"
+system-cargo = true
+#cargo-root = "/path/to/cargo"
+
+# If rustc-with-gold is true, will try to find and use gold linker with rustc.
+# Defaults to true
+rustc-with-gold = true
+
+# If uncommented, this command is used instead of the platform’s default
+# to notify at the end of a compilation that took a long time.
+# This is the name or path of an executable called with two arguments:
+# the summary and content of the notification.
+#notify-command = "notify-send"
+
+[build]
+# Set "mode = dev" or use `mach build --dev` to build the project with warning.
+# or Set "mode = release" or use `mach build --release` for optimized build.
+# Defaults to prompting before building
+#mode = "dev"
+
+# Whether to enable LLVM assertions in rustc.
+#llvm-assertions = false
+
+# Set "android = true" or use `mach build --android` to build the Android app.
+android = false
+
+# Set "debug-mozjs" or use `mach build --debug-mozjs` to build a debug spidermonkey.
+debug-mozjs = false
+
+# Set to the path to your ccache binary to enable caching of compiler outputs
+#ccache = "/usr/local/bin/ccache"
+
+# Any optional flags that will be added to $RUSTFLAGS
+#rustflags = ""
+
+# Enable rustc’s incremental compilation
+#incremental = false
+
+# Android information
+[android]
+# Defaults to the value of $ANDROID_SDK, $ANDROID_NDK, $ANDROID_TOOLCHAIN, $ANDROID_PLATFORM respectively
+#sdk = "/opt/android-sdk"
+#ndk = "/opt/android-ndk"
+#toolchain = "/opt/android-toolchain"
+#platform = "android-18"

servo-script-20170228/CONTRIBUTING.md

@@ -0,0 +1,56 @@
+# Contributing to Servo
+
+Servo welcomes contribution from everyone. Here are the guidelines if you are
+thinking of helping us:
+
+
+## Contributions
+
+Contributions to Servo or its dependencies should be made in the form of GitHub
+pull requests. Each pull request will be reviewed by a core contributor
+(someone with permission to land patches) and either landed in the main tree or
+given feedback for changes that would be required. All contributions should
+follow this format, even those from core contributors.
+
+Should you wish to work on an issue, please claim it first by commenting on
+the GitHub issue that you want to work on it. This is to prevent duplicated
+efforts from contributors on the same issue.
+
+Head over to [Servo Starters](http://servo.github.io/servo-starters/) to find
+good tasks to start with. If you come across words or jargon that do not make
+sense, please check [the glossary](docs/glossary.md) first. If there's no
+matching entry, please make a pull request to add one with the content `TODO`
+so we can correct that!
+
+See [`HACKING_QUICKSTART.md`](docs/HACKING_QUICKSTART.md) for more information
+on how to start working on Servo.
+
+## Pull Request Checklist
+
+- Branch from the master branch and, if needed, rebase to the current master
+  branch before submitting your pull request. If it doesn't merge cleanly with
+  master you may be asked to rebase your changes.
+
+- Commits should be as small as possible, while ensuring that each commit is
+  correct independently (i.e., each commit should compile and pass tests). 
+
+- If your patch is not getting reviewed or you need a specific person to review
+  it, you can @-reply a reviewer asking for a review in the pull request or a
+  comment, or you can ask for a review in `#servo` on `irc.mozilla.org`.
+
+- Add tests relevant to the fixed bug or new feature.  For a DOM change this
+  will usually be a web platform test; for layout, a reftest.  See our [testing
+  guide](https://github.com/servo/servo/wiki/Testing) for more information.
+
+For specific git instructions, see [GitHub workflow 101](https://github.com/servo/servo/wiki/Github-workflow).
+
+## Conduct
+
+In all Servo-related forums, we follow the [Rust Code of Conduct](http://www.rust-lang.org/conduct.html). For escalation or moderation issues, please contact Jack (jmoffitt@mozilla.com) and Lars (larsberg@mozilla.com) instead of the Rust moderation team.
+
+
+## Communication
+
+Servo contributors frequent the `#servo` channel on [`irc.mozilla.org`](https://wiki.mozilla.org/IRC).
+
+You can also join the [`dev-servo` mailing list](https://lists.mozilla.org/listinfo/dev-servo).