[Wikitech-l] Don't forgot, only 4 more days to become eligible to vote in Board elections

[K. Peachey]

Hi all,

Just a small reminder for any developers that they only have 4 more
days to become eligible to vote in the 2022 WMF Board of Trustees
election.

Developers can confirm their eligibility by reviewing the below list:

* are Wikimedia server administrators with shell access
* or have made at least one merged commit to any Wikimedia repos on
Gerrit, between 5 January 2022 and 5 July 2022.
* or have made at least one merged commit to any repo in
nonwmf-extensions or nonwmf-skins, between 5 January 2022 and 5 July
2022.
* or have made at least one merged commit to any Wikimedia tool repo
(for example magnustools) between 5 January 2022 and 5 July 2022.
* or have made at least 300 edits before 5 July 2022, and 20 edits
between 5 January 2022 and 5 July 2022, on Translatewiki.
* or maintainers/contributors of any tools, bots, user scripts,
gadgets, and Lua modules on Wikimedia wikis.
* or have substantially engaged in the design and/or review processes
of technical development related to Wikimedia.

This list was copied from
.

If you need help getting a patch(/s) merged in the next few days,
don't hesitate to reach out to the community in the next few days on
the mailing lists, other locations such as the various IRC channels or
phabricator.

Regards,
p858snake/Peachey88
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: Best practices for extensions

[K. Peachey]

On Tue, 1 Feb 2022, 3:00 am Thiemo Kreuz,  wrote:
> … snip …
> * What about CODE_OF_CONDUCT.md? Isn't this required by now?

Historically (aka when the file first got mass added) there were
arguments that ensured about that, From memory the outcome was that
the file is not required but none the less any code in our Gerrit
instance (and gitlab) is automatically covered and there is nil
exclusions to that
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: Upstream shutdowns

[K. Peachey]

There is also one of the search systems migrating to non O/S from memory...
elastic?

On Wed, 2 Jun 2021, 11:11 am Brian Wolff,  wrote:

> Also HHVM and Blazegraph.
>
> --
> Brian
>
> On Tuesday, June 1, 2021, Kunal Mehta  wrote:
>
>> On 5/29/21 5:59 PM, Brian Wolff wrote:
>>
>>> It sounds like phabricator upstream is going away:
>>> https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/
>>> <
>>> https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/
>>> >
>>>
>>
>> On the general topic, it's worrying to me this is the third major
>> platform/software that Wikimedia relies on that is gone, with little
>> notice. OTRS went EOL 2 days before Christmas last year[1] and Freenode
>> well, switched hands and imploded.
>>
>> In all 3 cases though it's been pretty clear beforehand that something
>> was wrong or unsustainable. OTRS didn't release their community edition on
>> time[2], Freenode has had questionable governance for a while now, the
>> "Freenode Limited" company was created in 2017, and Phabricator/Phacility
>> has been maintained by a single person (who's done great work, no doubt) in
>> a way that did not really encourage upstream contributions to build a
>> sustainable community of contributors (my impression, correct me if I'm
>> wrong).
>>
>> And with COVID-19, plenty of IRL businesses/shops/etc. have gone under or
>> just closed down so it's unsurprising that we're seeing the effect in
>> tech/FOSS too.
>>
>> I think it would be a good idea if we can check in on our upstreams[2],
>> have sustainable governance, identifying if they assistance/support, and
>> then figuring out how to provide what's needed.
>>
>> To start with, I think we have a unique opportunity to influence the
>> governance of Libera Chat given they're just starting off and appear to be
>> interested in getting our feedback[3].
>>
>> [1] https://phabricator.wikimedia.org/T275294
>> [2] https://www.mediawiki.org/wiki/Upstream_projects
>> [3]
>> https://meta.wikimedia.org/wiki/Wikimedia_Forum#Libera_Chat_governance
>>
>> -- Legoktm
>> ___
>> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
>> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
>>
>> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>>
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

Re: [Wikitech-l] Technical Decision Making Process Update and Change

[K. Peachey]

Are the Gerrit permission requests that techcom used to handle going to the
new forum or another team?

On Tue, 26 Jan 2021, 12:20 pm Kate Chapman,  wrote:

> Hello all,
>
> I’m pleased to announce that the Technical Decision Making Process[0]
> proposed as an evolution of the Wikimedia Technical Committee[1]
> (TechCom) process has been approved by the Wikimedia Foundation, and
> will begin operation on 22nd of January. Back in October[2] and
> November[3] I sought input into a proposed process and in December I
> incorporated that feedback into the approved process.
>
> This process is designed to be more inclusive by shifting the
> representations. It has clear timelines for when decisions will be
> made and to develop a clear lifecycle of a decision. The process is
> designed to be clear about how and which stakeholders will be engaged.
> It also introduces a Technical Decision Forum and Templates for the
> process.
>
> Currently a group from the Wikimedia Technology and Product
> Departments are in the process of forming the initial Decision Forum.
> The initial forum will include representatives from Wikimedia
> Foundation teams, Wikimedia Deutschland, and independent +2
> contributors. Please see the proposal for community representation on
> the Decision Forum[4] and provide input by 2021-02-15. We know we will
> need to adjust the representation in the forum over time. If you
> believe you are from a group that is not represented and should be,
> please contact us (tech-decision-forum-supp...@wikimedia.org).
>
> If you currently have an RFC in process with TechCom that is not on
> Last Call, it may need to be moved into this process. If you have
> filed an RFC that is no longer relevant please close it. The group
> setting up the process will be inquiring about the RFC status on the
> individual Phabricator tickets.
>
> To get started with this new process you just need to open a
> Phabricator Ticket on the Technical Decision Making Process board[5].
>
> If you need help getting started or have further questions please
> reach out at tech-decision-forum-supp...@wikimedia.org or reply on
> this thread.
>
> [0] https://www.mediawiki.org/wiki/Technical_Decision_Making_Process
> [1] https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee
> [2]
> https://lists.wikimedia.org/pipermail/wikitech-l/2020-October/093968.html
> [3]
> https://lists.wikimedia.org/pipermail/wikitech-l/2020-November/094037.html
> [4]
> https://www.mediawiki.org/wiki/Technical_Decision_Making_Process/Draft_Proposal_Community_Representation
> [5] https://phabricator.wikimedia.org/project/board/5179/
>
> Thanks,
>
> Kate
> --
> Kate Chapman (she/her/hers)
> Director of Architecture, Architecture Team
> Wikimedia Foundation
> kchap...@wikimedia.org
>
> ___
> 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] The future of UploadWizard

[K. Peachey]

That comment may be referring to improving the core uploader so the
extension can be depreciated.

Has UW gone under a code stewardship request?

On Thu, 4 Feb 2021, 8:33 am Strainu,  wrote:

> As the deafening silence of this thread probably shows, a discussion is
> not really possible. The WMF has had 0 interest in making uploads easier in
> the last few years.
>
> To be fair, faced with furios opposition from the Commons community for
> even basic improvements such as allowing imports from other sites except
> Flickr and requests to stop cross-wiki uploads, this decision does not seem
> out of place.
>
> As one of the few people that has enabled UW in another Wikimedia wiki, I
> would like to encourage you to follow on your plan to improve the wizard as
> much as possible. Plans at the WMF change often and not necessarily for the
> better. A responsive design would be awsome news for wikis that need to
> guide their users through the mess that is freedom of panorama.
>
> One thing that puzzles me in that ticket is this phrase from Mark Traceur:
> "It might be better to look at something (slightly) more modern, like the
> upload dialog in core". Does anyone know what that dialog is? AFAIK the
> uploader in core (Special:Upload) hasn't changed in decades, except maybe
> for the look of the buttons. Its usability is rubbish compared to UW. Wikis
> used to (no, actually they still do) customize it using the uselang
> param,which messes with the user's settings. I can't really understand how
> that would be better...
>
> Andrei
>
> Pe duminică, 31 ianuarie 2021, Ostrzyciel Nożyczek <
> ostrzycielnozyc...@gmail.com> a scris:
>
>> Hi,
>>
>> I would like to uhhh... start the discussion? ask for opinions? about the
>> future of UploadWizard.
>>
>> It is a rather special extension, that was from the start made mostly for
>> Commons' very specific needs and getting it to work anywhere else presents
>> some challenges (some of which I attempt to tackle here
>> ). Interestingly, it still is
>> used by many third-party wikis
>>  and although some
>> of them don't need its full set of capabilities related to describing
>> licenses, authors and sources, there are wikis that do need that. The wiki
>> I maintain, Nonsensopedia, has a Commons-like file description system based
>> on Semantic MediaWiki (see example here
>> ) and
>> UploadWizard has been a *blessing* for us, greatly simplifying the task
>> of file moderation.
>>
>> Opinion time: Wikis should be *encouraged* to properly describe the
>> authorship of files that they use, to meet the licensing requirements. IMO
>> Wikimedia Foundation as the maintainer of MediaWiki and a foundation
>> dedicated to dissemination of free culture should provide a usable tool
>> for properly describing free multimedia. UploadWizard could be just that.
>>
>> At the same time, the extension has been basically unmaintained
>>  since the Multimedia
>> team was dissolved and I've been rather surprised to discover that patches
>> improving third-party support were met with uhm... very limited
>> enthusiasm?  There
>> are a few obvious features lacking like mobile support (seriously, try
>> opening https://commons.wikimedia.org/wiki/Special:UploadWizard on a
>> narrow screen device, it's been like this since.. always) and
>> configurability (you have to jump through some serious hoops
>>  to just add a
>> license; customizing the tutorial is similarly hard).
>>
>> I've been thinking of what to do with the above and I really wouldn't
>> want to embark on something that will be rendered redundant or obsolete in
>> a year, so my question is: are there any plans for UploadWizard? What makes
>> me suspect that things may change is primarily Structured Data on Wikimedia
>> Commons, which in the future will maybe (?) supersede the description
>> system around the {{Information}} template. Are there any rough roadmaps or
>> outlines of anything resembling a plan for that? If Commons was to
>> implement full, structured file descriptions in the upload tool, that code
>> would be probably hardly usable outside Commons, given that Wikibase is not
>> something easy to install or maintain, it is also awfully overkill for the
>> vast majority of applications. In such a situation, would it make sense to
>> consider completely separating the "Wikimedia Commons Shiny Upload Tool"
>> from a more general extension that would be usable for third
>> parties, stripped of any Commons-specific code? A lot of things could be
>> much simplified if the extension was to target just the needs of third
>> parties and not Commons.
>>
>> I ask about this because I really don't see any sort of interest of the
>> 

Re: [Wikitech-l] List related to repositories which haven't mediawiki/mediawiki-codesniffer

[K. Peachey]

Perhaps it would be best to create a task for this request.


On Fri, 6 Mar 2020, 4:46 pm Zoran Dori,  wrote:

> Hello,
> can someone to update list https://phabricator.wikimedia.org/P10500 which
> contains repositories which haven't mediawiki/mediawiki-codesniffer.
>
> I found in list that much repositories are empty, and repositories which
> aren't available on Gerrit.
>
> So, can someone please update this list of repositories (in
> mediawiki/extensions) which haven't mediawiki/mediawiki-codesniffer, but at
> least, contains one PHP file. or to provide me command with which I can
> update list when I want, so I don't need to request it every time.
>
> Best regards,
> Zoran.
>
> P. S.: Happy weekend! :)
> ___
> 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] Phabricator Login Error

[K. Peachey]

It's been used on and off as required for the past few years.

On Thu, 4 Apr 2019 at 18:55, RhinosF1 Wikipedia  wrote:
>
> Do we know when it was implemented and why? Is it part of the response to 
> earlier security issues?
>
> On Thu, 4 Apr 2019 at 09:51, K. Peachey  wrote:
>>
>> It's a anti-spam measure, One of the Phab administrators will approve
>> when available.
>>
>> On Thu, 4 Apr 2019 at 18:28, RhinosF1 Wikipedia  wrote:
>> >
>> > Hi all,
>> > Is there any reason Phabricator accounts would be marked not approved?
>> > I've not noticed this happening before but there's been a report on IRC
>> > (see
>> > https://wm-bot.wmflabs.org/logs/%23wikimedia-tech/20190404.txt) by
>> > https://phabricator.wikimedia.org/p/Dusti/ saying they are getting the
>> > error:  'Your account has been created, but needs to be approved by an
>> > administrator. You'll receive an email once your account is approved.' (see
>> > https://snag.gy/InXbLz.jpg)
>> >
>> >
>> > Can someone approve and clarify what's happened?
>> > ___
>> > 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] Phabricator Login Error

[K. Peachey]

It's a anti-spam measure, One of the Phab administrators will approve
when available.

On Thu, 4 Apr 2019 at 18:28, RhinosF1 Wikipedia  wrote:
>
> Hi all,
> Is there any reason Phabricator accounts would be marked not approved?
> I've not noticed this happening before but there's been a report on IRC
> (see
> https://wm-bot.wmflabs.org/logs/%23wikimedia-tech/20190404.txt) by
> https://phabricator.wikimedia.org/p/Dusti/ saying they are getting the
> error:  'Your account has been created, but needs to be approved by an
> administrator. You'll receive an email once your account is approved.' (see
> https://snag.gy/InXbLz.jpg)
>
>
> Can someone approve and clarify what's happened?
> ___
> 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] wgEmergencyContact - n...@wikipedia.org

[K. Peachey]

Its not long used, see the documentation at
https://www.mediawiki.org/wiki/Manual:$wgEmergencyContact

On 30 May 2018 at 06:41, Martin Urbanec  wrote:
> Hello,
>
> is it intended to have *n...@wikipedia.org * in
> wgEmergencyContact in CommonSettings.php?
>
> Martin
> ___
> 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] Refactoring MonoBook

[K. Peachey]

On 18 March 2018 at 10:56, Isarra Yos  wrote:
>
> There are also some problems that need addressing down the road: that I'm
> not sure how safe it is for caching and the like to just go moving
> images/css files around willy-nilly, that there are no 'standard' skin
> practices as far as anyone can tell, and that some people seem to think
> MonoBook is bad and not worth this. But MonoBook is not bad. It is a
> delightful skin. We should preserve it, and not just in formaldehyde.

Just make it MonoBookV5? *runs*, or more realistically V2 then
progressively get rid of the orginal MonoBook?

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] MediaWiki Stakeholders' meta-repository of extensions not in gerrit

[K. Peachey]

https://www.mediawiki.org/wiki/Category:Extensions_in_GitHub_version_control
https://www.mediawiki.org/wiki/Category:Extensions_in_Google_Code_version_control
https://www.mediawiki.org/wiki/Category:Extensions_in_SourceForge_version_control

On 24 December 2017 at 09:05, Mark A. Hershberger  wrote:
>
> This afternoon, while procrastinating by cleaning up my clone of
> gerrit's mediawiki extensions repository, I decided to make a meta
> repository for some non-WMF-hosted extensions.  (Hopefully this will
> mean less need to clean up the clone in the future.)
>
> I got some low-hanging fruit to start it off, but I'm hoping I can get
> some pull requests to add more repositories.
>
> Check it out: https://github.com/MWStake/nonwmf-extensions
>
> Thanks,
>
> Mark.
>
> ___
> 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] Discussion on adding a CODE_OF_CONDUCT file to all Wikimedia repos

[K. Peachey]

On 10 June 2017 at 08:52, Gergő Tisza  wrote:
>
>  … snip …
>
> We started adding a CODE_OF_CONDUCT file with a link to all repos (this is
> a new convention for declaring what a project's code of conduct is,
> promoted by Github)

 No, CODE_OF_CONDUCT.md was added, which is a completely different
file in our universe as our standard is extension-less files for these
types of things, The only exemption that jumps to mind in core is
Readme.mediawiki which renders in github.

 How is this a new convention? This is a GitHub only format for what I
have seen and I have not seen any other service implement such a
standard (or discussions towards this) which displays a link in their
interface, which we don't even use (or encourage) for development?

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Open source JPG algorithm that reduces file size by 35%

[K. Peachey]

https://phabricator.wikimedia.org/T160834

On 19 March 2017 at 05:30, Pine W  wrote:
> Perhaps of interest to Mobile and Performance folks:
>
> https://research.googleblog.com/2017/03/announcing-guetzli-new-open-source-jpeg.html
>
> 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] Changes in colors of user interface

[K. Peachey]

Hi Pine,

Any chance to provide information or examples of these documents that
would need to be replaced if/when colours are changed?

To my knowledge, There is no where in MediaWiki core that relies on
colour only to convey information to the clients/end users. The colour
is used to enhance and/or supplement the information provided.

I know from personal experience, I have many times used documentation
where colouring and/or other user experience elements (examples:
icons, system dialog environments) have changed weather it's from
in-application/services changes and redesigns or from external changes
such as system user interface provided mechanisms without major
impacts to the documentation that i've used.

On 14 December 2016 at 18:39, Pine W  wrote:
> I have delayed responding to this thread until I felt that I could do
> with some degree of calmness.
>
> I view UI changes that affect millions of pages as a big deal. I
> realize that from a developer's perspective it may seem trivial to
> change a color setting. Let me try to illustrate a different
> perspective that might help to explain how seemingly small changes,
> when implemented at large scale, can have significant effects. I am
> going to ask for the collective patience of the people in this thread
> as I explain a perspective that appears to be different from a number
> of theirs.
>
> Marketers spend significant amounts of time and money designing their
> sales pitches to the public. One of the many elements considered in
> these communications is the use of color. WMF Fundraising appears to
> be very aware of this, as Fundraising tries different color variations
> in their banners and in-line marketing. I believe that in either the
> 2012 or 2013 fundraising campaign, I heard Sue say that Fundraising
> had found that year that displaying the banner message with a green
> background resulted in a significant increase in revenue for that
> year's fundraising campaign. Marketers make use of color on a regular
> basis in their research and communications to the public, and as WMF
> Fundraising seems to have experienced, these changes can lead to
> important changes in consumer (or donor) behavior. My guess is that
> the folks in WMF who work on user retention and usability studies also
> are mindful of small changes that could be made to the UI that could
> lead to important changes in user behavior.
>
> So, I believe that small UI changes that will be applied to millions
> of pages are not trivial matters, even if the changes are easy for a
> technical staffer or volunteer to implement.
>
> With that as my starting point, let me proceed further into describing
> four difficulties that surprise UI changes present, particularly when
> done on large scales. In the examples below I am speaking about UI
> changes in general, not only the particular case of color changes.
> (Perhaps splitting this more general discussion into a separate thread
> would be appropriate, and if someone wants to do that I think that
> would be OK.)
>
> * As described above, there may be important changes in reader or user
> behavior. (I realize that WMF lacks Google's financial and human
> resources for extensive testing, but this still should be kept in mind
> when considering UI changes. As mentioned above, WMF Fundraising seems
> to be aware of this, and I imagine that WMF staff in other departments
> are as well.)
>
> * Documentation may need to change in a large number of places, many
> of which are maintained with volunteer labor, and until those changes
> are made users may receive incorrect information that leads to adverse
> effects.
>
> * As I mentioned previously, designers and maintainers of templates
> may need to update them to sync with the changes to the UI, and I
> imagine that these people would appreciate advance notice instead of
> being surprised with a change.
>
> * Those of us who are trying to future-proof our work to the extent
> possible are put in a difficult position. In my case, WMF is paying me
> grant funds to develop instructional videos about Wikimedia. I think
> that everyone involved in the project understands that changes will
> happen and that the videos will need to be updated at some point in
> the future; the way we are designing the project is intended to make
> it relatively easy to make changes and do translation work. However,
> we are trying to design the videos such that they are very well
> aligned with the state of the UI that Wikimedia users will encounter
> when the videos are launched and for at least the next several months
> thereafter. If we spend thousands of dollars producing video and then
> there is a surprise UI change that makes all of our work out of date,
> perhaps even before the videos are fully published, this puts us in a
> difficult (and potentially expensive) situation that would have been
> avoided if we had known about the upcoming changes. Importantly, a
> significant UI change 

Re: [Wikitech-l] Changes in colors of user interface

[K. Peachey]

On 10 December 2016 at 19:07, Gergo Tisza  wrote:
> For reference, these are the changes being discussed:
> https://phabricator.wikimedia.org/F5022813

Is there any reason this is being discussed on a File compared to a task?
Is there any reason security has been changed on this file? (It's not
a security or a internal staff matter etc)

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Recently proposed patchsets by new contributors awaiting code review

[K. Peachey]

On 12 October 2016 at 23:21, Andre Klapper  wrote:
> == pywikibot/core: ==
>
> since 2016-09-25 (2nd time listed here):
> Checks the type of isbn and modifies accordingly
> https://gerrit.wikimedia.org/r/#/c/312726/

Might be better to send that one to the pywiki mailing lists.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Small old unreviewed MediaWiki Core patches waiting in Gerrit

[K. Peachey]

On 12 October 2016 at 23:29, Andre Klapper  wrote:
> https://gerrit.wikimedia.org/r/#/c/211034/
> Move up devunt's name to Developers
>   /CREDITS

I think we have combined both those lists into one and just have
CREDITs now sorted alphabetically.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] How to find a repository?

[K. Peachey]

"nasty bug" abd "useful" are very subject views.

Perhaps be more considerate to everyone views on this mailing list nemo?

On 26 July 2016 at 16:52, Federico Leva (Nemo)  wrote:
> To make the links to projects useful, one needs to visit every single
> project's "manage > configure menu"
> https://phabricator.wikimedia.org/project/291/panel/configure/ and click
> "make default" next to "project details" (known nasty bug
> https://phabricator.wikimedia.org/T89865 ).
>
> 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] MediaWiki pingback

[K. Peachey]

On 22 July 2016 at 10:29, Ori Livneh  wrote:
> Starting with version 1.28, MediaWiki will provide operators with the
> option of sharing anonymous data about the local MediaWiki instance and its
> environment with MediaWiki's developer community via a pingback to a URL
> endpoint on MediaWiki.org.
>
> The configuration variable that controls this behavior ($wgPingback) will
> default to false (that is: don't share data). The web installer will
> display a checkbox for toggling this feature on and off, and it will be
> checked by default (that is: *do* share data). This ensures (I hope) that
> no one feels surprised or violated.

If it's disabled by default, isn't our standard practice not to
pre-tick the option?

> The information that gets sent is described in <
> https://meta.wikimedia.org/wiki/Schema:MediaWikiPingback>. Here is a
> summary of what we send:
>
> - A randomly-generated unique ID for the wiki.

How is it randomly-generated? Is a true-random or a hash based on
provided info? Is there anything to prevent duplication?

> …
> - The chosen database backend (e.g., "mysql", "sqlite")
> - The version of MediaWiki in use
> - The version of PHP
> - The name of the web server software in use (e.g. "Apache/1.3.14")
>
> Neither the wiki name nor its location is shared.

If a organisation creates custom packages (with custom naming), this
could conceivably reveal information if they accidentally trigger this
option


> The plan is to make this data freely available to all MediaWiki developers.
> Before that can happen, I will need to solicit reviews from security folks
> and from the WMF's legal team, but I don't expect any major issues.


Has a draft of the Data Retention Guidelines and Data Access
Guidelines that you are planning to send to Legal been created/shared
yet?

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] git.wikimedia.org (Gitblit) going away on June 29th, redirected to Phabricator

[K. Peachey]

On 22 June 2016 at 07:16, Greg Grossmeier  wrote:
> One known issue to call out: Diffusion does not list commits by person.
> However Differential (the code-review tool) does this (not just for new
> commits). There is no easy/maintainable way to redirect those,
> unfortunately.

Is this being tracked anywhere? This used to work… Searches such as
(linked from the users profile)

have worked for me previously

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Which Phabricator project for site issues?

[K. Peachey]

What type of site issue is it?

You can always file in Wikimedia-General-or-Unknown and other users
will help with the correct tagging.

On 27 May 2016 at 18:57, Strainu  wrote:
> Hi,
>
> Is Wikimedia-Site-requests the correct project to log issues with a
> specific Wiki? If not, which is it?
>
> Thanks,
>   Strainu
> ___
> 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] FW: File with an unknown copyright status on MediaWiki.org

[K. Peachey]

I've created a redirect to our template for that

On 26 May 2016 at 19:21, Joaquin Oltra Hernandez
 wrote:
> I'm trying to fix the ones I've uploaded, but the {{Mediawiki screenshot}}
> template is not in mediawiki.org.
>
> Is just adding a license like {{cc-by-sa-4.0}} enough?
>
> On Wed, May 25, 2016 at 2:53 PM, Ricordisamoa 
> wrote:
>
>> Why not move them to Commons after review?
>> They'd benefit from all the goods, not only Information template but also
>> categories etc.
>>
>>
>> Il 25/05/2016 14:39, Steinsplitter Wiki ha scritto:
>>
>>> There are hundreds of files in
>>> https://www.mediawiki.org/wiki/Category:Files_with_unknown_copyright_status
>>>
>>> Likely they schould be nominated after one week or moor automatically for
>>> deletion (using parser function).  Then a human can review it and press
>>> delete.
>>>
>>> Likely Template:Information schould be preloaded at Special:Upload
>>> (similar to commons), so we would also have machine readable data for files.
>>>
>>>
>>> Best,
>>> --Steinspliter
>>>
>>> From: p858sn...@gmail.com
 Date: Wed, 25 May 2016 21:11:13 +1000
 To: wikitech-l@lists.wikimedia.org
 Subject: Re: [Wikitech-l] FW: File with an unknown copyright status on
 MediaWiki.org

 On 25 May 2016 at 20:40, Ricordisamoa 
 wrote:

> , while on mediawiki.org no one cares.
>
 That's not true, It's a project I plan to work on shortly (just need
 to finish a few other things first).

 And it's not a simple case of just hitting delete on everything.

 ___
 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 mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] FW: File with an unknown copyright status on MediaWiki.org

[K. Peachey]

On 25 May 2016 at 20:40, Ricordisamoa  wrote:
> , while on mediawiki.org no one cares.

That's not true, It's a project I plan to work on shortly (just need
to finish a few other things first).

And it's not a simple case of just hitting delete on everything.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Hey guys how ı can leave this e-mail list?

[K. Peachey]

On 25 April 2016 at 22:01, Muhammed Tatlısu 
wrote:

> Muhammed Tatlısu
> 34080/İstanbul-Türkiye
>

https://lists.wikimedia.org/mailman/listinfo/wikitech-l#manage and follow
the form details.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] My username

[K. Peachey]

On 24 April 2016 at 15:37, Muhammed Tatlısu 
wrote:

> Hı, I requested to change the user name (Kingbjelica to Müdür)
> Now I want to cancel it.
>
> Where?
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Fwd: Deploy freeze(s) in effect for the next 7 weeks (ish, read for more details)

[K. Peachey]

On Thursday, November 26, 2015, Brian Wolff  wrote:

> >> FTR: "High Priority" means security and data loss, really. There may be
> >> other exceptions but they need pre-approval from at least myself and
> >> sometimes Katie.
>
> Thanks for keeping us informed. I'm excited to hear that Katie will be
> "running Wikimedia" over the holiday season.
>
> --
> -bawolff
>

*smirk*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Audit of inline styling in the main namespace of the English Wikipedia

[K. Peachey]

Is this direct usage of the styling, or does it include styling introduced
by templates as well?

On Monday, October 26, 2015, MZMcBride  wrote:

> Hi.
>
> I was curious about the prevalence and types of inline styling (or more
> specifically, inline CSS) in articles on the English Wikipedia.
>
> The relevant task is here: .
> The results are here: .
>
> The following are the top ten instances of inline styling from main
> namespace pages on the English Wikipedia, as of about 2015-10-02:
>
> 1552197  text-align: center;
>  499756   text-align: left;
>  355952   background: #dfffdf;
>  235222   background: #cfcfff;
>  215038   background: #efcfff;
>  210702   text-align: right;
>  143095   display: none;
> 93646background: #efefef;
> 86391font-size: 90%;
> 80420background: #fff;
>
> My hope is that a better understanding of the uses of inline styling will
> allow us to reduce the overall amount of it in smart ways. Semantic CSS
> classes and per-page or per-template CSS files might be part of this.
>
> MZMcBride
>
>
>
> ___
> 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 feature: tool edit

[K. Peachey]

What if it a bot builder builds one?

On 22 February 2015 at 10:35, Ricordisamoa ricordisa...@openmailbox.org
wrote:

 What if a techie vandal builds a one-click disruption framework?

 Il 15/02/2015 10:54, Petr Bena ha scritto:

  I think it's pretty clear what I am proposing here :P there is a real
 problem and this is a real solution. Regarding vandals would have fun
 with that I think you are over estimating them, most of them are
 barely able to use regular web based interface for anything more
 clever than removing half of article, they don't even understand wiki
 code so far to understand API interface.

 On other hand if there was a privilege for this, each wiki could
 restrict it as they wanted. This is not a bot flag any more than this
 wikidata flag we have is. It's just another flag. That's all.

 On Sat, Feb 14, 2015 at 10:48 PM, Brian Wolff bawo...@gmail.com wrote:

 -- Every registered user would be able to flag edit as tool edit (bot
 needs special user group)

 Vandals would have fun with that, but bot group could be set up like that
 (e.g. flood group)

  -- The flag wouldn't be intended for use by robots, but regular users
 who used some automated tool in order to make the edit

 Semantics of flags are up to wiki communities. They can make it mean
 whatever they desire.

  -- Users could optionally mark any edit as tool edit through API only

 So like the bot flag (if they have the rights) :p

  other suggestion that was somewhere else in thread about retroactively

 matking rdits

 Sounds kind of like the little known bot rollback feature minus the
 rollback aspect.

 --
 This sounds either like you are proposing the bot flag, with a minor
 varation in the user given semantics. Or are proposing multiple levels of
 bot flaggedness so that tool edits could be independently hidden in rc
 separate from tool edits.

 --bawolff
 ___
 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

Re: [Wikitech-l] Extensions licensing

[K. Peachey]

On 8 February 2015 at 19:32, Federico Leva (Nemo) nemow...@gmail.com
wrote:

 Thanks! This is a nice cleanup. https://www.mediawiki.org/
 wiki/Category:Extensions_with_unknown_license has 1379 pages now, is your
 bot going to continue working there?


 That category is a bit dodgy, It's based on a very limited set of switches
in the Extension Infobox.  When I first started working on it, there was ~6
pages in the category and I was cleaning up the pages (did about just under
half) to use a standard based output using Template:EL (Wasn't aware about
SPDX when i searched), with the goal of removing that category magic out of
the infobox directly for the unknown cat then work on the other categories
to clean up their usage as well.

Clearly I never got finished. Good luck to who ever works on it.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Stance on Social Media

[K. Peachey]

Assuming that we even use icons! I think a text drop down box which lists
the various networks that one could share onto would work just as well.

On 12 January 2015 at 15:35, MZMcBride z...@mzmcbride.com wrote:

 Tim Starling wrote:
 Yes, there's a risk we could end up with an alphabetical list of
 hundreds of social networks to share an article on, like
 Special:Booksources. Better than nothing, I guess.

 You guess wrong. As quiddity points out, we don't want
 https://i.imgur.com/XGJHLvW.png or equivalent on our sites. Such a mess
 of icons is ugly and tacky and awful. It would be worse than nothing.

 Adding social media icons is a lot of pain for very little gain, in my
 opinion. People who want to tweet about an article or post about a page on
 Facebook can (and do!) copy and paste the URL. What problem are we trying
 to solve here? If the answer is that we want to make it painless to submit
 noise into the ether and our users are only capable of clicking a colorful
 icon and using a pre-filled tweet or Facebook post or e-mail body, we
 probably need to re-evaluate what we're trying to accomplish and why.

 MZMcBride



 ___
 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] Phabricator outage due to network issues, 11/29

[K. Peachey]

ASAP? when it's already hitting approx. five hours of down time?

On 30 November 2014 at 18:14, Erik Moeller e...@wikimedia.org wrote:

 As noted in the server admin log [1], Phabricator is currently down due to
 a network outage impacting one of our racks in the Ashburn data-center.
 We're investigating and will aim to restore service ASAP.

 Erik

 [1] https://wikitech.wikimedia.org/wiki/Server_Admin_Log

 --
 Erik Möller
 VP of Product  Strategy, Wikimedia Foundation
 ___
 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] {{TemplatesThatWorkOnMobile}}

[K. Peachey]

Perhaps someone could trail making a gadget that will display the template
loaded into the m.* mobile experience so its's easier for users to have a
look as a starting point?

On 9 October 2014 14:09, MZMcBride z...@mzmcbride.com wrote:

 Helder wrote:
 This is why we have proposals like
 https://meta.wikimedia.org/wiki/GlobalTemplates
 https://meta.wikimedia.org/wiki/Global-Wiki

 Yes, a million times this. We must figure out a way to centralize
 templates so that maintenance is easier. The current system of per-project
 wiki templates really strains under scale as many wikis have few active
 editors and most of them are not technical.

 Regarding inline styling specifically, I feel like we had this exact
 conversation a year ago on Bugzilla or wikitech-l. As I recall, the gist
 of the previous discussion was that we need to better educate users
 about what good practice is, perhaps provide testing better tools (make it
 easier to see how it looks on mobile, as Brion suggests), and then slowly
 try to deprecate inline styling over the next few years.

 I'm curious to see where the Allow styling in templates request for
 comments goes (cf. https://www.mediawiki.org/w/index.php?curid=130320),
 particularly with regard to the goal of atomizing content, which I think
 the Parsoid and VisualEditor (Editing!) teams seem to want. While I
 probably generally agree with trying to kill inline styling, it does have
 seem to have a convenient advantage of being more easily encapsulated.

 Related: https://bugzilla.wikimedia.org/show_bug.cgi?id=35704

 MZMcBride



 ___
 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] RFC meeting this week

[K. Peachey]

Tim was probably thinking of AEDT

On 9 October 2014 06:14, Roan Kattouw rkatt...@wikimedia.org wrote:

 On Tue, Oct 7, 2014 at 4:08 AM, Tim Starling tstarl...@wikimedia.org
 wrote:
  * Australia AEST: Thursday 07:00
 
 Ironically, Tim miscalculated the time in his own timezone :D it's 08:00
 AEST.

 Roan

 ___
 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] {{TemplatesThatWorkOnMobile}}

[K. Peachey]

Templates aren't protected by default =).

If they are protected there is generally a good reason such as heavy usage,
you can always put a comment on the talk page and tag it with
{{EditProtected}} which will summon someone with sysop rights.

You can also setup a /Sandbox page with the proposed changes so the person
that makes the changes can see the differences and make sure it works.

On 8 October 2014 10:48, Jon Robson jdlrob...@gmail.com wrote:

  The wiki way is not to ask and wait for someone else to act, but to act
  directly in good faith and communicate what you did and why so that if
  there is disagreement it can be resolved afterwards.

 Sadly I only have template edit rights on my staff account and I
 really don't like using that account. In addition to this there are
 hundreds of copies of the template I fix so this becomes a nightmare.

 ___
 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] IRC bots for phab

[K. Peachey]

On 29 September 2014 02:08, Jeremy Baron jer...@tuxmachine.com wrote:

 [[You spend way too much time (and other people's time too) on exaggerating
 or rehashing issues beyond their true proportions. You already knew that
 new user registration at that instance was disabled before the start of
 this thread, right? (granted it shouldn't be giving a 503 and maybe we
 should look into that but in any case you should have known login would not
 work]]


I have no idea where that is coming from, specifically since there was no
mention of creating accounts and the Login page clearly mentions using LDAP
credentials to log in.

Perhaps you need to be a bit more civil and less bitey, After all you did
link to the relevant discussion about it on Phab, it's not hard to expect
people to want to log-in and be involved...
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Help in modifying Template:Extension to support user ratings

[K. Peachey]

Probably the original IRC discussions.


On 19 August 2014 17:22, Merlijn van Deen valhall...@arctus.nl wrote:

 On 19 August 2014 07:36, K. Peachey p858sn...@gmail.com wrote:

  Personally I don't think in it's current state/design it is overly
 suitable
  for deployment onto MediaWiki wiki as it will introduce a external factor
  on the page load for each visitor, although I haven't looked at the
 current
  privacy policy but it is generally considered a no-no for us.
 

 What do you base that on? As far as I can see, there's just a bot that
 adds/updates the rating to the extension template:


 https://www.mediawiki.org/w/index.php?title=Extension:ConfirmEditdiff=prevoldid=1099093

 And that's also explicitly stated in the GSoC proposal:
 During this period I will work on the Data Syndication phase of the
 project.

 * For this, I will be extending the existing WikiApiary bot, creating new
 asynchronous worker tasks.
 ___
 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] Help in modifying Template:Extension to support user ratings

[K. Peachey]

I was meaning to comment on the overall GSoC proposal before the acceptance
stage and didn't get a chance.

Personally I don't think in it's current state/design it is overly suitable
for deployment onto MediaWiki wiki as it will introduce a external factor
on the page load for each visitor, although I haven't looked at the current
privacy policy but it is generally considered a no-no for us.

Also I do have concerns about the overall usefullness of the data and how
it will correlate with the extensions, especially when it comes to matching
to individual release versions and overall participation on data submission.



 On Mon, Aug 18, 2014 at 10:05 PM, Brad Jorsch (Anomie) 
 bjor...@wikimedia.org wrote:

  On Mon, Aug 18, 2014 at 12:08 PM, Mark A. Hershberger m...@nichework.com
 
  wrote:
 
   Legoktm legoktm.wikipe...@gmail.com writes:
  
On 8/18/14, 8:47 AM, Chad wrote:
On Mon, Aug 18, 2014 at 4:54 PM, Brad Jorsch (Anomie) 
   bjor...@wikimedia.org
Has it already been asked anywhere *whether* to make these ratings
available on mediawiki.org?
  
   Yes.  This is a GSoC project that was accepted.  Getting the ratings to
   mw.o is the final step of that.
  
   https://www.mediawiki.org/wiki/User:Adi.iiita/Gsoc2014
  
 
  I see no discussion there.
 
 
  --
  Brad Jorsch (Anomie)
  Software Engineer
  Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Dropping unused repos (was: Extension unit tests!)

[K. Peachey]

What issues are they causing by being there?

On Tuesday, August 12, 2014, addshorew...@gmail.com wrote:

 That is one thing we should take into account when clearing them out.
 We should look at the date of last commit or the date of creation and if
 they were in the last 6 months of so possibly leave them there.
 And naturally take a backup of the deleted repos and shove it somewhere?

 Addshore


 On 11 August 2014 14:05, Pavel Astakhov pastak...@yandex.ru
 javascript:; wrote:

  Please do not drop the PhpTagsCodeEditor, PhpTagsDebugger and PhpTags
  Widgets extensions.
  I'm going to do them.
 
 
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org javascript:;
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 



 --
 Addshore
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org javascript:;
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Sent from Gmail Mobile on my iPod.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Superprotect user right, Comming to a wiki near you

[K. Peachey]

Lets all welcome the new overlord Erik.

Add a new protection level called superprotect
Assigned to nobody by default. Requested by Erik Möller for the purposes
of protecting pages such that sysop permissions are not sufficient to


edit them.
Change-Id: Idfa211257dbacc7623d42393257de1525ff01e9e
https://gerrit.wikimedia.org/r/#q,Idfa211257dbacc7623d42393257de1525ff01e9e,n,z

https://gerrit.wikimedia.org/r/#/c/153302/



Someone clearly can't take criticism of their projects well.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Spam filter rules on the Wiki Loves Monuments Mailing list not working

[K. Peachey]

Can you please file the bug in our bugzilla installation? 
bugzilla.wikimedia.org under Wikimedia - Mailing Lists.


On 1 August 2014 08:39, Cristian Consonni kikkocrist...@gmail.com wrote:

 Hi all,

 (not really sure this is the right place, please redirect me if needed)

 Togheter with Effeietsanders I am administering the
 wikilovesmonuments-l mailing list[0].
 This list is receiveing huge amounts of spam messages (quick
 stat: we are talking about 20 messages per hour).

 We have tried to implement some spam filter rules following this[1] (a
 page which I have edited myself) but basically we were unable to get
 any effect of sorts.

 Here's the two spam filtering rules I have created:
 * Rule 1: X-Spam-Score: [+]{2,99}
 * Rule 2: X-Spam-Score: [*]{2,99}

 I have added both rules with + and * to be sure, and I have
 specified the numbers (more or equal than 2 and less or equal than 99)
 because in my first try the rule with just {2,} (i.e. more or equal
 than 2) was not working.

 The fact is that the solution didn't work out in the end (we were
 still holding in our moderation queue lots and lots of messages with
 an high spam score) and so we are
 changing the default policy for the list about non-member messages
 from Hold to Reject (If somebody can make a case for Discard
 over Reject please do so).

 This was quite frustrating, but we were unable to fix the problem is
 some other way. I am sharing this to make sure I wasn't making some
 sort of stupid mistake in the rules. I would also like to have an
 opinion about Reject vs Discard as a policy for non-members
 messages.

 Thank you.

 Cristian

 [0] https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments
 [1]
 https://wikitech.wikimedia.org/wiki/Mailing_lists#Fighting_spam_in_mailman

 ___
 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] User agent policy for bots

[K. Peachey]

It's designed so if there if there is a issue with the bot (eg: it's
malfunctioning etc) and causes issues the person whom is in control can
easily be identified.

As such, The user-agent you chose should reflect that.


On 11 July 2014 09:09, Amir Ladsgroup ladsgr...@gmail.com wrote:

 Hello,
 As discussions in pywikipedia-l people are not sure whether is necessary to
 add username of bot operator in user agent or not.

 In user agent policy https://meta.wikimedia.org/wiki/User-agent_policy
 it's mentioned that people need to add contacting information, but it's not
 clear it's about contacting the tool-maker or tool-user.

 Can you clarify it?
 Best
 --
 Amir
 ___
 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 tabs for images

[K. Peachey]

It is still accessible, It's just a utter pain to get to.


On 4 June 2014 20:35, Petr Kadlec petr.kad...@gmail.com wrote:

 On Sun, Jun 1, 2014 at 1:17 PM, bawolff bawolff...@gmail.com wrote:

  On Jun 1, 2014 5:12 AM, ENWP Pine deyntest...@hotmail.com wrote:
  
   So here I am working late night / early morning trying to get the
  Signpost published, and I see something new at the top of image pages on
  English Wikipedia such as
 https://en.wikipedia.org/wiki/File:Wikidata.png
  
   We now have View on Wikimedia Commons and Add local description
 tabs.
  Cool!
 
  I agree. Thank you This,_that_and_the_other for making that feature
 happen.
 

 Except that now (with Media Viewer deployed), the local file description
 page is no longer accessible, so this new feature is practically useless.

 -- [[cs:User:Mormegil | Petr Kadlec]]
 ___
 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] Bot flags and human-made edits

[K. Peachey]

Because humans use it these days, not boys generally in the web interface
and it would just make stuff harder for people that use it…

On Tuesday, May 20, 2014, John Mark Vandenberg jay...@gmail.com wrote:

 On May 20, 2014 8:39 AM, Dan Garry dga...@wikimedia.org javascript:;
 wrote:
 
  On 19 May 2014 19:36, Amir Ladsgroup ladsgr...@gmail.com javascript:;
 wrote:
 
   As a bot operator I think API parameter about flagging bot or not is
   necessary
  
 
  Sure, but as I'm not a bot operator, can you explain why and what you use
  this for, to help me understand? :-)
 
 
   Implementing the parameter (whether the current status quo or my
   suggestion) in UI is important, I think adding a mark box besides minor
 and
   watch options would be great (for bots, admins and flooders)
  
 
  I think so too. Display it only to people with the bot flag, and their
  edits will be tagged as bot edits iff they check the box. The API would
 be
  unaffected, and continue to function as it did before.
 
  As a product manager I am wary of adding more clutter into the already
 busy
  edit interface, but given the scope of the feature (i.e. it only displays
  to people flagged as bots), I think it'd be okay.

 If it is role based ('bot'), why not change it (in 1.24?) to always *not*
 flag the UI edits as bot edits, displaying a warning to that effect?

 Do we have many UI scaping bot frameworks in use these days?

 --
 John
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org javascript:;
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Sent from Gmail Mobile on my iPod.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Reducing botspam on #wikimedia-dev

[K. Peachey]

tbh -dev (or somewhere else) should be the master channel for bz output.


On 19 May 2014 00:36, Yuvi Panda yuvipa...@gmail.com wrote:

 Hello everyone!

 I just merged a change into the new wikibugs that will help reduce
 botspam on #wikimedia-dev. wikibugs will no longer report bugs on
 #wikimedia-dev that have been reported in other channels, thus
 reducing duplication. The previous behavior was that wikibugs will
 ping multiple channels - mobile bugs went to both #wikimedia-mobile
 and #wikimedia-dev, flow bugs to both #wikimedia-corefeatures and
 #wikimedia-dev, etc. Now they only go to the primary channel and
 bypass -dev. So mobile bugs will only go to #wikimedia-mobile, and not
 to #wikimedia-dev. This also matches the behavior of grrrit-wm.

 #mediawiki-feed still gets the full firehose of all changes, if you
 are interested in that.

 Thanks!

 --
 Yuvi Panda T
 http://yuvi.in/blog

 ___
 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] Change the installer to make Project: the default option for meta namespace name

[K. Peachey]

On 4 May 2014 05:38, Nathan Larson nathanlarson3...@gmail.com wrote:

 4) We don't have any other namespace names (User, Template, etc.) that are,
 by default, different from one wiki to the next; what is the logic for
 making an exception for the meta namespace?


Because the Template/User namespaces aren't the same thing as the project
namespace?
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Proposed body font stack for Latin

[K. Peachey]

On 12 April 2014 05:49, Steven Walling steven.wall...@gmail.com wrote:

   I'd like to test this locally on the English Wikipedia, and I am quit
  confident this makes everyone happy because 1) every OS should end up
 using
  a native font, and 2) it promotes a free font at the beginning of the
  stack (not a high priority in my book though).


 Why don't we test this on Beta Labs and Mediawiki.org first instead of
 using
 enwiki as a guinea pig? We can make you a sysop there.


MW wiki is a content wiki first and foremost, not a test bed wiki, First
level testing should take place elsewhere.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Mobile Operator IP Drift

[K. Peachey]

On 11 April 2014 05:53, Adam Baso ab...@wikimedia.org wrote:

 Your feedback is welcome here on wikitech-l. Next week we'd like to move
 the discussion to the wikimediaannounce-l mailing list, but we wanted to
 first cover it on this main developer list.


Announce-l isn't a discussion list, it forwards everything to wikimedia-l
(or whatever that list is called) which isn't technical at all. Annouce-l
shouldn't be used for Announcements.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Query

[K. Peachey]

Could you please provide the patch in git diff format, or alternatively
straight into our git environment for even easier reviewing? (See
https://www.mediawiki.org/wiki/Gerrit for more info)



On 16 March 2014 00:21, Rahul Mishra mishra_2...@yahoo.com wrote:

 Hi,


 My name is Rahul Mishra, I am from Kolkata, India. I was working on a
 Annoying Little Bug, Bug 54749. And i have modified the source code of
 thumb.php the way as i thought it should be, but i am not sure of its
 working.

Proposed Patch: http://fpaste.org/85648/94892293/
(the additions are between line 111 to line
 118).

 Please have a look at the bug 54749, and help me understand, as what was
 aimed to achieved by debugging this bug and did i succeed in my attempt. If
 not, in what direction should i work further to fix it.


 Thank you!!
 Rahul Mishra.

 ___
 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] How to ask for a python package into Labs

[K. Peachey]

bugzilla.


On 23 February 2014 16:51, Alex Brollo alex.bro...@gmail.com wrote:

 I'd  need internetarchive python package into Labs:
 https://pypi.python.org/pypi/internetarchive , a python bot for Internet
 Archive. I cant't find how to ask for installing it into Labs. Can you help
 me?

 It's an interesting package - it can be implemented into a pywikibot and
 manage both mediawiki pages and Internet Archive items both reading and
 editing metadata and uploading new items/pages. I've been encouraged to go
 on by Tpt.

 Alex brollo
 ___
 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] Latest Snowden docs MediaWiki

[K. Peachey]

On 18 February 2014 20:41, Antoine Musso hashar+...@free.fr wrote:

 Le 18/02/2014 08:18, Philip Neustrom a écrit :
  The last details on their technical infrastructure indicated that Snowden
  used web crawler (love the quotes) software to obtain information from
  their internal wiki:
 
 
 http://www.nytimes.com/2014/02/09/us/snowden-used-low-cost-tool-to-best-nsa.html?hp

 Hello,

 From a usability point of view, I am wondering why he had to rely on a
 web crawler to export the whole Wiki as HTML.  For those wondering, you
 could use:

  https://www.mediawiki.org/wiki/Extension:DumpHTML  maintenance script
 which generate a HTML version of your wiki for archival purposes

  https://www.mediawiki.org/wiki/Extension:Pdf_Book to assemble articles
 in a single document export as PDF.


 MediaWiki has Special:Export, but it only export Wikitext.

 cheers,


Because all the articles are just speculation?
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Design] Should MediaWiki CSS prefer non-free fonts?

[K. Peachey]

On 16 February 2014 18:54, Gerard Meijssen gerard.meijs...@gmail.comwrote:

 ULS is a huge success in doing what it was intended to do. I am afraid that
 we have lost sight of what our primary objective is about.
 Thanks,
   GerardM


TBH we probably lost most of that when everything was rolled into one
gigantic extensions, instead of separate tools that specialised in what
they were designed for.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Request Queue for Gerrit/Git

[K. Peachey]

On 24 January 2014 04:18, Ty Atkinson tya.w...@gmail.com wrote:

 Hello all, I am User:TyA. I noticed on the [[Annoying large bugs]] page
 there was a request for a Request Queue and I'm interested in working on
 that. I have some basic ideas of how to lay it out, however I'd like to
 hear other's opinions on it as well. I'm also curious if it is still
 needed.

 My current plan is to have 2 special pages, one for the requesting and the
 other for seeing the queue/examining the submitted items.

 I currently have a rough draft of the Requesting form complete, [
 http://i.imgur.com/zRAAyvh.png screenshot]. However before going too much
 further, I wanted to get some feedback on whether I'm collecting enough
 info, or maybe not enough.

 My plan for the actual queue page is to have it create a table or list that
 will give the current status of the request as well as the requester, the
 submitted date, and the project name. The page will also accept /id
 subpages to load up information about a certain request so that it can be
 marked as done, not done, or needs more info.


I would recommend you talk to Chad (^d/^demon), It would probably be nice
if this could interface with our Git/Gerrit setup so they can be created
directly from within the interface.

As for the subpage idea, I don't think that would really be needed, It's
one of the areas where we could just store information directly within the
database without using the wikipage model for storage.

You would probably need more than two special pages to cover a few things

- Request Overview page (Table Format/Options to filter based on certain
features)
- Request Creation page
- Request Management page (Edit/Update requests/Action the requests etc)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] PHP new version(s) 5.5.7 and other versions. (upgrade, if you can)

[K. Peachey]

Who? What? When? Where? Why?


On Mon, Dec 16, 2013 at 5:05 PM, Thomas Gries m...@tgries.de wrote:

 PHP users are strongly advised to upgrade their PHP versions:
 PHP 4.0.6 - PHP 4.4.9
 PHP 5.0.x
 PHP 5.1.x
 PHP 5.2.x
 PHP 5.3.0 - PHP 5.3.27
 PHP 5.4.0 - PHP 5.4.22
 PHP 5.5.0 - PHP 5.5.6
 Vendor Status: Vendor has released PHP 5.5.7, PHP 5.4.23 and PHP 5.3.28|.||


 If you compile PHP from its sources, then the following configure
 works well:
 |
 |./configure --prefix=/usr --datadir=/usr/share/php
 --mandir=/usr/share/man --bindir=/usr/bin --libdir=/usr/share
 --includedir=/usr/include --sysconfdir=/etc --with-libdir=lib64
 --with-config-file-path=/etc --with-apxs2=/usr/sbin/apxs2-prefork
 --with-openssl --with-bz2 --with-zlib --with-curl --with-ldap
 --with-mysql --with-mysqli=mysqlnd  --with-pdo-mysql --enable-mbstring
 --with-xsl --enable-calendar --with-gd --with-jpeg-dir=/usr/lib64
 --with-png-dir=/usr/lib64 --with-iconv --with-pspell --with-gmp
 --with-mcrypt --enable-zip --enable-bcmath
 make
 make install


 |
 ___
 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] FWD: [Bug 58236] New: No longer allow gadgets to be turned on by default for all users on Wikimedia sites

[K. Peachey]

For wider discussion

---
From: bugzilla-daemon at wikimedia.org
Subject: [Bug 58236] New: No longer allow gadgets to be turned on by
default for all users on Wikimedia
siteshttp://news.gmane.org/find-root.php?message_id=%3cbug%2d58236%2d3%40https.bugzilla.wikimedia.org%2f%3e
Newsgroups: 
gmane.org.wikimedia.mediawiki.bugshttp://news.gmane.org/gmane.org.wikimedia.mediawiki.bugs
Date: 2013-12-09 20:41:41 GMT (19 minutes ago)

https://bugzilla.wikimedia.org/show_bug.cgi?id=58236

   Web browser: ---
Bug ID: 58236
   Summary: No longer allow gadgets to be turned on by default for
all users on Wikimedia sites
   Product: Wikimedia
   Version: wmf-deployment
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: Unprioritized
 Component: Site requests
  Assignee: wikibugs-l at lists.wikimedia.org
  Reporter: jared.zimmerman at wikimedia.org
CC: benapetr at gmail.com,
bugzilla+org.wikimedia at tuxmachine.com,
dereckson at espace-win.org, greg at wikimedia.org,
tomasz at twkozlowski.net, wikimedia.bugs at snowolf.eu
Classification: Unclassified
   Mobile Platform: ---

Gadgets being turned on for all site users (including readers) can cause a
confusing users experience, especially when there is some disagreement and
defaults change without notice (readers are rarely if ever part of these
discussions)

Move to model where gadgets are per user rather than part of a default
experience for users

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l at
lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikibugs-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] FWD [Bug 58235] New: Remove skin selection from Wikipedia and Wikimedia site Special:Preferences for new user accounts

[K. Peachey]

For wider discussion


From: bugzilla-daemon at wikimedia.org
Subject: [Bug 58235] New: Remove skin selection from Wikipedia and
Wikimedia site Special:Preferences for new user
accountshttp://news.gmane.org/find-root.php?message_id=%3cbug%2d58235%2d3%40https.bugzilla.wikimedia.org%2f%3e
Newsgroups: 
gmane.org.wikimedia.mediawiki.bugshttp://news.gmane.org/gmane.org.wikimedia.mediawiki.bugs
Date: 2013-12-09 20:27:15 GMT (35 minutes ago)

https://bugzilla.wikimedia.org/show_bug.cgi?id=58235

   Web browser: ---
Bug ID: 58235
   Summary: Remove skin selection from Wikipedia and Wikimedia
site Special:Preferences for new user accounts
   Product: Wikimedia
   Version: wmf-deployment
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: Unprioritized
 Component: Site requests
  Assignee: wikibugs-l at lists.wikimedia.org
  Reporter: jared.zimmerman at wikimedia.org
CC: benapetr at gmail.com,
bugzilla+org.wikimedia at tuxmachine.com,
dereckson at espace-win.org, greg at wikimedia.org,
tomasz at twkozlowski.net, wikimedia.bugs at snowolf.eu
Classification: Unclassified
   Mobile Platform: ---

To reduce the support burden on foundation developers and designers when
creating new features or improving existing ones, skin selection and related
preferences should be removed for newly created accounts and the default skin
(currently vector) used for all new accounts.

A new access point for custom css/js should be added if necessary.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l at
lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikibugs-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] MediaWiki 1.22.0 released

[K. Peachey]

I only corrected the stable version number templates, Someone else will
have to do the others (As well as the [[MW 1.22]] and the release notes
page, if they havn't been done)


On Sat, Dec 7, 2013 at 12:51 PM, Andre Klapper aklap...@wikimedia.orgwrote:

 On Fri, 2013-12-06 at 23:02 +, Markus Glaser wrote:
  I am happy to announce the availability of the first stable release of
  the new MediaWiki 1.22 release series.

 Congratulations!

 I'm wondering which older versions are still supported.
 https://www.mediawiki.org/wiki/Template:DownloadMediaWiki lists 1.20.8
 as legacy but not 1.21.3, but now also states that 1.20.x [...] was
 discontinued.
 If the latter is correct, does
 https://www.mediawiki.org/wiki/Template:MW_legacy_release_number
 need to be changed from 1.20.8 to 1.21.3?

 andre
 --
 Andre Klapper | Wikimedia Bugwrangler
 http://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] Please use sitenotice when a new version of software is deployed

[K. Peachey]

People that are interested in the version will more than likely already
know about [[Special:Version]], if they want the added onscreen [clutter]
presence they could whip up a gadget or something to pull it from the API.


On Sat, Dec 7, 2013 at 4:53 PM, Bináris wikipo...@gmail.com wrote:

 There could be a small-sized version number somewhere on screen. Those who
 are interested in would learn where it is and could watch it, while others
 won't be disturbed.
 ___
 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] Please use sitenotice when a new version of software is deployed

[K. Peachey]

On Thu, Dec 5, 2013 at 8:28 PM, Alex Brollo alex.bro...@gmail.com wrote:

 Users are very confused and worried any time a new version of wiki software
 is launched and tested, and some major or minor bug comes invariably out.

  A clear message using central sitenotice, with links to doc pages listing
 the changes at different levels of detail and to their talk pages to
 discuss them and to alert for bugs, is mandatory IMHO. Tech news are
 largely insufficient; evidence of work in progress should be clearly
 visible into all pages of interested projects. It's a basic matter of
 Wikilove.



Every two weeks for major stuff?, Apart from Sitenotices being disruptive
and stupid, And people will just start to get that used to them that they
won't even notice (or worse, use blocking technologies to get rid of them).
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] 1.22.0rc3 ready for download

[K. Peachey]

Bad idea [to package/install],…

Is what I believe beta was saying Tyler.

On Friday, December 6, 2013, Tyler Romeo wrote:

 On Tue, Dec 3, 2013 at 4:39 PM, John phoenixoverr...@gmail.comjavascript:;
 wrote:

  VE is a BAD idea, its full of holes and bugs


 Those are two separate concepts. Just because something has bugs does not
 make the software itself a bad idea.

 *-- *
 *Tyler Romeo*
 Stevens Institute of Technology, Class of 2016
 Major in Computer Science
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org javascript:;
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Sent from Gmail Mobile on my iPod.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Tracking Extensions by License type / was WMFs stance on non-GPL code

[K. Peachey]

On Thu, Aug 29, 2013 at 6:36 AM, Ryan Kaldari rkald...@wikimedia.orgwrote:

 Just for fun, I added some license-parsing logic to Template:Extension on
 mediawiki.org. I think the job queue is still updating the categories, but
 so far we have:
 Extensions with no license specified: 596
 Extensions with an unknown license: 779
 GPL licensed extensions: 667
 MIT licensed extensions: 44
 BSD licensed extensions: 23
 AGPL licensed extensions: 10
 MPL licensed extensions: 1

 I was actually surprised to see how few MIT and BSD extensions we have
 considering how much animosity there is towards the GPL, but I suppose most
 people just want to match the licensing of MediaWiki.

 If you haven't specified the license of your extension, now would be a good
 time to do so :)

 Ryan Kaldari


(Separating this into it's own discussion)

A while ago I went though the first ~two pages of [[Cat:Extensions with an
unknown license]][1] and cleaned up a lot of the usages to use a template I
whipped up quickly where the license text directly matched a license I had
listed (T:EL)[2]

Although I didn't ever fix up logic in the infobox for the categories, so
if someone was still interested and fixed that up so they are still sitting
in unknown, but they should also be in their respective categories as well
now for people that want fuller numbers.

[1]. https://www.mediawiki.org/wiki/Category:Extensions_with_unknown_license
[2]. https://www.mediawiki.org/wiki/Template:ExtensionLicense
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Local Wikipedia mirror system messages

[K. Peachey]

wm-license-information-description will probably be comming from
E:WikimediaMessages, You will also want a dump containing the locally one
done on the wiki's MediaWiki: namespace.


On Sun, Nov 17, 2013 at 5:09 PM, Timothy Pearson 
kb9...@pearsoncomputing.net wrote:

 Hi all,

 I have successfully set up a local wikipedia instance using the English
 data dumps, but I cannot seem to find a copy of the MediaWiki translation
 files in use on the Wikipedia sites.  As a result, tags like
 wm-license-information-description are not displayed correctly.

 Is there a place I can download the Wikipedia-modified system message
 files (languages/messages/MessagesEn.php,
 languages/messages/MessagesQqq.php, etc.)?

 Thanks!

 Tim



 ___
 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] Secure and split

[K. Peachey]

On Fri, Nov 1, 2013 at 7:56 AM, Danese Cooper dan...@gmail.com wrote:

 Except it was yesterday in Oz, right?


Yes

Happy Tim Day, Mr. Starling...and belated congrats on that second daughter
 too!

 3 D


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Fix the Wikimedia Email Templates

[K. Peachey]

Hi, Can you please file this in our bug tracking system at 
https://www.bugzilla.wikimedia.org/.


On Tue, Oct 22, 2013 at 3:49 AM, Nasir Khan nasir8...@gmail.com wrote:

 Hi,

 I am Nasir, an active contributor of Bengali WIkipedia. I use the email
 notifications for the change on my watch list pages. The email is not
 formatted as it should. I faced the following issues for the Bengali emails
 and i think these should be fixed soon.

 * Sometimes a new line appeases between the words of a page name, and
 sometimes new line appears after 4/5 words in a sentence. I think we are
 using a fixed DIV width for these texts. If it will be removed then it may
 be fixed.

 * Unicode URLs are not readable at all. For the Bengali wiki urls we can
 make some changes to make the url more readable. like url format could be
 like this a href=PAGE_LINKhttp://bn.wikipedia.org/wiki/PAGE_NAME/a


 *--
 *regards
 *Nasir Khan Saikat* http://profiles.google.com/nasir8891
 www.nasirkhn.com
 ___
 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] Inline bug report history in Bugzilla

[K. Peachey]

On Tue, Oct 15, 2013 at 3:14 AM, Chad innocentkil...@gmail.com wrote:

 On Mon, Oct 14, 2013 at 1:26 AM, Željko Filipin zfili...@wikimedia.org
 wrote:

  On Sat, Oct 12, 2013 at 2:05 AM, Isarra Yos zhoris...@gmail.com wrote:
 
   So yeah, helpful for the majority, I'd say.
 
 
  +1
 
 
 I guess I'm in the minority then. That's really cluttered and
 gives me no useful information. Glad there's a way to turn
 it back off :D

 -Chad


+2
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Bulk download

[K. Peachey]

On Mon, Sep 23, 2013 at 11:22 PM, Mihai Chintoanu 
mihai.chinto...@skobbler.com wrote:

 Hi everyone,

 I have a list of about 1.8 million images which I have to download from
 commons.wikimedia.org.


Why?
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [RFC]: Clean URLs- dropping /wiki/ and /w/index.php?title=..

[K. Peachey]

On Tue, Sep 17, 2013 at 8:34 AM, Gabriel Wicke gwi...@wikimedia.org wrote:

 There *might* be, in theory. In practice I doubt that there are any
 articles starting with 'w/'. To avoid future conflicts, we should
 probably prefix private paths with an underscore as titles cannot start
 with it (and REST APIs often use it for special resources).


I bet people have said that about single letter interwikis, but we do have
quiet a few single letter: page titles around. have single letter/
is not un-believable.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Help users with screen readers on Wiktionary?

[K. Peachey]

Speak to hoo on IRC, he is been contracted by WMDE to work on a11y issues
and has been some wonderful work already from what I hear.

On Monday, September 16, 2013, Mark A. Hershberger wrote:

 A user who depends on a screen reader has recently found Wiktionary to
 be less useful than it was in the past.


 https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Site_accessibility_for_blinds

 I've contacted one administrator, but perhaps someone on wikitech-l can
 help the user or help figure out the cause of the  problem.

 Mark.


 --
 http://hexmode.com/

 Love alone reveals the true shape of the universe.
  -- Everywhere Present, Stephen Freeman

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org javascript:;
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
-- Sent from Gmail Mobile on my iPod.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] WMFs stance on non-GPL code

[K. Peachey]

On Thu, Aug 29, 2013 at 6:41 AM, Luis Villa lvi...@wikimedia.org wrote:

 Just out of curiosity, what code are you using to do license parsing? If
 you want seriously robust parsing, you might take a peek at
 https://github.com/dmgerman/ninka

 Luis

 standard parser functions via the template

{{lc:{{{license|}}} }}
|gpl|gplv2|gplv2 or later|gpl v2|gpl v2 or later|gplv2+|gplv3|gpl v3 = GPL
licensed extensions
|agpl|agplv2|agplv3 = AGPL licensed extensions
|mit|expat|expat (mit)|x11 = MIT licensed extensions
|bsd|new bsd|revised bsd|modified bsd|freebsd = BSD licensed extensions
|mpl|mplv2|mpl v2 = MPL licensed extensions
|#default = Extensions with unknown license
}}]]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] git.wikimedia.org dead?

[K. Peachey]

On Sun, Aug 11, 2013 at 10:44 AM, Leslie Carr lc...@wikimedia.org wrote:
 looks like the robots.txt isn't being served - so googlebot is
 grabbing things from the zip files
 client denied by server configuration: /var/www/robots.txt

 sadly too jetlagged to keep looking at this :(

make sure you look at robot.txt and not Robot.txt,

As chad points out, its being served now

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Gitblit down?

[K. Peachey]

On Wed, Jul 24, 2013 at 3:58 PM, Chad innocentkil...@gmail.com wrote:
 Things should be much better since this afternoon.


You gave into the server kittehs demands for fresher tuna?

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Remove 'visualeditor-enable' from $wgHiddenPrefs

[K. Peachey]

On Tuesday, July 23, 2013, Subramanya Sastry wrote:

 500+ edits are being done per hour using Visual Editor


500+ people are making edits with the default editor, I'm pretty sure
(without doing stats on it)  that a lot of them wouldn't be experienced
enough to kill it off


-- 
-- Sent from Gmail Mobile on my iPod.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] ContentHandler hook deprecations

[K. Peachey]

Didn't we just decide on a deprecation setup a few months ago? Marked for
two majors then removed iirc

On Monday, July 22, 2013, Mark A. Hershberger wrote:

 I just noticed that ContentHandler has understandably deprecated several
 hooks.

 However, not all the hooks have been updated as deprecated on the mw.o.
  Some of their replacements aren't even documented on mw.o.

 Worse, there isn't any schedule for how long the legacy hooks are going
 to be supported or any HOWTOs for developers interested in making their
 extensions work in MW 1.21+..

 This is especially frustrating for developers who may have used
 ArticleViewCustom (new in 1.19) only to have it be deprecated a year
 later in 1.21 for ArticleContentViewCustom.

 (If anyone did use this hook in 1.19, they didn't document that use on
 mw.o, so we don't know about it and can't warn them about the issues
 that may come from this.)

 Mark.

 --
 http://hexmode.com/

 Love alone reveals the true shape of the universe.
  -- Everywhere Present, Stephen Freeman

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org javascript:;
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
-- Sent from Gmail Mobile on my iPod.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Disambiguator extension deployed to all WMF wikis (action required)

[K. Peachey]

I bet the JobQueue would be loving that.

On Wed, Jul 10, 2013 at 4:52 PM, Federico Leva (Nemo)
nemow...@gmail.com wrote:
 As all templates requiring it are listed in
 [[MediaWiki:Disambiguationspage]], why not run a global bot? It's surely
 easier than trying to find 800 editors.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Please Welcome Sean Pringle, our latest TechOps member

[K. Peachey]

On Tue, Jun 25, 2013 at 1:17 AM, Ct Woo ct...@wikimedia.org wrote:
 Sean hails from Queensland, Australia and while he travels around
 frequently,  he inevitably always flee back to his down under home. He
 confessed  being forever distracted by all things geek and technology
 related though he can also be spotted behind a telescope on starry nights
 and with nose in a book when the cloud rolls in.

Woo! a Maroon!.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Bugzilla: Separate bug report status when patch is in Gerrit?

[K. Peachey]

How does a Status change work better than a Keyword change in this case?

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] ZERO architecture

[K. Peachey]

On Sat, Jun 1, 2013 at 4:25 AM, Adam Baso ab...@wikimedia.org wrote:
 Sorry to reply on a thread that will probably not sort nicely on the
 mailman web interface or threading mail clients. Anybody know of an
 easy way to reply to digest email in Gmail such that mailman will
 retain threading?

Don't use digest mode... (if you insist, you a external service to
reply, eg: Gmame or whatever its called seems popularish)

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] MediaWiki 1.21.0 released

[K. Peachey]

Yes, but that is a mistake in the file. That got fixed in Git today.

On Sun, May 26, 2013 at 1:29 PM, Jamie Thingelstad
ja...@thingelstad.com wrote:
 I just installed this tar ball and Special:Version is reporting 1.21.0rc5. 
 update also reports 'MediaWiki 1.21.0rc5 Updater'. Did the right files get 
 sent up?

 I downloaded 
 http://download.wikimedia.org/mediawiki/1.21/mediawiki-1.21.0.tar.gz

 MD5 of file I got is:

 bbe80b6299ced434aa99acb8866f1886  mediawiki-1.21.0.tar.gz
 Jamie Thingelstad
 ja...@thingelstad.com
 mobile: 612-810-3699
 find me on AIM Twitter Facebook LinkedIn

 On May 25, 2013, at 10:20 AM, Mark A. Hershberger m...@everybody.org wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 I'm happy to announce the availability of the first stable release
 of the new MediaWiki 1.21 release series.

 MediaWiki 1.21 is a large release that contains many new features and
 bug fixes. This is a summary of the major changes of interest to users.
 You can consult the RELEASE-NOTES-1.21 file for the full list of changes
 in this version.

 Our thanks go to everyone who helped to improve MediaWiki by testing
 the beta release and submitting bug reports.

 == What's new? ==

 MediaWiki 1.21 includes all changes released in the smaller, bi-weekly
 1.21wmfX software deployments to Wikimedia sites.

 === Clearer email notifications ===

 Bug 14901 ? Email notification mistakes log action for new page
 creation, the third most reported open MediaWiki bug, has been
 fixed. Consequently, notifications now state clearly what action was
 performed on the watched pages in case they are created, deleted,
 restored, moved or changed.

 There are still some known issues. If you customised MediaWiki:Enotif
 body on your wiki, you have to delete or update it; see also full
 documentation.

 === Skin ===

 The CologneBlue skin has been refactored to make it relevant again,
 more compatible with existing scripts, and more similar in structure
 to Vector and Monobook, reusing a lot of existing code.

 The only major difference for end-users should be a slight reordering
 of the sidebar menu (the Context submenu was removed and its
 contents merged into other ones). If you were, however, depending on
 the exact HTML it used to produce, you'll need to review your tools.

 === ContentHandler ===

 As part of the Wikidata initiative, 1.21 adopts an extensible
 framework (ContentHandler) so that pages can contain something other
 than wikitext.

 Right now, built-in content types are limited to

wikitext - wikitext, as usual
javascript - user-provided JavaScript code
css - user-provided CSS code
text - plain text

 Extension developers can create additional content
 types. Extension:EventLogging uses ContentHandler to implement a
 namespace for JSON schemas, and may be used as a reference. Other
 extensions, such as Scribunto, also make use of the new functionality.

 ContentHandler affects diff rendering, handing of CSS and JavaScript
 pages, import/export, and the API.

 === Support for high DPI displays ===

 MediaWiki now tries to deliver higher-res images to high pixel density
 screens such as Apple Retina Displays (see gerrit change 24115 for
 details). This is a work-in-progress, so normal-resolution images may
 still appear in some places and in some browser
 versions. Administrators may need to watch out for higher load on
 their image scaling software.

 === Ajax patrolling ===

 (bug 7851) The features users have waited for longest: one-click Ajax
 patrolling. With this new feature, users can mark revisions or pages
 as having been patrolled with a single click while staying on the
 current page.

 === Internationalization ===

 (bug 24156) The general logging framework was made completely
 localisable at last. The logging for each action (whether in core or
 extensions) might still need to be updated to use the new system,
 though.

 (bug 40367) MediaWiki:Contributions now reflects the gender of the
 user.

 === New accounts ===

 (bug 22457) It's now easier to create accounts for other users by
 sending a temporary password via e-mail: Special:CreateAccount now
 shows a checkbox for logged-in users to use this feature, rather than
 a button.

 Account API: bots and other scripts can now use the API to create user
 accounts, rather than attempting to pseudo-submit the HTML form.

 === Account creation welcome ===

 The MediaWiki:welcomecreation message was split up into
 MediaWiki:welcomeuser and MediaWiki:welcomecreation-msg so users no
 longer see Login successful when creating their accounts (bug
 42215). If you customized the former message and want to preserve your
 customization, you'll have to modify the new messages accordingly.

 === More wikitext now supported in JavaScript messages ===

 The jqueryMsg parser now supports wikilinks and int: transclusion. For
 more details, see Manual:Messages API.

 === Using semantic headings for the navigation menu ===

 The previous scheme of 

Re: [Wikitech-l] GSoC Virtual Keyboard

[K. Peachey]

GSoC projects have been accepted yet?

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] State of MediaWiki's render action (parameter to index.php)

[K. Peachey]

On Mon, May 20, 2013 at 4:34 AM, Matthew Flaschen
mflasc...@wikimedia.org wrote:
 We should give people a heads up, unless/until it's reconsidered and we
 decide to undeprecate it (maintain support indefinitely).

 Matt Flaschen

Um, how it be discussed and considered to deprecate it in the first place?

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] don't show certain links with the help of Special:AllMessages

[K. Peachey]

Try setting the message to -

On Fri, May 17, 2013 at 8:08 PM, Yury Katkov katkov.ju...@gmail.com wrote:
 Hi everyone!

 I think that Special:AllMessages and the idea that every message in the
 wiki has its own wikipage is just _awesome_.
 So, I can Replace the disclaimer label to smth different
 using MediaWiki:Disclaimers. That's great.

 However I haven't found the way to HIDE the element. For instance I don't
 need the policy link in my footer. Is that possible of should I use CSS?
 -
 Yury Katkov, WikiVote
 ___
 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 extension: Special:ExtensionStatus (opinions?)

[K. Peachey]

On Fri, May 17, 2013 at 11:15 AM, Moriel Schottlender mor...@gmail.com wrote:
 You can see a screenshot of the current working version here:
 http://www.mediawiki.org/wiki/File:Extstatus_screenshot.png

Please license your uploads to the wiki correctly (or more preferably
update to commons!).

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] New extension: Special:ExtensionStatus (opinions?)

[K. Peachey]

On Tue, May 14, 2013 at 4:43 PM, Matthew Flaschen
mflasc...@wikimedia.org wrote:
 Or set up some caching on Gitweb, so it's usable for this kind of thing.

I believe Chad is planning on sending Gitweb to /dev/null/, in-turn
for a better replacement (if it does caching better is another
question).

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Bugzilla for Extensions

[K. Peachey]

File a bug under Wikimedia/Bugzilla for it. Only pre-req is that you
are heavily involved in the dev of it (eg: maintainer) and you want
it.

On Wed, May 8, 2013 at 5:01 PM, Tyler Romeo tylerro...@gmail.com wrote:
 Hey,

 I was wondering what the qualifications are for getting a Bugzilla section
 for a MediaWiki extension, and how it can be set up? (It's difficult having
 to memorize or write down on notepads what things need to be fixed, and I
 don't want to have to set up my own Bugzilla instance.)

 *-- *
 *Tyler Romeo*
 Stevens Institute of Technology, Class of 2015
 Major in Computer Science
 www.whizkidztech.com | tylerro...@gmail.com
 ___
 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] Deploying alpha of VisualEditor to non-English Wikipedias

[K. Peachey]

On Fri, Apr 26, 2013 at 11:23 PM, Lukas Benedix
bene...@zedat.fu-berlin.de wrote:
 ...
 You can share your feedback on
 https://www.mediawiki.org/wiki/Project:VisualEditor/Feedback
 but 'visual editor' - 'review and save' - 'something is wrong' - 'report
 problem' is not working for me.


You can report it straight into Bugzilla, As mentioned at the top of
that page. Here is the direct link
https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditorcomponent=General

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Announcement: Erik Bernhardson joins Wikimedia as Features Engineer

[K. Peachey]

On Tue, Apr 23, 2013 at 9:00 AM, Terry Chay tc...@wikimedia.org wrote:
 ...
 His first official day is today (April 22). He is going to work with the 
 Editor Engagement team on Messaging, and any other stuff we can throw at him 
 until he feels sufficiently overwhelmed. I’m still trying to figure out how 
 to verbally distinguish between my boss and him (suggestions welcome!).

Does it have to verbally? I recommend some sort of crazy hat setup,
and the other staff members can choose the hats each day?

One day someone might choose a Sombrero, the next day someone might
choose [something cool] like a Fez

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Google Summer of Code '13] Project Idea - Inspire Me Button

[K. Peachey]

I believe E:Getting_Started is already working on something like this.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] No cascade protection on Mediawiki namespace

[K. Peachey]

Why not just protect the template when you add it? I think you may be
over thinking this just a tad.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417

[K. Peachey]

On Fri, Apr 19, 2013 at 1:10 AM, Mark A. Hershberger m...@everybody.org wrote:
 Wow, thank you for pointing to Framasoft.  Looks like they've got some
 really useful stuff going on there.

Could be done very easily and neatly in a MediaWiki page...

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417

[K. Peachey]

On Fri, Apr 19, 2013 at 8:54 AM, Rob Lanphier ro...@wikimedia.org wrote:
 We used to do that:
 https://www.mediawiki.org/wiki/Roadmap
...

How about just something simple like
 * https://www.mediawiki.org/w/index.php?title=User:Peachey88/Sandbox/table2 or
 * https://www.mediawiki.org/w/index.php?title=User:Peachey88/Sandbox/table1

once they are tided up slightly, they have a similar layout as the
spreadsheet and not as confusing as the previous attempt (Which I
think may have been a little over worked for the end goal) although I
do admit they may be harder to edit (but that maybe fixed by some
template wizards)

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Problems with file deletion on Commons

[K. Peachey]

On Tue, Apr 16, 2013 at 12:54 AM, Eugene Zelenko
eugene.zele...@gmail.com wrote:
 Hi!

 I'd like to bring to attention of developers and system administrators
 problems with file deletion on Commons:

 http://commons.wikimedia.org/wiki/Commons:Administrators%27_noticeboard#Daily_DR_issue

 Sorry, if it's known issue, but it persist for several days and
 definitely affects administrators job.

 Eugene.


https://bugzilla.wikimedia.org/show_bug.cgi?id=13921

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Clicktracking being phased out

[K. Peachey]

On Sat, Apr 13, 2013 at 5:46 AM, FastLizard4 fastliza...@gmail.com wrote:
 I thought we weren't supposed to use blink tags because they attracted
 Weeping Angels.  :P

That which holds the image of a angel...

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Bugzilla Weekly Report

[K. Peachey]

On Mon, Apr 8, 2013 at 11:07 PM, Željko Filipin zfili...@wikimedia.org wrote:
 Done:

 http://www.mediawiki.org/wiki/Bugzilla_Weekly_Report

 Željko


I hope you are going to go edit the descriptions for those files and
add the appropriate license tags?

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] whatcanidoforwikipedia.org

[K. Peachey]

Why not just point it to a page onwiki somewhere? that way everyone
can contribute!

(we could even semi-protect it I guess...)

On Mon, Apr 8, 2013 at 1:00 AM, Yuvi Panda yuvipa...@gmail.com wrote:
 On Sun, Apr 7, 2013 at 8:17 PM, MZMcBride z...@mzmcbride.com wrote:
 Thanks for working on this. You probably want to talk to Quim and others
 in his team about this. He's been doing related work:

 * https://www.mediawiki.org/wiki/How_to_contribute

 Will do :) It's a nice page, I hadn't checked it out before! I should
 be able to steal some from there

 And some of my old notes about this:

 * https://www.mediawiki.org/w/index.php?oldid=585568#Blueprint

 It's unclear whether you want to only focus on technologies or if you want
 to also focus on (for example) re-using content from Wikimedia wikis.
 What can I do for Wikimedia? -- re-use our content via XML dumps and
 the MediaWiki API.

 I think for now we should limit scope and only focus on the
 'contribute code to Wikimedia' part, rather than the 'use our data in
 interesting ways' part. The sit is, after all, what can I do *for*
 wikimedia/wikipedia/mediawiki, rather than *with*. We can get those
 domains too, but I think that's a much larger project than what I'd
 want to sign up for right now :)

 I'm thinking of limiting it to *just* developers to begin with, and
 add localization afterwards. Thoughts?

 --
 Yuvi Panda T
 http://yuvi.in/blog

 ___
 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] Proposal: Wikitech contributors

[K. Peachey]

On Thu, Apr 4, 2013 at 11:59 PM, Marc A. Pelletier m...@uberbox.org wrote:
 So yeah; perhaps SMW has issues that makes deployment to the bigger
 content wikis problematic, but rejecting it for the smaller data-based
 ones on a kneejerk is, at best, misguided.

It wasn't knee jerk the time it was discussed, and a few subsequent.
There was some known problems with the code, Most of these should be
cleaned up now since ryan is willing enough to run it on labs.

Plus we already have another system that is getting worked on and
rolled out to a few of the production wikis that will seem to do
similar features (based on comments in this thread already).

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] RFC: Alternative domains for Commons

[K. Peachey]

How is that meant to pervent confusion? you are just sticking a extra
.api in the address.

On Thu, Mar 28, 2013 at 5:41 PM, Petr Bena benap...@gmail.com wrote:
 What about inserting another domain just to prevent confusion and to
 keep current redirects, which would ONLY allow api, such as

 commons.api.wikipedia.org

 the *.api.project would just be some kind of universal api gateway
 for all domains

 On Wed, Mar 27, 2013 at 10:07 PM, Juliusz Gonera jgon...@wikimedia.org 
 wrote:
 On Fri, Mar 22, 2013 at 9:22 PM, MZMcBride z...@mzmcbride.com wrote:

 Please draft an RFC at https://www.mediawiki.org/wiki/RFC. :-)


 http://www.mediawiki.org/wiki/Requests_for_comment/Alternative_Commons_Domains
 Please share your comments.


 commons.wikipedia.org already redirects to commons.wikimedia.org (for
 historical reasons, maybe), so that has to be considered.


 Yes, it redirects. But to solve the problem I'm describing, the API would
 need to be served from commons.wikipedia.org.


 I think what
 you're proposing is also kind of confusing and I'm wondering if there
 aren't better ways to approach the problem.


 I'm open to suggestions, but I'd rather not wait until CentralAuth gets
 completely redesigned and rewritten.

 --
 Juliusz


 ___
 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] JobQueue

[K. Peachey]

AFAIK we already do that for some entries, Reedy will know more, I
will let you investigate his mind for more knowledge on that.

On Sun, Mar 24, 2013 at 7:27 AM, Matthew Walker mwal...@wikimedia.org wrote:
 Don't forget about the potentials of a priority based queue! (That being
 said I actually have no idea what goes into our job queues; so can't say if
 there's good candidates for priority based queuing.)

 ~Matt Walker
 Wikimedia Foundation
 Fundraising Technology Team


 On Sat, Mar 23, 2013 at 6:30 AM, Tyler Romeo tylerro...@gmail.com wrote:

 On Mar 23, 2013 12:10 AM, John phoenixoverr...@gmail.com wrote:
 
  I know Aaron has spent a lot of time on the job queue. But I have
  several observations and would like some feedback. The current workers
  apparently select jobs from the queue at random. A FIFO method would
  make far more sense. We have some jobs that can sit there in the queue
  for extended periods of time, while others added after that point may
  get completed in mere few minutes.

 Well random is not the only method. There is also timestamp based and FIFO.
 ___
 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] RFC: I suggest renaming of pages Cross-site scripting = Cross-site scripting (XSS, XSSI) and Cross-site request forgery = Cross-site request forgery (CSRF)

[K. Peachey]

What actual benefit with having their abbreviation in the title archive?

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Missing project ideas for GSOC

[K. Peachey]

On Fri, Mar 22, 2013 at 10:30 PM, Željko Filipin zfili...@wikimedia.org wrote:
 Most of these projects seem to be extension (and PHP?) centric. Can we
 have more diversity?


 Browser test automation? Not an extension, not in PHP, but in Ruby[2].

OPs don't want [any more] ruby on the clusters, So I wouldn't suggest that.

We should be focusing on stuff that is achievable and that can easily
be shown on benefit our users by actually getting it out there (we
have a shocking record for this)

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] FlaggedRevs at www.mediawiki.org

[K. Peachey]

What is your Username?, My crystal ball is still getting repaired.

On Tue, Mar 19, 2013 at 4:52 PM, Tyler Romeo tylerro...@gmail.com wrote:
 If possible, could I get the flag as well. I've run into the same problem
 before.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Github/Gerrit mirroring

[K. Peachey]

On Fri, Mar 15, 2013 at 12:19 PM, Tyler Romeo tylerro...@gmail.com wrote:
 Can we please be real here? The reason more contributors come in through
 GitHub than through Gerrit is because they *already have a GitHub account*.
 My browser is always logged into GitHub,

?!? Unless you magically had a account created for you at GitHub that
logic fails.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l