 | MWStake General | 129 Members |
| MediaWIki Stakeholders' Group general discussion | 25 Servers |
| MWStake General | 129 Members |
| MediaWIki Stakeholders' Group general discussion | 25 Servers |
| Sender | Message | Time |
|---|---|---|
| 14 Nov 2019 | ||
 rundg | Thanks for sharing nikerabbit | 21:34:50 |
 grin | nikerabbit: don't worry, the server plays fun on you | 22:04:31 |
| 15 Nov 2019 | ||
 adsvs | In reply to @darenwelsh:matrix.orgWe tend to think of technical improvements, but there is one thing that comes to mind first. That is broadcasting, shouting to the world (from space?) that MediaWiki is a platform for 'third parties' and that there is 'support' for use of MediaWiki by companies and 'other' organizations. The positioning and marketing of MediaWiki is way behind its technical capabilities. We would love to see MediaWiki on Gartner magic quadrants and in other comparisons against for example SharePoint. So the fact that there is third party support (whatever it is ;-) )is more important than what it is and what should be on the wishlist. Having said that I'll see what I can do to create such a list on the MWStake site :-). | 09:16:37 |
 darenwelsh | So rather than bringing forward any specific requests for technical implementation, your concern is just that the foundation acknowledge the platform is meant for more than Wikimedia sites and to support those use cases? Is that right? I guess I still don't know what you mean by "support", so it's hard to lobby for anything without specifics. | 12:49:37 |
| rundg |
I'm still working on the Ultimate Nginx config for MediaWiki. I intend to put it into a git repo so you can see the includes too. As a matter of fact, it will eventually be part of QualityBox v2 so the whole server setup will be shared. bryandamon if you want to do a hangout, I'd be happy to walk through the file with you to explain the rules | 13:55:20 |
 bryandamon | @freephile : I'd love to! Next week is better for me if that works for you. | 21:10:18 |
| 17 Nov 2019 | ||
| darenwelsh | https://phabricator.wikimedia.org/T238384 Notes from an unconference session led by Grant (new WMF CTO) on measuring success. There are mentions of external interrupts and priorities here (no mention in notes of third party, directly) | 16:26:53 |
| darenwelsh | https://phabricator.wikimedia.org/T238234 Notes from an unconference session led by Chris Koerner about defining "third party". | 16:30:25 |
| darenwelsh | https://phabricator.wikimedia.org/T238274 Notes from an unconference led by yours truly and Leon (MusikAnimal) asking developers what user metrics would help them better design their software. | 16:31:30 |
 cicalese | https://phabricator.wikimedia.org/T238234#5668778: "Our attempt to clarify our (WMDE) understanding of which "3rd party" (or rather: partners) . . .". I like the reframing of third parties as partners. | 16:36:06 |
| darenwelsh | https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/Program Plenty more things from the conference linked here | 16:47:00 |
| 18 Nov 2019 | ||
 tgr | In reply to @cicalese:matrix.orgI tried something similar at Wikimania: https://wikimania.wikimedia.org/wiki/2019:Partnerships/Free_software_as_a_partnership | 06:26:16 |
| tgr | In reply to @darenwelsh:matrix.orgI guess a bit late, but a decent wiki management experience (installer, upgrader, admin panel, config panel, extension marketplace) is the most obvious thing that's missing | 06:29:07 |
| tgr | also restricting read permissions, but it's debatable how well that fits into the vision / values of MediaWiki | 06:29:55 |
| tgr | on the culture side, better code review (widely recognized issue, there are efforts to fix it) and marketing of MediaWiki (although not clear if the WMF should be the one doing it) | 06:31:02 |
| 19 Nov 2019 | ||
 daw5423 joined the room. | 17:20:33 | |
| 20 Nov 2019 | ||
| cicalese |
The flow of the discussion at https://gerrit.wikimedia.org/r/c/mediawiki/core/+/551346 may be an example. | 14:03:19 |
 hexmode | What does "unmaintained code" mean? If it works, does it need to have any activity around to be maintained? If bugs are fixed when they appear, isn't that maintenance? | 14:30:02 |
| hexmode | When it comes to free software like MediaWiki, should functionality be removed because a developer doesn't want to fix it when other people are using it? | 14:30:50 |
| rundg | JS question... why would this fiddle work on it's own, but fail silently when added to MediaWiki:Common.js https://jsfiddle.net/freephile/jws1rbyn/ | 15:33:29 |
| rundg | I can only guess variable collision? | 15:37:48 |
| rundg | So I'm working to namespace the functionality | 15:38:14 |
| rundg | There is a global $wgUseSiteJs which defaults to true and is not overridden anywhere | 15:56:26 |
| hexmode | anybody know who has set up the github mirror of gerrit? | 23:08:40 |
| hexmode | mixed up github mirror | 23:09:38 |
| cicalese | hexmode: somebody involved in https://phabricator.wikimedia.org/T200736? | 23:17:50 |
| hexmode | cicalese: maybe? I'll post there, but there is no mirror using either case | 23:19:20 |
| cicalese | Aren't all extensions in gerrit mirrored on github? | 23:19:54 |
| cicalese | Well, there you go. | 23:31:41 |
| rundg |
This may be a bug... looks like MediaWiki:Common.js is either not loaded in mobile or loaded differently -- The code works when loaded as a module from an extension in both mobile and desktop. The code doesn't work on mobile when contained in MediaWiki:Common.js | 23:58:58 |