summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSeth Tisue <seth@tisue.net>2015-10-07 11:06:33 -0400
committerSeth Tisue <seth@tisue.net>2015-10-07 11:06:33 -0400
commit648c7a1635f88fb14b999a8d36e01a71761b9001 (patch)
tree077dcb3f31904f9224605127d16a3baefd19e30d
parente0b5891c15c3b9d40767f7ef2d9d2ffab61d8bb6 (diff)
parent40d12f17663079f61566388686d9206a9800d7b8 (diff)
downloadscala-648c7a1635f88fb14b999a8d36e01a71761b9001.tar.gz
scala-648c7a1635f88fb14b999a8d36e01a71761b9001.tar.bz2
scala-648c7a1635f88fb14b999a8d36e01a71761b9001.zip
Merge pull request #4790 from SethTisue/issue/9501
SI-9501 link README to Scala Hacker Guide
-rw-r--r--README.md11
1 files changed, 10 insertions, 1 deletions
diff --git a/README.md b/README.md
index 1b4dbb03c2..c8f3f206c4 100644
--- a/README.md
+++ b/README.md
@@ -1,9 +1,18 @@
# Welcome!
This is the official repository for the [Scala Programming Language](http://www.scala-lang.org).
+# How to contribute
+
To contribute to the Scala Standard Library, Scala Compiler and Scala Language Specification, please send us a [pull request](https://help.github.com/articles/using-pull-requests/#fork--pull) from your fork of this repository! We do have to ask you to sign the [Scala CLA](http://typesafe.com/contribute/cla/scala) before we can merge any of your work into our code base, to protect its open source nature.
-For more information on building and developing the core of Scala, read on! Please also check out our [guidelines for contributing](CONTRIBUTING.md).
+For more information on building and developing the core of Scala, read on!
+
+Please also check out:
+
+* our [guidelines for contributing](CONTRIBUTING.md).
+* the ["Scala Hacker Guide"](http://scala-lang.org/contribute/hacker-guide.html) covers some of the same ground as this README, but in greater detail and in a more tutorial style, using a running example.
+
+# Reporting issues
We're still using Jira for issue reporting, so please [report any issues](https://issues.scala-lang.org) over there.
(We would love to start using GitHub Issues, but we're too resource-constrained to take on this migration right now.)