Hello,
messages from marek(a)blahus.cz are held for moderation with reason saying
"Invalid header" in list wikimediacz-l. The list should allow members to
post everything, non-members should be held for moderation. This is the
only address that is problematic.
I've manually approved the post and I checked "hold the message for server
admins". I'm also attaching the message in question in the attachments,
including headers.
Can anybody help me?
Thanks,
Martin
*Martin Urbanec*
IT administrator
+420 602 844 067 <+420%20602%20844%20067>
*Wikimedia Czech Republic*
Web <http://www.wikimedia.cz/> |Facebook
<https://www.facebook.com/Wikimedia.CR> | Twitter
<https://twitter.com/Wikimedia_CR> | Newsletter
<http://wikimedia.us7.list-manage1.com/subscribe?u=24c9403aa67fc995b69c7e704…>
*Hello,We recently announced the new Wikimedia Technical Conference
(TechConf) during the closing session of the Barcelona Hackathon on May 20,
2018. We are sending this email to give an update on the planning and
organization, and to also let everyone know how the nomination process will
work for those interested in attending. The Wikimedia Technical Conference
will take place in Portland, OR, USA on October 22-25, 2018. And, as
mentioned in previous emails [1][2] and on the wiki page [3], this
conference will be focused on the cross-departmental program called
Platform Evolution. We will be providing more information and context as we
go along in the process.For this conference, we are looking for diverse
stakeholders, perspectives, and experiences that will help us to make
informed decisions for the future evolution of the platform. We need people
who can create and architect solutions, as well as those who actually make
decisions on funding and prioritization for the projects.Later this week,
we will send out a form to provide more detailed information on the
nomination process and how to nominate people (or it can be yourself) to
attend this conference, along with the skills, experiences, and/or
backgrounds that we are looking for. Due to the time needed for visa
application and other constraints, the deadline for nominations will be
June 8th. Please make sure that you don’t miss the deadline!If you have any
questions, please post them on the talk page [4][1]
https://lists.wikimedia.org/pipermail/mediawiki-l/2018-April/047367.html
<https://lists.wikimedia.org/pipermail/mediawiki-l/2018-April/047367.html>
[2] https://lists.wikimedia.org/pipermail/wikitech-l/2018-April/089738.html
<https://lists.wikimedia.org/pipermail/wikitech-l/2018-April/089738.html>
[3] https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018
<https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018> [4]
https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018
<https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018> *
*Cheers from the Program Committee:*
*Kate, Corey, Joaquin, Greg, Birgit and TheDJ*
--
deb tankersley
Program Manager, Engineering
Wikimedia Foundation
“Please just assume for the sake of this discussion that (a) I'm willing to abide by the rules of the Code of Conduct, and (b) I don't want the CODE_OF_CONDUCT.md file in my extensions.”
Ok, hear me out here. What if I told you those two things are incompatible? That abiding by the community agreements requires the file as an explicit declaration of said agreement. That is to say, if we had a discussion about amending the CoC to be explicit about this expectation you wouldn’t have issues with including it? Or at least you’d be OK with it?
Yours,
Chris K.
Yaron,
I read over the conversation and would like to posit the question in a
different way.
> Some corporate person, for example, downloading my software, could see that file and think
> that they're bound by the Code of Conduct when sending me a patch, when in fact (for better or worse) they're not.
If the patch is submitted to a Wikimedia technical space (Gerrit) then
the submitter would be expected to follow the community expectations
outlined in the Code of Conduct. This, in my opinion, is a benefit to
you and other extension contributors. The CoC says (paraphrasing), if
you want to participate, great. We do have some things that are
considered unacceptable behavior. We include mention of this in
visible locations where it makes sense so folks are aware.
This should deter most well-reasoned folks from letting the worst of
themselves get the best of them. For those that persist in ignorance
of the expectations of the community, we can show them the door.
This keeps you, and any other individual contributor, from having to
figure out how to respond to anyone being a jerk new again each and
every time. It sets clear expectations for new members of our
community on how we treat each other.
So, the question I would put to you or anyone asking "Why do I have to
have this here?" would be, "Does having the Code of Conduct make my
work in this space easier and more productive?"
In my opinion, yes. Please take a moment and consider this before
deleting anything.
Yours,
Chris Koerner
clkoerner.com
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-06-06
*=2018-06-06=*
== Callouts ==
* Readers Web needs help from RelEng with Ruby to JavaScript Cucumber
refactor: https://phabricator.wikimedia.org/T190710
* There is a new primary deployment host, deploy1001.eqiad.wmnet (tin is
gone).
** Protip: Avoid caring about the host name and just use
deployment.eqiad.wmnet for ssh
* Please take the Beta Cluster survey:
** Announcement:
https://lists.wikimedia.org/pipermail/wikitech-l/2018-May/090049.html
** Survey: https://goo.gl/forms/XgIxXiSi1G5eVHbp2
* Language -> SRE: DBAs Please take a look (again) at:
https://phabricator.wikimedia.org/T189088
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by:
* Blocking:
* Updates:
** 5.8.2 w/ event logging analytics and bug fixes released to public beta (
https://phabricator.wikimedia.org/project/view/3358/ )
** Continuing work on next major release, 6.0 - Feed customization and
design updates ( https://phabricator.wikimedia.org/project/view/3238/ )
==== Android native app ====
* Blocked by:
* Blocking:
* Updates:
==== Readers Web ====
* Blocked by:
** Ruby to JS Cucumber refactor needs help from the RelEng team:
https://phabricator.wikimedia.org/T190710
* Blocking:
* Updates:
** Page issues and A/B test framework continues
https://phabricator.wikimedia.org/T159262
** Page previews post-en/dewiki deploy clean up and bug fixes continues
https://phabricator.wikimedia.org/T192622
** Miscellaneous MobileFrontend / MinervaNeue refactors and maintenance.
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome
1, Objective 4]]: Continue improving the ways that users can download
articles of interest for later consumption
*** Reading Web depends on SRE, RelEng, Reading Infra
==== Readers Infrastructure ====
* Blocked by: n/a
* Blocking: n/a
* Updates:
** Team now includes James F. New contract engineer Mateus Batista Santos
(joining from São Paolo) starts next week.
** Safari browser extension for Reading Lists (
https://github.com/wikimedia/readinglists-extension-safari) to be launched
by end of week.
** Featured feed content availability (by language) endpoint launched.
** Ongoing work with Collaboration to transition maps infrastructure
maintenance to RI beginning next fiscal year.
**
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome
1, Objective 4]]: Continue improving the ways that users can download
articles of interest for later consumption
*** Reading Web depends on SRE, RelEng, Reading Infra
**[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of
client apps by coalescing and moving more logic to the server]]
***Reading Infra depends on Parsing, Services
===== Maps =====
* Blocked by:
* Blocking:
* Updates:
**
==== Multimedia ====
* Updates
** Got rid of reliance for PHP serialization in a GWToolset job
** Looking into OOUI migration for Wikibase
** Working on indexing wikibase statements with quantity qualifiers -
stalled because of holiday
*Quarterly goal dependency update:
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 3.1]] Prepare
for launch of the first Structured Data on Commons feature (multilingual
file captions)
***SDC depends on Multimedia,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 2.1]]
Integrate structured file captions into search
*** SDC depends on Search Platform, Multimedia
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment
4, Outcome 2]]: Develop a better understanding of existing needs for
Structured Commons- T171252
***Research depends on Multimedia
=== Contributors ===
==== Community Tech ====
* Blocked by:
* Blocking:
* Updates:
** GlobalPreferences will go live on Wikipedias as soon as we complete the
final round of bugfixes
** Same for CodeMirror, it's graduating from beta soon
** Working on integrating the Draft namespace into PageTriage
==== Anti-Harassment Tools ====
* Blocked by:
* Blocking:
* Updates:
** DateTime Selector on Special:Block has been deployed globally.
** IP Cookie Blocking is rolling out
** Working on Block Notices on Mobile
** Discussions on Granular Blocks
https://meta.wikimedia.org/wiki/Community_health_initiative/Per_user_page,_…
==== Editing ====
* Blocked by:
* Blocking:
** Updates:
**
==== Parsing ====
* Blocked by:
* Blocking:
* Updates:
** LanguageConverter support (limited to a few vairant languages initially)
in Parsoid will be deployed today (Wed) to help Services team with RESTBase
and API design work on their end.
** Work in Progress update: The current core parser hooks extension API
exposes parsing internals that cannot be supported in Parsoid since those
internals aren’t part of Parsoid. In Parsoid, we are developing a newer API
that can support existing deployed extensions while also not exposing
implementation details.
https://www.mediawiki.org/wiki/Parsing/Parser_Hooks_Stats has info about
what parser hooks are currently used by which deployed extensions (data as
of Oct 2017).
** Planning to replace Tidy everywhere on July 5th. Will send an email
update once this is confirmed.
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.6]]
Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
*** Parsing depends on MediaWiki Platform, Services
**[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of
client apps by coalescing and moving more logic to the server]]
Increase code sharing of client apps by coalescing and moving more logic to
the server.
*** Reading Infra depends on Parsing, Services
**
[[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better
data|Outcome 2: Objective 1]]: Revision storage scaling
*** Services depends on SRE, Parsing
==== Collaboration ====
* Blocked by:
* Blocking:
* Updates:
** Echo multi-DC patches merged, thanks Performance team
** Preparing to graduate RCFilters on watchlist out of beta; code is riding
the train this week, deployment to real wiks won't happen until the week of
June 18
==== Language ====
* Blocked by: DBAs Please take a look (again) at:
https://phabricator.wikimedia.org/T189088
* Blocking:
* Updates:
** Work on ContentTranslation version 2 continue.
** Planning to purge CX draft older than 1 year (See Blocked by)
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.1]] Improve and consolidate our unified editing platform so that it's
great on all devices
***Language depends on Editing
=== Audiences Design ===
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
** OOUI – v0.27.2 released today:
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v…
*** 9 style amendments & 6 feature/code improvement. Among those
**** FieldLayout: Add 'helpInline' config (Prateek Saxena) – This allows to
inline extended help labels, provides an alternative IXD feature for
product managers/designers
**** ActionFieldLayout: Visually combine inputs and their buttons (Volker
E.) https://phabricator.wikimedia.org/T195973
**** WikimediaUI theme: Apply distinct “pill” appearance to tags (Volker E.)
https://phabricator.wikimedia.org/T195257
** Continuing work on Design Style Guide, continuing 'Resources' page with
all repo resources
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** Druid datasources renamed to be usable with SQL querying
** Country + isp info for webrequest_sampled_128 in Druid (turnilo +
superset)
** Making plans on removing IPSec for Kafka communications (with Traffic)
** Helping IOs Team for EvenLogging Schema
** Still working on Wikistats backend resiliency
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
**
=== Fundraising Tech ===
* Blocked by: (scrambling to finish reviews)
* Blocking:
* Updates:
** CentralNotice: fixing some old bugs, still working on backend for new
stats pipeline: https://phabricator.wikimedia.org/T55443
** Audit parsers: update for contributions from main CC processor's new API
is now in review: https://phabricator.wikimedia.org/T195337
** DonationInterface: fixing bugs revealed in 1 hr trial of main CC
processor's new API
** CiviCRM
*** Deploying update to latest core version this afternoon:
https://phabricator.wikimedia.org/T194210
*** Creating our own Civi extension to delete donor data on request:
https://phabricator.wikimedia.org/T195261
*** Fixing some scrambled data from duelling merge jobs:
https://phabricator.wikimedia.org/T194699
*** Creating another Civi extension to charge recurring donations:
https://phabricator.wikimedia.org/T170973
=== MediaWiki Platform ===
* Blocked by:
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.6]] Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
***Parsing depends on MediaWiki Platform, Services
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the
first Structured Data on Commons feature]] (multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 1.1]] Assist
with deploying MultiContent Revisions on Commons
[[phab:T174022|T174022]] Implement multi-content revisions,
[[phab:T174023|T174023]] Implement MCR storage layer,
[[phab:T174045|T174045]] DB schema migration for MCR,
[[phab:T174044|T174044]] Deploy MCR storage layer,
[[phab:T174043|T174043]]Deploy Multi-Content Revisions
***SDC depends on MediaWiki Platform, WMDE
=== Performance ===
* Blocked by:
**
* Blocking:
**
* Updates:
**Investigating performance issues with Chrome 67 (released last week, just
being pushed to end users).
** Performance perception study is continuing (fr/ru/catalan wiki, en
wikivoyages)
** Last jQuery dep in mediawiki.base.js removed, working to separate the
startup js from core js. (Will remove a round trip, and allow us to defer
loading some large JS)
** Echo CR
** Getting our webperf software stack up in beta
** Found an issue with PHP7 memcached module Check-And-Set method, patched
that.
** Additional ChronologyProtector patches
=== Release Engineering ===
* Blocked by:
** N/A
* Blocking:
** Readers Web needs help with https://phabricator.wikimedia.org/T190710
*** zeljkof has been busy with other tasks, however, he will get back to
this task asap.
* Updates
** Please take the Beta Cluster survey:
*** https://lists.wikimedia.org/pipermail/wikitech-l/2018-May/090049.html
*** https://goo.gl/forms/XgIxXiSi1G5eVHbp2
** Heads up: There will be more people in the normal MW Train deployment
rotation (namely: Antoine, Zeljko, and Dan to start) and we'll be doing
some Train deployments during EU hours some weeks. Exact timing TBA (soon).
** Heads up: There is a new primary deployment host, deploy1001.eqiad.wmnet
(tin is gone)
*** Reminder: just use deployment.eqiad.wmnet for ssh
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome
1, Objective 4]]: Continue improving the ways that users can download
articles of interest for later consumption
*** Reading Web depends on SRE, RelEng, Reading Infra
=== Research ===
* Blocked by:
* Blocking:
* Updates:
*Quarterly goal dependency update:
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the
first Structured Data on Commons feature]] (multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment
4, Outcome 2]]: Develop a better understanding of existing needs for
Structured Commons- [[phab:T171252|T171252]]
***Research depends on Multimedia
=== Scoring Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Search Platform ===
* Blocked by:
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the
first Structured Data on Commons feature]] (multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|*Objective 2.1]]
Integrate structured file captions into search
*** SDC depends on Search Platform, Multimedia
=== Security ===
* Blocked by:
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.6]]: Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
***Parsing depends on MediaWiki Platform, Services
=== Services ===
* Blocked by: EchoNotificationJob still not JSON serializable
* Blocking: none
* Updates:
** Videoscalers: jobs switched to kafka, scalers and jobrunners clusters
have been merged
** cirrusSearch jobs were switched, playing with concurrencies and tweaking
settings
** medawiki.revision-score stream exposed with Analytics and ORES teams
** Cassandra upgrade to 3.11.2 ongoing right now, no impact expected
*Quarterly goal dependency update:
**[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of
client apps by coalescing and moving more logic to the server.]]
***Reading Infra/Parsing, Services
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal
3.6]] Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
***Parsing depends on MediaWiki Platform, Services
[[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better
data|Outcome 2: Objective 1]]: Revision storage scaling
*** Services depends on SRE, Parsing
=== Site Reliability Engineering ===
* Blocked by:
** Collaboration on flow dumps
* Blocking:
** None
* Updates:
** Re-scheduled with Services the deployment of proton for Thursday EU
morning
** Deprecation of non PFS ciphers ongoing (PS3 turns out to be an
interestingly old platform)
** Spectre is a gift that keeps on giving, lots of upgrades ongoing
** mcrouter deployed in production
*Quarterly goal dependency update:
**[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome
1, Objective 4]]: Continue improving the ways that users can download
articles of interest for later consumption
*** Reading Web depends on SRE, RelEng, Reading Infra
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the
first Structured Data on Commons feature]] (multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
[[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better
data|Outcome 2: Objective 1]]: Revision storage scaling
*** Services depends on SRE, Parsing
== Wikidata ==
* Blocked by:
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the
first Structured Data on Commons feature]] (multilingual file captions)
***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki
Platform, Research
**[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 1.1]] Assist
with deploying MultiContent Revisions on Commons
[[phab:T174022|T174022]] Implement multi-content revisions,
[[phab:T174023|T174023]] Implement MCR storage layer,
[[phab:T174045|T174045]] DB schema migration for MCR,
[[phab:T174044|T174044]] Deploy MCR storage layer,
[[phab:T174043|T174043]]Deploy Multi-Content Revisions
***SDC depends on MediaWiki Platform, WMDE
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
**
== SoS Meeting Bookkeeping ==
* Updates:
**
Hi all,
over the past 1,5 years WMDE’s Technical Wishes team was working on a major
improvement of wikidiff2 [1] - the engine behind the wikitext diff view.
The major outcome of our improvements got deployed to most wikis just now:
It is now easier to find moved paragraphs and text changes inside them. [2]
Why we worked on this:
The idea for the project arose from the wishlist of the German-speaking
communities: Show text changes in moved paragraphs. Before we worked on
this, moved paragraphs were shown in the diff as a deleted paragraph and
then as an added paragraph. This meant that you had to parse visually
through the paragraphs to find any potential changes - a fact that vandals
liked to make use of. [3]
Desktop version, mobile version
The desktop version of the feature already got deployed to Mediawiki.org
and deWP in December 2017. After further improvements of the diff
algorithm, the change could now get deployed to most wikis. The languages
unified Han, Thai and Japanese that don’t use spaces as delimiters will
follow soon.
The mobile version is in the making and will follow in the next weeks. The
backend work has been done by the WMDE team, the WMF’s mobile team is
taking care of the design work for the user interface of the mobile version.
Improving the algorithm of wikidiff2: More than a new feature
The work that has been done goes further than the original wish: First of
all, we not only highlighted text changes within a moved paragraph, but
also made it easier to find moved paragraphs in the first place: Clickable
arrows allow to follow the move of the paragraph.
Second, we generally improved the diff algorithm: For example, we could
find an old bug in the diff engine: Sometimes two paragraphs which are not
related at all were considered a changed paragraph. The bug fix was already
deployed in October 2017. [4]
If you are interested in learning more about the work that has been done,
we're going to publish the lessons learned by the dev team within the next
days (so stay tuned :-) !.
Thank you!
We would like to thank everyone who supported us in the work around
wikidiff2: People from different wikis looked into diffs and gave us
valuable feedback. Moritz Mühlenhoff supported us by updating the library,
and deploying it. Tim Starling and Max Semenik supported us with code
review and consultation during the Vienna Hackathon. The Desktop and Mobile
Web team is going to add a user friendly design to the mobile version. Your
advice, feedback and support is much appreciated :-)
Further feedback is very welcome!
Birgit (for the technical wishes team)
[1] Extension manual: https://www.mediawiki.org/wiki/Extension:Wikidiff2
[2] Deployment ticket: https://phabricator.wikimedia.org/T195375
[3] Main project page on meta:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Show_text_changes_whe…
[4] Patch on gerrit for the bug fix:
https://gerrit.wikimedia.org/r/#/c/356582/
--
Birgit Müller
Community Communications Manager
Software Development and Engineering
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.
Wikitech-l,
Greetings. I would like to ask about the best way to use conditional logic and branching wiki templates with Wikidata data to vary output upon whether properties are defined for an entity. Scenarios of interest include template-based natural language generation. I’m thinking about reusable Wikipedia templates and the functionalities of projects such as Reasonator (https://tools.wmflabs.org/reasonator/) and AutoDesc (https://tools.wmflabs.org/autodesc).
Thank you,
Adam Sobieski
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. 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 WMDE’s tech team)
--
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.