Chip/David, Sounds good to me. I've seen emails in the past that go to both lists (-dev and -users). In this case would it be a good idea to draft an email per topic and send out 1 email that copies both lists?
I'll get started on the conversions and then on the discussions after that. Thanks, On Mar 20, 2013, at 12:30 PM, David Nalley wrote: > On Wed, Mar 20, 2013 at 12:06 PM, Chip Childers > <chip.child...@sungard.com> wrote: >> Scratch that - Sorry Jessica / Radhika. >> >> David's looking for technical reviewers. >> >> David -- I think that the challenge here is that the actual material >> for each of those docs is very broad. Perhaps the right way to >> approach this is to attempt the fix, submit it, and initiate a content >> discussion (per topic) on the dev list. We can also consider asking >> for content reviews from cloustack-users@i.a.o, given that best >> practices, choosing a HV, etc... are all things the the user >> community may be qualified to help with. > > > That strategy worked very well for me recently - providing a chunk of > documentation for folks to review on -users found tons of problems > that I personally missed. > > --David >
