Skip to content

x/pkgsite: pkg.go.dev tracking issue #33654

Closed

Description

@julieqiu

This is the tracking issue for the Go discovery site, previously announced in the Go Modules in 2019 blog post. The parent umbrella issue for all “godoc”-like projects is #26827.

The website will display documentation for Go packages with version support and provide features that help developers discover and evaluate Go packages or modules.

The discovery site is currently in development. We are working towards launching by the end of the year.

As mentioned in golang/gddo#567 (comment), some early mockups of the discovery site were first shared in the "Finding Dependable Go Packages" talk (slides) at GothamGo 2019 (video). These can be seen starting at slide 92.

If you are interested in this topic, please subscribe to this issue. We will use it to post future updates. You can also find us in the #tools channel on the Gophers Slack.

Activity

  1. added
    NeedsFixThe path to resolution is known, but the work has not been done.
    on Aug 14, 2019
  2. added this to the Unreleased milestone on Aug 14, 2019
  3. self-assigned this
    on Aug 14, 2019
  4. locked and limited conversation to collaborators on Aug 14, 2019
  5. unlocked this conversation on Aug 21, 2019
  6. locked and limited conversation to collaborators on Aug 21, 2019
  7. julieqiu commented on Nov 13, 2019

    @julieqiu
    MemberAuthor

    The discovery site is now live at pkg.go.dev!

    You can read about it on the latest Go blog post.

    We hope that you will try it out, and we would love to hear your feedback! We are just getting started with building out pkg.go.dev, so some bugs are to be expected. Please file any issues and share your thoughts with us by clicking "Share Feedback" or "Report an Issue" in the footer of every page , or by emailing <removed>.

    We look forward to hearing everyone’s feedback!

  8. julieqiu commented on Nov 26, 2019

    @julieqiu
    MemberAuthor

    We would love to know if your organization is running an internal Go documentation service, to inform our open source strategy for pkg.go.dev.

    If this is something that your organization is currently doing, please share your use case with us by sending an email to <removed>, or filling out the Go Developer survey.

  9. julieqiu commented on Dec 30, 2019

    @julieqiu
    MemberAuthor

    We recently updated pkg.go.dev/license-policy to include our list of accepted licenses, and to clarify that we use github.com/google/licensecheck for license detection. If you still have questions about your license, feel free to file an issue email <removed>.

    We plan to respond to all issues in the new year, and to continue working with our legal team to resolve any license issues. Thanks for being patient with us as we work through them!

  10. changed the title [-]discovery: Go discovery site tracking issue[/-] [+]pkg.go.dev: Go discovery site tracking issue[/+] on Jan 22, 2020
  11. julieqiu commented on Jan 24, 2020

    @julieqiu
    MemberAuthor

    Thanks to everyone for all the feedback so far on go.dev!

    We’ve read it all, and it’s helping us to make the site better.

    A few themes have emerged, and one of them is about feedback itself. Many of you have pointed out that certain types of discussion would be better served by a public issue tracker.

    For that reason, we're opening up the Go issue tracker as an additional channel for feedback for go.dev. The issue tracker is useful to post issues that you think would be relevant to other members of the Go community, and to share features and issues that you would like to have discussed on a public forum.

    Feel free to start sharing your ideas on the Go issue tracker! Please prefix your issues with go.dev:.

    You can continue sending us feedback via our current channels:

    We look forward to hearing your feedback!

  12. added and removed
    NeedsFixThe path to resolution is known, but the work has not been done.
    on Jan 28, 2020
  13. julieqiu commented on Jan 31, 2020

    @julieqiu
    MemberAuthor

    We are planning to redirect traffic from godoc.org to pkg.go.dev, and want to hear your feedback on what you want to see on pkg.go.dev! For details, see the Next steps for pkg.go.dev blog post.

    You can share your feedback with us by:

    • Posting on the Go issue tracker
    • Email <removed>
    • Clicking “Share Feedback” or“Report an Issue” in the footer on the site
  14. gopherbot commented on Feb 3, 2020

    @gopherbot
    Contributor

    Change https://golang.org/cl/217539 mentions this issue: devapp/owners, internal/gophers: add owners for {pkg,learn,}.go.dev

  15. julieqiu commented on Feb 14, 2020

    @julieqiu
    MemberAuthor

    You can now redirect your own requests from godoc.org to pkg.go.dev, by visiting godoc.org?redirect=on.

    This will set a cookie in your browser, so that any request you make to godoc.org will be redirected to pkg.go.dev.

    If you want to turn this feature off, you can do so by visiting godoc.org?redirect=off.

    Thanks to @jamalc for this contribution! (Go issue 37099)

  16. changed the title [-]pkg.go.dev: Go discovery site tracking issue[/-] [+]x/pkgsite: pkg.go.dev tracking issue[/+] on Jun 15, 2020
  17. julieqiu commented on Aug 17, 2020

    @julieqiu
    MemberAuthor

    Closing this tracking issue, as information on the project direction will be shared in the x/pkgsite README Roadmap.

    Additionally, the following milestones are used to track work for 2020:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions