content: rename articles to reinforce convention of short URLs

The Go blog started out on Blogger
(http://web.archive.org/web/20100325005843/http://blog.golang.org/).
Later, we moved to the current self-hosted blog server
with extra Go-specific functionality like playground snippets.

The old Blogger posts have very long URLs that Blogger chose
for us, such as "go-programming-language-turns-two" or
"two-go-talks-lexical-scanning-in-go-and", predating
the convention of giving posts shorter, more share-friendly,
typeable names.

The conversion of the old Blogger posts also predated
the convention of putting supporting files in a subdirectory.

The result is that although we've established new conventions,
you wouldn't know by listing the directory - the old Blogger
content presents a conflicting picture.

This commit renames the posts with very long names
to have shorter, more share-friendly names, and it moves
all supporting files to subdirectories. It also adds a README
documenting the conventions.

For example, blog.golang.org/go-programming-language-turns-two
is now blog.golang.org/2years, matching our more recent birthday
post URLs, and its supporting files are moved to the new 2years/ directory.

The old URLs redirect to the new ones.

Change-Id: I9f46a790c2c8fab8459aeda73d4e3d2efc86d88f
Reviewed-on: https://go-review.googlesource.com/c/blog/+/223599
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>

1 files changed, 55 insertions, 0 deletions

diff --git a/content/cwg.article b/content/cwg.article
new file mode 100644
index 0000000..d38dbf4
--- /dev/null
+++ b/content/cwg.article
@@ -0,0 +1,55 @@
+# Community Outreach Working Group
+5 Sep 2017
+Tags: community
+Summary: Annoucing the Go Community Outreach Working Group (CWG).
+OldURL: /community-outreach-working-group
+
+Steve Francia & Cassandra Salisbury
+spf@golang.org
+
+## Announcing the Go Community Outreach Working Group
+
+The Go project has grown considerably with over half a million users and
+community members all over the world. To date all community oriented activities
+have been organized by the community with minimal involvement from the Go
+project. We greatly appreciate these efforts.
+
+After talking to many community organizers we have heard consistent
+feedback that they would like better collaboration between organizers and
+the Go project. We are forming the Community outreach Working Group (CWG)
+to help support these community efforts.
+
+## The CWG Mission
+
+The mission of the CWG is to act as a conduit between the broader Go
+community, it’s organizers and the Go project. The CWG will help provide
+the structures and community management necessary to create an online and
+in person community that is enjoyable and rewarding to participate in. The
+CWG leadership represents the Go project in these efforts.
+
+**The CWG is responsible for:**
+
+  - Defining programs to facilitate deeper collaboration across the community.
+  - Facilitating the coordination of Go events
+  - Establishing growth and expansion plans for the community
+  - Project exposure and accessibility
+  - Ecosystem Development
+
+**Leadership:**
+
+  - [Ashley McNamara](https://twitter.com/ashleymcnamara)
+  - [Cassandra Salisbury](https://twitter.com/Cassandraoid)
+  - [Francesc Campoy](https://twitter.com/francesc)
+  - [Steve Francia](https://twitter.com/spf13)
+
+## Plans for Action
+
+The CWG has an [open GitHub repo](https://github.com/golang/cwg) we’ve created for complete transparency
+of our efforts.  We have various [GitHub projects](https://github.com/golang/cwg/projects) which are acting as our
+primary initiatives. Each project has a variety of [issues](https://github.com/golang/cwg/issues) tied to them
+with assignees from our Leadership team and [our members](https://github.com/golang/cwg/issues/15).
+
+.image cwg/project.png
+
+If you’d like to get involved, we encourage you to comment on the issue
+that interests you or [submit an issue](https://github.com/golang/cwg/issues/new) yourself!