I think they are still open to it, in a very sceptical way. Basically they are asking [1] the public/users for papers/documents/articles/blogs, describing the use cases of generics in Golang. How would they use it? Why is it required (as in can you not do it easily/better without generics)? Stuff like that. They basically aren't convinced that generics is something they need/want in Go, but if the users can convince them, they will still go for it in the future of Go.
"I'm focusing today on possible major changes, such as
additional support for error handling, or introducing
immutable or read-only values,
or adding some form of generics,
or other important topics not yet suggested.
We can do only a few of those major changes.
We will have to choose carefully."
[1]: https://blog.golang.org/toward-go