Yeah might be wise to at least reach out to en.wp and de.wp. Or maybe Tech
News even ?
DJ
On Wed, Dec 12, 2018 at 6:45 PM Andre Klapper
wrote:
> On Wed, 2018-12-12 at 14:39 +0100, Derk-Jan Hartman wrote:
> > This is just another small reminder that, because the servers which host
> >
On Thu, Dec 13, 2018 at 9:24 AM Derk-Jan Hartman <
d.j.hartman+wmf...@gmail.com> wrote:
> Yeah might be wise to at least reach out to en.wp and de.wp. Or maybe Tech
> News even ?
>
"Hey folks, this might not work in the future" could be reason enough to
include it in Tech News, yes.
//Johan
> […] why the tag parameter follow= is not turned off in wiki sites that
> are not wikisource?
As the Technical Wishes team at Wikimedia Germany is currently working
on the Cite extension, I had a look to find an answer to your
question.
The follow="…" feature was introduced in 2010[1] as part
I'm pleased to announce that MediaWiki 1.32.0-rc.1 is now ready for testing.
Links to the archives, signatures and keys relevant to this release are at
the end of this
message.
There have been a few changes[1] since the previous release candidate.
Unless we discover new
blocking bugs in this
Thank you.
But even so, what about the weird order of precedence? I really do not like
that this code actually works:
text1{{citetext3|title=google|url=
http://google.com}}text5
Or it's implemented like this in purpose?
Igal
בתאריך יום ה׳, 13 בדצמ׳ 2018 ב-12:58 מאת Thiemo Kreuz <
Hi DJ,
Out of curiosity, what all would be involved in the OS change?
The bike layers could be a nontrivial loss for some folks.
If no regular WMF staff are available for the OS changes and ongoing
maintenance, and if the use of bike lanes (or other features) is
significant in the opinion of
The wikitext snippet you posted appears to be seriously broken. More
precisely: It is unbalanced. Technically, there is no such thing as
"broken" wikitext. The parser will always output something (as he does
in the example). However, this doesn't mean such wikitext is ok. Sure,
nobody is stopping
I have a wikitech account, checked through the userlist and wrote mails to the
admins who listed their mails and assuming I get access I'll use puppet. I'll
update the conversation if I get word back from them.
alexan...@vassilevski.com
‐‐‐ Original Message ‐‐‐
On Thursday, 13 December
You'll basically need to create a wikitech account (if you don't already
have one) and convince one of the existing project admins (listed at
https://tools.wmflabs.org/openstack-browser/project/maps) to add you.
Please use Puppet instead of manually setting up servers by hand.
On Thu, 13 Dec 2018
I have some free time this December and I could manually create the new vm's
and replicate the configs/installs by hand on newly created Ubuntu 18 vm's (
after figuring out how the old ones are installed and configured and if given
access, of course .. ).
Keep in mind that I'm new to
On Thu, Dec 13, 2018 at 9:36 AM Johan Jönsson
wrote:
> On Thu, Dec 13, 2018 at 9:24 AM Derk-Jan Hartman <
> d.j.hartman+wmf...@gmail.com> wrote:
>
>> Yeah might be wise to at least reach out to en.wp and de.wp. Or maybe Tech
>> News even ?
>>
>
> "Hey folks, this might not work in the future"
I think I was not clear enough. I know the code is broken, and I know noone
should use it. I show it as a symptom of the system problem - wrong
precedence order implemented in the parser.
Igal
בתאריך יום ה׳, 13 בדצמ׳ 2018 ב-19:03 מאת Thiemo Kreuz <
thiemo.kr...@wikimedia.de>:
> > I
N3: The lonk you provides expects the transclusion (preprocessor 3.4)
before tags (processor 2.2). So the follow parameter behavior is broken.
Igal
בתאריך יום ה׳, 13 בדצמ׳ 2018 ב-18:25 מאת יגאל חיטרון <
khit...@post.bgu.ac.il>:
> The problem is the precedence, once again. I expect from the
I don't think WMF should be hiring contractors purely for the purpose of
supporting individual tools which are not in production.
On Thu, 13 Dec 2018 at 15:46, Pine W wrote:
> Hi DJ,
>
> Out of curiosity, what all would be involved in the OS change?
>
> The bike layers could be a nontrivial
> I expect from the parser to parse wiki markup before parsing html tags […]
As I said. As neither the wiki markup nor the XML tags in the given
example are valid, one can't expect anything. Seriously. Code like
{{cite|}} is just broken. It's like having two nested Klein
bottles. Both structural
The problem is the precedence, once again. I expect from the parser to
parse wiki markup before parsing html tags, because templates can create
new tags by transclusion. If the ref tag is parsed first, glueing the
unbalanced parts to one proper template call, that means that (1) the
template can't
On Thu, 2018-12-13 at 07:46 -0800, Pine W wrote:
> Out of curiosity, what all would be involved in the OS change?
See https://wikitech.wikimedia.org/wiki/News/Trusty_deprecation
Cheers,
andre
--
Andre Klapper | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
Hello All,
We've opened the feedback cycle for the current Code Stewardship
Review candidates. They include:
CodeReview extension[0]
UserMerge extension[1]
Graphoid service[2]
Feedback can be provided via the talk pages for each of the items
under review and/or their associated Phabricator
18 matches
Mail list logo
