Namespace bikeshedding

[exodist]

At this point it is very likely that Test::Stream is going to be split into 2 or more dists. At the moment I have a branch that works on splitting the core-essentials aka "the guts" out. At the moment the working name for that dist is Test-Sync. See issues #74 and #79.

What namespace should the guts be? Currently I am going with Test-Sync just to get the work done, but the name is not locked in yet. Test::Core, Test::Base and Test::Builder are all taken.

[kentfredric]

Test::Wheel appeals to me for a whole bunch of reasons right now.
Test::Wheel::Hub

[exodist]

I am reminded of Aristotle's suggestion of Test2 as a namespace.

[rjbs]

I think Test2 is a good choice. We don't need this sorted right now. We can settle the name question after the design is finalized.

@exodist - let's work under Test2 and if we think something is better later we can fix it. I think Test2 would be just fine to settle on, though.

[dolmen]

The subject of this discussion is the name of the Test::Stream::Sync module on the split_dist branch, isn't it?

[kentfredric]

@dolmen this is about the split_head branch, pretty much all the "internals only" parts get name shifted at present. https://github.com/Test-More/Test-Stream/tree/split_head/lib/Test

split_dist the "user facing" parts of the Test::Stream

[exodist]

that branch was a demo branch, i will be creating an offical branch for the Test2 split.