Better late than never, I finally got around writing up my time at the hackathon: https://luciekaffee.github.io/posts/2012/08/2019-05-19-wikimedia-hackathon-prague/

Prototype video: https://youtu.be/VWeQwhkzvEw
Code on GitHub: https://github.com/ISNIT0/mediawiki-scribe
User script on Czech Wikipedia: https://cs.wikipedia.org/w/index.php?title=Wikipedista:Ondrej.merkun/common.js

I'd suggest splitting (at least the nt dump as I work mostly with those and therefore have an opinion on that side) in the following:

Hi @DarTar and @Halfak as you mentioned me in the previous task, I'm here to have all the conversations :)
The work Aaron mentioned, that I presented at OpenSym is this one: http://dl.acm.org/citation.cfm?id=3125465
I'm generally working on under-served languages, Wikidata, and all the fun things around that (and especially the overlap of the two topics).

I agree. Since there's no active discussion here, it might be appropriate to find another medium for a discussion- maybe there's interest to do a follow up based on our conclusion from last time to file specific actions?
The next event would probably be Wikimania?

I changed the documentation, but I would like someone else to have a look and close the task if it is sufficient as kind of a "review"

Basically, my patch just removes the text, because it doesn't give a lot of value to the page anyway. (It also does a lot of other things to make the site prettier :) )

Make ArticlePlaceholder grid layout great again!

Certainly needed. We need to fix https://phabricator.wikimedia.org/T152958 first though

To answer all of those to my best knowledge at once:

• bzip2 should be fine
• Including property definitions will most likely be very handy, though I am not sure what that means exactly- it just includes all statements for properties? Than yes!
• Version info absolutely
• Normalized values make a lot of sense
• Not sure what resolved entities should therefore I can't say whether it makes sense

I would suggest the following pattern as meta description:

Ah, the extension is indeed a bit hidden, we should push it more. Maybe it would be helpful to link it on the installation page?

The results from the group works are in the etherpad here: https://etherpad.wikimedia.org/p/devsummit17-diversity
Feel free to add things

I am afraid it is not possible to connect to wikidata.org.
However, you could import test data from Wikidata to your Wikibase repository with the extension https://github.com/filbertkm/WikibaseImport
Thanks for working on this!

Since we didn't take notes, I will do a write-up of the session next week and add it here or in an etherpad to keep the discussion going.

Sounds great! Another thing, I have on my todo list since forever is to add a list of Wikipedias, where the extension is deployed. They are all mentioned here for example: https://grafana.wikimedia.org/dashboard/db/article-placeholder

@MtDu The edits are pretty nice already, but if anyone could go further over the text and improve it in general, that would be amazing. I don't think it's really helpful as is.
Thanks!

@Qgil, sorry for the delay. I am planning the workshop at the moment. Since I don't want it to be top down, I would like to have space for people to walk around and exchange, so it would be good if the room could provide that.
I am not sure if the filming will make sense, since it will be a lot of working in groups and discussing. However, since I want to conclude with a presentation of the findings and the actions that will be taken as a following step, there might be a chance to film that part. It will be pretty hard to properly contribute remotely since it's mainly face to face discussions.
I need a few materials for the workshop: post-its, enough sharpies for everyone to write on the post-its, a big timer, dot stickers, and multiple (depending on number of attendees) flip charts. I assume it would make more sense if you could provide those rather than bringing that from Germany.

Even though this is closed, we should open a ticket to observe whether it actually changes anything.

A room where everyone can speak freely, we have chairs and tables we can arrange in groups for people to work together would be good I. We will probably only have a short intro and presentation of ideas, so no need for a theater style room.

Can't reproduce the error anymore.

@Qgil I fully agree. It might be worth to prepare a proper workshop with questions to solve then rather than just having a discussion round? I did something similar with @Juscwmde and @Incabell at viewsource, but the scope was too big (multiple people from various projects), it could be worth to prepare a similar workshop focusing on growing the diversity of the MediaWiki community.

We could think about merging it with the diversity proposal if no one feels responsible. I am very interested in both, but I am happy if someone with more experience feels like picking it up.

Wow, that's weird, it's coming from the getLanguageCode() call on a site object. And the same item works here: https://ht.wikipedia.org/wiki/Espesyal:AboutTopic/Q15905 Might be worth opening an investigation ticket for this to not lose track of it.
Same for the number localization.
Thank you so much!

@Juscwmde is working on the evaluation of the event at them moment btw. I will try to wrap up some of the things we got as a feedback for the summit if it fits in this context or any other.

So far I mainly thought of the parts of this including people. Even though I agree with Quim, that we are not directly aiming at teaching programming languages, I think there is an important question we can draw from that: What technologies can be used and how in order to make our community more accessible for a bigger group of people? Is there any technologies we should improve, new ones to use or old ones to use less to engage more people?

@hoo anything happening on this one?

I'll wait before abandoning my patch though until this becomes relevant again in case we can reuse parts of it.

@hoo do you have the rights to create such a page on Wikidata? Or should I chase someone doing that for us?
I just remember, we should probably open a task to propagate that the ordering can be changed IIRC none touched any of the MediaWiki:Wikibase-SortedProperties on the Wikis yet. (Should wait with the promotion until it's centralized though.)

Even though I prefer #2 for aesthetic reasons, I think @thiemowmde makes a very good point here for option #1. So I'd suggest to go with #1, too.

It would be great to not expose the word snak anymore. I think it's pretty confusing for people using the Lua functions not being familiar with the internal structure. Anyway, formatValues() sounds good to me, too!

So, our event (Ladies That FOSS in Berlin) happened ~ two weeks ago for the first time ever. It was great, and even though we don't have any evaluation (yet), there are some things, that I can certainly summarize, that has been at least for me true.

Right! IIRC @01tonythomas is involved with Outreachy (and might be at the summit, too?), would be great to have someone participating who's involved (as mentor or organizer) with GSoC. In general, would be great if someone could ping the people, who mentored in the recent years to share what worked and didn't work.

I discussed with Lydia recently that we should set a higher limit of number of statements/sitelinks in the items to be an indexing placeholder.
For the start, we should consider to not index more than 5000 placeholder and see how that works.

So far the plan is for it to be very similar to https://en.wikipedia.org/wiki/Special:AllPages even without the top part that let's you filter things. It's mainly for search engines to find the placeholder pages.
It can be found on the https://en.wikipedia.org/wiki/Special:SpecialPages
The notability criteria is set in the source code and is not editable by the community (atm it's an item has to have at least 2 sitelinks and 3 statements to be notable)