website: merge x.blog branch

The x.blog branch was created out-of-band by rewriting the
x/blog history to have this repo's first commit as its initial commit
and moving all the work into a blog/ subdirectory.

This merge brings the blog/ subdirectory into the main branch
of x/website.

After this merge, all work on the blog will happen here in x/website,
first in the blog/ directory and then eventually merged into the website
proper.

Change-Id: I25b94377a1f111ee0a640afcb7e2e4a4384d0733

Author: rsc

blog/.gcloudignore

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

blog/.gitattributes

@@ -0,0 +1,10 @@
+# Treat all files in this repo as binary, with no git magic updating
+# line endings. Windows users contributing to Go will need to use a
+# modern version of git and editors capable of LF line endings.
+#
+# We'll prevent accidental CRLF line endings from entering the repo
+# via the git-review gofmt checks.
+#
+# See golang.org/issue/9281
+
+* -text

blog/AUTHORS

@@ -0,0 +1,3 @@
+# This source code refers to The Go Authors for copyright purposes.
+# The master list of authors is in the main Go distribution,
+# visible at https://tip.golang.org/AUTHORS.

blog/CONTRIBUTING.md

@@ -0,0 +1,26 @@
+# Contributing to Go
+
+Go is an open source project.
+
+It is the work of hundreds of contributors. We appreciate your help!
+
+## Filing issues
+
+When [filing an issue](https://golang.org/issue/new), make sure to answer these five questions:
+
+1.  What version of Go are you using (`go version`)?
+2.  What operating system and processor architecture are you using?
+3.  What did you do?
+4.  What did you expect to see?
+5.  What did you see instead?
+
+General questions should go to the [golang-nuts mailing list](https://groups.google.com/group/golang-nuts) instead of the issue tracker.
+The gophers there will answer or ask you to file an issue if you've tripped over a bug.
+
+## Contributing code
+
+Please read the [Contribution Guidelines](https://golang.org/doc/contribute.html)
+before sending patches.
+
+Unless otherwise noted, the Go source files are distributed under
+the BSD-style license found in the LICENSE file.

blog/CONTRIBUTORS

@@ -0,0 +1,3 @@
+# This source code was written by the Go contributors.
+# The master list of contributors is in the main Go distribution,
+# visible at https://tip.golang.org/CONTRIBUTORS.

blog/LICENSE

@@ -0,0 +1,27 @@
+Copyright (c) 2009 The Go Authors. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are
+met:
+
+   * Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+   * Redistributions in binary form must reproduce the above
+copyright notice, this list of conditions and the following disclaimer
+in the documentation and/or other materials provided with the
+distribution.
+   * Neither the name of Google Inc. nor the names of its
+contributors may be used to endorse or promote products derived from
+this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

blog/PATENTS

@@ -0,0 +1,22 @@
+Additional IP Rights Grant (Patents)
+
+"This implementation" means the copyrightable works distributed by
+Google as part of the Go project.
+
+Google hereby grants to You a perpetual, worldwide, non-exclusive,
+no-charge, royalty-free, irrevocable (except as stated in this section)
+patent license to make, have made, use, offer to sell, sell, import,
+transfer and otherwise run, modify and propagate the contents of this
+implementation of Go, where such license applies only to those patent
+claims, both currently owned or controlled by Google and acquired in
+the future, licensable by Google that are necessarily infringed by this
+implementation of Go.  This grant does not include claims that would be
+infringed only as a consequence of further modification of this
+implementation.  If you or your agent or exclusive licensee institute or
+order or agree to the institution of patent litigation against any
+entity (including a cross-claim or counterclaim in a lawsuit) alleging
+that this implementation of Go or any code incorporated within this
+implementation of Go constitutes direct or contributory patent
+infringement, or inducement of patent infringement, then any patent
+rights granted to you under this License for this implementation of Go
+shall terminate as of the date such litigation is filed.

blog/README.md

@@ -0,0 +1,69 @@
+# Go Blog
+
+[![Go Reference](https://pkg.go.dev/badge/golang.org/x/blog.svg)](https://pkg.go.dev/golang.org/x/blog)
+
+This repository holds the Go Blog server code and content.
+
+## Download/Install
+
+The easiest way to install is to run `go get -u golang.org/x/blog`. You can also
+manually git clone the repository to \$GOPATH/src/golang.org/x/blog.
+
+## Running Locally
+
+To run the blog server locally:
+
+```
+go run . -reload
+```
+
+and then visit [http://localhost:8080/](http://localhost:8080) in your browser.
+
+## Contributing
+
+Articles are written in the [x/tools/present][present] format.
+Articles on the blog should have broad interest to the Go community, and
+are mainly written by Go contributors. We encourage you to share your
+experiences using Go on your own website, and [to share them with the Go
+community][community]. [Hugo][hugo] is a static site server written in Go that
+makes it easy to write and share your stories.
+
+[present]: https://godoc.org/golang.org/x/tools/present
+[community]: https://golang.org/help/
+[hugo]: https://gohugo.io/
+
+## Report Issues / Send Patches
+
+This repository uses Gerrit for code changes. To learn how to submit changes to
+this repository, see https://golang.org/doc/contribute.html.
+
+The main issue tracker for the blog is located at
+https://github.com/golang/go/issues. Prefix your issue with "x/blog:" in the
+subject line, so it is easy to find.
+
+## Deploying
+
+The Google Cloud project triggers a fresh deploy of the blog on each submit
+but that deployment is published to a temporary URL.
+
+To publish the blog to blog.golang.org, you need access to the
+Cloud Console for the golang-org project.
+Then:
+
+1. Visit the
+   [builds list](https://console.cloud.google.com/cloud-build/builds?project=golang-org&query=trigger_id%3D%22c99674d3-32c1-4aec-ade4-ae2d5a844369%22)
+   and click on the build hash for the most recent build
+   with trigger name “Redeploy-blog-on-blog-commit”.
+
+   Scrolling to the bottom of the build log, you will find a URL in a log message like
+
+       Deployed service [blog] to [https://TEMPORARYURL.appspot.com]
+
+2. Copy that URL and load it in your browser. Check that it looks OK.
+
+3. Assuming it does, visit the
+   [AppEngine versions list](https://console.cloud.google.com/appengine/versions?project=golang-org&serviceId=blog).
+   Click “Migrate Traffic” on the new entry to move 100% of the blog.golang.org
+   traffic to the new version.
+
+4. You're done.

blog/_content/10years.article

@@ -0,0 +1,137 @@
+# Go Turns 10
+8 Nov 2019
+Summary: Happy 10th birthday, Go!
+
+Russ Cox, for the Go team
+[email protected]
+
+##
+
+Happy birthday, Go!
+
+This weekend we celebrate the 10th anniversary of
+[the Go release](https://opensource.googleblog.com/2009/11/hey-ho-lets-go.html),
+marking the 10th birthday of Go as an open-source programming language
+and ecosystem for building modern networked software.
+
+To mark the occasion,
+[Renee French](https://twitter.com/reneefrench),
+the creator of the
+[Go gopher](https://blog.golang.org/gopher),
+painted this delightful scene:
+
+<a href="10years/gopher10th-large.jpg">
+.image 10years/gopher10th-small.jpg _ 850
+</a>
+
+Celebrating 10 years of Go makes me think back to early November 2009,
+when we were getting ready to share Go with the world.
+We didn’t know what kind of reaction to expect,
+whether anyone would care about this little language.
+I hoped that even if no one ended up using Go,
+we would at least have drawn attention to some good ideas,
+especially Go’s approach to concurrency and interfaces,
+that could influence follow-on languages.
+
+Once it became clear that people were excited about Go,
+I looked at the history of popular languages
+like C, C++, Perl, Python, and Ruby,
+examining how long each took to gain widespread adoption.
+For example, Perl seemed to me to have appeared fully-formed
+in the mid-to-late 1990s, with CGI scripts and the web,
+but it was first released in 1987.
+This pattern repeated for almost every language I looked at:
+it seems to take roughly a decade of quiet, steady improvement
+and dissemination before a new language really takes off.
+
+I wondered: where would Go be after a decade?
+
+Today, we can answer that question:
+Go is everywhere, used by at least [a million developers worldwide](https://research.swtch.com/gophercount).
+
+Go’s original target was networked system infrastructure,
+what we now call cloud software.
+Every major cloud provider today uses core cloud infrastructure written in Go,
+such as Docker, Etcd, Istio, Kubernetes, Prometheus, and Terraform;
+the majority of the
+[Cloud Native Computing Foundation’s projects](https://www.cncf.io/projects/)
+are written in Go.
+Countless companies are using Go to move their own work to the cloud as well,
+from startups building from scratch
+to enterprises modernizing their software stack.
+Go has also found adoption well beyond its original cloud target,
+with uses ranging
+from
+controlling tiny embedded systems with
+[GoBot](https://gobot.io) and [TinyGo](https://tinygo.org/)
+to detecting cancer with
+[massive big data analysis and machine learning at GRAIL](https://medium.com/grail-eng/bigslice-a-cluster-computing-system-for-go-7e03acd2419b),
+and everything in between.
+
+All this is to say that Go has succeeded beyond our wildest dreams.
+And Go’s success isn’t just about the language.
+It’s about the language, the ecosystem, and especially the community working together.
+
+In 2009, the language was a good idea with a working sketch of an implementation.
+The `go` command did not exist:
+we ran commands like `6g` to compile and `6l` to link binaries,
+automated with makefiles.
+We typed semicolons at the ends of statements.
+The entire program stopped during garbage collection,
+which then struggled to make good use of two cores.
+Go ran only on Linux and Mac, on 32- and 64-bit x86 and 32-bit ARM.
+
+Over the last decade, with the help of Go developers all over the world,
+we have evolved this idea and sketch into a productive language
+with fantastic tooling,
+a production-quality implementation,
+a
+[state-of-the-art garbage collector](https://blog.golang.org/ismmkeynote),
+and [ports to 12 operating systems and 10 architectures](https://golang.org/doc/install/source#introduction).
+
+Any programming language needs the support of a thriving ecosystem.
+The open source release was the seed for that ecosystem,
+but since then, many people have contributed their time and talent
+to fill the Go ecosystem with great tutorials, books, courses, blog posts,
+podcasts, tools, integrations, and of course reusable Go packages importable with `go` `get`.
+Go could never have succeeded without the support of this ecosystem.
+
+Of course, the ecosystem needs the support of a thriving community.
+In 2019 there are dozens of Go conferences all over the world,
+along with
+[over 150 Go meetup groups with over 90,000 members](https://www.meetup.com/pro/go).
+[GoBridge](https://golangbridge.org)
+and
+[Women Who Go](https://medium.com/@carolynvs/www-loves-gobridge-ccb26309f667)
+help bring new voices into the Go community,
+through mentoring, training, and conference scholarships.
+This year alone, they have taught
+hundreds of people from traditionally underrepresented groups
+at workshops where community members teach and mentor those new to Go.
+
+There are
+[over a million Go developers](https://research.swtch.com/gophercount)
+worldwide,
+and companies all over the globe are looking to hire more.
+In fact, people often tell us that learning Go
+helped them get their first jobs in the tech industry.
+In the end, what we’re most proud of about Go
+is not a well-designed feature or a clever bit of code
+but the positive impact Go has had in so many people’s lives.
+We aimed to create a language that would help us be better developers,
+and we are thrilled that Go has helped so many others.
+
+As
+[\#GoTurns10](https://twitter.com/search?q=%23GoTurns10),
+I hope everyone will take a moment to celebrate
+the Go community and all we have achieved.
+On behalf of the entire Go team at Google,
+thank you to everyone who has joined us over the past decade.
+Let’s make the next one even more incredible!
+
+<div>
+<center>
+<a href="10years/gopher10th-pin-large.jpg">
+.image 10years/gopher10th-pin-small.jpg _ 150
+</center>
+</div>