I’d like to join as well, but today is crammed with too many things, including dinner plans. If you end up having the call at 7PM EST and I can get our dinner planed moved up, I will try to join before the call ends (but I’m a firm “maybe” at best).
FYI – from further discussions at the end of camp, I was told that, for the Platform objective, we should make two copies of the plan for the upcoming year: (1) a with-the-resource-we-have-now plan and a (2) assuming-we-get-the-resources-we-need plan. It might be worth considering the same here – i.e., if we think that we could do more with specific dedicated resources, then lay out a strategy for the year without those resources followed by a strategy for the year if we could get specific resources (and what those additional needed resources would be).
Other than that, one concern I’d have for our Distribution strategy would be how we would be to consider how we would handle dozens of distributions – i.e., where do people go with questions if they’re running a different distribution than others in the community, where do expectations/responsibilities of the distributor vs. community start & end, how does the community address upgrades (if at all), etc.
As for item #3 (“a best practice library”), I would favor an approach that was community sustainable. If we dream up an approach to sharing best practices that requires continued central maintenance, it would be more likely to fail. For example, making it clear & easy to “vote up” or centrally share links to real-world examples of best practices and anticipating some way of having those decay or even drop off over time if not updated would be better IMHO than creating some central repository we expect someone in the community to keep clean & updated.