Go package management proposal process
860 views
Skip to first unread message
Peter Bourgon
Jul 29, 2016, 3:46:01 AM7/29/16
to golang-nuts
Hello,
For well over a year, a group of dedicated Gophers have been
discussing the package management situation on a dedicated mailing
list, in Slack #vendor, and several communication channels. A few
tools have emerged from those broad conversations, including Glide,
govendor, gb, and the SAT solver gps. And at GopherCon 2016, a panel
with several members of the core Go team was held.
While much remains to be decided, a few things are clear. The package
management solution, whatever it will be, will take the form of one or
more official Go language proposals. And the proposals (and their
eventual implementation) will be driven by a small committee of
dedicated Gophers.
In the interest of progress, I've volunteered to shepherd this process
from start to finish. I've created a document detailing a proposal for
the process itself. If this topic interests you, please review and
comment.
https://docs.google.com/document/d/18tNd8r5DV0yluCR7tPvkMTsWD_lYcRO7NhpNSDymRr8
As much as anything can be official, I hope that this will be the
official process, leading to the long-desired blessed solution.
Regards,
Peter Bourgon.
For well over a year, a group of dedicated Gophers have been
discussing the package management situation on a dedicated mailing
list, in Slack #vendor, and several communication channels. A few
tools have emerged from those broad conversations, including Glide,
govendor, gb, and the SAT solver gps. And at GopherCon 2016, a panel
with several members of the core Go team was held.
While much remains to be decided, a few things are clear. The package
management solution, whatever it will be, will take the form of one or
more official Go language proposals. And the proposals (and their
eventual implementation) will be driven by a small committee of
dedicated Gophers.
In the interest of progress, I've volunteered to shepherd this process
from start to finish. I've created a document detailing a proposal for
the process itself. If this topic interests you, please review and
comment.
https://docs.google.com/document/d/18tNd8r5DV0yluCR7tPvkMTsWD_lYcRO7NhpNSDymRr8
As much as anything can be official, I hope that this will be the
official process, leading to the long-desired blessed solution.
Regards,
Peter Bourgon.
omarsharif...@gmail.com
Jul 29, 2016, 5:39:03 AM7/29/16
to golang-nuts, pe...@bourgon.org
This is great news! For me this was the last wrinkle in the Go eco system, glad to here its getting an official solution with some talented people involved. Kudos to everyone involved in this.
Dave Cheney
Aug 6, 2016, 12:58:48 AM8/6/16
to golang-nuts, pe...@bourgon.org
Hello,
I wish to nominate myself to be part of the working group. I have written up my position statement here:
I am seeking a second for my nomination.
Thank you
Dave
James Pirruccello
Aug 6, 2016, 1:16:42 AM8/6/16
to golang-nuts, pe...@bourgon.org
I'd be happy to second your nomination.
Peter Bourgon
Aug 6, 2016, 4:10:13 AM8/6/16
to James Pirruccello, golang-nuts
To be clear, there is no self-nomination or seconding/voting process
in place at this time. Thanks for bearing with me as I iron out the
final details of the process.
in place at this time. Thanks for bearing with me as I iron out the
final details of the process.
Jessica Frazelle
Aug 6, 2016, 11:11:12 AM8/6/16
to golang-nuts
+1 to Dave Cheney.
I agree we need as simple a solution as possible.
I propose myself for the working group. I have dealt with the vendoring in the docker project as well as medium to small sized projects and most currently in kubernetes.
If elected, my platform will fight to make vendoring as simple and seamless to use as the tool we love so much, gofmt.
Let's stop the madness of jumping 3 steps ahead, and arguing in circles. Let's solve the problems from ground zero. Starting with a problem statement.
Make go vendoring great again (wait... great for the first time ;).
Jess
I agree we need as simple a solution as possible.
I propose myself for the working group. I have dealt with the vendoring in the docker project as well as medium to small sized projects and most currently in kubernetes.
If elected, my platform will fight to make vendoring as simple and seamless to use as the tool we love so much, gofmt.
Let's stop the madness of jumping 3 steps ahead, and arguing in circles. Let's solve the problems from ground zero. Starting with a problem statement.
Make go vendoring great again (wait... great for the first time ;).
Jess
Peter Bourgon
Aug 6, 2016, 11:24:07 AM8/6/16
to Jessica Frazelle, golang-nuts
Again, there is no nomination process for the committee right now. Please don't propose yourself or others.
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jessica Frazelle
Aug 6, 2016, 11:51:51 AM8/6/16
to Peter Bourgon, golang-nuts
Sorry Peter that got stuck in moderation I wrote it before your other message
--
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Peter Bourgon
Aug 6, 2016, 2:24:39 PM8/6/16
to Jessica Frazelle, golang-nuts
Ah! Ha. All good.
On Sat, Aug 6, 2016 at 17:51 'Jessica Frazelle' via golang-nuts <golan...@googlegroups.com> wrote:
Sorry Peter that got stuck in moderation I wrote it before your other message
On Saturday, August 6, 2016, Peter Bourgon <pe...@bourgon.org> wrote:
Again, there is no nomination process for the committee right now. Please don't propose yourself or others.
On Sat, Aug 6, 2016 at 17:11 'Jessica Frazelle' via golang-nuts <golan...@googlegroups.com> wrote:
+1 to Dave Cheney.
I agree we need as simple a solution as possible.
I propose myself for the working group. I have dealt with the vendoring in the docker project as well as medium to small sized projects and most currently in kubernetes.
If elected, my platform will fight to make vendoring as simple and seamless to use as the tool we love so much, gofmt.
Let's stop the madness of jumping 3 steps ahead, and arguing in circles. Let's solve the problems from ground zero. Starting with a problem statement.
Make go vendoring great again (wait... great for the first time ;).
Jess
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
Rob Pike
Aug 6, 2016, 7:41:10 PM8/6/16
to Peter Bourgon, Jessica Frazelle, golang-nuts
I would like to propose a cloture vote to abrogate the need to entable a veto to the de facto habeas corpus motion that is de jure blocking progress on this endeavor.
Or else just get on with it.
-rob
On Sun, Aug 7, 2016 at 4:24 AM, Peter Bourgon <pe...@bourgon.org> wrote:
Ah! Ha. All good.
On Sat, Aug 6, 2016 at 17:51 'Jessica Frazelle' via golang-nuts <golan...@googlegroups.com> wrote:
Sorry Peter that got stuck in moderation I wrote it before your other message
On Saturday, August 6, 2016, Peter Bourgon <pe...@bourgon.org> wrote:
Again, there is no nomination process for the committee right now. Please don't propose yourself or others.
On Sat, Aug 6, 2016 at 17:11 'Jessica Frazelle' via golang-nuts <golan...@googlegroups.com> wrote:
+1 to Dave Cheney.
I agree we need as simple a solution as possible.
I propose myself for the working group. I have dealt with the vendoring in the docker project as well as medium to small sized projects and most currently in kubernetes.
If elected, my platform will fight to make vendoring as simple and seamless to use as the tool we love so much, gofmt.
Let's stop the madness of jumping 3 steps ahead, and arguing in circles. Let's solve the problems from ground zero. Starting with a problem statement.
Make go vendoring great again (wait... great for the first time ;).
Jess
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
Peter Bourgon
Aug 8, 2016, 2:04:05 PM8/8/16
to golang-nuts
Thank you to the 40+ Gophers who have already signaled interest. We
will be using Google Docs for future work and discussion, so if you've
added your name, can you please send me an email address for future
Google Docs invites? You can reply to this email privately, or contact
me on Gophers Slack peterbourgon.
will be using Google Docs for future work and discussion, so if you've
added your name, can you please send me an email address for future
Google Docs invites? You can reply to this email privately, or contact
me on Gophers Slack peterbourgon.
Lucio
Sep 7, 2016, 12:40:18 AM9/7/16
to golang-nuts, pe...@bourgon.org
Probably too obvious a suggestion to be taken seriously, but just in case no one else has thought of this, would a "go vendor" command be useful as the main objective here?
Lucio.
Reply all
Reply to author
Forward
0 new messages