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

x/website/blog: write a post on go.mod and go.sum misconceptions #48539

Open
mvdan opened this issue Sep 22, 2021 · 1 comment
Open

x/website/blog: write a post on go.mod and go.sum misconceptions #48539

mvdan opened this issue Sep 22, 2021 · 1 comment
Labels
Milestone

Comments

@mvdan
Copy link
Member

@mvdan mvdan commented Sep 22, 2021

This issue aims to track https://groups.google.com/g/golang-dev/c/wkIlHZL-NNk/m/xy2fFHs6BwAJ. We all seemed to agree that this blog post would be a good idea, but tracking who will do that and when it will happen is hard if all we have is an old email thread that's easy to forget.

I am more than happy to volunteer my help in this, or to even write the first draft. I don't think I've authored anything on the Go blog before. That said, I'm not a technical writer, and there are others who know the details of how go.mod and go.sum work better than I do. So I'm also happy to stand aside or simply provide reviews.

cc @jayconrod @stevetraut

@gopherbot gopherbot added this to the Unreleased milestone Sep 22, 2021
@mvdan
Copy link
Member Author

@mvdan mvdan commented Sep 22, 2021

In that email thread, Jay mentions whether this should be a maintained doc page as opposed to a mostly-frozen blog post. I replied to that point by mentioning that a blog post gets much wider attention as "new content" that can be digested in fifteen minutes. As opposed to a section within a large body of documentation that would likely take a full day's worth of attention to slowly go through.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants