Hello,
If you are using the python linter "flake8", a new version has been
released today.
If your dependency is unbound, CI will pick up the new version (3.6.0)
which will most probably report new errors and breaks the build.
You can either fix the lint issues, or set an upper bound to the version
with:
flake8<=3.6.0
Ref:
https://pypi.org/project/flake8/#history
--
Antoine Musso
Google Code-in 2018 just started:
https://www.mediawiki.org/wiki/Google_Code-in/2018
You might remember the announcement email from a few weeks ago.[1]
In the next seven weeks, many young people are going to make their
first contributions to Wikimedia. Expect many questions on IRC and
on mailing lists by newcomers who have never used IRC or lists
before. Your help and patience is welcome to provide a helping hand!
Thanks to all mentors who have already registered & provided tasks!
You have not become a mentor yet? Please consider it!
For the full info, please check out
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
and ask if something is unclear.
Thank you again for giving young contributors the opportunity to learn
about and work on all aspects of Free & Open Source Software projects.
Now bring your tasks! :)
Cheers,
andre
[1] https://lists.wikimedia.org/pipermail/wikitech-l/2018-September/090799.html
--
--
Andre Klapper | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on
#wikimedia-tech.
Question can be asked in English & German.
The Technical Advice IRC Meeting is a weekly support event for volunteer
developers. Every Wednesday, two full-time developers are available to help
you with all your questions about Mediawiki, gadgets, tools and more! This
can be anything from "how to get started" over "who would be the best
contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Hi Lodewijk,
I want to encourage people to feel comfortable with posting in-scope and
civil emails to WMF mailing lists, but my personal opinion is that the
number of reminders is sometimes excessive and the related costs are
non-trivial.
My view is that excessive reminders about meetings have recently been
especially afflicting Wikitech-l, but have also taken place on Wikimedia-l
periodically.
If we multiply the quantity of seconds that the average person spends
clicking or scanning through a reminder email by (1) the number of
recipients and (2) the average hourly value of recipients' time, I don't
know what the total costs (in money and time) would be but I think that
they would be non-trivial.
I think that I'm being reasonable in requesting that people make
announcements about most one-time meetings 14 days in advance.
However, I seem to be a minority of one. And speaking of time management,
my guess is that there are hundreds or thousands of other busy people on
these mailing lists who might not appreciate my continuing to press this
subject, so I'm moving on.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
On Sun, Oct 21, 2018 at 11:34 PM effe iets anders <effeietsanders(a)gmail.com>
wrote:
> Hi Pine,
>
> I would also suggest not to get overly bureaucratic with this :) If the
> public meeting you refer to requires a large attendance, the 14 days makes
> sense for example - but I cannot recall many meetings of that style.
> Rather, most meetings are either scheduled taking the availability of
> participants in mind, or it is to get input (where it is more important to
> have a bunch of people show up, than to have everyone participate).
>
> Whether more than one reminder is excessive, is imho quite subjective. I
> appreciate most reminders, especially if they stick to the same thread.
>
> On a side note: are there any weekly meetings being announced on this list?
> Again, it highly depends on the topic, and whether the reminder may also
> contain more information.
>
> My point? Don't worry about it so much :) Be flexible with this, and go
> with the flow. People can figure this out quite well if they use their
> common sense without added bureaucracy.
>
> Lodewijk
>
>
I've heard little support for new norms regarding reminders and
announcements of deadlines on Wikimedia-l and Wikitech-l, so I withdraw my
proposal. I may revisit this subject in the future.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
Hi,
just wondering what the situation is with
$wgVisualEditorParsoidForwardCookies these days. The documentation for
visual editor says that it's needed if you have a wiki that's not
editable by the public. But I've just set it up on such a wiki and
editing/saving an article through visual editor works fine without me
having set this or allowed anonymous edits by localhost. Is there no
longer any need to worry about settings specifically for locked down wikis?
Thanks,
Aran
I would like to share, for discussion, some knowledge representation ideas with respect to a URL-addressable predicate calculus.
In the following examples, we can use the prefix “mw” for “https://machine.wikipedia.org/” as per xmlns:mw="https://machine.wikipedia.org/" .
mw:P1
→ https://machine.wikipedia.org/P1
mw:P1(arg0, arg1, arg2)
→ https://machine.wikipedia.org/P1?A0=arg0&A1=arg1&A2=arg2
mw:P2
→ https://machine.wikipedia.org/P2
mw:P2<t0, t1, t2>
→ https://machine.wikipedia.org/P2?T0=t0&T1=t1&T2=t2
mw:P2<t0, t1, t2>(arg0, arg1, arg2)
→ https://machine.wikipedia.org/P2?T0=t0&T1=t1&T2=t2&A0=arg0&A1=arg1&A2=arg2
Some points:
1. There is a mapping between each predicate calculus expression and a URL.
2. Navigating to mapped-to URLs results in processing on servers, e.g. PHP scripts, which generates outputs.
3. The outputs vary per the content types requested via HTTP request headers.
4. The outputs may also vary per the languages requested via HTTP request headers.
5. Navigating to https://machine.wikipedia.org/P1 generates a definition for a predicate.
6. Navigating to https://machine.wikipedia.org/P2?T0=t0&T1=t1&T2=t2 generates a definition for a predicate after assigning values to the parameters T0, T1, T2. That is, a definition of a predicate is generated by a script, e.g. a PHP script, which may vary its output based on the values for T0, T1, T2.
7. The possible values for T0, T1, T2, A0, A1, A2 may be drawn from the same set. T0, T1, T2 need not be constrained to be types from a type system.
8. The values for T0, T1, T2, A0, A1, A2, that is t0, t1, t2, arg0, arg1, arg2, could also each resolve to URLs.
Best regards,
Adam Sobieski
http://www.phoster.com/contents/