code review 6395043: faq: add status section

faq: add status section
Fixes issue 3822.

[r, 2012-07-13 20:37:01]

Hello golang-dev@googlegroups.com,

I'd like you to review this change to
https://code.google.com/p/go

[r2, 2012-07-13 20:39:10]

note: i put the links explicitly to golang.org to encourage reference to the
"standard". i can be talked out of this if i hear a good counterargument.

-rob

[dsymonds, 2012-07-14 01:15:29]

On Sat, Jul 14, 2012 at 6:39 AM, Rob 'Commander' Pike <r@google.com> wrote:

> note: i put the links explicitly to golang.org to encourage reference to the
"standard". i can be talked out of this if i hear a good counterargument.

Using absolute references there means that they are not usable if you
are reading the page offline, say on an aeroplane.

[r2, 2012-07-14 01:16:47]

how do i handle blog.golang.org?


On Fri, Jul 13, 2012 at 6:15 PM, David Symonds <dsymonds@golang.org> wrote:

> On Sat, Jul 14, 2012 at 6:39 AM, Rob 'Commander' Pike <r@google.com>
> wrote:
>
> > note: i put the links explicitly to golang.org to encourage reference
> to the "standard". i can be talked out of this if i hear a good
> counterargument.
>
> Using absolute references there means that they are not usable if you
> are reading the page offline, say on an aeroplane.
>

[dsymonds, 2012-07-14 01:23:57]

On Sat, Jul 14, 2012 at 11:16 AM, Rob 'Commander' Pike <r@google.com> wrote:

> how do i handle blog.golang.org?

That's a different situation. That is just simply going to have to be
an absolute link, since blog.golang.org is the only place that data
lives. /pkg and the like are all available any time you are running
godoc, so it seems like they should just stay that way.

You said you wanted to encourage reference to the standard, meaning
golang.org. What exactly do you mean by that? I don't see anyone
passing around URLs that aren't already rooted at golang.org.


Dave.

[minux1, 2012-07-14 01:24:09]

On Friday, July 13, 2012, David Symonds wrote:

> On Sat, Jul 14, 2012 at 6:39 AM, Rob 'Commander' Pike
<r@google.com<https://mail.google.com/mail/mu/mp/392/?source=na&hr=1&hl=en>>
> wrote:
> > note: i put the links explicitly to golang.org to encourage reference
> to the "standard". i can be talked out of this if i hear a good
> counterargument.
> Using absolute references there means that they are not usable if you
> are reading the page offline, say on an aeroplane.
>
I think there is an issue about this problem in general.
IMO, godoc should rewrite the golang.org URL if running
locally, because URLs in pkg docs are also forced to
refer to golang.org in order to be recognized as URLs.

[r2, 2012-07-14 04:52:36]

ok, this is getting off topic. i'll give the usual locally-rooted links.
please review the content.

-rob



On Fri, Jul 13, 2012 at 6:24 PM, minux <minux.ma@gmail.com> wrote:

>
> On Friday, July 13, 2012, David Symonds wrote:
>
> On Sat, Jul 14, 2012 at 6:39 AM, Rob 'Commander' Pike
<r@google.com<https://mail.google.com/mail/mu/mp/392/?source=na&hr=1&hl=en>>
>> wrote:
>> > note: i put the links explicitly to golang.org to encourage reference
>> to the "standard". i can be talked out of this if i hear a good
>> counterargument.
>> Using absolute references there means that they are not usable if you
>> are reading the page offline, say on an aeroplane.
>>
> I think there is an issue about this problem in general.
> IMO, godoc should rewrite the golang.org URL if running
> locally, because URLs in pkg docs are also forced to
> refer to golang.org in order to be recognized as URLs.
>

[adg, 2012-07-16 19:48:02]

http://codereview.appspot.com/6395043/diff/1/doc/go_faq.html
File doc/go_faq.html (right):

http://codereview.appspot.com/6395043/diff/1/doc/go_faq.html#newcode74
doc/go_faq.html:74: In fact, Go 1 provides some <a
href="http://golang.org/doc/go1compat.html">guarantees</a> of long-term
compatibility,
Do you want to say guarantees?

In fact, the purpose of Go 1 is to provide <a>long-term stability</a>.
Backwards-incompatible changes will not be made to any Go 1.x release.

http://codereview.appspot.com/6395043/diff/1/doc/go_faq.html#newcode81
doc/go_faq.html:81: Of course, development will continue on Go itself, but the
focus will be more on topics like performance and
focus will be on performance, reliability, portability, and the addition of new
functionality...

[r, 2012-07-16 19:53:55]

Hello golang-dev@googlegroups.com, r@google.com, dsymonds@golang.org,
minux.ma@gmail.com, adg@golang.org (cc: golang-dev@googlegroups.com),

Please take another look.

[adg, 2012-07-16 20:06:59]

LGTM

[r, 2012-07-16 20:31:19]

*** Submitted as http://code.google.com/p/go/source/detail?r=2819b5a4f07d ***

faq: add status section
Fixes issue 3822.

R=golang-dev, r, dsymonds, minux.ma, adg
CC=golang-dev
http://codereview.appspot.com/6395043