gt;> Yes, that sounds like a good idea. I typically recommend
> >> <https://www.mediawiki.org/wiki/User:Wctaiwan/Gerrit_cheatsheet> to
> >> people who are confused with git.
> >>
> >
> > +1, as someone who uses it rarely enou
On Tue, Nov 10, 2015 at 6:31 PM, Isarra Yos <zhoris...@gmail.com> wrote:
> On 11/11/15 02:06, S Page wrote:
>
>> I meant the on-wiki three-part skinning thing that's been
>> around for a while and introduces in a nutshell as "This page is part 1 of
>> a thre
tter.
>
> -I
>
> ps - Yes, I may have read motherfuckingwebsite.com a few too many times
> before writing that up. I, uh, sort of apologise.
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.
On Tue, Nov 10, 2015 at 2:39 PM, Isarra Yos <zhoris...@gmail.com> replied:
> On 10/11/15 21:59, S Page wrote:
>
>> The tutorial is pretty good IMO, the problem is it forced repetition
>
>
> This may just be because I did it at three in the morning; it probably
> do
Niedzielski mentioned.
[1]
https://www.mediawiki.org/w/index.php?title=Manual%3ACoding_conventions=revision=1931325=1931314
[2] https://help.github.com/articles/supported-mediawiki-formats/
[3] https://phabricator.wikimedia.org/T91626
[4] https://en.wikipedia.org/wik
On Oct 30, 2015 11:06, "Florian Schmidt"
wrote:
[Thanks for helping the developer community!]
> I'm wondering, if dependencies like yours are widely used and if
extending the requires section support to extensions would help to solve
your problem (with that
dding one class rises to the
level of an architectural change that would prompt an RFC.
[1] https://www.mediawiki.org/wiki/Requests_for_comment/Process
Cheers,
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https:
he hard work of a lot of different people, PHP CodeSniffer is
> now voting on all MediaWiki core patchsets! It checks for basic code
> style issues automatically
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.w
ax and escaping rules that the Cirrus back-end supports, but
a helper that inserts the prefixes could work.
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Congratulations on the container, mention it on mw.org somewhere. It seems
with that you've got half the battle won. MediaWiki-vagrant's roles let you
easily add features to a development wiki, but maybe instead of trying to
get all MediaWiki-vagrant's vagrant and puppet machinery running in your
wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29
[2]
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Directory/Science,_technology,_and_engineering_WikiProjects
[3] https://en.wikipedia.org/wiki/140_New_Montgomery
--
=S Page WMF Tech writer
___
when vector came out. We could create another skin
> to
> > replace vector as we did with monobook or update vector with a new look
> > that has bold colours and goes along with mediawiki code and is also
> mobile
> > optimised even though we have the mobilefrontend extension so
t; Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
19 [1]; and it's more
efficient for me. The recent DWIM ("Do what I mean") improvements while
you're writing a post are a delight. Thanks Collaboration team <3 !
--
=S Page WMF Tech writer
[1] > The main goals for the Flow project are:
- to make the wiki discussion system **more ac
://devhub.wmflabs.org/wiki/API:Web_APIs_hub
--
=S Page WMF Tech writer, and Quim Gil Engineering Community manager
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
were to rewrite
morebits.js from scratch, wouldn't it be better to create
mediaWiki.moreBits.{quickForm, simpleWindow, ...} rather than
window.MoreBits ?
Cheers,
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
with
coordinates that are nearby.
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
like there's a full replacement.
All the code name suggestions would be making things less clear, not
more.
If it had started out with a code name there would be historical
inertia,
but using a code name now would just be silly.
--
=S Page WMF Tech writer
/Manual:Coding_conventions/JavaScript
[3]
https://www.mediawiki.org/wiki/ResourceLoader/Developing_with_ResourceLoader#Debugging
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo
:)
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
There's an article about getting pages nearby with action=geosearch,
http://devhub.wmflabs.org/wiki/API:Showing_nearby_wiki_information [1], I
welcome feedback.
On Jul 21, 2015 10:40, Sylvain Arnouts sylvain.arno...@wanadoo.fr wrote:
I know it's possible with Wikidata API to enter a position
of Use must be prominently featured in the Developer
Hub'. I was thinking of mentioning it in the three adding it to the footer,
but maybe that's not prominent enough.
Great feedback, thanks.
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l
Thanks for the feedback (seriously).
On Fri, Jun 26, 2015 at 5:53 AM, MZMcBride z...@mzmcbride.com wrote:
More to the point: why not just make dev.wikimedia.org a round robin that
points to either https://meta.wikimedia.org/wiki/Research:Data or
://www.mediawiki.org/wiki/dev.wikimedia.org , or file Phabricator
tickets in the project dev.wikimedia.org [1].
Since December 2013 Moiz Syed and others discussed creating a thing to
expose our APIs and data to developers. When S Page moved to WMF tech
writer, he wrote some articles
://phabricator.wikimedia.org/T91683
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
://phabricator.wikimedia.org/T103454
[2]
https://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_hide_the_main_page_title.3F
[3] https://www.mediawiki.org/wiki/Manual:Skinning
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
be reserved for experimental or even beta
APIs. Continuing queries seems like a stable—and pervasive—part of the API.
Cheers,
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo
#1 sounds right, Jenkins serves us, not vice versa. The core change's
commit message should reference the two required extension changes.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
not a full reference.
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
?
Cheers,
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
#Using_the_new_JSON_results_format
Cheers,
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Benito, Grossmeier! He made the trains run on time [1]
Tuesday: New branch cut, deployed to test wikis
and mediawiki.org as before, I assume.
[1] Or not, http://www.transportmyths.co.uk/mussolini.htm
--
=S Page WMF Tech writer
___
Wikitech-l
://www.mediawiki.org/wiki/HTMLForm
[2] https://phabricator.wikimedia.org/F169381
[3] https://phabricator.wikimedia.org/T100401
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman
and encourage a standard format?
Independent of Differential and separately from whether we make it
mandatory. It seems developers have to do
git config --global commit.template ~/path/to/better/git_commit.message
, but we could put the file in a MediaWiki project like core
Regards,
--
=S Page WMF
,
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
, code using
ApiResult::getResultData() and not using ApiResult::transformForBC() may
need updating.
Brad, is it OK to use formatversion=2 in extensions running on 1.25?
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l
modules, please do reach out to me.
Let me know off-list how I can help update the docs. To start, I think this
change description should go on the wiki.
[1]
https://wikitech.wikimedia.org/wiki/Incident_documentation/20150428-EventLogging
[2] https://gerrit.wikimedia.org/r/#/c/207297/
--
=S
, Daniel
Let's all welcome them into the Wikimedia family!
Thanks,
Niharika.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
=S Page WMF Tech writer
(),
'mediawiki.ui.button' = array(),
'mediawiki.ui.input' = array(),
'mediawiki.ui.icon' = array(),
'mediawiki.ui.text' = array(),
);
I added this to
https://www.mediawiki.org/wiki/Manual:$wgResourceModuleSkinStyles and
mention this global in Manual:Skinning.
--
=S Page WMF Tech
/Architecture/API#Use_cases
[3] https://www.mediawiki.org/wiki/Extension:Flow/API
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
A reorg that makes sense without TLA buzzword decoding \o/
(Are you sure you didn't leave out the MediaWiki Platform Community API
Core Features Development team :) )
Best wishes and high hopes for y'all.
--
=S Page WMF Tech writer
___
Wikitech-l
as an LXC in a VM on a Mac can be faster than running
Vagrant as its own VM. 8-)
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
] https://github.com/zapty/forever-service
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
.
I added a section Online conversion tools to
https://commons.wikimedia.org/wiki/Help:Converting_video
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
or maybe join the existing
videoconvert tool account).
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
, or both? (And even for the legacy LTS releases 1.23.8 and
1.19.23.)
[1]
https://www.mediawiki.org/wiki/Backward_compatibility#Trunk_extensions.27_compatibility_with_old_MediaWiki_versions
[2] https://www.mediawiki.org/wiki/Extension_registration
--
=S Page WMF Tech writer
On Tue, Jan 20, 2015 at 9:22 AM, Tei oscar.vi...@gmail.com wrote:
a open door to things that can freak us again.
^ world's greatest job title for Brion's business card
Robla wrote
Brion,let me know how I can help!
Ditto.
Great news indeed.
--
=S Page WMF Tech writer
://github.com/CannyComputing/*frontend-mediawiki
https://github.com/CannyComputing/frontend-mediawiki* , or you'd have
separate container for each service. I can't figure out the pricing.
--
=S Page WMF Tech writer
___
Wikitech-l mailing list
Wikitech-l
in Trello to Phabricator, using
string and glue or whatever. I invite anyone else attempting project
migration to https://phabricator.wikimedia.org/T36 and the team practices
mailing list https://lists.wikimedia.org/mailman/listinfo/teampractices
--
=S Page Features engineer
to the title bars of new posts.
We could add a Highlight all posts newer than this to each post's action
menu, but it feels a bit esoteric. User JS or a gadget could easily do it.
Regards,
--
=S Page Features engineer
___
Wikitech-l mailing list
Wikitech
appearance to replace homebrew and jQuery UI dialogs. As I
understand it, besides VE of course Media Viewer has an OOUI dialog in its
Use this file pop-up.
--
=S Page Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
signature below :)
--
=S Page Core features team (not MediaWiki core or platform) engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
tries to
display whatever users gave as the topic title in the page heading,
notifications, recent changes, watchlists, etc. rather than the page title.
Thanks for helping to localize Flow!
--
=S Page WMF Features engineer
___
Wikitech-l mailing list
Node.js programs.
[1] https://www.mediawiki.org/wiki/Extension:Mantle#Developer_features
--
=S Page Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
share dialog uses it.)
Regards,
--
=S Page WMF Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
for
discussion pages.
You can view the diff between revisions of a post, but editing posts is
somewhat rare. Generating a diff of an entire topic with new posts,
updates, hide operations, etc. seems challenging.
--
=S Page Features engineer
___
Wikitech-l
in a [$1 link text] link.
Thanks for any advice,
--
=S Page Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
of
JavaScript inserting the CSS?
[1]
http://stackoverflow.com/questions/15481088/are-unquoted-data-uris-valid-in-css
--
=S Page Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
to *want* it enabled on the talk pages they visit.
--
=S Page Core Features (Flow) engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
code :)
[1] https://www.mediawiki.org/wiki/Extension:Mantle#Templates
[2] https://www.mediawiki.org/wiki/Flow/Architecture/Templating
--
=S Page WikiMedia Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
a template in a new tab just to remind me of its parameters.
--
=S Page Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
be improved further, but the answer is to respond to their
comment with I've filed bug N for that suggestion, and invite them to
remove the -1.
--
=S Page Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
and overt
hostility towards the art of design here (its debatable whether this
actually represents progress, it seems like things have shifted more to
managers at WMF make the decisions, etc.).
Regards,
--
=S Page Features engineer
___
Wikitech-l mailing
#Existing_implementations_in_MediaWiki_extensions
[2] https://www.mediawiki.org/wiki/Flow/Epic_Front-End#Templating
[3] https://www.mediawiki.org/wiki/Multimedia/About_Media_Viewer
--
=S Page Features engineer on the Flow team
___
Wikitech-l mailing list
Wikitech-l
Special:Version says PHP 5.3.10-1ubuntu3.9 (fpm-fcgi) :-(
I've tried killing php5-fpm, restarting apache2, ` sudo /etc/init.d/hhvm
start` etc. More details in
https://bugzilla.wikimedia.org/show_bug.cgi?id=60384
--
=S Page Features engineer
___
Wikitech-l mailing
,
with some app manifest munging might the Firefox app work on them too? At
what point does a Web app become a modern HTML5 web site, or is it vice
versa? :)
[1] https://wiki.mozilla.org/WebAPI#APIs
--
=S Page Features engineer
___
Wikitech-l mailing list
to
extract one file is
$ dpkg --fsys-tarfile /path/to/gsfonts_blahblah.deb | tar xOf -
./usr/share/fonts/type1/gsfonts/n019003l.pfb /tmp/NimbusSansL.pfb
and I sent the files to you on a 3 1/2 floppy ☺
Cheers,
--
=S Page Features engineer
___
Wikitech-l
of MediaWiki, so their font stack was removed. The VectorBeta
feature applies better typography everywhere. It's really nice IMO.
--
=S Page Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo
/18f719ef3d297878e198a864f5bb31dd9cb047af/manifests%2Frole%2Fcoredb.pp
--
=S Page WMF Features engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
it in
https://www.mediawiki.org/wiki/Manual:How_to_debug#PHP_errors :)
--
=S Page software engineer on Editor Engagement Experiments
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Nell + OLPC/Litl nth-gen + (Wikipedia + WikiBooks) + WP:Zero = the Young
Lady's Illustrated Primer: a Propædeutic Enchiridion for us thetes!
( https://en.wikipedia.org/wiki/The_Diamond_Age )
Welcome C. Scott and thanks for all your past, present, and future
contributions.
--
=S Page software
in Category:Not_LTS_ready .
Cheers,
--
=S Page software engineer on Editor Engagement Experiments
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I like Josef Assad's explanation of SMW in place of the big load of
do-not-care on its Wikipedia page :
Semantic Mediawiki allows you to attach properties to wiki pages. And to
query the pages based on these properties.
It doesn't quite capture the elephant (e.g. you add these properties
machine. For those that have access,
https://wikitech.wikimedia.org/wiki/How_to_deploy_code#Test_and_monitor_your_live_code
and https://wikitech.wikimedia.org/wiki/Logs have advice about monitoring
logs and graphs.
--
=S Page engineer on Editor Engagement Experiments
On Thu, Jun 20, 2013 at 12:06 PM, S Page sp...@wikimedia.org wrote:
On Wed, Jun 19, 2013 at 1:36 PM, Brian Wolff bawo...@gmail.com wrote:
just the exception names w/o backtrace should be safe (?))
[20-Jun-2013 18:54:45] Fatal error: Call to a member function getCode() on
a non-object
/docs/structured_data talks
about rich snippets available to custom search (I've never tried it).
[1] like the essential jump to Wikipedia page 'w' bookmarklet
https://en.wikipedia.org/wiki/%s . Why search when you can go direct.
--
=S Page software engineer on E3
don't know the details on the above.
--
=S Page software engineer on Editor Engagement Experiments
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
near the wfRunHooks call it's more likely people will
update it when making changes.
Now that we have mw.hook() in JavaScript we have a second universe of hooks
to think about :)
--
=S Page software engineer on Editor Engagement Experiments
___
Wikitech
Perhaps Ori is pointing out that doxygen (and jsduck) require needless
verbiage. The tools aren't smart enough to infer obvious information from
source on their own (or maybe they are but you're not sure and you see
other comments using these symbols so you copy and paste), so you wind up
:
MyProjRepo% git branch --set-upstream-to origin/master master
MyProjRepo% git branch --set-upstream-to origin/master my_new_feature
etc.
--
=S Page
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo
}}that template add a lot of verbiage to
Extension pages, and should just output a link to a
git.wikimedia.org/summary/ URL and a link to Help downloading an
extension. But I'm not familiar with its history.
--
=S Page software engineer on E3
___
Wikitech-l mailing
|vb|
vb.gui = true
end
end
--
=S Page software engineer on E3
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
).
A big problem with the documents is inconsistent setup. They don't even
agree whether the remote should be called origin, gerrit, or review,
because the experts who add to them have different opinions.
--
=S Page software engineer on E3
___
Wikitech
was different back then, or perhaps there was a
different coding style.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
=S Page software engineer on E3
]])
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
=S Page software engineer on E3
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
#Test_and_monitor_your_live_code
I think we can express best practices better than stay on IRC in case
people yell 'Fire!' (though that's a good start :)
Cheers,
--
=S Page software engineer on Editor Engagement Experiments
___
Wikitech-l mailing list
Wikitech-l
the extension:
http://wikiapiary.com/wiki/Extension:Click_Tracking
Very useful, thanks.
--
=S Page software engineer on Editor Engagement Experiments
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman
has
an up-to-date view of the remote master.
Roan
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
=S Page software engineer on E3
://bugzilla.wikimedia.org/show_bug.cgi?id=46792
--
=S Page software engineer on E3
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
APICreateAccountBeforeCreate
hook.
It would be nice if captcha was always checked on its own hook instead
of sharing a hook with other extensions. That would let a future
validation API run the username past TitleBlacklist and AntiSpoof
without getting shot down by the captcha.
Cheers,
--
=S Page
://wikitech.wikimedia.org/wiki/How_to_deploy_code
--
=S Page software engineer on E3
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
://www.wikidata.org/wiki/Q164757 ! I
assume that other knowledge projects have noticed these entities, and
that Q numbers are becoming a lingua franca. I'm reserving Q42666789
for my talented sure-to-be famous offspring. :-)
Google clearly enjoys the fruits of Wikipedians' hard work.
--
=S Page
community to start using it :-]
Yes, so many facts!
--
=S Page software engineer on E3
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
meeting
buttonlabel=Create a new page for a Human Resources meeting
default=Human Resources/Meetings/{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}
width=40
bgcolor=#f0f0ff
/inputbox
[3] http://en.wikipedia.org/wiki/Template:Search_box and similar.
--
=S Page software engineer on Editor Engagement
.
Thanks for any insight, I'll add it to mediawiki.org.
--
=S Page software engineer on Editor Engagement Experiments
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
what is loading
your module.
If you only want to load the module for certain configurations, that sounds
like a job for $wgExtensionFunctions
-bawolff
On 2013-01-27 8:58 PM, S Page sp...@wikimedia.org wrote:
How can an extension have a soft requirement on a module, so that it
only adds
://translatewiki.net/w/i.php?title=Special%3ATranslationsmessage=Welcomecreationnamespace=8
[5]
https://translatewiki.net/w/i.php?title=Special%3ATranslationsmessage=Welcomecreation-msgnamespace=8
--
=S Page software engineer on E3
___
Wikitech-l mailing list
Wikitech
On Tue, Dec 4, 2012 at 12:17 PM, Amir E. Aharoni
amir.ahar...@mail.huji.ac.il wrote:
2012/12/4 S Page sp...@wikimedia.org:
https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29/welcomecreation_messages
This made me feel very \o/.
Research about current customizations of messages on projects
my `git clone https://github.com/walm/jshint.vim.git`
in ~/.vim/bundle is loaded.
Timo, should we be using .jshintrc per directory or lines like
/*jshint multistr:true */
at the top of files? Or both?
grunt.js build, love it
--
=S Page software engineer on E3
1 - 100 of 113 matches
Mail list logo