Page MenuHomePhabricator
Feed Advanced Search

Mon, May 31

Jan_Dittrich added a comment to T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.

From: "How Long Do Wikipedia Editors Keep Active?"

Mon, May 31, 11:45 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich updated subscribers of T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.

Some new pointers (via @MGerlach ):

Mon, May 31, 7:31 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

Tue, May 25

Jan_Dittrich added a comment to T282835: Evaluate use of TypeScript in WVUI.

Barrier to entry: Two thoughts on this.

Tue, May 25, 3:41 PM · Design-Systems-team-board, WVUI
Jan_Dittrich added a comment to T282835: Evaluate use of TypeScript in WVUI.

I believe TypeScript's JSDoc mode does support defining full shapes as well. Right?

Tue, May 25, 3:11 PM · Design-Systems-team-board, WVUI
Jan_Dittrich added a comment to T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.

I am beginning to think that we might need to readjust the definition of when we consider the editor to has left Wikidata as I have proposed it. What do you think? Any ideas?

Tue, May 25, 9:54 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich added a comment to T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.

Also, I have a vague and anecdotal memory that Wikidata has a lot of users who are semi- or fully-automated bots but are not registered as such. Is this the case? If so, is there some other heuristic like overly rapid editing that we can use to filter out these users or analyze them separately?

Tue, May 25, 8:01 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

May 11 2021

Jan_Dittrich updated the task description for T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.
May 11 2021, 2:44 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich renamed T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey from User Retention Wikidata: Exploring the resons for patterns in the 2021 Wikidata Community Survey to User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.
May 11 2021, 2:25 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich updated the task description for T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.
May 11 2021, 2:23 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich updated the task description for T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.
May 11 2021, 2:20 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich updated the task description for T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.
May 11 2021, 2:17 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich updated the task description for T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.
May 11 2021, 2:15 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich assigned T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey to GoranSMilovanovic.
May 11 2021, 2:12 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich created T282563: User Retention Wikidata: A model for "participating since" patterns in the 2021 Wikidata Community Survey.
May 11 2021, 2:02 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

May 10 2021

Jan_Dittrich updated subscribers of T282046: [Session] Modeling the Future of Wikimedia APIs.

People at Wikidata worked on having a part of the API possibilities accessible via REST but we also explored a bit of GraphQL and other ideas. If you are interested, @Silvan_WMDE and @Addshore can probably tell more.
This report has some survey results concerning skills in various API standards of the people from the Wikidata community who answered the survey.

May 10 2021, 7:41 AM · Wikimedia-Hackathon-2021
Jan_Dittrich added a comment to T282111: [Session] Untangling MediaWiki.

@daniel maybe "refactoring Mediawiki" might be more descriptive? I looked at the title and wondered what you want to decouple Mediawiki from.

May 10 2021, 7:33 AM · Wikimedia-Hackathon-2021

Apr 17 2021

Moebeus awarded T139081: Improve usability of rank selector a Like token.
Apr 17 2021, 2:58 PM · Design, WMDE-Design, Wikidata

Apr 14 2021

Jan_Dittrich added a comment to T278746: Design refinements.

Yes, looks great! Thansk

Apr 14 2021, 8:53 AM · Item Quality Evaluator
Jan_Dittrich added a comment to T278746: Design refinements.

1 swapped

Apr 14 2021, 8:17 AM · Item Quality Evaluator

Mar 29 2021

Jan_Dittrich added a comment to T275998: score/scoring explanation.

So, as I learned from a team member the WMF has put up their modal design. They use a right-upper corner x.

Mar 29 2021, 8:42 AM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275998: score/scoring explanation.

Here is the text from the mockup above:

Mar 29 2021, 7:56 AM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275993: access to further info about the tool itself.
Mar 29 2021, 7:50 AM · Wikidata, Item Quality Evaluator

Mar 23 2021

Jan_Dittrich added a comment to T275316: Start with a SPARQL query instead of a list of Item IDs.

It is relevant that the "Assess Quality"-button is in the "box" that also contains the items or SPARQL, respectively; otherwise we might suggest, UI-wise, that the button is bound to all inputs not just what is in the currently activated tab.

Mar 23 2021, 9:28 AM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275316: Start with a SPARQL query instead of a list of Item IDs.
Mar 23 2021, 9:15 AM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275316: Start with a SPARQL query instead of a list of Item IDs.
Mar 23 2021, 9:13 AM · Item Quality Evaluator, Wikidata

Mar 22 2021

Jan_Dittrich added a comment to T275998: score/scoring explanation.

There is no x to keep it easy to use (aka hit with your fingers and find it at an expectable position) on mobile. I could try to find out what Wikit is doing with popups and if they change between mobile and desktop and suggest a matching behavior here.

Mar 22 2021, 3:01 PM · Item Quality Evaluator, Wikidata

Mar 15 2021

Jan_Dittrich added a comment to T270109: Hoover Inequality Score Data Retrival and Calculation.

Looks fine to me!

Mar 15 2021, 3:55 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

Mar 10 2021

Jan_Dittrich added a comment to T270109: Hoover Inequality Score Data Retrival and Calculation.

Plotly already provides for that: if a user zooms in the diagram, an overlay message should pop up …

Mar 10 2021, 11:37 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich added a comment to T270109: Hoover Inequality Score Data Retrival and Calculation.
  • If it is possible to give "human" labels to the variables, and if I understand them right it might be useful to do the following
    • current_year → over last 12 month
    • current_snapshot → over last month
    • history_to_current_snapshot → all time
  • For the diagram it would be great to have a reset button somewhere in case one creates a mess by zooming in or panning away from the graph. Hope that is just a config option.
Mar 10 2021, 9:17 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich added a comment to T270109: Hoover Inequality Score Data Retrival and Calculation.

One variable I did not ask for: current_year – is this from beginning of the calendar year to the current snapshot or from the snapshot 12 months ago until the current snapshot?

Mar 10 2021, 9:04 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

Mar 3 2021

Jan_Dittrich added a comment to T275995: expand result list by default.

This would look like this:

Mar 3 2021, 10:46 AM · Item Quality Evaluator, Wikidata
Jan_Dittrich moved T275991: Add Wikidata logo from Done to Needs design on the Item Quality Evaluator board.
Mar 3 2021, 9:59 AM · Wikidata, Item Quality Evaluator
Jan_Dittrich reopened T275991: Add Wikidata logo as "Open".

Is there some (implicit) standard where the logo should be?
Currently is it as big as on Wikidata itself, on the right side and linked to Wikidata. So currently is has undue weight.

Mar 3 2021, 9:59 AM · Wikidata, Item Quality Evaluator
Jan_Dittrich added a comment to T275313: Download results as CSV for further processing.

I am generally fine with not providing them but afaic we make at least two mathematically dubious steps so I would have the tendency to be transparent. We could also explain how the score is created in the help file, though.

Mar 3 2021, 9:37 AM · Item Quality Evaluator, Wikidata

Mar 2 2021

Jan_Dittrich added a comment to T275629: Ensure the user that the app did not crash while data is retrieved.

Discussion about error messages to T276236

Mar 2 2021, 4:05 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich created T276236: meaningful error messages in case of API- or Parsing-Problems.
Mar 2 2021, 3:25 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich added a comment to T275629: Ensure the user that the app did not crash while data is retrieved.

Can we distinguish the problems? Cause then we could have:

Mar 2 2021, 2:33 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich added a comment to T275998: score/scoring explanation.

I considered the flyout, but it turns out to be harder to integrate in existing layouts, so I went ahead with a popup.

Mar 2 2021, 2:10 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275629: Ensure the user that the app did not crash while data is retrieved.

Isn’t the most likely reason for an error that the WiFi is flaky?

Mar 2 2021, 12:25 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich created T276203: Favicon is smudged.
Mar 2 2021, 9:52 AM · Wikidata, Item Quality Evaluator
Jan_Dittrich added a comment to T275993: access to further info about the tool itself.

Where should the links go? Wikimedia Deutschland e.V.,
Github project and github issues?

Mar 2 2021, 9:49 AM · Wikidata, Item Quality Evaluator
Jan_Dittrich renamed T275993: access to further info about the tool itself from access to further info to access to further info about the tool itself.
Mar 2 2021, 9:47 AM · Wikidata, Item Quality Evaluator
Jan_Dittrich added a comment to T275995: expand result list by default.

If our primary target group is editors, then we could just show the whole table directly and I put all relevant information and action above the table so nothing is pushed into invisibility.

Mar 2 2021, 9:40 AM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275998: score/scoring explanation.

We could have a "How is this score calculated" flyout and put all info about ORES, difference between the things items refer to and the content of the items themselves etc. inside there.

Mar 2 2021, 8:55 AM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275629: Ensure the user that the app did not crash while data is retrieved.

Lets split the "other developers should be able to report problems" in a separate ticket; as we should do with "have a error message that provides helpful guidance to problem solving (for non-developers)"

Mar 2 2021, 8:53 AM · Wikidata, Item Quality Evaluator

Mar 1 2021

Jan_Dittrich added a comment to T275629: Ensure the user that the app did not crash while data is retrieved.

This may be problematic for users who don't have Github but would like to get your thoughts anyway.

Mar 1 2021, 12:25 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich added a comment to T275998: score/scoring explanation.

Currently we have

Mar 1 2021, 12:21 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275629: Ensure the user that the app did not crash while data is retrieved.

Not yet. I think we should solve this with T275993.

Mar 1 2021, 10:11 AM · Wikidata, Item Quality Evaluator
Jan_Dittrich added a comment to T275629: Ensure the user that the app did not crash while data is retrieved.

That makes sense.

Mar 1 2021, 9:29 AM · Wikidata, Item Quality Evaluator

Feb 24 2021

Jan_Dittrich created T275629: Ensure the user that the app did not crash while data is retrieved.
Feb 24 2021, 2:38 PM · Wikidata, Item Quality Evaluator

Feb 22 2021

Jan_Dittrich updated the task description for T275313: Download results as CSV for further processing.
Feb 22 2021, 3:59 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275313: Download results as CSV for further processing.

Ideally, the table would give the item label, item QId, weighted ORES Score and the ORES-probabilities for a score of 1,2,3,4,5:

Feb 22 2021, 3:58 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich moved T275312: error handling: no score can be retrieved from Needs design to Ready to discuss on the Item Quality Evaluator board.
Feb 22 2021, 3:54 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275312: error handling: no score can be retrieved.
Feb 22 2021, 3:53 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275312: error handling: no score can be retrieved.
Feb 22 2021, 3:51 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich moved T275315: error handling: allow only Item IDs from Needs design to Ready to discuss on the Item Quality Evaluator board.
Feb 22 2021, 3:50 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275315: error handling: allow only Item IDs.

Suggestion: ADD: an error is shown when providing anything but an Item ID. There is an error pointing out each of the offending inputs, rather than only the first one. (at least up to, lets say, 10 Errors or so)

Feb 22 2021, 3:45 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275315: error handling: allow only Item IDs.

Depending on the "cost" of queries and checking we might either show the evaluation results on the input page (1) or on the results page (2)

Feb 22 2021, 3:44 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275315: error handling: allow only Item IDs.
Feb 22 2021, 3:43 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich moved T275311: Make the result actionable from Needs design to Ready to discuss on the Item Quality Evaluator board.
Feb 22 2021, 3:42 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275311: Make the result actionable.

Suggestion: DELETE "a call to action exists that asks the editor to improve the worst Items"
Suggestion: ADD "The table is inserted in the page as-it-is, meaning rather than the table having a scrollbar, the page grown in length. (This is less sensitive to design changes in the future)

Feb 22 2021, 3:41 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275311: Make the result actionable.
Feb 22 2021, 3:39 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich added a comment to T275311: Make the result actionable.

As suggested in the meeting, I would not provide a separate text or so for it, but go by a "show-don’t-tell"-approach that makes the actual improvement of the times easy by linking them in the table and enabling to sort the table easily.

Feb 22 2021, 3:39 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich moved T275307: Put the result in context from Needs design to Ready to discuss on the Item Quality Evaluator board.
Feb 22 2021, 3:37 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich moved T275306: Calculate the average score for all Items from Needs design to Ready to discuss on the Item Quality Evaluator board.
Feb 22 2021, 3:37 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275307: Put the result in context.
Feb 22 2021, 3:37 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275306: Calculate the average score for all Items.
Feb 22 2021, 3:37 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275306: Calculate the average score for all Items.
Feb 22 2021, 3:29 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich moved T275305: Get the quality score for several Items from Needs design to Ready to discuss on the Item Quality Evaluator board.
Feb 22 2021, 3:28 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich updated the task description for T275305: Get the quality score for several Items.
Feb 22 2021, 3:27 PM · Item Quality Evaluator, Wikidata
Jan_Dittrich moved T275304: Get score for one Item from Needs design to Ready to discuss on the Item Quality Evaluator board.
Feb 22 2021, 3:27 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich moved T275302: intro to the tool from Needs design to Ready to discuss on the Item Quality Evaluator board.
Feb 22 2021, 3:26 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich updated the task description for T275302: intro to the tool.
Feb 22 2021, 3:26 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich moved T275302: intro to the tool from Ready to discuss to Needs design on the Item Quality Evaluator board.
Feb 22 2021, 3:24 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich moved T275302: intro to the tool from Needs design to Ready to discuss on the Item Quality Evaluator board.
Feb 22 2021, 3:24 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich updated the task description for T275304: Get score for one Item.
Feb 22 2021, 3:24 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich added a comment to T275304: Get score for one Item.

If I understand it correctly, we will not build an interface getting the score specifically for one item, thus I wouldn’t/couldn’t not provide a mockup.
In this case the BBD criteria would need to be adjusted to work abstractly without UI.

Feb 22 2021, 3:23 PM · Wikidata, Item Quality Evaluator
Jan_Dittrich updated the task description for T275379: Add privacy statement link to Wikidata Community Survey Banner.
Feb 22 2021, 12:18 PM · WMDE-FUN-Sprint-2021-02-22, WMDE-Fundraising-Tech, WMDE-FUN-Team
Jan_Dittrich created T275379: Add privacy statement link to Wikidata Community Survey Banner.
Feb 22 2021, 12:18 PM · WMDE-FUN-Sprint-2021-02-22, WMDE-Fundraising-Tech, WMDE-FUN-Team
Jan_Dittrich added a comment to T275304: Get score for one Item.

If I understand it correctly, we will not build an interface getting the score specifically for one item, thus I wouldn’t/couldn’t not provide a mockup.
In this case the BBD criteria would need to be adjusted to work abstractly without UI.

Feb 22 2021, 9:11 AM · Wikidata, Item Quality Evaluator

Feb 15 2021

Jan_Dittrich added a comment to T274779: Wikidata Community Survey Banner: Change "Deutschland"→ "Germany".

True as well.

Feb 15 2021, 1:03 PM · WMDE-FUN-Team
Jan_Dittrich created T274779: Wikidata Community Survey Banner: Change "Deutschland"→ "Germany".
Feb 15 2021, 12:28 PM · WMDE-FUN-Team
Jan_Dittrich created T274755: Illustration in Wikidata Community Survey Banner not crisp.
Feb 15 2021, 9:20 AM · WMDE-FUN-Team

Feb 8 2021

Jan_Dittrich added a comment to T270109: Hoover Inequality Score Data Retrival and Calculation.

Thanks!
Just to understand it correctly – what do the 3 values refer to, particularly, are they from beginning of time until some point ("wealth") or for a specific timeframe ("income")?

Feb 8 2021, 8:38 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

Feb 1 2021

Jan_Dittrich updated subscribers of T270109: Hoover Inequality Score Data Retrival and Calculation.

The dashboard for this can be produced in a minimal time. It will be included to our Wikidata Analytics portal, under "Analytics", if you agree.

Feb 1 2021, 1:01 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata
Jan_Dittrich added a comment to T270109: Hoover Inequality Score Data Retrival and Calculation.

If I understand you correctly, you can/did calculate scores based on

Feb 1 2021, 12:01 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

Dec 14 2020

Jan_Dittrich created T270109: Hoover Inequality Score Data Retrival and Calculation.
Dec 14 2020, 3:21 PM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

Dec 9 2020

Jan_Dittrich added a comment to T195033: Contribution inequality graphs for Wikistats.

Thanks – that’s great! I created the calculation in JavaScript but did not have an R version yet.

Dec 9 2020, 1:14 PM · Product-Analytics, Contributors-Analysis, Analytics-Wikistats, Analytics

Dec 1 2020

Jan_Dittrich added a comment to T266960: investigate sharing of query builder queries via URL [timebox: 4h].

Just a reminder from user research: Participants love a sharing option; the problem with storing state in URLs is that the data that the URL can carry was, at least for some the handwritten requests, rather limited and people started to code-golf their queries.

Dec 1 2020, 9:53 AM · Wikidata Query Builder (Wikidata Query Builder - sprint 6), Wikidata
Jan_Dittrich closed T267635: Get 2020 user/editcount data to determine count at percentiles as Resolved.

Again, please: did we resolve this one?

Dec 1 2020, 9:08 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

Nov 24 2020

Jan_Dittrich added a comment to T195033: Contribution inequality graphs for Wikistats.

I calculated the hoover index for some contribution metrics recently and it was rather easy to do using a table with the columns edit count | count of accounts with this edit count which has somewhat between 100 and 1000 rows. Hoover also seems to be rather easy to understand, working without area-under-the-curve and varies between 0 (all equal) and 1 (maximum unequal).

Nov 24 2020, 4:52 PM · Product-Analytics, Contributors-Analysis, Analytics-Wikistats, Analytics
Jan_Dittrich renamed T207406: Recommendation API: resolve interlanguage conflicts from Recommendation API: resolve interlanguage confclits to Recommendation API: resolve interlanguage conflicts.
Nov 24 2020, 3:49 PM · Recommendation-API, Research-Backlog
Jan_Dittrich added a comment to T205014: Data input: Forms for Item Entry.

See related T217233 (Implement Model Items on Wikidata)

Nov 24 2020, 3:46 PM · wdwb-tech, Wikibase-Containers, Wikidata, Federated-Wikibase-Workshops@NewYork-2018
Jan_Dittrich added a comment to T217233: Implement Model Items on Wikidata.

See related T205014 (Data input: Forms for Item Entry)

Nov 24 2020, 3:45 PM · WMSE-Tools-for-Partnerships-2020, User-John_Cummings

Nov 17 2020

Jan_Dittrich added a comment to T205014: Data input: Forms for Item Entry.

On this issue, the research with GLAM partners might be interesting, as many voiced problems with data modeling. See the Report, Chapter "There is no obvious way to get your data into Wikidata 'the right way'", page 11ff.

Nov 17 2020, 12:25 PM · wdwb-tech, Wikibase-Containers, Wikidata, Federated-Wikibase-Workshops@NewYork-2018

Nov 10 2020

Jan_Dittrich created T267635: Get 2020 user/editcount data to determine count at percentiles .
Nov 10 2020, 11:59 AM · User-GoranSMilovanovic, WMDE-Analytics-Engineering, Wikidata

Oct 28 2020

Jan_Dittrich added a comment to T194748: Research: How are bot edits different than human edits on Wikidata?.

I'd still be interested in case resources are allocated to this.

Oct 28 2020, 8:08 AM · Wikidata, User-GoranSMilovanovic, WMDE-Analytics-Engineering

Oct 14 2020

Jan_Dittrich added a comment to T264733: Include a mini sample project that shows use of component, CSS, Tokens.

What you mean is clear but any concrete example exhibits the problem that it would showcase (and thus, arguably, favor) the use of one particular technology

Oct 14 2020, 11:44 AM · Wikidata, Wikidata Design System
Jan_Dittrich added a comment to T264733: Include a mini sample project that shows use of component, CSS, Tokens.

It always was assumption that the "Show code" link…

Oct 14 2020, 10:15 AM · Wikidata, Wikidata Design System

Oct 7 2020

Jan_Dittrich added a comment to T264733: Include a mini sample project that shows use of component, CSS, Tokens.

…I did write the original issue on github, in case anyone has questions.

Oct 7 2020, 8:07 AM · Wikidata, Wikidata Design System