Daniel Nephin

Here's my proposal for dealing with `pkg/`: ## Summary `github.com/moby/moby/pkg` should be split up as following: 1. packages that only have a single consumer should be moved to a sub-package...

The general idea is that each of these new repos are functionally very different and are not called from the same components. Any `pkg`s with high coupling were merged into...

Ya `go-locker` is the smallest of them. I couldn't find any other packages for concurrency primitives. I guess over time we could add more, so renaming it to something more...

The goal of this effort is support breaking out components. Any `pkg` that is only used by a single component could be moved to an `internal`, or some other subpackage....

> Creating components is the process of finding the correct interfaces Yes the interface **for the component**, not the interface for every library used by a component. > If we...

Adding some more details based on a discussion during slack standup. This proposal is only a guideline to follow as we hit `pkg` that are needed by components. We should...

Perfect, that one was an outlier so moving it to containerd would be great. I've updated the proposal and the summary.

Does anyone have an example of the schema that puts `system-out` under `test-case` ? If I look at all the top hits on google (https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd, https://github.com/testmoapp/junitxml, https://stackoverflow.com/a/9410271/444646) they put `system-out`...

Thank you for your interest in contributing new gotestsum formats! Looking at the example output, the two changes from the existing `pkgname` format seem to be: 1. grouping of packages...

I think this is a cool idea! Instead of `↶` could we remove the trimming of the shared part of the package path? Every package would be printed with it's...