<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
In my quality of Engagement section reporter, here is the summary of
the Warsaw days:<br>
<ul>
<li>for those interested in the whole conversation, the etherpad:
<a class="moz-txt-link-freetext"
href="https://etherpad.mozilla.org/QNUuZdC0pU">https://etherpad.mozilla.org/QNUuZdC0pU</a></li>
<li>for those who want to look at the presentation, see
attachment. <br>
</li>
</ul>
<p>End-User communication<br>
</p>
<ul>
<li>Facebook account: 12,000 fans to care about once a week. If
the update is not happening repeatedly, the fans will walk away.
=> AM to find a contributor who would be interested</li>
<li>Twitter account: => Usul volunteers to take ownership and
run the account. <br>
</li>
<li>Thunderbird blog: this is the voice of Mozilla. => AM to
work with Mozilla communication team. Communication would
prepare content and post.</li>
<li>Thunderbird Start page: Rotate the content once a week or each
other week. => Sancus to automate the process</li>
</ul>
Product release<br>
<ul>
<li>Thunderbird website: New features Page usually localized after
release => both text and screen shots could go under
Documentation section. Sancus working with web team to get the
new look and feel for Thunderbird pages.<br>
</li>
<li>Thunderbird What's new page: always localized BEFORE release:
a lot of options have been discussed to provide content, but the
solution has to be found. Bugzilla content could be leveraged as
long as each developer write a proper comment when closing a
bug. </li>
<li>Thunderbird Release notes (never localized): => content
could be done by to TB drivers. Bugzilla content could be
leveraged as long as each developer write a proper comment when
closing a bug. <br>
</li>
<li>Thunderbird Enterprise mailing list/ information flow to the
list: => one note per ESR release<br>
</li>
</ul>
Engagement<br>
<ul>
<li>How to keep contributors community live and running: <br>
</li>
<ul>
<li>Friend of the Tree: => AM to investigate how it could be
"outsourced" to Mozilla gear infrastructure</li>
<li>Adding "credit" page to Thunderbird: the list could be
validated by the drivers. => Mark to check how to update
this.<br>
</li>
<li>Kick starting the Open Badges program: "Rewarding the
Community": it doesn't appeal to seasoned developers, but this
kind of program can attract junior contributors who need to
build credentials on their resume/blog. there was almost a
consensus that this kind of program can be a good incentive
for newbies. The program can be prepared before TB17 but it
requires one or more leader(s) NOW as this kind of program is
a long term commitment.</li>
<li>How to fund swags or occasional meetings: what about using
the revenue generated by biz partners? <br>
</li>
</ul>
</ul>
Accessing Mozilla monitoring tools<br>
<ul>
<li>Allow Community to access Metrics: Paid staff has access to
more data than non-paid staff today: i.e locales, countries, ESR
ADU... => AM to get go ahead from Metrics team</li>
<li>Provide a Survey Gizmo license to Community in order for her
to run end-users survey => AM to come back on this. Mozilla
is currently renegotiating the contract with Survey G</li>
<ul>
<li>AM offers to run the same survey than the one she ran in
2011. Decision to be made asap.<br>
</li>
</ul>
<li>Test Pilot: Standard8 confirms that testing Test Pilot was a
little bit hectic. => Standard8 to document the process if we
want to leverage the tool.<br>
</li>
<li>=> Triggering either a survey with Survey Gizmo or Test
Pilot requires a decision process. <br>
</li>
</ul>
Conclusion<br>
<ul>
<li>Should Communication/Engagement become a Module with a Module
Owner? Who would be the module owner? The decision is not to be
made right now, but probably at the time of TB17</li>
<li>Engagement is critical to maintain TB awareness and the
solution is not clear yet.<br>
</li>
</ul>
<p>Voila,<br>
</p>
<p>AM<br>
</p>
<pre class="moz-signature" cols="72">--
Anne Marie Bourcier
Mozilla Thunderbird</pre>
</body>
</html>