Proposal: package layout

[inkel]

Heya. I've been looking at this with more detail, and I'd like to propose a new package layout that I think it will make things easier to maintain.

At the top level we have the current import path, github.com/mplzik/rnr/golang/pkg/rnr, which contains the Task interface and the Job struct.

Then we have github.com/mplzik/rnr/golang/pkg/rnr/tasks/web with the Server struct for what it currently resides in webserver.go.

Last but not least, we have for each type of class, the following:

• github.com/mplzik/rnr/golang/pkg/rnr/tasks/nested
• github.com/mplzik/rnr/golang/pkg/rnr/tasks/shell
• github.com/mplzik/rnr/golang/pkg/rnr/tasks/callback

Each of these packages rename the existing FooTask into a Task structure, making the code a little less verbose or more familiar across sub-packages, as in:

t1 := nested.New("foo", nested.Options{})

t2 := shell.New("bar", "kubectl", "get", "pods")`

t3 := callback.New("quux", someFunc)

By doing so we remove the need to use prefixes for each type, and it gives more isolation between definitions, code, and tests.

I believe this should be done first before my other proposal in #6.

What do you think?