Re: [go-nuts] Downloading go1

[Will Norris]

https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.darwin-386.pkg
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.darwin-amd64.pkg
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.freebsd-386.tar.gz
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.freebsd-amd64.tar.gz
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.linux-386.tar.gz
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.linux-amd64.tar.gz
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.src.tar.gz
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.windows-386.msi
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.windows-386.zip
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.windows-amd64.msi
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/go/go.go1.windows-amd64.zip

On Fri, Dec 2, 2016 at 4:17 PM, Brad Fitzpatrick 
wrote:

> I've asked for a list of our objects under that prefix.
>
>
> On Thu, Dec 1, 2016 at 1:56 PM, Edward Muller 
> wrote:
>
>> For $reasons I need to download the original linux amd64 version of go1.
>>
>> Older go versions are stored under https://storage.googleapis.com
>> /google-code-archive-downloads/v2/code.google.com/go/
>>
>> I have retrieved go1.0.1 (https://storage.googleapis.co
>> m/google-code-archive-downloads/v2/code.google.com/go/go1.0.
>> 1.linux-amd64.tar.gz) and later successfully.
>>
>> But I can't seem to find the right key for go1. I've tried:
>> https://storage.googleapis.com/google-code-archive-downloads
>> /v2/code.google.com/go/go1.linux-amd64.tar.gz
>> 
>> https://storage.googleapis.com/google-code-archive-downloads
>> /v2/code.google.com/go/go1-linux-amd64.tar.gz
>> 
>> https://storage.googleapis.com/google-code-archive-downloads
>> /v2/code.google.com/go/go1.0.linux-amd64.tar.gz
>> 
>> https://storage.googleapis.com/google-code-archive-downloads
>> /v2/code.google.com/go/go1.0-linux-amd64.tar.gz
>> 
>> https://storage.googleapis.com/google-code-archive-downloads
>> /v2/code.google.com/go/go1.0.0.linux-amd64.tar.gz
>> 
>> https://storage.googleapis.com/google-code-archive-downloads
>> /v2/code.google.com/go/go1.0.0-linux-amd64.tar.gz
>> 
>>
>> All respond with:
>> > encoding='UTF-8'?>NoSuchKeyThe
>> specified key does not exist.
>>
>> I've also tried the getting an index (https://storage.googleapis.co
>> m/google-code-archive-downloads/v2/code.google.com/go
>> /),
>> like you can with https://storage.googleapis.com/golang/ (where modern
>> go releases are stored), but that just returns the same error.
>>
>> Can anyone point me to the right https://storage.googleapis.com url for
>> the go1 release?
>>
>> Thanks!
>>
>> --
>> 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+unsubscr...@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Re: [llgo-dev] Re: New home for GoLLVM

[Will Norris]

% curl http://llvm.org/llvm/bindings/go/llvm/?go-get=1

http://www.w3.org/TR/html4/strict.dtd";>


  
  https://llvm.org/svn/llvm-project/llvm/trunk";>


  Redirecting to llvm.org.



On Tue, Dec 27, 2016 at 9:36 AM, Peter Waller  wrote:

> godoc.org shows the documentation, but go get currently gives a 404 if I
> follow the instructions. Has it moved again?
>
> [404] https://llvm.org/llvm/bindings/go/llvm
> [works] https://godoc.org/llvm.org/llvm/bindings/go/llvm
>
> On 21 March 2015 at 08:28, Andrew Wilkins  wrote:
>
>>
>> On Sat, 21 Mar 2015 at 14:55  wrote:
>>
>>> Moved again?...
>>>
>>
>> The old package is still there, but it was recently merged into the LLVM
>> repository, and that is where development happens. Info on building the
>> bindings here:
>> http://llvm.org/svn/llvm-project/llvm/trunk/bindings/go/README.txt
>>
>> Cheers,
>> Andrew
>>
> --
> 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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Re: [llgo-dev] Re: New home for GoLLVM

[Will Norris]

On Sat, Dec 31, 2016 at 4:22 AM, Peter Waller  wrote:

> I don't know about you, but when I do `go get`, go get uses https, not
> HTTP, and the HTTPS link gives a 404 not found.
>

Yes, go get defaults to https, but depending on whether the -insecure flag
is passed, it then falls back to http (see httpsOrHTTP
<https://github.com/golang/go/blob/19adf8aeaae7c898e8efeab18e3162c3807a8756/src/cmd/go/http.go#L73>).
But that only happens when there is an error from httpClient.Get, which
would happen if they didn't have https configured at all.  In the case of a
404, it doesn't fall back to http, so looking more closely I agree that
this is a bit odd.

Trying to refresh the package on godoc.org results in "Error refreshing
package: Timeout getting package files from the version control system." so
it does at least agree that it can't fetch the package anymore.  So
definitely something for the llvm.org admins to fix.


>
> Additionally, when I follow the link in my browser to
> http://llvm.org/llvm/bindings/go/llvm - I get redirected to the LLVM
> homepage, which makes it hard to discover how to use the bindings if I'm
> just looking at an import URL.
>
> $ curl -I http://llvm.org/llvm/bindings/go/llvm/?go-get=1
> HTTP/1.1 200 OK
> Date: Sat, 31 Dec 2016 12:09:29 GMT
> Server: Apache/2.2.22 (Ubuntu)
> Last-Modified: Tue, 14 Oct 2014 01:06:10 GMT
> ETag: "286e03f-15d-505579eea4480"
> Accept-Ranges: bytes
> Content-Length: 349
> Vary: Accept-Encoding
> Content-Type: text/html
>
> $ curl -I https://llvm.org/llvm/bindings/go/llvm/?go-get=1
> HTTP/1.1 404 Not Found
> Date: Sat, 31 Dec 2016 12:09:34 GMT
> Server: Apache/2.2.22 (Ubuntu)
> Vary: Accept-Encoding
> Content-Type: text/html; charset=iso-8859-1
>
>
> On 27 December 2016 at 18:21, Will Norris  wrote:
>
>> % curl http://llvm.org/llvm/bindings/go/llvm/?go-get=1
>>
>> >   "http://www.w3.org/TR/html4/strict.dtd";>
>> 
>> 
>>   
>>   https://llvm.org/svn/llvm-project/llvm/trunk";>
>> 
>> 
>>   Redirecting to llvm.org.
>> 
>> 
>>
>> On Tue, Dec 27, 2016 at 9:36 AM, Peter Waller 
>> wrote:
>>
>>> godoc.org shows the documentation, but go get currently gives a 404 if
>>> I follow the instructions. Has it moved again?
>>>
>>> [404] https://llvm.org/llvm/bindings/go/llvm
>>> [works] https://godoc.org/llvm.org/llvm/bindings/go/llvm
>>>
>>> On 21 March 2015 at 08:28, Andrew Wilkins  wrote:
>>>
>>>>
>>>> On Sat, 21 Mar 2015 at 14:55  wrote:
>>>>
>>>>> Moved again?...
>>>>>
>>>>
>>>> The old package is still there, but it was recently merged into the
>>>> LLVM repository, and that is where development happens. Info on building
>>>> the bindings here:
>>>> http://llvm.org/svn/llvm-project/llvm/trunk/bindings/go/README.txt
>>>>
>>>> Cheers,
>>>> Andrew
>>>>
>>> --
>>> 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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] explain CLA terms

[Will Norris]

The Google CLA is based on the Apache CLA
, which shares the same copyright
language as the Apache 2.0 License
 (section 2).  The vast
majority of Google's open source projects use the Apache license, so in
those cases the copyright language is the same.  I get why it can seem a
little bit odd for BSD licensed projects like Go, but as Ian mentions, we
use a single CLA for all projects, so there will be some minor
discrepancies like this from time to time.

(not on from my google.com account right now, but I manage Google's CLA
system)

On Thu, Jan 5, 2017 at 9:48 AM, Ian Lance Taylor  wrote:

> On Wed, Jan 4, 2017 at 10:58 PM, Xavier Combelle
>  wrote:
> > Le 05/01/2017 à 07:01, Ian Lance Taylor a écrit :
> >
> >> On Wed, Jan 4, 2017 at 8:21 PM, Xavier Combelle
> >>  wrote:
> >>> I was interested in contributing in golang, but was afraid to
> contribute
> >>> because of signing the CLA. After rereading it, I thought that I might
> be
> >>> too much worrying.
> >>>
> >>> Can someone explain in non juridical words what it means.
> >>>
> >>> I was particularly worried by the copyright license terms.
> >>>
> >>> "Grant of Copyright License. Subject to the terms and conditions of
> this
> >>> Agreement, You hereby grant to Google and to recipients of software
> >>> distributed by Google a perpetual, worldwide, non-exclusive, no-charge,
> >>> royalty-free, irrevocable copyright license to reproduce, prepare
> derivative
> >>> works of, publicly display, publicly perform, sublicense, and
> distribute
> >>> Your Contributions and such derivative works."
> >>>
> >>> For what I understand it goes further than BSD licensing, for example
> it
> >>> doesn't imply that the BSD copyright notice must stay in code source
> and
> >>> along with binary distribution.
> >> I'm not sure I understand exactly what you are asking.  The copyright
> >> license agreement, which you sign if you want to contribute code to
> >> the Go project, is not the same as the BSD license, which is the
> >> license used for the Go distribution.  We explicitly don't want every
> >> contributor to produce their own version of the BSD license; we want
> >> all the code to be distributed under the copyright of "The Go
> >> Authors."
> >>
> >> It is true that if you sign the CLA and give the code to Google that
> >> Google could then re-release the code under a license other than the
> >> BSD license.  There is no reason for Google to do that, but it would
> >> be permitted to do so.  But that is not significantly different from
> >> what the BSD license permits anyhow.  The BSD license, unlike, say,
> >> the GPL, permits additional restrictions to be placed on the code.
> >> The only relevant difference between the CLA and using the BSD license
> >> yourself is that Google could distribute the code while omitting the
> >> BSD license entirely.  Do you find that to be troublesome?
> >>
> >> Ian
> >>
> > Yes I found very troublesome that google has the right to omit BSD
> license entirely by doing that it has rights that other contributors don't
> have.
> > They have also the right to totally replace it by their license of choice
>
> What specific rights are you concerned about?
>
> The BSD license already allows everyone to add additional
> restrictions, provided that they do not actually remove the BSD
> license.  So, yes, contributing code under the CLA would permit Google
> to take your code and distribute it with additional restrictions and
> also without the BSD license used by the Go project.  That is a
> change, but it does not seem to me to be a change that actually
> matters.
>
> The reason that Google writes the CLA in this way is so that people
> can sign a single CLA in order to contribute to any Google project.
> Google has many free software projects under different licenses.  It's
> simpler for most people, and certainly simply for the project
> developers, if people sign a single CLA, rather than to sign a
> separate CLA for each project.
>
>
> >> We explicitly don't want every
> >> contributor to produce their own version of the BSD license; we want
> >> all the code to be distributed under the copyright of "The Go
> >> Authors."
> >
> > The point of using the go license as it is stated is to guarantee that
> by reusing the code, contributors can't produce their own version of BSD
> license.
>
> That isn't what I said, and it's not what I meant.  Contributors can
> make their own copy of the Go code and add their own license.  What I
> meant is that the Go distribution itself, the one that we distribute
> on golang.org, comes with a single license.  Once someone has a copy
> of that code, there is nothing preventing them from distributing it
> under a different license, as long as they also keep a copy of the BSD
> license.
>
> > The fact it will be distributed under this terms is pretty much
> guaranteed for all distribution except precisely the dis

Re: [go-nuts] Urlwatch

['Will Norris' via golang-nuts]

I've also had a lot of success using https://github.com/gregjones/httpcache
for a few projects

On Tue, Jun 28, 2016 at 9:18 AM, Tong Sun  wrote:

> Just want to get into the loop for future updates...
>
>
> On Saturday, June 25, 2016 at 9:08:23 AM UTC-4, Mohammad Nasirifar wrote:
>>
>> Btw I would like to work on that!
>>
>> On Saturday, June 25, 2016 at 5:11:34 PM UTC+4:30, Henrik Johansson wrote:
>>>
>>> Cache headers, etags etc and dynamic scheduling of re-fetch sounds
>>> useful. Why not start a little library?
>>>
>>> On Sat, Jun 25, 2016, 13:51 Johann Höchtl  wrote:
>>>


 Am Donnerstag, 23. Juni 2016 17:04:54 UTC+2 schrieb Shawn Milochik:
>
> What do you need it to do, specifically? Doing an http.Get on a page
> and storing and comparing the bytes or a hash is something you could write
> in under a minute. Why not just do that?
>

 Get notified when a change happens. Your approach would certainly work
 but it's super-naive. Perform a Head Lookup and check the Timestamp when
 the resurce was changed, ETags, etc. all come to my mind to checl before
 downloading the whle resource. Or being able to specify a nesting level
 upto which embeded resources will be fetched recursively to check for
 change etc.

 So I think somebody else spent more time to think about that. There are
 services in other languages of course but I was hoping for some sort of
 getable service in Golang / package.

 --
 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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Go is for everyone

['Will Norris' via golang-nuts]

I don't think the GopherCon 2016 videos are online yet, but when they are
I'd recommend taking a look at Katrina Owen's talk, "Mind the Gap" which
touches on exactly this topic.  It might give you some ideas.

On Tue, Jul 19, 2016 at 8:39 AM, Daniel Skinner  wrote:

> is the Go tour really that out of touch for people with little to no
> programming experience? I'd think there's enough in there to keep one busy
> for quite a while. Now, whether that work is actually interesting to them
> is another matter...
>
> I sat my 9 year old daughter in front of the tour a few months back and
> she completed a number of samples. She had questions for words she's never
> heard so maybe extending the tour with pop-out help on jargon might be a
> nice contrast to how the tour currently compares itself to other languages
> for basic constructs (the inexperienced vs the experienced).
>
> Understanding errors on the screen is another important part that's pretty
> much uncovered, and so biased towards those that have dealt with errors
> before from other languages.
>
> On Tue, Jul 19, 2016 at 10:16 AM Matt Aimonetti 
> wrote:
>
>> I just wanted to point out a post I published today talking about the
>> fact that we are often leaving new / less experienced Go developers high
>> and dry:
>> https://medium.com/@mattetti/go-is-for-everyone-b4f84be04c43
>>
>> I'd love to see what you all in mind to help new or junior developers.
>> Maybe share some of the pain points you've experienced or seen (for
>> instance setting up the Go path, finding resources to get started etc...)
>> I'm thinking about a bunch of very short posts on basic topics and maybe a
>> real beginner tour of Go. We are going to do a beginner night next month at
>> our LA/Santa Monica Go meetup and hopefully better understand what the
>> current pain points/blockers are.
>>
>> What do you think?
>>
>> --
>> 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+unsubscr...@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Re: Who wants to use Go to process your camera's raw files?

['Will Norris' via golang-nuts]

If you start in a separate repo, make sure you are checking CLAs all along
the way (I can help you set that up if needed).  Otherwise, any move into
/x/image just becomes that much more difficult.

And yes, I would definitely start with the standard Go license.

On Thu, Sep 1, 2016 at 12:28 AM, Nigel Tao  wrote:

> On Thu, Sep 1, 2016 at 12:46 PM, Jonathan Pittman
>  wrote:
> > Does the license need to be the same as the standard Go License if it
> starts
> > in another repo and then moves over?
>
> IANAL, but that seems best.
>
> --
> 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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.