Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes
Thanks Gergő. I think that what I am seeking occupies a middle ground between Tech News and and the quarterly check-ins. Quarterly check-ins can have lengthy slide decks which are wonderfully detailed but require considerable time to read. Tech news is less comprehensive than the type of resource that I am seeking. The Discovery / Search Platform newsletters are great but they are also more detailed than I need on a per-team basis. I'll use some vocabulary from baseball in trying to describe the info that I would like to see from each Audiences and Technology team each week: LAST PLAY: activities that were completed last week, such as "We completed planning of deployment for desktop beta of Wikistats 2.1. Hiring of new dev and DBA was finalized; their first day of work is two weeks out. Fixed a regression that caused an unplanned failover (Phabricator task link here); service is back to normal." AT BAT: highlights of current activities that are happening prior to the release of the next weekly update, such as "This week we are deploying the desktop beta of Wikistats 2.1 (Phabricator task link here) and we are working with Research to improve API documentation. Work on the incident report for last week's unplanned failover (link to document here) is continuing." ON DECK: activities that are planned for the next 1 to 2 weeks after the completion of the "at bat" activities, such as "Survey of needs for API users is in final design and awaiting sign-offs (Phabricator task link here); staff onboarding for new dev and DBA; IRC office hour to discuss the beta desktop Wikistats 2.1". IN THE HOLE: highlights of activities that are 2 to 6 weeks away. Such as "Budget planning associated with Annual Planning; early design of the mobile interface for Wikistats 2.1 (Phabricator task link here); planning of documentation (Phabricator task link here) and test methodology (Phabricator task link here) for mobile Wikistats 2.1; staff cross-training". My guess is that there are routine internal meetings where this information is discussed. I would like for information at approximately this level of detail to be published, with allowance for redactions of security and privacy sensitive information. Is there interest from others in publishing or reading information like this? My guess is that other people might also benefit from reports like these, including people at WMF who might want to know what other teams are doing, but if no one else is interested then I'll try to go along with the status quo. Pine ( https://meta.wikimedia.org/wiki/User:Pine ) On Fri, Jan 11, 2019 at 8:04 PM Gergő Tisza wrote: > On Fri, Jan 11, 2019 at 11:29 AM Pine W wrote: > > > [...] Are there any upcoming plans for systematic > > study or development of WMF-to-public communications processes from > > Audiences and Technology? > > > > Not quite the same thing, but touches on communication: > > https://meta.wikimedia.org/wiki/Research:Growth_and_diversity_of_Technology_team_audiences > > There are a couple existing ways to learn about new developments, though. > There is Tech News (focused on immediate user-facing changes), quarterly > department checkins (focused on the big picture and progress of annual plan > goals and other large projects), most teams have a monthly or sometimes > weekly newsletter and/or on-wiki updates page, there are some regular > showcases (research and more recently language), and people write blog > posts about larger or more interesting developments on Phabricator and the > WMF blog. (The discoverability of all of these things could certainly be > improved.) And if you are sufficiently interested in a specific team, team > Phabricator boards are public. > > On Fri, Jan 11, 2019 at 11:29 AM Pine W wrote: > > > On Fri, Jan 11, 2019, 9:31 AM Dan Garry (Deskana) > > wrote: > > > > > On Wed, 9 Jan 2019 at 20:25, Pine W wrote: > > > > > > > I would like to request that every Audiences and Technology team > submit > > > > highlights of recent and upcoming activities for inclusion in every > set > > > of > > > > SoS notes, even if no one personally attends the SoS meeting from a > > > > particular team, so that readers of these notes can keep better track > > of > > > > what is happening in the Audiences and Technology departments and so > > that > > > > readers can make adjustments to our own plans as needed. > > > > > > > > > Scrum of scrums meetings are intended to be a venue for development > teams > > > to surface upcoming blockers and dependencies on other teams, so that > > teams > > > can better work together and not block each other. Scrum of scrums > > meetings > > > are not intended to be a forum for general announcements about > activities > > > by end-users. These are very different use cases with different target > > > audiences. > > > > > > I understand your concerns about visibility of the actions inside the > > > Wikimedia Foundation. It's certainly difficult to see things from the > > > outside. Th
Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes
On Fri, Jan 11, 2019 at 11:29 AM Pine W wrote: > [...] Are there any upcoming plans for systematic > study or development of WMF-to-public communications processes from > Audiences and Technology? > Not quite the same thing, but touches on communication: https://meta.wikimedia.org/wiki/Research:Growth_and_diversity_of_Technology_team_audiences There are a couple existing ways to learn about new developments, though. There is Tech News (focused on immediate user-facing changes), quarterly department checkins (focused on the big picture and progress of annual plan goals and other large projects), most teams have a monthly or sometimes weekly newsletter and/or on-wiki updates page, there are some regular showcases (research and more recently language), and people write blog posts about larger or more interesting developments on Phabricator and the WMF blog. (The discoverability of all of these things could certainly be improved.) And if you are sufficiently interested in a specific team, team Phabricator boards are public. On Fri, Jan 11, 2019 at 11:29 AM Pine W wrote: > On Fri, Jan 11, 2019, 9:31 AM Dan Garry (Deskana) > wrote: > > > On Wed, 9 Jan 2019 at 20:25, Pine W wrote: > > > > > I would like to request that every Audiences and Technology team submit > > > highlights of recent and upcoming activities for inclusion in every set > > of > > > SoS notes, even if no one personally attends the SoS meeting from a > > > particular team, so that readers of these notes can keep better track > of > > > what is happening in the Audiences and Technology departments and so > that > > > readers can make adjustments to our own plans as needed. > > > > > > Scrum of scrums meetings are intended to be a venue for development teams > > to surface upcoming blockers and dependencies on other teams, so that > teams > > can better work together and not block each other. Scrum of scrums > meetings > > are not intended to be a forum for general announcements about activities > > by end-users. These are very different use cases with different target > > audiences. > > > > I understand your concerns about visibility of the actions inside the > > Wikimedia Foundation. It's certainly difficult to see things from the > > outside. That said, taking a meeting with a well-defined purpose and > > objective, and expanding that objective to add an additional, quite > > different use case, is not good practice; doing so may cause people to > > disengage or lose focus, thereby meaning the original objective of the > > meeting is no longer met. > > > > Some reading you might find useful: > > > >- https://www.agilealliance.org/glossary/scrum-of-scrums/ > >- https://www.scruminc.com/scrum-of-scrums/ > > > > Dan > > > > Hi Dan, > > That is helpful. Perhaps the info I am seeking would be better communicated > in a different way. I am reluctant to request a new communications process > that would require nontrivial effort to start and to maintain if I am the > only one who is interested. Are there any upcoming plans for systematic > study or development of WMF-to-public communications processes from > Audiences and Technology? If so, perhaps I could have a conversation with > whomever will work on that communications effort. > > Pine > ( https://meta.wikimedia.org/wiki/User:Pine ) > > > > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes
On Fri, Jan 11, 2019, 9:31 AM Dan Garry (Deskana) wrote: > On Wed, 9 Jan 2019 at 20:25, Pine W wrote: > > > I would like to request that every Audiences and Technology team submit > > highlights of recent and upcoming activities for inclusion in every set > of > > SoS notes, even if no one personally attends the SoS meeting from a > > particular team, so that readers of these notes can keep better track of > > what is happening in the Audiences and Technology departments and so that > > readers can make adjustments to our own plans as needed. > > > Scrum of scrums meetings are intended to be a venue for development teams > to surface upcoming blockers and dependencies on other teams, so that teams > can better work together and not block each other. Scrum of scrums meetings > are not intended to be a forum for general announcements about activities > by end-users. These are very different use cases with different target > audiences. > > I understand your concerns about visibility of the actions inside the > Wikimedia Foundation. It's certainly difficult to see things from the > outside. That said, taking a meeting with a well-defined purpose and > objective, and expanding that objective to add an additional, quite > different use case, is not good practice; doing so may cause people to > disengage or lose focus, thereby meaning the original objective of the > meeting is no longer met. > > Some reading you might find useful: > >- https://www.agilealliance.org/glossary/scrum-of-scrums/ >- https://www.scruminc.com/scrum-of-scrums/ > > Dan Hi Dan, That is helpful. Perhaps the info I am seeking would be better communicated in a different way. I am reluctant to request a new communications process that would require nontrivial effort to start and to maintain if I am the only one who is interested. Are there any upcoming plans for systematic study or development of WMF-to-public communications processes from Audiences and Technology? If so, perhaps I could have a conversation with whomever will work on that communications effort. Pine ( https://meta.wikimedia.org/wiki/User:Pine ) > ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes
On Wed, 9 Jan 2019 at 20:25, Pine W wrote: > I would like to request that every Audiences and Technology team submit > highlights of recent and upcoming activities for inclusion in every set of > SoS notes, even if no one personally attends the SoS meeting from a > particular team, so that readers of these notes can keep better track of > what is happening in the Audiences and Technology departments and so that > readers can make adjustments to our own plans as needed. Scrum of scrums meetings are intended to be a venue for development teams to surface upcoming blockers and dependencies on other teams, so that teams can better work together and not block each other. Scrum of scrums meetings are not intended to be a forum for general announcements about activities by end-users. These are very different use cases with different target audiences. I understand your concerns about visibility of the actions inside the Wikimedia Foundation. It's certainly difficult to see things from the outside. That said, taking a meeting with a well-defined purpose and objective, and expanding that objective to add an additional, quite different use case, is not good practice; doing so may cause people to disengage or lose focus, thereby meaning the original objective of the meeting is no longer met. Some reading you might find useful: - https://www.agilealliance.org/glossary/scrum-of-scrums/ - https://www.scruminc.com/scrum-of-scrums/ Dan ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes
Hi, On Thu, 2019-01-10 at 12:09 -0800, Pine W wrote: > When I read the SoS notes and I see nothing from some teams, this leaves me > to guess what their current states are. IMHO when there is nothing relevant to share, what do you expect to see? An explicit "nothing to share"? When an SOS notes edition lists nothing for a team, the current state of that team is likely described in the last edition in which that team's entry was not empty. :) andre -- Andre Klapper | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes
Hi Andre, When I read the SoS notes and I see nothing from some teams, this leaves me to guess what their current states are. I do not know whether teams are working on backlogs of bugs, developing a new feature, at a team retreat, conducting a post-deployment evaluation, designing an interface change, evaluating survey results, writing grant requests, hiring new staff, upgrading hardware, installing new cables, etc. I don't need to know, and I don't want to know, every detail of what teams are doing, but there is a happy medium between reporting nothing and reporting too much. Does that help to explain what I would like to see in SoS notes? If there is an alternative way to learn the same information, I would be glad to hear suggestions. Pine ( https://meta.wikimedia.org/wiki/User:Pine ) On Thu, Jan 10, 2019, 4:25 AM Andre Klapper wrote: > On Wed, 2019-01-09 at 12:25 -0800, Pine W wrote: > > I would like to request that every Audiences and Technology team > > submit > > highlights of recent and upcoming activities for inclusion in every > > set of > > SoS notes, even if no one personally attends the SoS meeting from a > > particular team > > What is your assumption based that this is not already the case > (if/when a team or project has something to share)? > > andre > -- > Andre Klapper | Bugwrangler / Developer Advocate > https://blogs.gnome.org/aklapper/ > > > > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes
On Wed, 2019-01-09 at 12:25 -0800, Pine W wrote: > I would like to request that every Audiences and Technology team > submit > highlights of recent and upcoming activities for inclusion in every > set of > SoS notes, even if no one personally attends the SoS meeting from a > particular team What is your assumption based that this is not already the case (if/when a team or project has something to share)? andre -- Andre Klapper | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes
Hi, I think that I previously made this request and it went unanswered, so I am escalating this request to Toby who I believe reads at least some of these SoS notes. If someone else is better suited to answer authoritatively than Toby, or if someone else would like to share their thoughts regarding this request, please feel free to comment. Also, please feel free to fork this request to a new thread if you think that a new thread would be a better place for this discussion. I would like to request that every Audiences and Technology team submit highlights of recent and upcoming activities for inclusion in every set of SoS notes, even if no one personally attends the SoS meeting from a particular team, so that readers of these notes can keep better track of what is happening in the Audiences and Technology departments and so that readers can make adjustments to our own plans as needed. I would guess that, in addition to myself, other people who are not WMF staff might also benefit from this, along with WMF staff who miss SoS meetings. Thanks, Pine ( https://meta.wikimedia.org/wiki/User:Pine ) On Wed, Jan 9, 2019, 11:43 AM Grace Gellerman wrote: > https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-01-09 > > =2019-01-09= > == Callouts == > * Fundraising campaigns > https://meta.wikimedia.org/wiki/CentralNotice/Calendar > * Language blocked by RelEng: > https://gerrit.wikimedia.org/r/#/c/integration/config/+/482766/ > * Security: if there are notes from the Proton security review, they would > be useful for the handover from Reading Web to Reading Infrastructure. See > also https://phabricator.wikimedia.org/T177765#4822198 > * Growth: Who do I (mdholloway) talk to about/add for review on changes to > Extension:GettingStarted? > * Readers Web and Performance, in case you notice performance hits on the > mobile site: #Research ran reader trust survey from 01/07 till 01/09: > https://phabricator.wikimedia.org/T209882 > * Core Platform (from Analytics) > https://phabricator.wikimedia.org/T202781#4865947 (same for MediaWiki > history reconstruction). > * Release Engineering: January 28 - wmf.15 - No Train (due to All Hands > week) > > == Audiences == > > > === Contributors === > Community Tech > * Blocked by: > * Blocking: > * Updates: > ** > > Anti-Harassment Tools > * Blocked by: > * Blocking: > * Updates: > ** > > Editing > * Blocked by: > * Blocking: > ** Updates: > ** > > Growth > * Blocked by: > * Blocking: > * Updates: > **Deploying Help Panel this week > https://www.mediawiki.org/wiki/Growth/Focus_on_help_desk > > Language > * Blocked by: CI/RelEng: > https://gerrit.wikimedia.org/r/#/c/integration/config/+/482766/ > * Blocking: > * Updates: > ** Google Translate available for ContentTranslation now! > > https://wikimediafoundation.org/2019/01/09/you-can-now-use-google-translate-to-translate-articles-on-wikipedia/ > > === Readers === > iOS native app > * Blocked by: > * Blocking: > * Updates: > **completed user testing of the Editing prototype - > https://phabricator.wikimedia.org/T211152 > ** will be conducting user testing of the Editing prototype among internal > users this week > **still working on/refining editing tools and syntax highlighting - > https://phabricator.wikimedia.org/tag/ios-app-v6.2-beluga-on-a-pogo-stick/ > > Android native app > * Blocked by: > * Blocking: > * Updates: > ** > > Readers Web > * Blocked by: > * Blocking: > * Updates: > > ** Summary: starting Advanced Mobile Contributions work and Webpackifying > the remaining MobileFrontend modules. Say hello to our new test engineer, > Edward Tadros! > > ** Responsive website (MinervaNeue / MobileFrontend): > > *** Invest in the MobileFrontend & MinervaNeue frontend architecture > > https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture > Webpackify mobile.languages.structured and mobile.mediaViewer > asynchronous ResourceLoader modules T210210 T210209 > Drawers and Overlays should not auto-append themselves T209129 T211691 > Replace inheritance with composition T205592 > > *** Advanced mobile contributions > https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions > Build AMC opt-in toggle T211197 T212516 > Team planning > > *** Page issues > https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues > Deploy to enwiki and all remaining projects on January 14th T210554 > > *** Miscellaneous bug fixes and maintenance T212518 T211724 T212970 > > ** Desktop website (Vector, Popups) > > *** Popups https://www.mediawiki.org/wiki/Page_Previews > Generate all possible combinations of page previews with Storybook > T205989 https://zen-pasteur-e92b1e.netlify.com/ > WMDE reference previews are in progress > https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/ReferencePreviews > > ** PDF rendering (Proton) > https://www.mediawiki
[Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes
https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-01-09 =2019-01-09= == Callouts == * Fundraising campaigns https://meta.wikimedia.org/wiki/CentralNotice/Calendar * Language blocked by RelEng: https://gerrit.wikimedia.org/r/#/c/integration/config/+/482766/ * Security: if there are notes from the Proton security review, they would be useful for the handover from Reading Web to Reading Infrastructure. See also https://phabricator.wikimedia.org/T177765#4822198 * Growth: Who do I (mdholloway) talk to about/add for review on changes to Extension:GettingStarted? * Readers Web and Performance, in case you notice performance hits on the mobile site: #Research ran reader trust survey from 01/07 till 01/09: https://phabricator.wikimedia.org/T209882 * Core Platform (from Analytics) https://phabricator.wikimedia.org/T202781#4865947 (same for MediaWiki history reconstruction). * Release Engineering: January 28 - wmf.15 - No Train (due to All Hands week) == Audiences == === Contributors === Community Tech * Blocked by: * Blocking: * Updates: ** Anti-Harassment Tools * Blocked by: * Blocking: * Updates: ** Editing * Blocked by: * Blocking: ** Updates: ** Growth * Blocked by: * Blocking: * Updates: **Deploying Help Panel this week https://www.mediawiki.org/wiki/Growth/Focus_on_help_desk Language * Blocked by: CI/RelEng: https://gerrit.wikimedia.org/r/#/c/integration/config/+/482766/ * Blocking: * Updates: ** Google Translate available for ContentTranslation now! https://wikimediafoundation.org/2019/01/09/you-can-now-use-google-translate-to-translate-articles-on-wikipedia/ === Readers === iOS native app * Blocked by: * Blocking: * Updates: **completed user testing of the Editing prototype - https://phabricator.wikimedia.org/T211152 ** will be conducting user testing of the Editing prototype among internal users this week **still working on/refining editing tools and syntax highlighting - https://phabricator.wikimedia.org/tag/ios-app-v6.2-beluga-on-a-pogo-stick/ Android native app * Blocked by: * Blocking: * Updates: ** Readers Web * Blocked by: * Blocking: * Updates: ** Summary: starting Advanced Mobile Contributions work and Webpackifying the remaining MobileFrontend modules. Say hello to our new test engineer, Edward Tadros! ** Responsive website (MinervaNeue / MobileFrontend): *** Invest in the MobileFrontend & MinervaNeue frontend architecture https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture Webpackify mobile.languages.structured and mobile.mediaViewer asynchronous ResourceLoader modules T210210 T210209 Drawers and Overlays should not auto-append themselves T209129 T211691 Replace inheritance with composition T205592 *** Advanced mobile contributions https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions Build AMC opt-in toggle T211197 T212516 Team planning *** Page issues https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues Deploy to enwiki and all remaining projects on January 14th T210554 *** Miscellaneous bug fixes and maintenance T212518 T211724 T212970 ** Desktop website (Vector, Popups) *** Popups https://www.mediawiki.org/wiki/Page_Previews Generate all possible combinations of page previews with Storybook T205989 https://zen-pasteur-e92b1e.netlify.com/ WMDE reference previews are in progress https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/ReferencePreviews ** PDF rendering (Proton) https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality *** Remaining work tracked in deploy Proton T181084 *** Passing ownership to Readers Infrastructure pending security follow-up T210652 Readers Infrastructure * Blocked by: ** Security: if there are notes from the Proton security review, they would be useful for the handover. See also https://phabricator.wikimedia.org/T177765#4822198 ** Growth: Who do I (mdholloway) talk to about changes to Extension:GettingStarted? * Blocking: * Updates: ** Building new APIs to support the App Editor Tasks initiative ( https://phabricator.wikimedia.org/T212793 ) *** Counts of edits meeting specific criteria: https://phabricator.wikimedia.org/T212795 *** Suggested entities/articles for adding descriptions: https://phabricator.wikimedia.org/T206504 **Maps: *** Test Kartotherian/Tilerator with node 10 https://phabricator.wikimedia.org/T209990 *** Stretch Upgrade: Tile generation report published https://www.mediawiki.org/wiki/Wikimedia_Maps/Tile_generation_report Ready to move on with whole cluster upgrade and data replication Multimedia * Updates ** Parsing * Blocked by: none * Blocking: none * Updates: ** This patch needs VE folks to take a look and validate that they can work with this change https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/456520 -- Add support for server side mg
