Re: [Wikitech-l] [Wikimedia-l] Quarterly reviews of high priority WMF initiatives
Minutes and slides from three recent quarterly review meetings held last week are now available: Language Engineering team: https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews/Language_Engineering/January_2015 MediaWiki Core team https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews/MediaWiki_Core/January_2015 Talent Culture team (slides only:) https://commons.wikimedia.org/wiki/File:WMF_Quarterly_Review-_2014-15_Q2_-_Talent_%26_Culture,_Redacted.pdf On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller e...@wikimedia.org wrote: Hi folks, to increase accountability and create more opportunities for course corrections and resourcing adjustments as necessary, Sue's asked me and Howie Fung to set up a quarterly project evaluation process, starting with our highest priority initiatives. These are, according to Sue's narrowing focus recommendations which were approved by the Board [1]: - Visual Editor - Mobile (mobile contributions + Wikipedia Zero) - Editor Engagement (also known as the E2 and E3 teams) - Funds Dissemination Committe and expanded grant-making capacity I'm proposing the following initial schedule: January: - Editor Engagement Experiments February: - Visual Editor - Mobile (Contribs + Zero) March: - Editor Engagement Features (Echo, Flow projects) - Funds Dissemination Committee We’ll try doing this on the same day or adjacent to the monthly metrics meetings [2], since the team(s) will give a presentation on their recent progress, which will help set some context that would otherwise need to be covered in the quarterly review itself. This will also create open opportunities for feedback and questions. My goal is to do this in a manner where even though the quarterly review meetings themselves are internal, the outcomes are captured as meeting minutes and shared publicly, which is why I'm starting this discussion on a public list as well. I've created a wiki page here which we can use to discuss the concept further: https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_reviews The internal review will, at minimum, include: Sue Gardner myself Howie Fung Team members and relevant director(s) Designated minute-taker So for example, for Visual Editor, the review team would be the Visual Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker. I imagine the structure of the review roughly as follows, with a duration of about 2 1/2 hours divided into 25-30 minute blocks: - Brief team intro and recap of team's activities through the quarter, compared with goals - Drill into goals and targets: Did we achieve what we said we would? - Review of challenges, blockers and successes - Discussion of proposed changes (e.g. resourcing, targets) and other action items - Buffer time, debriefing Once again, the primary purpose of these reviews is to create improved structures for internal accountability, escalation points in cases where serious changes are necessary, and transparency to the world. In addition to these priority initiatives, my recommendation would be to conduct quarterly reviews for any activity that requires more than a set amount of resources (people/dollars). These additional reviews may however be conducted in a more lightweight manner and internally to the departments. We’re slowly getting into that habit in engineering. As we pilot this process, the format of the high priority reviews can help inform and support reviews across the organization. Feedback and questions are appreciated. All best, Erik [1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus [2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate ___ Wikimedia-l mailing list wikimedi...@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Fwd: Phabricator monthly statistics - 2015-01
On Sun, Feb 1, 2015 at 11:49 AM, Quim Gil q...@wikimedia.org wrote: Number of active users (any activity) in (2015-01): 669 Number of task authors in (2015-01): 401 Number of users who have closed tasks in (2015-01): 199 How does that compare to the last months of Bugzilla? Also, if there is an easy way to calculate what percentage of (active|all) Bugzilla accounts were linked to Phabricator, that would be interesting to know. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Grafana production configs
Hello, I'm working on adding performance instrumentation to the Parsoid codebase with statsd/node-txstatsd, and then visualizing the metrics via Grafana. I'm at the stage where I'm looking to add the metrics' namespaces and schema to the WMF Grafana configs. It looks like WMF has Grafana working with Graphite/Carbon as a metrics database and ElasticSearch as the db database, where can I find the production Carbon config files to input the settings for my metrics? Also, from my research WMF's carbon data retention schema is set to '1m:1y, 10m:10y', should I default to this as my retention schema? Note that the metrics are fired off anytime the Parsoid API is used, so each datapoint doesn't necessarily represent a minute/second/etc of data. Thanks, Christy ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New Reference Tooltips beta feature
Adding a Beta Feature to the Cite extension is fine. Note that there was (dormant) code in that repo to do exactly this for years, never enabled. On 2 February 2015 at 16:49, Ricordisamoa ricordisa...@openmailbox.org wrote: Hi everyone, I've come up with a rough OOjs-UI-based rewrite of the long-standing Reference Tooltips https://www.mediawiki.org/wiki/Reference_Tooltips gadget. I'd like to see it enabled on Wikimedia sites as a beta feature, to ultimately replace the gadget, but I'm not sure it is worth an extension on its own. It could share some code with the Popups extension https://www.mediawiki.org/wiki/Extension:Popups but, unlike the latter, the former does not depend on neither TextExtracts nor PageImages. The Cite extension https://www.mediawiki.org/wiki/Extension:Cite is required for references to work, so the tooltips could just be an additional feature. However, I don't feel comfortable with embedding such an experiment into a cornerstone of ours like Cite. VectorBeta https://www.mediawiki.org/wiki/Extension:VectorBeta includes many features of this kind, but reference tooltips are really not Vector-specific. Which do you think is the most suitable repository? ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- James D. Forrester Product Manager, Editing Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] New Reference Tooltips beta feature
Hi everyone, I've come up with a rough OOjs-UI-based rewrite of the long-standing Reference Tooltips https://www.mediawiki.org/wiki/Reference_Tooltips gadget. I'd like to see it enabled on Wikimedia sites as a beta feature, to ultimately replace the gadget, but I'm not sure it is worth an extension on its own. It could share some code with the Popups extension https://www.mediawiki.org/wiki/Extension:Popups but, unlike the latter, the former does not depend on neither TextExtracts nor PageImages. The Cite extension https://www.mediawiki.org/wiki/Extension:Cite is required for references to work, so the tooltips could just be an additional feature. However, I don't feel comfortable with embedding such an experiment into a cornerstone of ours like Cite. VectorBeta https://www.mediawiki.org/wiki/Extension:VectorBeta includes many features of this kind, but reference tooltips are really not Vector-specific. Which do you think is the most suitable repository? ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New Reference Tooltips beta feature
Oh, I see T69282 https://phabricator.wikimedia.org/T69282 now. But my version is much cleaner and doesn't use deprecated components :-) Il 03/02/2015 01:54, James Forrester ha scritto: Adding a Beta Feature to the Cite extension is fine. Note that there was (dormant) code in that repo to do exactly this for years, never enabled. On 2 February 2015 at 16:49, Ricordisamoa ricordisa...@openmailbox.org wrote: Hi everyone, I've come up with a rough OOjs-UI-based rewrite of the long-standing Reference Tooltips https://www.mediawiki.org/wiki/Reference_Tooltips gadget. I'd like to see it enabled on Wikimedia sites as a beta feature, to ultimately replace the gadget, but I'm not sure it is worth an extension on its own. It could share some code with the Popups extension https://www.mediawiki.org/wiki/Extension:Popups but, unlike the latter, the former does not depend on neither TextExtracts nor PageImages. The Cite extension https://www.mediawiki.org/wiki/Extension:Cite is required for references to work, so the tooltips could just be an additional feature. However, I don't feel comfortable with embedding such an experiment into a cornerstone of ours like Cite. VectorBeta https://www.mediawiki.org/wiki/Extension:VectorBeta includes many features of this kind, but reference tooltips are really not Vector-specific. Which do you think is the most suitable repository? ___ 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
[Wikitech-l] Beta bounce handling completed with new beta-mx
Hello, Happy to inform that beta got is now routing through its new working mx ( mx.beta.wmflabs.org ). We had discussions regarding adding a separate mx for beta back in[1] and [2]. Today, we have the mx records added for beta ( dig +short -t mx beta.wmflabs.org ) and beta is sending out mails with a $domain part set as beta.wmflabs.org and bounces coming right back to it. This would make us testing patches related to polonium easy as we never had a polonium equivalent in beta. BounceHandler is working perfectly in the cluster, and bounces are redirected to the API installed in deploymentwiki[3]. In the production cluster, we still have the deployment to group0 wikis[4], which we hope to get done soon. Thanks to Jeff, hoo, Yuvipanda and other devs for the fast deployment and discussions. [1] https://lists.wikimedia.org/pipermail/labs-l/2014-October/002977.html [2] https://phabricator.wikimedia.org/T88215 [3] deployment.wikimedia.beta.wmflabs.org [4] https://gerrit.wikimedia.org/r/#/c/186242/ Thanks, Tony Thomas http://tttwrites.wordpress.com/ FOSS@Amrita http://foss.amrita.ac.in *where there is a wifi, there is a way * ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Fwd: Phabricator monthly statistics - 2015-01
Hi, On Sun, Feb 1, 2015 at 11:16 PM, Pine W wiki.p...@gmail.com wrote: Thanks. Just wondering, do we have a graph somewhere that shows trends? For Bugzilla we had http://korma.wmflabs.org/browser/its.html and http://korma.wmflabs.org/browser/bugzilla_response_time.html but now we miss graphs for Maniphest (see https://phabricator.wikimedia.org/T28 ) There is quite a gap between tasks created and tasks closed, and if that's normal each month then there needs to be some thought about how to fix the gap, yes? Andre is the expert here, but he often says that all the free software projects he is aware of have ever-growing lists of open tasks. In our case, we also need to take into account these new factors: * Phabricator is not only for bugs, and many new tasks that didn't have a place in Bugzilla are being created. * Several teams had tasks open in Mingle or Trello, and now they are cloning them in Phabricator. They are not new, but count as new. * Phabricator is not only for software development projects, and this is becoming another source of new tasks. Said that, I think that everybody would benefit from having more discipline * including a % of old yet relevant tasks in current sprints * marking tasks as Needs Volunteer if nobody in the current teams plans to work on them * declining tasks that have been around for a long time and are not relevant, or not worth the effort of anybody Your ideas are welcome to How to address the long tail of low priority tasks https://phabricator.wikimedia.org/T78639 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Add members to extension owners
On Fri, Jan 30, 2015 at 11:18 AM, Stephan Gambke s7ep...@gmail.com wrote: Are there any plans to streamline that process? Stephan http://www.mediawiki.org/wiki/Gerrit/Project_ownership#To_make_a_new_Project_Owner Yes, and community input is welcome: Migrate Gerrit project ownership request system (+2 rights) to Phabricator https://phabricator.wikimedia.org/T86639 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New Reference Tooltips beta feature
See also https https://phabricator.wikimedia.org/T67114:// https://phabricator.wikimedia.org/T67114phabricator.wikimedia.org https://phabricator.wikimedia.org/T67114/T67114 https://phabricator.wikimedia.org/T67114 ( Hovercards: Show cards for references ) CCing Prateek. On Feb 2, 2015 5:10 PM, Ricordisamoa ricordisa...@openmailbox.org wrote: Oh, I see T69282 https://phabricator.wikimedia.org/T69282 now. But my version is much cleaner and doesn't use deprecated components :-) Il 03/02/2015 01:54, James Forrester ha scritto: Adding a Beta Feature to the Cite extension is fine. Note that there was (dormant) code in that repo to do exactly this for years, never enabled. On 2 February 2015 at 16:49, Ricordisamoa ricordisa...@openmailbox.org wrote: Hi everyone, I've come up with a rough OOjs-UI-based rewrite of the long-standing Reference Tooltips https://www.mediawiki.org/wiki/Reference_Tooltips gadget. I'd like to see it enabled on Wikimedia sites as a beta feature, to ultimately replace the gadget, but I'm not sure it is worth an extension on its own. It could share some code with the Popups extension https://www.mediawiki.org/wiki/Extension:Popups but, unlike the latter, the former does not depend on neither TextExtracts nor PageImages. The Cite extension https://www.mediawiki.org/wiki/Extension:Cite is required for references to work, so the tooltips could just be an additional feature. However, I don't feel comfortable with embedding such an experiment into a cornerstone of ours like Cite. VectorBeta https://www.mediawiki.org/wiki/Extension:VectorBeta includes many features of this kind, but reference tooltips are really not Vector-specific. Which do you think is the most suitable repository? ___ 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Engineering] DevSummit appreciation
I want to hook up to this e-mail from @Tony Thomas. First: Special thanks to Jon, Quim and Rachel (and the Wikimedia travel team!) to make it possible to be there so shortly. It was a great experience, see all people in real live and in color, talk to them and be part of the discussions, presentations and shared ideas and visions :) For me, it was really productive to talk to the peoples directly and discussed recent problems and find solutions and first steps to a solution. Thanks! Florian -Ursprüngliche Nachricht- Von: wikitech-l-boun...@lists.wikimedia.org [mailto:wikitech-l-boun...@lists.wikimedia.org] Im Auftrag von Tony Thomas Gesendet: Freitag, 30. Januar 2015 15:17 An: Wikimedia developers Cc: Development and Operations engineers Betreff: Re: [Wikitech-l] [Engineering] DevSummit appreciation Thanks again to the Foundation for inviting volunteers ( like me ) to the summit. It was a great experience to see my mentors and other guys in IRC off-line face to face for the first time. Regarding the BounceHandler extension - I could get various inputs from other devs who had implemented the same in their environment. The stay and location was superb. I missed some Indian foods though ( thanks to the fruits ). Our deployment plans got delayed due to the security bug that came, making the Ops team busy. We hope to get it done this week though. Thanks again Qum and Rachel and other staff+volunteers for such a great event. Thanks, Tony Thomas http://tttwrites.wordpress.com/ FOSS@Amrita http://foss.amrita.ac.in *where there is a wifi, there is a way* On Fri, Jan 30, 2015 at 4:04 AM, Rob Lanphier ro...@wikimedia.org wrote: Huge +tons to everything below (and top posting to drive Mz up the wall) :-) As Erik said, I know I'm probably going to be driving Rachel and Quim nuts with my handwringing and second guessing as we figure out the pros and cons of how things went this year so that we can keep improving this. But, both of them (and everyone they pulled in) worked like hell put on a great show, and gave us a wonderful space to have some great conversations about our future engineering direction. Thank you! Rob On Wed, Jan 28, 2015 at 9:15 AM, Brion Vibber bvib...@wikimedia.org wrote: Agreed - we had a great space and good support, the WiFi worked, power strips everywhere, and there was always coffee. I can ask for little more... ;) Thanks also to our fellow attendees -- I had a lot of great conversations and got a lot of data points to help set my work directions for the coming months. Everybody there was awesome even when we had contentious issues -- I want to thank everybody for having a positive attitude and working together. -- brion On Jan 27, 2015 10:44 PM, Erik Moeller e...@wikimedia.org wrote: Just a quick note that I really appreciated everyone's help making the summit come together. As always, we'll be doing lots of second-guessing of everything we did and didn't do, and how we want to use future time together. Before we go into that, I'd like to thank the event team and _everyone_ who worked to and beyond the point of exhaustion to organize the event, support attendees, plan sessions, facilitate conversations, negotiate sometimes difficult terrain. Thank you. :) Erik -- Erik Möller VP of Product Strategy, Wikimedia Foundation ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering ___ 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 ___ 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
[Wikitech-l] C2.com switches to single-page app distributed nodejs backend
The original wiki is getting a technical facelift: - http://c2.com/cgi/wiki?WikiWikiSystemNotice - http://c2.fed.wiki.org/view/welcome-visitors - https://news.ycombinator.com/item?id=8983158 Gabriel ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Improving our code review efficiency
But this doesn't remove it from the projects review queue (or search queries, if you just use project:mediawiki/extensions/MobileFrontend status:open). Kind regards, Florian -Ursprüngliche Nachricht- Von: wikitech-l-boun...@lists.wikimedia.org [mailto:wikitech-l-boun...@lists.wikimedia.org] Im Auftrag von Federico Leva (Nemo) Gesendet: Freitag, 30. Januar 2015 08:52 An: wikitech-l@lists.wikimedia.org Betreff: Re: [Wikitech-l] Improving our code review efficiency The remove from code review queue is not that hard really, you can just remove yourself (and reviewers you added) from reviewers. The most helpful reviewers also comment on why they've removed themselves. If reviewers removed themselves from patches they have no intention whatsoever to review (which is fine), things would be much easier. Other effective ways to effectively remove an open patch from the review workflows (and from the korma stats, though not from [[Gerrit/Reports]]) is to self-give a -1 and/or slap a [WIP] in the first line. Nemo ___ 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] C2.com switches to single-page app distributed nodejs backend
This is an interesting change. I wonder how they keep the site accessible by search engine indexers, and folks with older/limited/text-only browsers or limited connectivity. On Mon, Feb 2, 2015 at 8:20 AM, Gabriel Wicke gwi...@wikimedia.org wrote: The original wiki is getting a technical facelift: - http://c2.com/cgi/wiki?WikiWikiSystemNotice - http://c2.fed.wiki.org/view/welcome-visitors - https://news.ycombinator.com/item?id=8983158 Gabriel ___ 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] Beta bounce handling completed with new beta-mx
quote name=Tony Thomas date=2015-02-02 time=19:38:51 +0530 Hello, Happy to inform that beta got is now routing through its new working mx ( mx.beta.wmflabs.org ). Great work, Tony! -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] SMWCon Spring 2015 Tickets Now Available!
(Apologies in advance for the cross-post) I’d like to let you know that tickets are now available for SMWCon Spring 2015. Get them here: http://smwcons2015.eventbrite.com SMWCon (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015), the twice-yearly conference about Semantic MediaWiki, is coming to St. Louis this Spring. The event, organized by local volunteers, will be hosted at T-Rex May 6-8. Attendance is open to anyone wanting to learn about the intersection of the semantic web and collaborative wikis. ==What is Semantic MediaWiki?== Semantic MediaWiki (https://semantic-mediawiki.org/wiki/Semantic_MediaWiki) (SMW) is a free, open-source extension to MediaWiki – the wiki software that powers Wikipedia – that lets you store and query data within the wiki's pages. Semantic MediaWiki is also a full-fledged framework, in conjunction with many spinoff extensions, that can turn a wiki into a powerful and flexible knowledge management system. All data created within SMW can easily be published via the Semantic Web, allowing other systems to use this data seamlessly. Semantic MediaWiki is used on sites like Gamepedia’s League of Legends wiki (http://lol.gamepedia.com/League_of_Legends_Wiki), the W3C’s WebPlatform.org (https://docs.webplatform.org/wiki/Main_Page) and Practical Plants (http://practicalplants.org). It’s also used by numerous organizations internally to document and share information. At past SMWCon’s we’ve had folks from NATO, NASA, MITRE, and Cirque du Soleil talking about how they use a wiki within their organizations. ==What is SMWCon?== SMWCon is a twice annual gathering of SMW administrators, developers, and users who come together to discuss the latest in SMW developments, share what they’re working on, and learn how others are using SMW in various industries. SMWCon Spring 2015 is a 3-day event. The first day focuses on tutorials and introductions to Semantic MediaWiki. The second day is a traditional single-track series of presentations from various folks within the community. The third day is a continuation of talks, and breakout sessions for groups to discuss project work - planning for new development, documentation, or other SMW-related efforts. The conference is May 6-8, 2015 and will be at T-Rex, a local tech incubator and co-working space. We’ll have breakfast for all three days, lunch for two, and a social night out at a local venue. If you’re thinking about attending, visit the conference page (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015) and add your name to the list. That’s right, just edit the page. It’s a wiki after all. Formal registration and tickets can be found at http://smwcons2015.eventbrite.com We have Early-bird and Academic pricing available. ==Speakers Wanted== We’re looking for folks to share their experience using wikis - from the technology and administration to the community building and philosophy behind open collaborative sharing platforms like Semantic MediaWiki. If you’d like to present, you guessed it, just edit the conference page (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015) with your proposed talk. I hope you’ll attend this year and please help spread the word to anyone you think might be interested. For more information or questions, contact the local chair, Chris Koerner, at chris.koer...@mercy.net. This electronic mail and any attached documents are intended solely for the named addressee(s) and contain confidential information. If you are not an addressee, or responsible for delivering this email to an addressee, you have received this email in error and are notified that reading, copying, or disclosing this email is prohibited. If you received this email in error, immediately reply to the sender and delete the message completely from your computer system. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] C2.com switches to single-page app distributed nodejs backend
Actually, it has a nice HTML-only fallback, and Googlebot executes JS these days. On Mon, Feb 2, 2015 at 8:53 AM, James Douglas jdoug...@wikimedia.org wrote: This is an interesting change. I wonder how they keep the site accessible by search engine indexers, and folks with older/limited/text-only browsers or limited connectivity. On Mon, Feb 2, 2015 at 8:20 AM, Gabriel Wicke gwi...@wikimedia.org wrote: The original wiki is getting a technical facelift: - http://c2.com/cgi/wiki?WikiWikiSystemNotice - http://c2.fed.wiki.org/view/welcome-visitors - https://news.ycombinator.com/item?id=8983158 Gabriel ___ 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 -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] C2.com switches to single-page app distributed nodejs backend
Oh, cool. +1 for progressive enhancement! On Mon, Feb 2, 2015 at 9:47 AM, Max Semenik maxsem.w...@gmail.com wrote: Actually, it has a nice HTML-only fallback, and Googlebot executes JS these days. On Mon, Feb 2, 2015 at 8:53 AM, James Douglas jdoug...@wikimedia.org wrote: This is an interesting change. I wonder how they keep the site accessible by search engine indexers, and folks with older/limited/text-only browsers or limited connectivity. On Mon, Feb 2, 2015 at 8:20 AM, Gabriel Wicke gwi...@wikimedia.org wrote: The original wiki is getting a technical facelift: - http://c2.com/cgi/wiki?WikiWikiSystemNotice - http://c2.fed.wiki.org/view/welcome-visitors - https://news.ycombinator.com/item?id=8983158 Gabriel ___ 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 -- Best regards, Max Semenik ([[User:MaxSem]]) ___ 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] New Reference Tooltips beta feature
On Tue, Feb 3, 2015 at 8:25 AM, Nick Wilson (Quiddity) nwil...@wikimedia.org wrote: See also https://phabricator.wikimedia.org/T67114 ( Hovercards: Show cards for references ) CCing Prateek. And https://gerrit.wikimedia.org/r/#/c/139827/ for a very old patch that implements this. On 2 February 2015 at 16:49, Ricordisamoa ricordisa...@openmailbox.org wrote: It could share some code with the Popups extension https://www.mediawiki.org/wiki/Extension:Popups but, unlike the latter, the former does not depend on neither TextExtracts nor PageImages. It could easily share code with the Popups. You can register a new renderer that corresponds to a certain kind of link. There is no compulsion to use TextExtracts or PageImages within a renderer. I'd love to see this functionality within the extension. —prtksxna ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Collections--Project: Gather
Hi Folks, Thank you for your feedback around the collections project*. One of the strongest pieces of feedback was that the project name was easily confused with the collections:extension. Yes. As a result, the collections project is now named project gather. This is effective immediately. The name of the product itself is yet to be settled-on, but the lists themselves are still referred to as collections in mocks etc. There is now a project page up on media wiki: https://www.mediawiki.org/wiki/Gather Comments welcome! Best, J * for context, see thread with subject: New feature in development: collections or first email from that thread repasted here: Hi, For those of you I haven't yet met, I am a new product manager in SF, working with the mobile web team (I look forward to meeting you)! I just wanted to let you all know about a new project we are starting for Wikipedia's mobile website. The project has been dubbed Collections, and our pilot will let users create and share collections of articles. Here are some ways that this project is exploring new ways to move our mission forward: - *New ways to contribute: * through curation, wikipedia readers who are not interested in traditional editing can have meaningful, creative interactions with our content - *Personal:* gives users a way to make content more relevant for them Peter's list of most important Philosophers is not subject to consensus or editing by others. For the time being, a list will only be accessible via shared url. - *Shareable: *this project will experiment with the ability to use Wikipedia to share ones' perspective with others and, in doing so, encourage new users to engage - *[Future] Browseable:* because each list is not exhaustive, there is a possibility of using popular lists to promote meaningful content. It's nice to know the full list of statisticians https://en.wikipedia.org/wiki/List_of_statisticians is there, but I might want to find a subset that have been picked out by a human for one reason or another. Though the pilot is targeting and supporting readers, we think there are also potential use cases for editors that we could explore in the future. One can easily imagine lists for editors to track or share their contributions, such as: Articles that I want to write/expand during 2015 or Articles I created in 2013. A fair amount of thought has gone into why we are launching this particular project and how we might approach it, but we have just started exploratory development work last week. Here is the team: Jon Robson Rob Moen Joaquin Hernandez Moiz Syed [me] *Ask:* [I know that this project overlaps with several existing features in terms of raw functionality, so if you have any relevant experience with either the editing or technical support of lists, collections extension (books) or watchlist and are interested in sharing your experience, please feel reach out to me directly. We very much want to learn from previous efforts] Also, please reach out to me or anyone else on the team if you have any questions or concerns about the feature, team, etc. Best, Jon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Fwd: Phabricator monthly statistics - 2015-01
It would be interesting to compare our trends to those of other open source projects with open bug or task trackers. Pine On Feb 1, 2015 7:47 PM, James Forrester jforres...@wikimedia.org wrote: On 1 February 2015 at 14:16, Pine W wiki.p...@gmail.com wrote: Hi Quim, Thanks. Just wondering, do we have a graph somewhere that shows trends? There is quite a gap between tasks created and tasks closed, and if that's normal each month then there needs to be some thought about how to fix the gap, yes? I believe that the difference has been positive (*i.e.*, the gap has been increasing) almost every month since the beginning of using Bugzilla a decade ago… To some extent, you'd expect the limits of our ambitions to continue extending at a faster rate than our ability to address them, so I'm not entirely sure about whether we should consider this a bad thing, or something to be addressed. J. -- James D. Forrester Product Manager, Editing Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ 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] Fwd: Phabricator monthly statistics - 2015-01
On Sun, Feb 1, 2015 at 2:16 PM, Pine W wiki.p...@gmail.com wrote: Hi Quim, Thanks. Just wondering, do we have a graph somewhere that shows trends? There is quite a gap between tasks created and tasks closed, and if that's normal each month then there needs to be some thought about how to fix the gap, yes? Thanks, Pine Also keep in mind that it is used by many people to track feature-requests (long and short-term, planned and wishlist), as well as bugs, so some growth is both inevitable and desired. (I believe this is what James is saying). But I agree that an increase of old-bug triage and resolving, would be welcomed. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
