[10:04:24] andre__afk, when you return, https://phabricator.wikimedia.org/T119703#1951424 [10:05:18] In fact, I'm wondering whether we should simply post this to all tasks under https://phabricator.wikimedia.org/tag/community-wishlist-survey/ [11:14:35] That was also my thought so far [11:19:35] (because rachel covered eng & wikitech-l and I don't see any other on-wiki venues etc) [11:31:02] tinajohnson__, tonythomas Glaisher addshore meeting time! [11:31:11] violetto, you are here but probably sleeping... [11:31:16] Hi ! I'm here [11:31:41] (we should think of finding a different time for this meeting so violetto and others in the Americas can join) [11:32:00] sure [11:32:04] we can do that [11:33:43] Let's wait to see if someone else pings back [11:33:45] hi tinajohnson__ :) [11:34:14] qgil: yeah, let's wait [11:36:30] ... or maybe it is you and me today :) [11:37:29] hehe... seems like it [11:37:42] qgil: Let's start then ? [11:38:24] ok, it's been a while, sorry [11:38:48] https://phabricator.wikimedia.org/tag/mediawiki-extensions-newsletter/ [11:39:06] Where do you want to start? [11:39:28] Let's just go over what needs to be done ASAP ? [11:39:51] I'm sure most of the tasks are priortised right though [11:39:57] OK, I want to discuss why this extension is so important and how to get violetto finally involved in UX [11:40:17] Okay, great [11:40:43] So [11:41:08] We already know that this extension will make life easier for publishers and subscribers of newsletters [11:41:31] in a way that MassMessage is not solving and is not interested in solving -- we have complementary purposes [11:41:32] yes [11:41:33] Good [11:41:54] What is now a new use case that is very important [11:42:15] yes, the one with stages of development [11:42:25] Is the product development process that is being cooked at https://www.mediawiki.org/wiki/WMF_product_development_process [11:42:38] Long story short: [11:42:50] a key aspect of this process is that there will be stages of development\ [11:42:59] right [11:43:18] and people should be able to subscribe to a specific stage in order to get news every time a project is entering that stage [11:43:21] For instance [11:43:35] okay [11:43:51] Design is your thing. You are not going to discuss code implementations, and you are not really interested in participating in intense RfCs [11:44:05] However, if you get a notification whenever a new design review is available [11:44:17] You will go there, volunteer time, and provide feedback or improvements [11:44:25] yes true [11:44:57] or imagine that you just want to test early prototypes, or software considered ready to start the deployment phase [11:45:11] or new concepts just landing for the first time [11:45:18] anyway, you get the point [11:45:19] yeah [11:45:30] for each of these stages, users should find a way to subscribe easily [11:45:41] this will help us all be more informed [11:45:42] and then publishes should have an easy to way to announce updates [11:45:55] Well, the Newsletter extension is a perfect fit [11:46:07] very true [11:46:25] for users, easy to subscribe and decide whether they want email or web notifications [11:46:35] (even better with the uopcoming interwiki notifications?) [11:46:42] For the maintainers of these stages [11:46:42] yup [11:47:00] so, you say we have a newsletter for each stage ? [11:47:06] they only need to add the URL where a new concept, a new beta, etc is found, press send, done [11:47:41] yes, we can have as many specialized "newsletters"as needed [11:47:49] They are not newsletters in the classical sense [11:48:03] okay, makes sense [11:48:06] But they need the same tool and they serve the same purpose [11:48:53] The only requirement that I can imagine [11:48:57] in the case of normal newsletters, the maintainers are volunteers but what about this case ? [11:49:01] is some flexibility in the introduction of URLs [11:49:17] Now an allowed URL could be i.e. a Phabricator task [11:49:26] a page in mediawiki.org, an instance in Labs... [11:49:35] okay [11:50:00] Still, there would be a limited set of URLs within the Wikimedia domain that would be allowed [11:50:11] (no link to YouTube, less chances of spam, etc) [11:50:17] right [11:50:33] How does this sound? [11:50:47] That's some good thinking there, qgil [11:50:54] :) [11:51:01] I think it is great! [11:51:26] Cool, I hope this serves as motivation to this team of volunteers [11:51:44] Also, having a tool used regularly by developers, designers product managers... cannot harm. :) [11:51:44] yup [11:51:51] We might get more bugd and patches [11:52:25] right, will keep newsletter alive [11:52:27] OK, I will take this log and create a task with it [11:52:35] sure [11:52:48] This means no short changes, but a different, better future scenario [11:52:57] short term changes, I mean [11:52:57] ofcourse [11:53:05] Next: violetto [11:53:25] the maintainers of these specialized newsletters, are we going to ask people to volunteer ? [11:53:30] I actually failed to talk to her during my days in SF. My bad, these were crazy days [11:53:41] okay [11:53:46] Ah, these stages will need maintainers [11:53:52] nothing we need to care about here [11:54:07] okay cool [11:54:20] So violetto was willing to help with UX work (which we badly need) [11:54:36] But the last I heard is that she was having problems registering when our instance was broken [11:54:44] What is the situation of the instance today? [11:54:44] oh yeah [11:54:53] let me check [11:55:17] I remember that new instances were created [11:55:30] URLs changed? [11:56:03] no no [11:56:07] it's the same [11:56:12] http://newsletter-test.wmflabs.org/wiki/ [11:56:56] I logged in as admin and everything seems okay [11:57:26] qgil: I will contact violetto and take her through the extension if you want [11:57:27] And I just created a new account and it works. Good. [11:57:37] Yes, please, I would really appreciate that [11:57:52] I will do that ASAP [11:57:54] She is such a good designer! I hope she has not given up with us. :) [11:58:05] sure hope so! [11:58:05] Thank you [11:58:19] Also good that you are in touch directly [11:58:28] I don't wsant to become a bottleneck [11:58:32] she had contacted me earlier but then I had a lot of traveling and end of the year stuff to do [11:58:51] and I'm getting plenty of extra work these days, so there is a real risk of me becoming bottleneck, a thick one [11:59:06] Busy times. :) [11:59:17] Alright, something else? [11:59:18] don't worry, I'll make sure violetto is well taken care of [11:59:53] I still have some of those tasks left to resolve, should be getting to those ASAP [12:00:01] nothing else from me [12:00:19] OK, good. [12:00:24] I will create this task [12:00:33] and I will also ping csteipp about the security review [12:00:33] sure [12:00:40] oh yes [12:01:11] Great, see you around tinajohnson__ [12:01:38] qgil: sure, have a great weekend! [12:03:41] tinajohnson__, actuaslly, before pinging him, when do you think that https://phabricator.wikimedia.org/T110491 could be done? [12:03:46] It is blocking the security review task [12:04:28] qgil: is Saturday fine ? [12:04:38] totally :) [12:05:08] Thanks [12:11:31] andre__, hi, sorry for not seeing your reply before [12:11:40] andre__, is everything clear, or...? [12:17:13] qgil, It is. :) I was more like wondering yesterday if I missed an email or such. All fine, no worries :) [12:17:30] ok [12:17:31] (though not sure I really want to spam all 107 tasks) [12:17:38] but well :) [12:17:40] up to you [12:17:54] if you do it, you can blame me [12:19:12] haha [14:35:24] andre__, have you sent the mesage? [14:38:04] qgil: can I say "I'm on it"? The thing is that CommTech in quite some cases created a dedicated Wishlist task separate from an already existing task requesting basically the same thing, where the actual people are CCed :-/ [14:38:30] I'm on it is a good answer. :) [14:38:33] but I should at least start with those tasks tagged as Wishlist *now*, yeah, and do the rest later [14:38:44] We are late, but it is my fault in the first place. [14:38:46] Meh. Things always turn out to be more complicated. Sigh. [14:39:40] No big worries. People had a chance to request sponsorship and we got many candidates already. We are just stretching to do evenb better. :) [14:42:37] Garrrr, and mass-commenting of course does not support line breaks, hence no red "Important" banner... [14:42:48] Well. Let me tweak that a bit... [15:12:04] hi [15:12:29] hej hej [15:13:20] qgil: I also won't be available at that time nowadays so, yeah, agree that we need to change the time [17:17:38] Glaisher, noted.