Re: Email to Doc Sprint registrants

Really nice draft, Julee.

The second sentence wanders in focus, subject, and tense -- "we would
like to ... give us feedback...".

The big thing I would want to see added is the opportunity to step up
and design and provide infrastructure and lay out the track in front
of us.  Don't limit them to what we can serve up ready to work on.  We
still have all that stuff we can't get ready in time for them, and we
know they're up to it.  I'm hereby repeating my votes for strategic
engagement in topics of the month (review cycle) and periodic site
design upgrade sprints, along with near-term (at least) recruiting for
big-picture assistance.

Also, given the juxtaposition with the h5devconf, this wouldn't be a
bad time to invite people interested in the test side of the project
to show up and work with us to make it whole.  Maybe too late to boost
Shepazu's application for GSoC, but we can't be the lid on what
volunteers can provide.


On Wed, Mar 27, 2013 at 7:50 PM, Julee <> wrote:
> Hi, everyone:
> Let's circle back around to Doc Sprint registrants, let them know what's up,
> and ask them to re-join the fold. I've drafted an email that I'd like to
> send out tomorrow.
> Please let me know of any changes you'd make to the following email blast:
> --------------------------------------------------------------------------------------------------------------------------------------------
> Hello from!
> We are emailing you because you registered for a Doc Sprint.
> We thought you'd like to know some of our activities. Also, we would like to
> circle back around to, help a bit, and give us feedback
> about your experience this time. If you don't want to receive emails, please
> email and I'll remove you from this list.
> We have been working to improve the experience for folks like you, who want
> to contribute content and code or otherwise participate. We have a long way
> to go, but we've accomplished a few key things:
> Based on surveys and 1-1 feedback, we've updated the Getting Started
> experience ( and the
> Editorial Guide ( Give
> them a whirl and let us know (on the IRC or the public list) what you think.
> At, we've installed a playground! You can sketch
> a code idea, test a sample, and then share your code. Right now, you share
> it by adding the key snippet to the article page and also linking to the
> example on (for example, see
> In the next
> round, your examples can be embedded directly in the article.
> We have just installed a new projects space,
> Besides filing issues and enhancements there, you can:
> * have your own dashboard showing what's on your plate
> * assign yourself tasks for the next time you stop by
> * get a bird's eye view of any project area
> Again, we're in Alpha here, so a lot of patience and feedback is much
> appreciated.
> We would like to move quickly to declare Beta. But that depends on the help
> we get. So if you're available to edit CSS properties pages, contribute
> examples, help with the MediaWiki LAMP infrastructure, or just want to hit
> some of the low-hanging fruit on the Getting Started page, please do! And
> let us know.
> Looking forward to documenting the web with you all!
> The busy folks at
> (And again, if you don't want to receive emails, please email
> and I'll remove you from this list.)
> --------------------------------------------------------------------------------------------------------------------------------------------
> Thanks! J
> ----------------------------
> @adobejulee

Received on Thursday, 28 March 2013 03:46:42 UTC