Hi Quim, Would it be possible to set up a 60-minute Hangouts or Zoom meeting to discuss this set of issues (UX change communications, possibly aided by the newsletter extension and/or a wiki page with some kind of UX checkpoint)? If so, perhaps you and I could have an off-list discussion to find a time that works for both of us, and after that we can send a public meeting announcement to invite other people who also might like to participate. I'd suggest that we have this meeting after January 2nd.
Thanks, Pine On Mon, Dec 19, 2016 at 2:13 AM, Quim Gil <[email protected]> wrote: > On Sat, Dec 17, 2016 at 4:38 AM, Pine W <[email protected]> wrote: > > > The Newsletter extension could be useful in all kind of ways, and I > > was glad to see that it's apparently still in active development. > > > > Oh yes, check https://phabricator.wikimedia.org/project/profile/888/ > > It would be helpful for me to have proposals shown in the newsletter > > divided by approximate time horizon (next week, next month, next > > quarter, etc), as well as their status (proposed but not in > > development, in development, stalled, ready for review by (insert team > > here), deploying soon, under discussion, deployment complete on X > > wikis and deploying to Y soon, etc.) > > > > If that UX Review checkpoint would be created (something that needs to be > decided by the Product teams who would maintain it)... > > ... that information would be available in the UX review checkpoint (a > regular wiki page, updated as reviews come and go). > > The UX Review newsletters would consist on something a lot lighter: > > * A title, i.e. "New WikiEtc design concept looking for reviews" > * A URL where the news would be explained and discussed. > > These newsletters would arrive to users via Echo and/or email notifications > -- their choice via their Preferences. > > In other words, there is no need to "write a newsletter". The Newsletter > extension just collects and advertises existing pages. > > > What would it take to get a newsletter like that launched, when might > > it happen, and who should coordinate and publish it? > > > > As a promoter of the Newsletter extension, I feel co-responsible (with Tony > Thomas, lead developer and a lot more) for deploying it in Wikimedia > (getting there, it has been available in the Beta cluster for a while now). > If you are interested about this event, please subscribe to > https://phabricator.wikimedia.org/T110170 > > Once the extension is deployed, if the idea of checkpoints has been found > interesting indeed, we could start with a pilot. Note that setting up the > checkpoint and the newsletter is relatively easy. The complex part is to > define a reliable process followed by everyone. This is why I would put the > words "experimental" and "pilot" upfront. > > -- > Quim Gil > Engineering Community Manager @ Wikimedia Foundation > http://www.mediawiki.org/wiki/User:Qgil > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
