Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proposal: x/website: golang.org/s: print an index at the root #43676

Open
robpike opened this issue Jan 13, 2021 · 9 comments
Open

proposal: x/website: golang.org/s: print an index at the root #43676

robpike opened this issue Jan 13, 2021 · 9 comments
Assignees
Labels
FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Proposal website

Comments

@robpike
Copy link
Contributor

robpike commented Jan 13, 2021

The URL shortener for the golang.org web site, golang.org/s/ contains useful historical links, but I cannot discover a way to see the list. Both golang.org/s and golang.org/s/index produce

not found

A simple feature request: golang.org/s could list the entries.

@changkun
Copy link
Member

I was interested in all /s links, but could not find a way to view them. So I searched these places: 1) the source code 2) all commit messages 3) golang-nuts 4) golang-dev 5) wiki 6) google and summarized most of them as a list at golang.design/history.

People who interested in this, can search from the README document via golang.org/s, here are some of them (not sure if there are more):

https://golang.org/s/semicolon-proposal
https://golang.org/s/go1
https://golang.org/s/go11sched
https://golang.org/s/go11func
https://golang.org/s/go11return
https://golang.org/s/go12nil
https://golang.org/s/go12slice
https://golang.org/s/go12symtab
https://golang.org/s/go12encoding
https://golang.org/s/go13todo
https://golang.org/s/go13linker
https://golang.org/s/go13heapdump
https://golang.org/s/go13compiler
https://golang.org/s/go13nacl
https://golang.org/s/go14android
https://golang.org/s/go14internal
https://golang.org/s/go14nopkg
https://golang.org/s/go14gc
https://golang.org/s/go14customimport
https://golang.org/s/go15vendor
https://golang.org/s/go15bootstrap
https://golang.org/s/go15gomaxprocs
https://golang.org/s/go15gcpacing
https://golang.org/s/go15trace
https://golang.org/s/go17ssa
https://golang.org/s/go19inliningtalk
https://golang.org/s/generatedcode
https://golang.org/s/gctoc
https://golang.org/s/go2designs
https://golang.org/s/dev.cc
https://golang.org/s/execmodes
https://golang.org/s/better-linker
https://golang.org/s/win2000-golang-nuts
https://golang.org/s/contigstacks
https://golang.org/s/types-tutorial
https://golang.org/s/using-guru
https://golang.org/s/stdwhy
https://golang.org/s/oracle-design
https://golang.org/s/oracle-user-manual
https://golang.org/s/cgihttpproxy
https://golang.org/s/sqldrivers
https://golang.org/s/builderplan

@ALTree
Copy link
Member

ALTree commented Jan 14, 2021

@changkun here's one you're missing:

@robpike
Copy link
Contributor Author

robpike commented Jan 14, 2021

@changkun Thanks very much! But I'd still like the site to offer its own, automatically maintained index.

@changkun
Copy link
Member

We would love that feature too :)

@agnivade agnivade added FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Jan 14, 2021
@agnivade agnivade changed the title golang.org/s: print an index at the root x/website: golang.org/s: print an index at the root Jan 14, 2021
@gopherbot gopherbot added this to the Unreleased milestone Jan 14, 2021
@gopherbot
Copy link
Contributor

Change https://golang.org/cl/283753 mentions this issue: x/website: golang.org/s: print an index at the root

@rsc
Copy link
Contributor

rsc commented Feb 23, 2021

I can see the full index, and it's kind of full of junk.
I'm not convinced that publishing the full table of junk is worthwhile.
Even worse, there are clearly links there that were created assuming
that the full names and links would not be made into a public table.
(You can argue that was a mistake, but they exist.)

If we are going to publish an index on /s, there should be a separate
"public bool" bit stored with each link that must be set explicitly
for a link to appear in the index.

Please do NOT do this, at least not without adding that bit.

@changkun
Copy link
Member

Thanks for the clarification about the junk and privately created links. Then I don't think that the community can do anything about this as the sent CL was done blindly by just reading the code and marking public bool would require admin permission to at least view them all. Still looking forward to the feature be launched in the future as reason commented previously.

@robpike robpike changed the title x/website: golang.org/s: print an index at the root proposal: x/website: golang.org/s: print an index at the root Feb 23, 2021
@robpike
Copy link
Contributor Author

robpike commented Feb 23, 2021

I have made this a proposal to try to force discussion and closure.

@rsc
Copy link
Contributor

rsc commented Feb 24, 2021

I don't think we really need a proposal. I am happy to add this feature as long as there is a public/private bit too.
I'm already working on golang.org recently. If you leave it for me, I will implement it.

@rsc rsc changed the title proposal: x/website: golang.org/s: print an index at the root x/website: golang.org/s: print an index at the root Feb 24, 2021
@rsc rsc self-assigned this Feb 24, 2021
@hyangah hyangah modified the milestones: Unreleased, website/later Jun 15, 2022
@rsc rsc changed the title x/website: golang.org/s: print an index at the root proposal: x/website: golang.org/s: print an index at the root Jun 22, 2022
@rsc rsc moved this to Accepted in Proposals Aug 10, 2022
@rsc rsc added this to Proposals Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Proposal website
Projects
Status: Accepted
Development

No branches or pull requests

8 participants
@rsc @agnivade @ALTree @robpike @hyangah @changkun @gopherbot and others