Re: Golang mudules to follow common grouping

[Sharlatan Hellseher]

Hi,

I stick to this flow

- pick a package from golang.scm e.g. go-package-a

- identify destination (any of golang-*.scm)

- place go-package-a to e.g. golang-web.scm in alphabetic order

- remove go-package-a from golang.scm

- by using magit find all authors contributing to go-package-a

- place found copyright headers to golang-web.scm if they are unique 

- grep -l -r go-package-a gnu/packages/

- identify if the module(s) missing use-module (gnu packages golang-web), add if so

- guix build go-package-a

- build all dependent to go-package-a

- make a commit ...

...

repeat as many times as needed.

Batch of 40-50 is a golden median amount to review.

Thanks,

Oleg