aboutsummaryrefslogtreecommitdiff
path: root/content/getthee-to-go-meetup.article
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2020-03-15 15:50:36 -0400
committerRuss Cox <rsc@golang.org>2020-03-17 20:58:46 +0000
commit972d42d925e6cae3f8eebd9b21d445e06c2eb386 (patch)
tree737af27f0d49318b612efec874b1d1328c699d1a /content/getthee-to-go-meetup.article
parentfaf1e2da2d911edc717993e8edb24fe88f99b2b5 (diff)
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>
Diffstat (limited to 'content/getthee-to-go-meetup.article')
-rw-r--r--content/getthee-to-go-meetup.article33
1 files changed, 0 insertions, 33 deletions
diff --git a/content/getthee-to-go-meetup.article b/content/getthee-to-go-meetup.article
deleted file mode 100644
index e2a5e49..0000000
--- a/content/getthee-to-go-meetup.article
+++ /dev/null
@@ -1,33 +0,0 @@
-# Get thee to a Go meetup
-27 Feb 2013
-Tags: community, talk
-Summary: How to find or start a local group of gophers.
-
-Andrew Gerrand
-
-##
-
-Last week, David Symonds and I each gave talks at Sydney's Go meetup,
-[golang-syd](http://www.meetup.com/golang-syd/).
-Dave spoke about [Go API design in the context of Protocol Buffers](http://talks.godoc.org/github.com/dsymonds/talks/2013-feb-golang-syd/golang-syd.slide),
-and I discussed some neat tricks in the construction of [a small command-line program](http://talks.godoc.org/github.com/nf/streak/talk.slide).
-The presentations were short but provoked some good questions and interesting discussion.
-Of the 50-odd attendees, most were regular Go programmers and a fair chunk
-write Go code professionally. It was a fun night.
-
-It would have been great to see you there but,
-statistically, you're not from Sydney.
-Despair not, however, as there are likely some people in your area who either
-run a Go meetup or want to start one.
-
-The Go wiki lists [Go user groups](https://golang.org/wiki/GoUserGroups) around the world,
-so if there's one nearby you should consider going along to the next event.
-
-If not, why not start your own? To gauge interest,
-ask around in the [Go+ Community](https://plus.google.com/communities/114112804251407510571) and
-the [golang-nuts mailing list](http://groups.google.com/group/golang-nuts), and
-take a look at this [list of people](http://golang.meetup.com/all/) waiting
-for a Go meetup in their area.
-Once you have a few people interested - and at least one person willing
-to present something - pick a venue and set a date.
-If you build it, they will come.