Package Management Proposal

2722 views
Skip to first unread message

Peter Bourgon

unread,
Aug 12, 2016, 7:24:55 AM8/12/16
to go-package...@googlegroups.com
Hi all,

Just wanted to drop an update to the package management proposal
process, as well as create a thread for the purpose. For reference,
here's the original email to this list[0], and the Google Doc
describing the process[1]. I'm trying to update the latter with the
current state of the world every few days.

[0] https://groups.google.com/d/msg/go-package-management/a55P0_FU_jA/Y9t_mBroBwAJ
[1] https://docs.google.com/document/d/18tNd8r5DV0yluCR7tPvkMTsWD_lYcRO7NhpNSDymRr8

If you're interested in being part of the process, please make sure
your name is added to the list (suggest an addition and I will approve
it) — and please also contact me with an email address that can be
used to interact with Google Docs. You can email me privately with
that information, or message me (peterbourgon) on the Gophers Slack.
If you've added yourself already, and I don't have an email address,
your name is annotated with NEED EMAIL.

We will likely go with a Google Doc-centered workflow, where members
of the Committee have editing rights; all interested Gophers have
commenting rights; and the general public has viewing rights.

Finally, thanks to everyone who's decided to take part! The feedback
has been really positive and encouraging. I'm optimistic that we're on
the right path :)

Cheers,
Peter.

Peter Bourgon

unread,
Aug 26, 2016, 2:24:43 PM8/26/16
to go-package...@googlegroups.com
As a reminder, in July I started the Go Packaging Proposal doc[0] with
the goal “To produce, have accepted, and implement a complete proposal
which addresses the concern of package management.” Thanks to everyone
who’s signaled interest. That process involves creating a small
committee to drive the proposal from start to finish.

In forming the committee I’ve focused on three important points—

1. First and foremost, that the design and discussion process, and
ultimate technical solution, should be driven by a data- and
user-needs-centric methodology.

2. That the schedule outlined in the process doc should be adhered to
as closely as possible. That means design-complete by end September,
and proposal-complete by end October, so that any possible language or
tooling changes can make the 1 November feature freeze for Go 1.8.

3. Each member should have or make time to devote to this process, so
that both points above are feasible :)

A committee size of four I believe most effectively balances a variety
of voice and opinion, and an ability to effectively decide and act.
After a great deal of consultation with, and feedback from, key
members of the Go language and package management/vendoring
communities, I'm happy to announce that Andrew Gerrand, Edward Muller,
Jessie Frazelle, and Sam Boyer have all agreed to serve on the package
management committee.

Andrew needs no introduction, as he's been leading the Go community
advocacy efforts from within the Go team since nearly the very
beginning. Andrew brings an unmatched perspective on the current state
and evolution of the Go language and tooling, and will be instrumental
in shepherding any possible language or tooling changes through the
proposal process.

Ed has been maintaining the godep project for the past two years, and
brings a pragmatic and user-centric perspective to the committee.

Jessie has been on the Go package management front lines for years,
originally with Docker and now with Kubernetes. I can't think of
anyone better to represent the needs of large Go projects and
organizations.

Sam may be best known in the Go community for his article "So you want
to write a package manager[1]." With his background and work on the Go
Package Solver, Sam brings theoretical depth and rigor to the
committee.

Keeping the committee small was absolutely essential, but it quickly
became apparent that several unquestionably qualified individuals,
whose efforts and experience would be critical to our success, would
be excluded. We decided that an advisory group, while not part of the
original Process doc, would enable the committee to remain small and
nimble, while leveraging the value, effort, and experience of a larger
group. The maintainers of popular package management tools Glide (Matt
Farina), govendor (Daniel Theophanes) and gb (Dave Cheney), as well as
Steve 'spf13' Francia (Hugo, Cobra) have all graciously agreed to
support in this role. Their job will be to help compile user and
domain research, and to represent user needs whenever the committee
needs input. Matt and Steve in particular have been hard at work on an
updated tool survey and user requirement doc; details forthcoming.
Both I and the committee are incredibly grateful to each of them for
their support.

I'll act as secretary, note-taker, and communications director for the
committee on an as-needed basis, to free them from the overhead. If
you have any questions about the process, please direct them to me.
And stay tuned for links to research and design Google Docs.

[0] https://docs.google.com/document/d/18tNd8r5DV0yluCR7tPvkMTsWD_lYcRO7NhpNSDymRr8
[1] https://medium.com/@sdboyer/so-you-want-to-write-a-package-manager-4ae9c17d9527#.iqtluxnrr

Andrew Gerrand

unread,
Aug 26, 2016, 5:19:45 PM8/26/16
to Peter Bourgon, go-package...@googlegroups.com
On behalf of the committee and the Go community in general, thanks Peter for stepping up to organize this. I'm excited to get started.

--
You received this message because you are subscribed to the Google Groups "Go Package Management" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-package-management+unsub...@googlegroups.com.
To post to this group, send email to go-package-management@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jessica Frazelle

unread,
Aug 26, 2016, 5:36:35 PM8/26/16
to Andrew Gerrand, Peter Bourgon, go-package...@googlegroups.com
Yes! I second that! Thanks Peter! And I'm so stoked!
To unsubscribe from this group and stop receiving emails from it, send an email to go-package-management+unsubscri...@googlegroups.com.

To post to this group, send email to go-package-management@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Go Package Management" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-package-management+unsub...@googlegroups.com.
To post to this group, send email to go-package-management@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--


Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu

Edward Muller

unread,
Aug 26, 2016, 6:03:02 PM8/26/16
to Jessica Frazelle, Andrew Gerrand, Peter Bourgon, go-package...@googlegroups.com
:+100:

To unsubscribe from this group and stop receiving emails from it, send an email to go-package-manag...@googlegroups.com.
To post to this group, send email to go-package...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Go Package Management" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-package-manag...@googlegroups.com.
To post to this group, send email to go-package...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--


Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu

--
You received this message because you are subscribed to the Google Groups "Go Package Management" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-package-manag...@googlegroups.com.
To post to this group, send email to go-package...@googlegroups.com.

Dave Cheney

unread,
Aug 26, 2016, 10:57:07 PM8/26/16
to Go Package Management
I want to continue to add my voice of support to Peter for sheparding this process.

Peter Bourgon

unread,
Sep 8, 2016, 4:25:23 PM9/8/16
to go-package...@googlegroups.com
A small update. The committee has now been around for about ten days,
and they've had several productive meetings. For the most part,
everyone is still building a shared context, and getting a feel the
problem space.

There are 3 research documents which are "due" at the end of the
month; my goal is to have preliminary versions of those docs publicly
accessible by the end of this week or, latest, early next week. I'll
post links here when that happens.

Also, the dependency management survey
(https://spf13.typeform.com/to/zkP0lx) will be closing tomorrow. If
you haven't taken it, please do! The results will take a little while
to analyze and make generally consumable, but I'm pushing to have that
done as soon as possible, and we'll be sure to make it public as well.

Cheers,
Peter.

joa...@gmail.com

unread,
Nov 1, 2016, 4:47:27 PM11/1/16
to Go Package Management, pe...@bourgon.org
Awesome to see this is happening!
Reply all
Reply to author
Forward
0 new messages