On Mon, Jul 20, 2020 at 11:13 AM medienwer...@gmail.com <medienwerksalzb...@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-in-one-project > https://github.com/marketplace/actions/assign-to-one-project > https://github.com/marketplace/actions/github-projects-column-mirror > https://github.com/marketplace/actions/automate-projects > ... > > My proposal: > > - you configure a public github project with columns ("proposal", "language > change", "Go2", "Feature Request",...) that operates on golang organizational > level; link it to go language repo! > - the contributer files a "request" issue(just title, feature, subject; no > details) in the go repo > - @settings/users of the public project you invite the contributor to drop a > "proposal" note (maybe through github actions(?); this is the detailed > contribution, proposal....! > - in the project columns you make the "triage" by editing the note and/or > converting notes to issues ("RFCs") for tracking, label adding,... > > let me work on the github actions side in the next couple of days; maybe I > can figure out automation...
Thanks, but it's not the mechanical steps that are time consuming. Ian > Ian Lance Taylor schrieb am Freitag, 17. Juli 2020 um 19:54:46 UTC+2: >> >> On Fri, Jul 17, 2020 at 10:20 AM medienwer...@gmail.com >> <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 feasible and/or practicable "next steps". >> > >> > Also a collection of "reference cases" can guide the growing number of >> > gophers, viable ideas and solutions. >> > >> > Following posts explain the needs: >> > >> > https://blog.golang.org/toward-go2 >> > >> > https://blog.golang.org/experiment >> > >> > https://blog.golang.org/go2-here-we-come >> >> Thanks for the suggestion. However, I don't understand how to make >> that work in practice. Who is going to take the time to show feasible >> and practical next steps for each proposal? How is that different >> from what we have been doing for the last year? >> >> Ian > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/86ba57c2-7c82-4f0f-8a52-007c8ded6fd4n%40googlegroups.com. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcXEZiyW%3D0imRBAej0wf8E78j_dScOZLTOzj82WVX0%3DC6g%40mail.gmail.com.
