code review 180069: Add roadmap document.

Add roadmap document.

Also adds Development heading on navbar, with Roadmap being
the only current entry.

[iant, 2009-12-16 21:03:28]

Hello r (cc: golang-dev@googlegroups.com),

I'd like you to review the following change.

[r, 2009-12-16 21:24:30]

http://codereview.appspot.com/180069/diff/6/7
File doc/devel/roadmap.html (right):

http://codereview.appspot.com/180069/diff/6/7#newcode5
doc/devel/roadmap.html:5: The following are features and ideas currently being
developed or
change first sentence:

This page lists features and ideas being developed or discussed by the Go team.

http://codereview.appspot.com/180069/diff/6/7#newcode7
doc/devel/roadmap.html:7: be launched or rejected within the following six
months.  We'll do our
"launched or rejected" is a tough dichotomy, plus the time scale is rooted in
the moment, which means as time passes the list and the six-month scale will
conflict.

i favor just dropping this sentence.

http://codereview.appspot.com/180069/diff/6/7#newcode8
doc/devel/roadmap.html:8: best to update this roadmap as the team continues its
work.
switch of subject.  "The list will be updated as work continues."

http://codereview.appspot.com/180069/diff/6/7#newcode14
doc/devel/roadmap.html:14: This is a list of language changes that are currently
being
,s/currently//g  present tense means 'currently'

http://codereview.appspot.com/180069/diff/6/7#newcode17
doc/devel/roadmap.html:17: will in fact be added to the language.
you don't need to say it twice.

Appearance on this list is no guarantee the change will be accepted.

http://codereview.appspot.com/180069/diff/6/7#newcode23
doc/devel/roadmap.html:23: Adjust definition of <code>...</code> in parameter
list.
s/list/lists/

http://codereview.appspot.com/180069/diff/6/7#newcode39
doc/devel/roadmap.html:39: Improved garbage collector.  We are currently
considered a reference
s/considered/considering/

i would try to get rid of the "We" everywhere too.  it sounds exclusive.

http://codereview.appspot.com/180069/diff/6/7#newcode67
doc/devel/roadmap.html:67: Implement goto restrictions.
there's probably a language change tied to this

http://codereview.appspot.com/180069/diff/6/7#newcode70
doc/devel/roadmap.html:70: memory address other than via <code>import
"unsafe"</code>.
s/which can not/guaranteed not to/

http://codereview.appspot.com/180069/diff/6/7#newcode98
doc/devel/roadmap.html:98: </ul>
probably want to tell people how to discuss the topics. just a brief note
mentioning golang-nuts is enough.

also: are we asking for help?

http://codereview.appspot.com/180069/diff/6/8
File lib/godoc/godoc.html (right):

http://codereview.appspot.com/180069/diff/6/8#newcode110
lib/godoc/godoc.html:110: <li class="navhead">Development</li>
i worry that the nav bar is getting very cluttered. i'd rather see a separate
page linked from here, with roadmap linked from  that. then devel.html can get
messy without cluttering the landing page.

[rsc, 2009-12-16 21:29:39]

> http://codereview.appspot.com/180069/diff/6/8#newcode110
> lib/godoc/godoc.html:110: <li class="navhead">Development</li>
> i worry that the nav bar is getting very cluttered. i'd rather see a
> separate page linked from here, with roadmap linked from  that. then
> devel.html can get messy without cluttering the landing page.

i'm not disagreeing but i think that change needs
to be a separate code review.  we need to figure out
how multiple related nav bars would work in the UI.

[r2, 2009-12-16 21:32:27]

On 17/12/2009, at 8:29 AM, Russ Cox wrote:

>> http://codereview.appspot.com/180069/diff/6/8#newcode110
>> lib/godoc/godoc.html:110: <li class="navhead">Development</li>
>> i worry that the nav bar is getting very cluttered. i'd rather see a
>> separate page linked from here, with roadmap linked from  that. then
>> devel.html can get messy without cluttering the landing page.
>
> i'm not disagreeing but i think that change needs
> to be a separate code review.  we need to figure out
> how multiple related nav bars would work in the UI.

The development page doesn't need a special nav bar.

It's fine if you want to do this in a separate CL (or discussion for  
that matter).   Perhaps drop the changes to godoc.html?  We can post  
the roadmap without having a top-level link while we sort things out.

-rob

[rsc, 2009-12-16 21:34:57]

sure.  nothing gets posted until we do a release anyway.

[r2, 2009-12-16 21:35:36]

also: the roadmap (why not road map? what road? what map? isn't this a  
schedule? oh never mind) should say something about a package manager

-rob

[iant, 2009-12-16 21:54:16]

http://codereview.appspot.com/180069/diff/6/7
File doc/devel/roadmap.html (right):

http://codereview.appspot.com/180069/diff/6/7#newcode5
doc/devel/roadmap.html:5: The following are features and ideas currently being
developed or
On 2009/12/16 21:24:31, r wrote:
> change first sentence:
> 
> This page lists features and ideas being developed or discussed by the Go
team.

Done.

http://codereview.appspot.com/180069/diff/6/7#newcode7
doc/devel/roadmap.html:7: be launched or rejected within the following six
months.  We'll do our
On 2009/12/16 21:24:31, r wrote:
> "launched or rejected" is a tough dichotomy, plus the time scale is rooted in
> the moment, which means as time passes the list and the six-month scale will
> conflict.
> 
> i favor just dropping this sentence.

Done.

http://codereview.appspot.com/180069/diff/6/7#newcode8
doc/devel/roadmap.html:8: best to update this roadmap as the team continues its
work.
On 2009/12/16 21:24:31, r wrote:
> switch of subject.  "The list will be updated as work continues."
> 

Done.

http://codereview.appspot.com/180069/diff/6/7#newcode14
doc/devel/roadmap.html:14: This is a list of language changes that are currently
being
On 2009/12/16 21:24:31, r wrote:
> ,s/currently//g  present tense means 'currently'

Done.

http://codereview.appspot.com/180069/diff/6/7#newcode17
doc/devel/roadmap.html:17: will in fact be added to the language.
On 2009/12/16 21:24:31, r wrote:
> you don't need to say it twice.
> 
> Appearance on this list is no guarantee the change will be accepted.

Done.

http://codereview.appspot.com/180069/diff/6/7#newcode23
doc/devel/roadmap.html:23: Adjust definition of <code>...</code> in parameter
list.
On 2009/12/16 21:24:31, r wrote:
> s/list/lists/
> 

Done.

http://codereview.appspot.com/180069/diff/6/7#newcode39
doc/devel/roadmap.html:39: Improved garbage collector.  We are currently
considered a reference
On 2009/12/16 21:24:31, r wrote:
> s/considered/considering/
> 
> i would try to get rid of the "We" everywhere too.  it sounds exclusive.

Done.

http://codereview.appspot.com/180069/diff/6/7#newcode67
doc/devel/roadmap.html:67: Implement goto restrictions.
On 2009/12/16 21:24:31, r wrote:
> there's probably a language change tied to this

The spec has a restriction on goto which the compilers do not yet enforce.  I
also added a language change "Possibly rewrite restriction on goto across
variable declarations."

http://codereview.appspot.com/180069/diff/6/7#newcode70
doc/devel/roadmap.html:70: memory address other than via <code>import
"unsafe"</code>.
On 2009/12/16 21:24:31, r wrote:
> s/which can not/guaranteed not to/

Done.

http://codereview.appspot.com/180069/diff/6/7#newcode98
doc/devel/roadmap.html:98: </ul>
On 2009/12/16 21:24:31, r wrote:
> probably want to tell people how to discuss the topics. just a brief note
> mentioning golang-nuts is enough.

I added a note about golang-nuts at the top of the doc.
 
> also: are we asking for help?

For the implementation, yes, but how to say it?

http://codereview.appspot.com/180069/diff/6/8
File lib/godoc/godoc.html (right):

http://codereview.appspot.com/180069/diff/6/8#newcode110
lib/godoc/godoc.html:110: <li class="navhead">Development</li>
On 2009/12/16 21:24:31, r wrote:
> i worry that the nav bar is getting very cluttered. i'd rather see a separate
> page linked from here, with roadmap linked from  that. then devel.html can get
> messy without cluttering the landing page.

I'll take this out of this changelist.

[iant2, 2009-12-16 21:55:00]

"Rob 'Commander' Pike" <r@google.com> writes:

> also: the roadmap (why not road map? what road? what map? isn't this a
> schedule? oh never mind) should say something about a package manager

"Roadmap" seems to be standard jargon.

I added a note about a package manager.

PTAL.

Ian

[r, 2009-12-16 21:56:11]

LGTM

[dho, 2009-12-16 21:56:25]

>> also: are we asking for help?
>
> For the implementation, yes, but how to say it?

``If you are interested in implementing any of these
(tasks|enhancements|features), please let us know'' or something to
that effect?

--dho

[iant, 2009-12-16 23:30:41]

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

Add roadmap document.

Also adds Development heading on navbar, with Roadmap being
the only current entry.

R=r
CC=golang-dev
http://codereview.appspot.com/180069