[Wikitech-l] Timeless grant final report

Hey all, the Timeless grant has wrapped up and I've submitted the final report for the project. Please check it out if you're interested: https://meta.wikimedia.org/wiki/Grants:Project/Timeless/Post-deployment_support/Final A couple of things to highlight: * The associated learning pattern is

[Wikitech-l] Help merge patch (Interwiki)

How do you get patches merged when you don't actually know anyone to review it? Sometimes you just get lucky, but sometimes you add a bunch of people, a few others even wander in and +1 it, you ask a few people with core +2 to take a look, and then you're still waiting on a product owner to

Re: [Wikitech-l] 今週あなたを幸せにするものは何ですか？ / What's making you happy this week? (Week of 16 June 2019)

Mailing lists aren't really a good place to establish consensus, as every time someone weighs in, everyone is notified, so 'me too's are frowned upon in principle. Perhaps you might want to create an actual poll about preferred venues etc onwiki and then send out a message to wikimedia-l

Re: [Wikitech-l] Improving the mediawiki.org frontpage: It's available!

It looks good in Modern. On 13/04/2019 13:17, Andre Klapper wrote: Hi everybody, https://www.mediawiki.org has a new frontpage! Thank you to everyone who provided great feedback and comments on https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_improvements_2018 and

Re: [Wikitech-l] Uploading new versions of other people's patches to gerrit

On 09/04/2019 19:40, Tyler Cipriani wrote: Hello, On 19-04-09 17:50:12, Isarra Yos wrote: To clarify, I get what you're trying to do, but there has got to be a better solution besides denying key features to and thus impairing long-term contributors, because disabling this for everyone

Re: [Wikitech-l] Uploading new versions of other people's patches to gerrit

On 09/04/2019 17:53, Greg Grossmeier wrote: PS: I just saw your follow-up reply. Sadly Gerrit is not mediawiki ;) so it doesn't have all of the other built in anti-abuse features that comes with the nice user features. Most of MediaWiki's anti-abuse features consist of only applying certain

Re: [Wikitech-l] Uploading new versions of other people's patches to gerrit

On 09/04/2019 17:38, Isarra Yos wrote: On 09/04/2019 16:44, Tyler Cipriani wrote: On 19-04-09 05:17:17, Isarra Yos wrote: This seems to be broken, or something. It's causing problems for collaboration. Please fix. This is the addPatchSet permission in Gerrit. That particular permission

Re: [Wikitech-l] Uploading new versions of other people's patches to gerrit

On 09/04/2019 16:44, Tyler Cipriani wrote: On 19-04-09 05:17:17, Isarra Yos wrote: This seems to be broken, or something. It's causing problems for collaboration. Please fix. This is the addPatchSet permission in Gerrit. That particular permission was recently abused, and at that time

Re: [Wikitech-l] Uploading new versions of other people's patches to gerrit

On 09/04/2019 09:21, Bartosz Dziewoński wrote: Hopefully this will not stay disabled forever, for I also miss the feature. In the meantime, you can use the traditional Git way of generating patch files and sending them by email (or perhaps, in a modern twist, via Phabricator). To generate

Re: [Wikitech-l] Uploading new versions of other people's patches to gerrit

On 09/04/2019 05:17, Isarra Yos wrote: This seems to be broken, or something. It's causing problems for collaboration. Please fix. I now hear that this is intentional for spam/vandalism reasons. This seems unwise. Regardless, where is the documentation about this? What is the recommended

[Wikitech-l] Uploading new versions of other people's patches to gerrit

This seems to be broken, or something. It's causing problems for collaboration. Please fix. -I ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] New Gerrit privilege policy

On 16/03/2019 14:35, Bartosz Dziewoński wrote: On 2019-03-16 14:48, Merlijn van Deen (valhallasw) wrote: 1. According to the policy, self-+2'ing is grounds for revocation of Gerrit privileges. For a Toolforge tool, self +2-ing is common and expected: the repository is hosted on Gerrit to

Re: [Wikitech-l] New Gerrit privilege policy

On 16/03/2019 13:48, Merlijn van Deen (valhallasw) wrote: On Sat, 16 Mar 2019 at 03:01, Tim Starling wrote: No, managing +2 permissions is not up to the maintainer of the tool, that's the whole point of the change. I feel that this policy, although well-meaning, and a step forwards for

[Wikitech-l] Request for comment: Themes in core

For those who weren't aware, Jack Phoenix and I have drafted a Request for Comment[1] and related initial patch[2] proposing to merge the logic from the Theme extension[3] into MediaWiki core. From the RfC: This will provide built-in functionality that skins can implement in a simple and

Re: [Wikitech-l] A difficult goodbye

Sad to see you go - from what I saw as a volunteer, things only improved under your leadership here. We were lucky to have you. All the best. -I On 11/01/2019 00:29, Victoria Coleman wrote: Dear all, I have some difficult news to share. A few months ago and completely out of the blue, an

Re: [Wikitech-l] My Phabricator account has been disabled

ask would be: What do you gain from getting more clarity? On Wed, Aug 15, 2018 at 6:58 PM Isarra Yos wrote: On 10/08/18 14:31, David Barratt wrote: yet this is clearly precisely what is needed to avoid incidents like this in the future. Based on what has been provided in this thread, I do

Re: [Wikitech-l] My Phabricator account has been disabled

to was the unclear CoCC action taken and subsequent confusion and disagreement, including this email thread. We absolutely do not need this all to happen again in another six months with yet another incident which cannot be explained. -I On Fri, Aug 10, 2018 at 9:23 AM Isarra Yos wrote

Re: [Wikitech-l] My Phabricator account has been disabled

On 15/08/18 22:40, David Barratt wrote: In this particular case, it was based on a comment that was deleted. https://web.archive.org/web/20180803232905/https://phabricator.wikimedia.org/T200742#4475216 And no, my intention was not to imply "if you did nothing wrong, you have nothing to

Re: [Wikitech-l] My Phabricator account has been disabled

On 15/08/18 22:08, David Barratt wrote: This isn't a he said, she said type of issue, it's based on evidence that is public and difficult (if not impossible) to delete. If you feel that you would have to defend your behavior, perhaps the

Re: [Wikitech-l] My Phabricator account has been disabled

On 15/08/18 20:50, Nuria Ruiz wrote: Given that here is a narrative going around that the CoC is unfairly biased in favour of staff, would you mind sharing what deliberations took place that resulted in sactions against only one of the participants in a dispute The deliberations as well as the

Re: [Wikitech-l] My Phabricator account has been disabled

, 2018, 21:49 Isarra Yos wrote: Expecting every single comment to specifically move things forward seems... a bit excessive, frankly. Not everyone is going to have the vocabulary to properly express themselves, let alone the skill to fully explain exactly what the issues are, why they are, how

Re: [Wikitech-l] My Phabricator account has been disabled

Expecting every single comment to specifically move things forward seems... a bit excessive, frankly. Not everyone is going to have the vocabulary to properly express themselves, let alone the skill to fully explain exactly what the issues are, why they are, how to move forward, or whatever.

Re: [Wikitech-l] [Wikimedia-l] C-team Statement on the Code of Conduct

Sorry, I apparently replied to the wrong mailing list. On 14/08/18 18:19, Isarra Yos wrote: As a total random, I'd also like to second this - as much as I think the CoC and the committee in particular have room to improve in how things are handled, this will never happen without proper support

Re: [Wikitech-l] My Phabricator account has been disabled

ssed. On Thu, Aug 9, 2018 at 6:33 PM Isarra Yos wrote: An interesting comparison, democracy. Community consensus and transparency were what brought our shared project to the great heights we now see, and yet the CoC and especially its enforcement are rooted in none of this. If this trainwreck t

Re: [Wikitech-l] My Phabricator account has been disabled

An interesting comparison, democracy. Community consensus and transparency were what brought our shared project to the great heights we now see, and yet the CoC and especially its enforcement are rooted in none of this. If this trainwreck that we are currently experiencing on this list is

Re: [Wikitech-l] My Phabricator account has been disabled

On 09/08/18 07:40, Amir E. Aharoni wrote: No, it was not thoughtful. What actually happened is that the other users are now submerged with dozens of emails analyzing that interjection. Sure, it's pretty easy to ignore this thread or even mute it in one's email reader, but one could just as well

Re: [Wikitech-l] My Phabricator account has been disabled

Er, apologies for my previous email, I may have gone a bit overboard with it. Is it generally improper to blame the cold medicine, in such cases, bow out, and generally just go straight to bed? Because I blame the cold medicine. Again, sorry about that. -I

Re: [Wikitech-l] My Phabricator account has been disabled

Having personally been subject of a case of sexual harassment at an unrelated event a few years back where I was supposedly the victim, I have to wonder even about those. Seriously, what the hell /is/ sexual harassment? Because in my case, apparently me butting into a conversation just to be

Re: [Wikitech-l] My Phabricator account has been disabled

should really be learning from that. -I On 08/08/18 20:15, Isarra Yos wrote: Nope! But this just seems /worse/ in practice. -I On 08/08/18 20:12, Ryan Kaldari wrote: Are you suggesting that ArbCom does a good job of maintaining a collegial, harassment-free environment on English Wikipedia

Re: [Wikitech-l] My Phabricator account has been disabled

Nope! But this just seems /worse/ in practice. -I On 08/08/18 20:12, Ryan Kaldari wrote: Are you suggesting that ArbCom does a good job of maintaining a collegial, harassment-free environment on English Wikipedia? Just wanted to double-check ;) On Aug 8, 2018, at 1:02 PM, Isarra Yos wrote

Re: [Wikitech-l] My Phabricator account has been disabled

On other projects, we have community-elected groups among whom we see oversight in the form of new members upon subsequent elections who can audit the backlogs, and who conduct their primary functions in the open and issue clear statements when a matter does indeed merit not discussing openly,

Re: [Wikitech-l] coc ban

Yeah, even if it seems like volunteers are treated as second class citizens, advocating mistreatment of staff too isn't going to resolve anything. We should all just try to do our best, and all realise that these are /peolpe/ we're dealing with. It's not always going to be perfect, it's not

Re: [Wikitech-l] My Phabricator account has been disabled

This is actually a rather good point, and one I would argue also shows why we need more transparency from the CoC committee in the first place - lacking that, all the community at large can really go on is what the accused provides, which does no favours toward the effectiveness of any actions

Re: [Wikitech-l] My Phabricator account has been disabled

I see two issues here: 1. Lack of logging of autodisabled accounts means that confusions such as this may arise, but more especially, we appear to lack any way to track for false positives of accounts from new users who do mean well, who instead of going to someone to bring up the issue,

[Wikitech-l] Timeless Newsletter

Hey all, For anyone not familiar, the Timeless skin has been available as an option on Wikimedia wikis since november or so, and development of the skin is now being funded by a Project Grant. If you're interested in receiving updates about this, I've created a newsletter which should be

Re: [Wikitech-l] Gerrit as a shared community space

On 09/06/18 17:30, Brion Vibber wrote: On Sat, Jun 9, 2018 at 10:21 AM Alex Monk wrote: For example where you said "IMHO specifically because some people are trying to avoid being bound by it or protesting its existence by looking for loopholes to avoid it", which is not at all what that

Re: [Wikitech-l] Can/should my extensions be deleted from the Wikimedia Git repository?

On 08/06/18 09:29, Gergo Tisza wrote: ... I'm sure you wouldn't act (inside or outside Wikimedia technical spaces) in ways inconsistent with the spirit of the code of conduct anyway, but this was a silly fight to pick and I hope you'll reconsider (or if you have pragmatic reasons for not wanting

Re: [Wikitech-l] Can/should my extensions be deleted from the Wikimedia Git repository?

This. The links should be in the interfaces in which we actually interact with each other, not the repositories themselves. A repository isn't even inherently a wikimedia technical space because it can be cloned anywhere, as Yaron rightfully points out; using gerrit/phab/things wikimedia

Re: [Wikitech-l] "PHP test coverage decreased" - really?

On 26/04/18 19:02, Daniel Kinzler wrote: Also, am I correct in thinking that I could introduce a completely new 1000 line class with no tests, and that would *not* be detected as decreasing coverage, since the new class didn't have any coverage before? Given that I've done similar (not a

Re: [Wikitech-l] Mobile MonoBook

On 03/04/18 22:52, Strainu wrote: Well, it looks a bit dated, but in cute and geekish way. I love the way you took the menu out of the way without hiding it under a hamburger button, Well, admittedly, that approach was largely just so it would work at all without js. I was kind of planning on

[Wikitech-l] Mobile MonoBook

I have made a patch for a responsive version of MonoBook with mobile support. See: https://gerrit.wikimedia.org/r/c/421199/ or if you just want a live demo, https://wiki.zaori.org/wiki/Page_title?useskin=monobook - load it on a phone or make your browser window narrow or something and you can

Re: [Wikitech-l] Refactoring MonoBook

your problem anymore, and Modern can slowly further bitrot ;) Its not ideal, but I would consider it acceptable. DJ On Sun, Mar 18, 2018 at 2:03 AM, Isarra Yos <zhoris...@gmail.com> wrote: I have just been informed that Modern works by extending MonoBookTemplate. This is a problem. -I On

Re: [Wikitech-l] Refactoring MonoBook

On 18/03/18 03:09, K. Peachey wrote: Just make it MonoBookV5? *runs*, or more realistically V2 then progressively get rid of the orginal MonoBook? The problem with splitting things up like that is then you need to deal with transitions from a v1 to a v2, which make everyone's lives more

Re: [Wikitech-l] Refactoring MonoBook

I have just been informed that Modern works by extending MonoBookTemplate. This is a problem. -I On 18/03/18 00:56, Isarra Yos wrote: I'm refactoring MonoBook, starting with MonoBookTemplate. The current change gets rid of the entire immediate print/html soup approach and instead assembles

[Wikitech-l] Refactoring MonoBook

I'm refactoring MonoBook, starting with MonoBookTemplate. The current change gets rid of the entire immediate print/html soup approach and instead assembles a giant string and prints that in one statement at the end. See: https://gerrit.wikimedia.org/r/#/c/420154/ and

[Wikitech-l] WikiProject X followup grant to fund finalising CollaborationKit

Hey all, I'm pleased to announce a proposed followup for WikiProject X, a project previously funded by an Individual Engagement Grant. I have now submitted a Project Grant, according to the new system, with which I intend to complete and fully assess the development of CollaborationKit, the

[Wikitech-l] Timeless grant resubmission

Hey all, As many of you know, the Timeless skin was deployed for testing across all Wikimedia projects in late November last year. I submitted a Project Grant proposal at the time seeking funding to more actively support for this deployment as well as enable further development based on user

Re: [Wikitech-l] Thank you 2017 code reviewers

Do the extensions numbers also include skins? That's an excellent goal, and I hope others will indeed do the same! Also I really like how Krinkle beat the translatewiki bot in core. -I On 08/01/18 06:56, Kunal Mehta wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Nemo generated

[Wikitech-l] Post-deployment support for Timeless

As you may be aware, the Timeless skin has been undergoing deployment to various Wikimedia projects over the past couple of months, thus far deployed to five french projects, with a pending deployment for five more hebrew, german, and english projects in the works. As the primary developer

Re: [Wikitech-l] Update to web print styles

On 30/08/17 17:41, Jon Robson wrote: On Wed, Aug 30, 2017, 10:16 AM Bartosz Dziewoński <matma@gmail.com> wrote: On Mon, Aug 28, 2017 at 10:18 PM, Isarra Yos <zhoris...@gmail.com> wrote: Are these changes in core, or in the skins themselves (Vector and Minerva)? In

Re: [Wikitech-l] Update to web print styles

Are these changes in core, or in the skins themselves (Vector and Minerva)? In other words, will printing from other deployed skins such as MonoBook also see improvement, or is it up to the maintainers of each other skin to independently apply similar changes? Thanks. -I On 03/08/17 20:42,

Re: [Wikitech-l] Timeless skin now available on mw.org

I'm going with both. (Width cuttoffs are a bit unnecessarily narrow in Timeless, but we need content stuff to scale down better as well, as there are also a lot of devices that are just plain narrower, and such, too.) On 12/08/17 20:42, Jan Dittrich wrote: This means on the Wikibase UI you

Re: [Wikitech-l] Timeless skin now available on mw.org

.kinz...@wikimedia.de wrote: Wow, this looks great! Am 11.08.2017 um 18:26 schrieb Isarra Yos: The Timeless skin has been deployed to test, test2, and mw.org. Anyone interested, please go ahead an enable it and find everything wrong and swear at me about it. Note that the current design is not

[Wikitech-l] Timeless skin now available on mw.org

The Timeless skin has been deployed to test, test2, and mw.org. Anyone interested, please go ahead an enable it and find everything wrong and swear at me about it. Note that the current design is not the final design and I haven't quite worked out what the final design should be, either, so

Re: [Wikitech-l] Improvements to developer events in the WMF Annual Plan draft

First off, thank you for your excellent response. On 05/05/17 12:58, Quim Gil wrote: Sorry for being so late replying. Isarra asks a good question and I have been thinking of a good answer. On Thu, Apr 27, 2017 at 8:35 PM, Isarra Yos <zhoris...@gmail.com> wrote: Different events serv

Re: [Wikitech-l] Improvements to developer events in the WMF Annual Plan draft

this makes sense. Victoria On Apr 27, 2017, at 11:35 AM, Isarra Yos <zhoris...@gmail.com> wrote: Thanks. Different events serve very different purposes, though - hackathons, for instance, seem to be largely useful for onboarding newcomers and giving staff and other occupational contri

Re: [Wikitech-l] Improvements to developer events in the WMF Annual Plan draft

learn and adapt. If we collectively decide to try for a different configuration the following year, we can totally do that. Please keep the feedback coming! Best regards, Victoria On Apr 26, 2017, at 12:23 PM, Isarra Yos <zhoris...@gmail.com> wrote: Regarding the Developers Summit in part

Re: [Wikitech-l] Improvements to developer events in the WMF Annual Plan draft

Regarding the Developers Summit in particular, how do you plan to reconcile making the event smaller with your goal of better retention of newcomers and volunteers in general when that's often the only venue they have at which to discuss the high-level technical issues with other stakeholders?

Re: [Wikitech-l] Editing JSON in MediaWiki

Sounds like what they want is what collaborationlistcontent/handler does, specifically, at least for now. On 09/04/17 06:30, James Hare wrote: Why, exactly, do you want a wikitext intermediary between your JSON and your HTML? The value of wikitext is that it’s a syntax that is easier to edit

[Wikitech-l] Timeless skin on Wikimedia projects - current status, grant proposal

Hi, Timeless is a new responsive skin based on the Vector layout, incorporating in design principles from Winter and other modern sites, which I originally started in 2015 as an example for a tech talk. I kind of forgot about it for awhile since, but then we (essentially a bunch of random

Re: [Wikitech-l] Extension compatibility styles and responsive skins

interesting. But you know. -I On 27/03/17 01:54, Pine W wrote: Hi Isarra, You might try the design@ email list if you don't get a satisfactory reply here within a day or two. Also pinging Quiddity in case he has ideas. HTH, Pine On Sat, Mar 25, 2017 at 11:40 AM, Isarra Yos <zho

[Wikitech-l] Extension compatibility styles and responsive skins

Basically: skins style the interface, extensions add new interface. Compatibility then needs to be added to the skins for the extensions, so they can style the new interface too, but we don't want to load the extension-specific styles unless the extensions is actually used. Thus we use

Re: [Wikitech-l] MVVM/Single-State solution for our UIs?

Er, what does this mean? What is MVVM? On 30/01/17 13:57, Jan Dittrich wrote: Hello Wikitext-l, --- TL;DR: The Wikidata team is considering to use a MVVM/Single-State solution for Wikidata’s UI. What are requirements and concerns would be important to consider?

Re: [Wikitech-l] Gerrit 2.12.2 test instance - PLEASE TEST

On 13/07/16 06:50, Niklas Laxström wrote: Many good and bad changes I can live with. One thing I will miss: * Columns setting no longer wraps the diff lines. Horizontal scroll is now unavoidable and cumbersome due to having to use either the mouse or the arrow keys to move the cursor on the

Re: [Wikitech-l] Diff algorithms: the shootout

Cool! It's entirely possible that the shortcuts it takes correspond to what makes a more cohesive thing to present to the user - the same shortcuts in the diff implementation are what we want in the front-end when looking for meaningful changes anyway. I mean, this is just random

Re: [Wikitech-l] tags are a usability nightmare for editing on mediawiki.org

Is there any way to just flag pages to not get translated? These tags are basically the main reason I've given up on documenting any of my extensions/skins. On 01/04/16 16:31, Brion Vibber wrote: Lots of pages on mediawiki.org are pretty much uneditable because they're strewn with spanning

Re: [Wikitech-l] Hackathon buddy familiar with page content type stuff needed

I'm sort of familiar with content handling in general, since I've been working on an extension using this stuff as well, so I might be able to help. I've found it difficult to get help in this area as well just because so few folks have had the opportunity to properly figure it out, and there

Re: [Wikitech-l] RfC: Notifications in core

Ye. On 01/03/16 21:41, Legoktm wrote: Hi, I've written an RfC about moving most of the Echo extension code into MediaWiki core: . RobLa has written a summary of it on the Phab task:

Re: [Wikitech-l] Appreciation thread, 2015

Perhaps a thanks to the people we don't think about, who we often never even work with. Volunteers and third-party developers who contribute to and maintain repositories not part of the big tickets. People who take the time to file bugs, and triage them, and sort things out. The ops who keep

Re: [Wikitech-l] [BREAKING CHANGE] IE 8 will go JavaScript-less starting January 2016

Your email client seems to have mangled the indenting for some reason, so I tried to repair it. Apologies if I've messed anything up in the process. On 15/11/15 09:47, Jon Robson wrote: On 15 Nov 2015 2:31 p.m., "Isarra Yos" <zhoris...@gmail.com> wrote: I agree that it's i

Re: [Wikitech-l] [BREAKING CHANGE] IE 8 will go JavaScript-less starting January 2016

he requests for these modules are initialized by JS). -Original-Nachricht- Von: "Isarra Yos" <zhoris...@gmail.com <lt%3bzhoris...@gmail.com>> Using js got around this whole problem as with that you can simply check the browser there and then conditionally mw.loader.l

Re: [Wikitech-l] [BREAKING CHANGE] IE 8 will go JavaScript-less starting January 2016

to adopt this tried and tested approach. On 13 Nov 2015 2:20 a.m., "Isarra Yos" <zhoris...@gmail.com> wrote: Perhaps I should clarify why this is a problem. In fully responsive skins, you generally have separate stylesheets for desktop, mobile, really big desktop, whatever in order

Re: [Wikitech-l] [BREAKING CHANGE] IE 8 will go JavaScript-less starting January 2016

: "Isarra Yos" zhoris...@gmail.com An: "Wikimedia developers" wikitech-l@lists.wikimedia.org Perhaps I should clarify why this is a problem. In fully responsive skins, you generally have separate stylesheets for desktop, mobile, really big desktop, whatever in order to keep

Re: [Wikitech-l] [BREAKING CHANGE] IE 8 will go JavaScript-less starting January 2016

-free module for IE8. Is there any other way around this? On 12/11/15 02:56, Isarra Yos wrote: Is there a way to conditionally load RL modules for folks using IE8? Because I couldn't figure out any proper way to do that in my skins and I've just been using js to do it instead as a result

Re: [Wikitech-l] Skinning tutorial

On 12/11/15 03:39, S Page wrote: On Tue, Nov 10, 2015 at 6:31 PM, Isarra Yos <zhoris...@gmail.com> wrote: On 11/11/15 02:06, S Page wrote: I meant the on-wiki three-part skinning thing that's been around for a while and introduces in a nutshell as "This page is part 1 of a

Re: [Wikitech-l] [BREAKING CHANGE] IE 8 will go JavaScript-less starting January 2016

Is there a way to conditionally load RL modules for folks using IE8? Because I couldn't figure out any proper way to do that in my skins and I've just been using js to do it instead as a result. But that's not going to work anymore. But it's also stupid regardless. On 12/11/15 02:11, Krinkle

[Wikitech-l] Skinning tutorial

As a bit of a follow up to the talk I did last week, I wrote up a tutorial on-wiki how to make a skin: https://www.mediawiki.org/wiki/User:Isarra/How_to_make_a_motherfucking_skin The plan is to eventually replace Manual:Skinning with that and some subpages with specific info, but if anyone

Re: [Wikitech-l] Skinning tutorial

On 10/11/15 21:59, S Page wrote: The tutorial is pretty good IMO, the problem is it forced repetition. part 1 "Here are some page elements you need to worry about"; part 2 "Let's output some of those page elements"; part 3 "How to test these page elements". But maybe that's OK. This may just

Re: [Wikitech-l] Skinning tutorial

On 11/11/15 02:06, S Page wrote: On Tue, Nov 10, 2015 at 2:39 PM, Isarra Yos <zhoris...@gmail.com> replied: On 10/11/15 21:59, S Page wrote: The tutorial is pretty good IMO, the problem is it forced repetition This may just be because I did it at three in the morning; it probably d

[Wikitech-l] Summit proposal: Turning the Table of Contents into a discrete object

Hi! I would like to turn the mw ToC into a discrete object within the codebase. Write a ToC class and pull all the random building parts out of the parser and five levels of pageoutput, and make it stop messing up the page caching and stuff. Make this class a thing, separate from the content

Re: [Wikitech-l] Forking, branching, merging, and drafts on Wikipedia

On 07/11/15 00:32, David Gerard wrote: On 7 November 2015 at 00:29, Brian Wolff wrote: I feel like different people want different things, and what is really needed is a user-centric discussion of use-cases to drive a feature wishlist, not any sort of discussion about

Re: [Wikitech-l] Fwd: [MediaWiki-l] An "advanced search" page for CirrusSearch?

On 06/10/15 17:12, Daniel Barrett wrote: MZMcBride writes: It also seems worthwhile to note that "Special:Search" already has an advanced profile/tab where users can select arbitrary namespaces to search. Technically that is true, but I suspect that 95% of the time, 95% of users care only

[Wikitech-l] Fwd: [MediaWiki-l] An "advanced search" page for CirrusSearch?

This strikes me as a rather good idea, but I don't really know that much about cirrussearch in the first place. Anyone know, or have any thoughts on this? Forwarded Message Subject:[MediaWiki-l] An "advanced search" page for CirrusSearch? Date: Mon, 5 Oct 2015

Re: [Wikitech-l] Would anyone be interested in a tech talk about how to make a mw skin?

. Alternatively you might want to consider doing a skin hack day/afternoon where people build skins and learn for themselves the horror of that process :) On Mon, Sep 28, 2015 at 3:08 PM, Bryan Davis <bd...@wikimedia.org> wrote: On Mon, Sep 28, 2015 at 3:00 PM, Isarra Yos <zhoris...@gmail.c

Re: [Wikitech-l] Would anyone be interested in a tech talk about how to make a mw skin?

be advertised so anyone can join. Essentially it would be a hackathon focused on skins. If you were really ambitious you'd add prizes for best judged skin etc :) On 30 Sep 2015 12:49 pm, "Isarra Yos" <zhoris...@gmail.com> wrote: How would a hack day/afternoon work? Is that an office thi

[Wikitech-l] Skins in tarball releases

I would like to get a skin added as an option to the tarball releases. What all do they generally need to have done before that's possible? For reference, this is the skin: https://www.mediawiki.org/wiki/Skin:GreyStuff Any feedback about the skin in general would also be appreciated. -I

Re: [Wikitech-l] The "other" developers at the Wikimedia Developer Summit

On 28/09/15 16:16, Quim Gil wrote: On Mon, Sep 28, 2015 at 6:07 PM, Isarra Yos <zhoris...@gmail.com> wrote: In the example of template editors, gadget and tool developers, etc used earlier in this thread, how would that apply? Folks just do enough templates etc elsewhere and poke a r

Re: [Wikitech-l] The "other" developers at the Wikimedia Developer Summit

On 28/09/15 11:05, Quim Gil wrote: On Sun, Sep 27, 2015 at 12:48 AM, Isarra Yos <zhoris...@gmail.com> wrote: Here's a question. For volunteers or third-party folks less close to core - suppose we do want to come talk about whatever pertains to us. How do we bring these things up? How

[Wikitech-l] Would anyone be interested in a tech talk about how to make a mw skin?

Jack Phoenix and I were considering doing a tech talk about how to make a MediaWiki skin. Would there be any interest in this? What would you folks want to see from such a talk? -I ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org

Re: [Wikitech-l] The "other" developers at the Wikimedia Developer Summit

On 16/09/15 06:11, Quim Gil wrote: The content of the Summit is derived from the proposals submitted discussed well before the Summit. If a developer had topics to discuss before the Summit, they will have topics to discuss during the Summit. However, if a developer didn't have any topic to

Re: [Wikitech-l] Do you run mediawiki on shared hosting? Tell us about it

On 24/09/15 17:46, Daniel Barrett wrote: Brian Wolff writes: I feel like the types of people who use shared hosting are very unlikely to be following this list. I am one of those people. I happily use shared hosting for MediaWiki because (1) it is very cheap and (2) I don't have to maintain

Re: [Wikitech-l] Code of conduct committee

On 21/08/15 14:39, Oliver Keyes wrote: On 21 August 2015 at 06:43, Quim Gil q...@wikimedia.org wrote: Hi, On Fri, Aug 21, 2015 at 11:49 AM, Steinsplitter Wiki steinsplitter-w...@live.com wrote: * I see a lot (maybe 70%) staffer edits there. I also would like to see more edits from

Re: [Wikitech-l] Code of conduct

I'm curious who all 'we' is as well. On 07/08/15 17:29, Steven Walling wrote: On Fri, Aug 7, 2015 at 7:32 AM MZMcBride z...@mzmcbride.com wrote: Matthew Flaschen wrote: We're in the process of developing a code of conduct for technical spaces. This will be binding, and apply to all

Re: [Wikitech-l] Data and Developer Hub protoype

On 07/07/15 08:07, Quim Gil wrote: Sorry for my misunderstanding. Then we agree. Right now the proposal is to improve the API: namespace in mediawiki.org, instead of creating a new Dev: namespace in mediawiki.org. See and join

Re: [Wikitech-l] Data and Developer Hub protoype

On 06/07/15 16:41, Quim Gil wrote: The problem I have with this reasoning is that we are not proposing a different skin for Wikipedia. This has nothing to do with skins. This is making another new site when we already have sites that could serve this purpose, that are already /supposed/ to

Re: [Wikitech-l] Data and Developer Hub protoype

On 26/06/15 21:21, Quim Gil wrote: Note that probably the complementary side of your frustration is the frustration of designers and others trying to improve Wikimedia and its projects, only to find a strong resistance to change almost every time that fresh ideas are proposed. In our case here,

Re: [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org

On 19/03/15 07:00, Daniel Friesen wrote: On 2015-03-18 11:31 PM, Isarra Yos wrote: On 19/03/15 01:42, Danny Horn wrote: Brad: unfortunately, it's really hard to tell very much from a conversation with messages like 3: Post C: reply to Post A. You could do that with the old model, the new model

Re: [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org

On 19/03/15 01:42, Danny Horn wrote: Brad: unfortunately, it's really hard to tell very much from a conversation with messages like 3: Post C: reply to Post A. You could do that with the old model, the new model or the perfect magic Nobel-Prize-winning discussion threading still to be

Re: [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org

On 17/03/15 15:32, Brad Jorsch (Anomie) wrote: On Tue, Mar 17, 2015 at 11:17 AM, Marc A. Pelletier m...@uberbox.org wrote: Indentation is a crappy workaround for when your communication system does not support a sane threading model - it isn't a threading model or a substitute for one. Err,

Re: [Wikitech-l] Tor proxy with blinded tokens

On 10/03/15 16:00, Chris Steipp wrote: On Tue, Mar 10, 2015 at 7:45 AM, Kevin Wayne Williams kwwilli...@kwwilliams.com wrote: Chris Steipp schreef op 2015/03/10 om 7:23: Jacob Applebaum made another remark about editing Wikipedia via tor this morning. Since it's been a couple months since

  1   2   3   >