Kunal Mehta is a user on mastodon.technology. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Kunal Mehta @legoktm@mastodon.technology

My two WikiConference North America submissions:

wikiconference.org/wiki/Submis - yes, I'm giving away all the secrets.

wikiconference.org/wiki/Submis - if you consider yourself a developer, feel free to add yourself to the list.

Kunal Mehta boosted

We have another #Librem5 progress report for everyone.

"Designing the scope of the Librem 5’s communication apps" by @feeef, our Director of Creative


Kunal Mehta boosted

*wipes a tear from eye*
their first industry kill.
they grow up so fast.

Kunal Mehta boosted

@brennen Telemetry as a decision driver for software development will kill us all.

Kunal Mehta boosted


Across research in Brazil and Indonesia, the team found only one user of the Wikipedia app. Thus, optimizing the mobile site should be a priority for low-awareness communities. For the site, there are lessons to be gleaned from the popularity of browsers such as Opera Mini and UC Browser, which allow users to view data usage and customize preferences for data compression." (Direct link to this section of the summary: meta.wikimedia.org/wiki/Strate.)

Kunal Mehta boosted

I'm #hiring for a Senior Engineer to join an awesome team of Release Engineers here at #Wikimedia:


#remote friendly #job working on #opensource #floss making software better

(plz boost)

Let's take a more muscular public policy stance. But we need to stay rooted in facts. -- Jimmy Wales

New project: Road to +2

We do outreach for newcomers to development, but not really for people who fall in the middle. They're established patch contributors, but not yet maintainers.

The goal is to provide a guide and mentors on how a "middle" contributor can move up and become a maintainer with +2. This is a quick draft, edits welcome!


Katherine's keynote at is about to start - we all have our bingo cards ready!

At WMF staff time is scarce, so we need to automate creation of new projects, as well as making failure/cleanup cheap.

"Delegate to the community where possible" <-- exactly.

Comparison to Stack Exchange's "Area 51" incubator system. Requires dedication and a community to gather, will go through a one year beta process, and then be reviewed by staff on whether it will survive or not.

"Wikidata is an outlier here, though it was conceptualized in 2005."


Sister project incubator - how to deal with knowledge gaps inherent in "What Wikipedia is not" (by Gergo!)

Next talk: "Building tools to serve diverse users: Community Centered Software Development" by WMDE about their technical wishes project.

"Have at least one tech guy/girl and always stay kind with him/her" <-- don't upset your programmers!

Also he noted that it's important to make sure editors are aware of what the bots are doing so they don't duplicate the work. (I think this is a problem on en.wp).

Disambiguation pages that don't exist are auto populated by bots. They don't have descriptions, but it provides a pretty important bootstrap IMO.

It seems easier to have editors add to a page that already has most of the formatting and stuff instead of creating it from scratch.

They also pull external links for social media straight from Wikidata.

I'm sensing a theme here...

They have a bot that adds categories to their articles based on categories on other projects for the same interwiki-linked articles.

Now they import categories straight from Wikidata.

In a talk about building tools to improve content and quality in smaller wikis.