aboutsummaryrefslogtreecommitdiff
path: root/content/survey2018-company.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/survey2018-company.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/survey2018-company.article')
-rw-r--r--content/survey2018-company.article40
1 files changed, 40 insertions, 0 deletions
diff --git a/content/survey2018-company.article b/content/survey2018-company.article
new file mode 100644
index 0000000..aa9acbe
--- /dev/null
+++ b/content/survey2018-company.article
@@ -0,0 +1,40 @@
+# Participate in the 2018 Go Company Questionnaire
+4 Oct 2018
+Tags: survey, community
+Summary: Please take the 2018 Go Company Questionnaire.
+OldURL: /company-questionnaire2018
+
+Ran Tao, Steve Francia
+spf@golang.org
+
+## The Go project wants to hear from you!
+
+We need your help to create the best programming language for developing
+simple, reliable, and scalable software. To do this, we need to better
+understand how companies are using Go. Please help by participating in a
+7-minute company questionnaire.
+
+**Who:** If you are in a position to share details like “company name,” “if your
+company is hiring Go developers,” and “reasons your team or company adopted Go”
+then please help us by taking this company questionnaire. We only need one
+response per company (or per department for larger companies). If you aren’t the
+right person, please forward this onto the right person at your company.
+
+_Please note: this is different from our annual anonymous Go user survey, which_
+_will be announced in November._
+
+**Where:** Please take this 7-minute questionnaire by October 30th:
+[Go Company Questionnaire 2018](http://goo.gl/nnPfct).
+
+The questionnaire is confidential, but not anonymous. For more information,
+please refer to Google’s privacy policy
+[here](https://policies.google.com/privacy).
+
+The Go project leadership will use your responses to better understand how
+companies use Go and in what ways we can improve their experience.
+
+## Spread the word!
+
+We would like as many companies as possible to participate to help us better
+understand our global user base. Please help us spread the word by sharing this
+post on your social network feeds, at meetups, and in other communities.