Re: [go-nuts] Go 2 review process

2020-07-20 Thread Ian Lance Taylor
On Mon, Jul 20, 2020 at 11:13 AM medienwer...@gmail.com wrote: > > re : "However, I don't understand how to make > that work in practice. " > > from my research so far I found tons of Github Actions related to > "Projects"... > > just some examples: > https://github.com/marketplace/actions/all-i

Re: [go-nuts] Go 2 review process

2020-07-20 Thread medienwer...@gmail.com
Dear Ian re : "However, I don't understand how to make that work in practice. " from my research so far I found tons of Github Actions related to "Projects"... just some examples: https://github.com/marketplace/actions/all-in-one-project https://github.com/marketplace/actions/assign-to-one-p

Re: [go-nuts] Go 2 review process

2020-07-20 Thread David Skinner
Not having a GitHub account is a non-issue. - It is an issue now because the enhancement process is on GitHub issues which does not include voting or weighting of votes. It is a trivial matter to use gohugo.io with a package that integrates GitHub issues as the repository for comments. ---

Re: [go-nuts] Go 2 review process

2020-07-20 Thread 'Axel Wagner' via golang-nuts
Hi, ISTM that all those filtering-suggestions are quietly redefining the problem. The Go team didn't say "we don't have time to read all proposals", they said "we don't have time to argue every proposal in-depth". So if your concern was "that is bad, because I want all proposals to get enough atte

Re: [go-nuts] Go 2 review process

2020-07-20 Thread Jan Mercl
On Mon, Jul 20, 2020 at 1:00 PM Markus Heukelom wrote: > > Would it be an idea to allow people only to label something as proposal if > they have at least some support / voucher for the idea? Say N>10 general > upvotes or 1 upvote from a golang committer? The problem is that not everyone has a

Re: [go-nuts] Go 2 review process

2020-07-20 Thread David Skinner
I really like Markus Heukelon's suggestion. There is no need for the Go team to evaluate each proposal, that is a silly waste of a valuable and limited resource. Having a list of all proposals with voting means that the most popular items float to the top and the worst float to the bottom and newb

Re: [go-nuts] Go 2 review process

2020-07-20 Thread Markus Heukelom
Would it be an idea to allow people only to label something as proposal if they have at least some support / voucher for the idea? Say N>10 general upvotes or 1 upvote from a golang committer? By allowing the "proposal" label, you sort of give people the idea that their idea will be "triaged",

Re: [go-nuts] Go 2 review process

2020-07-19 Thread Tyler Compton
I had forgotten about the multidimensional slices proposal. That's a very good counter-example. On Sun, Jul 19, 2020 at 4:12 AM Ian Davis wrote: > On Sun, 19 Jul 2020, at 2:08 AM, Ian Lance Taylor wrote: > > On Sat, Jul 18, 2020 at 12:19 AM Tyler Compton > wrote: > > > > > > I'm beginning to th

Re: [go-nuts] Go 2 review process

2020-07-19 Thread Ian Davis
On Sun, 19 Jul 2020, at 2:08 AM, Ian Lance Taylor wrote: > On Sat, Jul 18, 2020 at 12:19 AM Tyler Compton wrote: > > > > I'm beginning to think that community members (like myself) can't > > reasonably be expected to put in the necessary effort to champion a sizable > > language change. I think

Re: [go-nuts] Go 2 review process

2020-07-18 Thread Ian Lance Taylor
On Sat, Jul 18, 2020 at 12:19 AM Tyler Compton wrote: > > I'm beginning to think that community members (like myself) can't reasonably > be expected to put in the necessary effort to champion a sizable language > change. I think it was Ian who made multiple generics draft proposals just to > re

Re: [go-nuts] Go 2 review process

2020-07-18 Thread David Skinner
While I have over 50 years of programming experience, I am also quite old and sometimes have senile moments. I once wrote an extremely well-written bug report complaining about the use of the backtick which is not on my keyboard, explained why it should not be used, and then presented a workaro

Re: [go-nuts] Go 2 review process

2020-07-18 Thread Randall Oreilly
> On Jul 16, 2020, at 3:35 PM, Ian Lance Taylor wrote: > > The language is stable and is not looking to change in any > significant way (except perhaps for adding generics). We've realized > that we need to be upfront about that. The Go2 process certainly created the expectation that the la

Re: [go-nuts] Go 2 review process

2020-07-18 Thread 'Axel Wagner' via golang-nuts
There seems to be an assumption that, given enough time and effort, any idea could get accepted into the language. But that clearly can't be so. It might be frustrating to hear that your particular idea just isn't considered a good idea, but it's a necessity that most ideas go that route. It's not

Re: [go-nuts] Go 2 review process

2020-07-18 Thread Max
I have a proposal for improving Go proposal procedure. It stems from two "issues" highlighted in several occasions: 1. core Go team is spending an increasing amount of time discussing a larger number of proposals. All of them are commented and discussed by core Go team, and in the end

Re: [go-nuts] Go 2 review process

2020-07-18 Thread Tyler Compton
I'm beginning to think that community members (like myself) can't reasonably be expected to put in the necessary effort to champion a sizable language change. I think it was Ian who made multiple generics draft proposals just to reject them himself, then Ian and Robert Griesemer spent more untold h

Re: [go-nuts] Go 2 review process

2020-07-17 Thread Ian Lance Taylor
On Fri, Jul 17, 2020 at 10:20 AM medienwer...@gmail.com wrote: > > With your considerations in mind I suggest a well defined triage > mode/"traffic light" - system for processing language feature proposals. > > When your/the teams bias is clear, the indication shows the proposer/the > community

Re: [go-nuts] Go 2 review process

2020-07-17 Thread Ian Lance Taylor
On Fri, Jul 17, 2020 at 5:40 AM giuliom...@gmail.com wrote: > > I believe this is an important part of the community, without such process, > we would not get new smart ideas for Go. I don't know exactly the rejection > rate, but even if it was 1 accepted idea out of 100, all of them must be >

Re: [go-nuts] Go 2 review process

2020-07-17 Thread medienwer...@gmail.com
Dear Ian With your considerations in mind I suggest a well defined triage mode/"traffic light" - system for processing language feature proposals. When your/the teams bias is clear, the indication shows the proposer/the community feasible and/or practicable "next steps". Also a collection of

Re: [go-nuts] Go 2 review process

2020-07-17 Thread giuliom...@gmail.com
I believe this is an important part of the community, without such process, we would not get new smart ideas for Go. I don't know exactly the rejection rate, but even if it was 1 accepted idea out of 100, all of them must be reviewed in order to spot the right one. On the other hand, I unders

Re: [go-nuts] Go 2 review process

2020-07-16 Thread Ian Lance Taylor
On Thu, Jul 16, 2020 at 1:32 PM Brandon Bennett wrote: > > I have just read > https://github.com/golang/go/issues/33892#issuecomment-659618902 and since it > was posted on a closed issue I wanted to comment a bit more. > > I subscribed to this issue and read the updates for both the Go2 proposal

[go-nuts] Go 2 review process

2020-07-16 Thread Brandon Bennett
I have just read https://github.com/golang/go/issues/33892#issuecomment-659618902 and since it was posted on a closed issue I wanted to comment a bit more. I subscribed to this issue and read the updates for both the Go2 proposals as well as the Go1 proposals and I enjoy reading them. I unders