Combine strategy chapters into single chapter

[semioticrobotic]

This pull request suggests combining two chapters into a single chapter in order to create a more robust resource for addressing the nature of open source strategy.

In particular, it combines @dneary's separate chapters on project goal-setting and open source product strategy into a single chapter called (for now) "Building a Strategy." That chapter would then consist of two principal halves: a first half on project strategy and a second on product strategy. The introduction would distinguish projects from products to set the stage for what follows.

I intend to work on this as able, but wanted to at least create the branch and open the PR in the hope that @dneary might still be lurking somewhere and wish to collaborate.

[dneary]

I intend to work on this as able, but wanted to at least create the branch and open the PR in the hope that @dneary might still be lurking somewhere and wish to collaborate.

Ears burning You called? Happy to review and comment, the idea sounds great!

[semioticrobotic]

Pushed a few additional updates today, @dneary, and while I'm only about halfway finished with the re-write I think there's enough here for you to at least skim and see where I'm headed. Leave any early feedback you like. I'm away for a bit and will need to set this aside but am enjoying it and will return to it soon. Marginalia in code comments gives you a sense of where I'm going!

[semioticrobotic]

A little more work today, @dneary—a more difficult section on goal-setting. Like everything else, it's not quite there yet but would certainly benefit from your review.

[semioticrobotic]

Something like a full draft now, @dneary. It need polish and perhaps a little more coherence but I think the bones are there. Please see what you think!

[semioticrobotic]

@dneary: Finally had some time to return to this and clean it up. I believe it's ready for review. I'd love your notes, of course, and am also interested in whether you think an outside reader might take a look at it for us (maybe @geekygirldawn)? It needn't be perfect (The Open Source Way is always iterating), but I prefer at least avoiding any obvious blunders. 😄