Last modified: 2013-06-27 21:33:50 UTC
During the month that follows the first release of Echo in April, we would like to add two links to help prominently socialize this tool with the community. The links would appear in these two touchpoints: • on the archive page (at the top, next to the title 'My notifications') • in the email notifications (at the bottom, above the legal footer) The links would be roughly the same in both touchpoints: 'Learn more · Leave feedback' The 'Learn more' link would take users to this project overview on en-wiki: https://en.wikipedia.org/wiki/Wikipedia:Editor_engagement/Echo The 'Leave feedback' link will display a small popup window with a quick survey asking people if they find this tool useful, as described here: http://www.mediawiki.org/wiki/Echo/Metrics#Usefulness_Survey The links to the survey will be added once it is ready.
Here is a link to the proposed survey (which you are welcome to test): https://www.surveymonkey.com/s/notifications1 And here is a link to the updated requirements for that survey: http://www.mediawiki.org/wiki/Echo/Metrics#Survey We will prominently invite our users to take that survey for a one-month period after launch, ideally both on the web (e.g. archive page) and by email (e.g message footers). Vibha will prepare some design recommendations on how to best invite users to either go to the project page to learn more (and post on the talk page) -- and/or to participate in that survey at launch, in order to achieve the effect proposed above.
Related URL: https://gerrit.wikimedia.org/r/58444 (Gerrit Change Ifb9a287e2dc11067efac48bdbf700fe7997d19f0)
https://gerrit.wikimedia.org/r/58444 (Gerrit Change Ifb9a287e2dc11067efac48bdbf700fe7997d19f0) | change APPROVED and MERGED [by jenkins-bot]
Here's our updated requirement for this feature, based on today's conversation with Vibha and Kaldari. The archive page would have two icons on the same line as the 'Notifications': * a 'question mark' (?) icon next to the title (linking to the notifications portal) * a 'cog' icon on the far right (linking to notification preferences) For a period of one month following launch, we would also display a small 'Feedback' text link next to the preferences icon, linking to the user survey. That text link would be removed when the survey ends. This archive page header would look roughly like this: Notifications (?) Feedback | (cog icon) Here are the links for this header: * question mark on en-wiki: https://en.wikipedia.org/wiki/Wikipedia:Notifications * question mark on mediawiki.org and other sites: http://www.mediawiki.org/wiki/Echo * feedback link on all sites: https://www.surveymonkey.com/s/notifications1 * cog icon link on en-wiki: https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-echo Linked pages would open in a separate tab or window, so the user doesn't lose their place. We may also consider including the question mark icon on the flyout as well, if that makes sense. This would help users learn more about this project -- and take a survey or contribute to our talk page discussions. See updated feature requirements for the 'all notifications' archive page: http://www.mediawiki.org/wiki/Echo_(Notifications)/Feature_requirements#All_notifications
Partially implemented in change Icc9f2c66. This adds help and feedback links to the archive page.
Since the web components are finished, I'm going to assign the remainder of this bug to Luke since he's working on the email components currently. (Otherwise, we would likely cause conflicts.) Probably the best way to do this would be to have a config var like... $wgEchoEmailFooterLinks = array( 'echo-feedback' => 'https://www.surveymonkey.com/s/notifications1', 'echo-learn-more' => 'https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Extension:Echo' ); And these get fed into a horizontal list in the email footer.
As discussed with Kaldari, we just updated the feature requirements for these archive links in the header section. The two links we changed apply to the question mark icon next to the 'Notifications' title: * question mark on en-wiki: https://en.wikipedia.org/wiki/Wikipedia:Notifications/FAQ * question mark on mediawiki.org and other sites: http://www.mediawiki.org/wiki/Help:Extension:Echo The full requirements for the archive page are here: http://www.mediawiki.org/wiki/Echo_(Notifications)/Feature_requirements#All_notifications (see 'Header' section for the above changes)
As discussed during today's site walkthrough, let's also add a small question mark icon on the notifications flyout, next to the Notifications title. This would be implemented in the same way as for the question mark that is now in the archive page, except that the icon would be smaller, so it's a bit more discrete. That small flyout icon will link to the same pages as the archive icon: * question mark on en-wiki: https://en.wikipedia.org/wiki/Wikipedia:Notifications/FAQ * question mark on mediawiki.org and other sites: http://www.mediawiki.org/wiki/Help:Extension:Echo This is intended to be a temporary feature, in order to help drive more users to the FAQ page, where they will be invited to give feedback, so we can improve Notifications based on user recommendations.
(In reply to comment #8) > As discussed during today's site walkthrough, let's also add a small question > mark icon on the notifications flyout, next to the Notifications title. This sounds like a separate bug. :-) Please file one if there isn't one already.
(In reply to comment #1) > Here is a link to the proposed survey (which you are welcome to test): > > https://www.surveymonkey.com/s/notifications1 English only, seriously? I see a vague mention of "other projects" but all this seems to be en.wiki-only, is the deploy planned only for en.wiki?
The first deploy? Yes. It seems silly to deploy elsewhere until we've had a chance to identify if high-level usage causes problems.
(In reply to comment #11) > The first deploy? Yes. It seems silly to deploy elsewhere until we've had a > chance to identify if high-level usage causes problems. So you're working on ways to collect non-English feedback from further deploys? This bug is not clear at all.
Further deployments will probably work in much the same way as with AFT5 releases - with conversations with the local community, a vector for feedback, so on and so forth, yes. The bug does not explain what happens with further deploys, no: its scope is quite clearly set by the opening of "During the month that follows /the first release of Echo/" (emphasis mine).
If my parser for comment 13 works correctly, this new bug summary may be true.
We are planning to take down this link after July 4th
