Thanks, everyone who expressed interest in attending the GSoC mentor summit!

• Link to the PDF with trainer notes: https://drive.google.com/file/d/1Run9C774m2ZPap8UK-D-0PIGK5HkuLno/view?usp=sharing (via Google Drive).
• Link to the PDF source (via Google Slides): https://docs.google.com/presentation/d/1vG1oAYuEVRU_sXFMLrX7IHroMNNSjQyKFJwY2Q6AqgM/edit.

Update >Wikimedia APIs toolkit is ready, and in it MediaWiki Action API, Wikidata and Wikimedia Commons are covered. Link to the PDF and source files are here:
https://drive.google.com/file/d/1Run9C774m2ZPap8UK-D-0PIGK5HkuLno/view?usp=sharing. https://docs.google.com/presentation/d/1vG1oAYuEVRU_sXFMLrX7IHroMNNSjQyKFJwY2Q6AqgM/edit. I will be uploading them to Wikimedia Commons soon.

@Ladsgroup Yes, please! Go ahead and enable it for some on MediaWiki.org. Is it okay if @Jayprakash12345 creates a topic on https://www.mediawiki.org/wiki/Project:Current_issues and seek any feedback or concern on enabling the Gadget for everyone??

I've updated the script on test wiki with the changes @Jayprakash12345 has made. https://test.wikipedia.org/wiki/MediaWiki:Gadget-tabbedwindow.js.

Thanks, @Ladsgroup for your helpful feedback. I am not sure what the implications on performance would be, but I am wondering if for Gadgets we recommend adding dependencies in the Gadget definition itself, then would it matter at what point in the code we use $.when( mw.loader.using( 'oojs-ui', 'oojs-ui-core' ), $.ready ).then( function () {... and do we even have to load modules via mw.loader.using in the script?

@leila There might be some software development related volunteering opportunities/resources to point to from in here.

(with recent documentation changes to the Wikibase page, I am closing this task)

Will you be preparing some slides soon for a workshop or session to share a technical skill that will benefit small wiki contributors? If so, I encourage you to take a look at the toolkit development guidelines here: https://wikimania.wikimedia.org/wiki/2019:Small_wiki_toolkits#Developing_workshop_toolkits.

@Ladsgroup Could you help us with code review and enabling of this Gadget on MediaWiki.org? I'm guessing that after the code review step we share about the Gadget on the Project:Current_issues page to get community consensus...

@Ladsgroup Yes, that makes sense! I was referring to the "Existing APIs" list in here: https://www.mediawiki.org/wiki/Web_APIs_hub#Internal_resources_for_developers. So, maybe Recent Changes Stream, Pageviews, Parsoid (not sure what this is based on), and OOUI?

(feel free to re-open if there are any issues)

(feel free to re-open if there are any issues)

Closing this, as I got some initial idea on the needs of technical contributors that was required to kick-off the development of small-wiki toolkits:
https://www.mediawiki.org/wiki/User:SSethi_(WMF)/Sandbox/Technical_contributors_workshop

Hello folks! This workshop topic sounds exciting. I had plans of developing a toolkit and running a workshop around MediaWiki Action API: T225772 similar to T225771#5339609. Originally this was about Action API only. But recently I am interested in focusing on all Wikimedia APIs that might be helpful for technical contributors (particularly of small wikis).
Would there be any interest in collaborating on this topic both developing and running a workshop around Wikimedia APIs?

Update on this task >

Update >
Based on the presentation template provided here: https://meta.wikimedia.org/wiki/Brand/Presentations, we now have a toolkit template that potential trainers can use to prepare their toolkit: https://docs.google.com/presentation/d/1Ptzp5Th7rTg9wPE49x3JVApJ-WHkBMHkOGuI0j9o4WQ/edit. The most important thing to keep in mind for potential toolkit developers would be to add notes on the slides where applicable so that potential trainers or learners can benefit from it.

Update >

• Link to the PDF with trainer notes: https://drive.google.com/file/d/1Feq1XdniZ-rROxb3cK8b76vYWaBhFP42/view (via Google Drive).
• Link to the PDF source (via Google Slides): https://docs.google.com/presentation/d/1NdmuE0SlYXOCLJ9vNlmCzuUQVis-hsLbwCnpR9MLwZs/edit.

@matmarex Indeed that did the trick! But, ideally, there is a way to auto-detect/ fix this?

Your Gadget is available here now: https://test.wikipedia.org/wiki/MediaWiki:Gadget-tabbedwindow.js. The OOUI tabbed window is showing up here: https://test.wikipedia.org/wiki/API:Sandbox :) You can test it further. I made a small change in the variable declaration for indexLayout and panelLayout to get this to work.

In T227397#5329319, @Aklapper wrote:

(Off-topic here: Would love to get an answer on-wiki to my question on metawiki why anyone wants to query task assignment (not: task created by an author) in Phabricator Maniphest. That question is off-topic in this task, but I'd still appreciate an answer on wiki.)

I've responded to your question on meta-wiki: :)

@Jayprakash12345 It looks like I have the interface admin rights on test wiki: https://test.wikipedia.org/wiki/Special:ListUsers/interface-admin. I can help enable your Gadget there.

@Aklapper Could you share your thoughts on whether this argument that ElasticSearch is going to be helpful over Phabricator and Gerrit APIs for building this tool is valid? It is here: https://meta.wikimedia.org/wiki/Contraband#Benefits_of_using_ElasticSearch_over_Gerrit_and_Phabricator_APIs. And, if or not whether it is possible for us to get access to the ElasticSearch API to do the queries that we need to move forward?

Looking at the tutorial again, I see that instructions to install the oojs-ui modules via npm is in here:
https://doc.wikimedia.org/oojs-ui/master/demos/tutorials/index.html. Maybe I was hoping to see that in the Part 1 tutorial as well. But, I feel it is not necessary. We can close this task.

@jeropbrenda Nice work! Thanks :)

Thanks @jeropbrenda! Nice work on this :)

@Aklapper @mmodell It would be great if you can help answer @Rammanojpotla's question. It will help us move forward with the project cc @Tuxology

(closing this task, filed it for documentation purposes, but don't need the extension any more)

@bd808 I expressed interest in working on code related stuff to @Bmueller and she proposed this idea :) First, just making sure this is not in your TODO list?
Then, I am considering to integrate the visualization in Wikistats2 tool, what do you think about that? Birgit mentioned about Pageviews, but I think it is more about views than edits and this visualization won't fit there. Also, who should I reach out to when I dig deeper into investigating where the data is coming from, you or Andrew?

Testing complete. @Wargo @Tomybrz Please help replicate the changes on MediaWiki.org.

(this project is no longer part of the Outreachy internship. for further questions, send me an email)

Thanks @DannyS712 for reporting this! After testing the changes @bd808 has made to the script, I will request the interface admins to replicate the same on MediaWiki.

@Nikitrain Thinking more on Andre's comment, creating a new template and making sure all the future release notes adhere to it makes sense to me, but does not seem like a big task. And, I'm wondering what would be the advantage of structuring pre-1.0.0 release notes, how much of these notes get read after a while, etc.

@Pavithraes Wonderful proposal! :) Here are a few comments:

• +1 to Quiddity's comment on Hackathons tasks.
• What use case will you be focusing on more for templates/user-guides for the video (software features, tool, technical implementation, a running program, etc. )? It's okay if you are considering to develop one that caters all use cases, but it would be nice if you could indicate that in the proposal.
• You've mentioned that "in the end, there will be a hub..". Are you considering to work on the hub as well as part of your proposal? If you think there is some room still in the timeline, it would be nice to have this there as well and in the Deliverables section. I imagine a landing page for all the resources you might end up developing somewhere on MediaWiki.org.
• About the Phabricator screenshot, check with Andre. I see that there are a bunch of related tasks he has assigned to himself and may have plans of working on some of them.
• I see that your semester is overlapping with this program. That shouldn't be a problem, but make sure you have read all the program rules: https://developers.google.com/season-of-docs/terms/program-rules. I am also not quite sure what works, as we are doing this the first time :-/

@bd808 If there is any other channel you recommend, we should ask this question, let us know! As @Jayprakash12345 is getting the same error with the "my-first-flask.." tutorial, we thought it has something to do with Toolforge, and you might have an answer.

(unassigning myself from this task as I am not planning to work on the proposed changes)
Pasting the same comment I added on Zulip in response to your question:

@Shirayuki @Tomybrz I don't seem to find a quick method to make messages in the form translatable. I see this documentation https://www.mediawiki.org/wiki/Extension:Gadgets/Gadgets_2.0#Adding_multi-language_support_to_a_gadget but it is for 2.0 :-/ If I find an easy fix for this, I will work on it soon!

In T127640#5181169, @mmodell wrote:

@Aklapper should we look at making zulip more widely available to the broader technical community? It seems like a really good chat platform from my initial evaluations.

@Pavithraes All of these tasks that you are planning to address seem like good ideas to me! Feel free to suggest in your proposal whatever seems doable for a ~3-month long project. And, yes, it would be ideal if the tasks you plan to work on are all related, and linked to an umbrella project exactly like this one. Whenever you are ready, create a proposal on Phabricator following our guidelines and then we might be able to give more feedback on what seems feasible or not.

Here is some preliminary research work that would help me get started on developing the toolkits: https://www.mediawiki.org/wiki/User:SSethi_(WMF)/Sandbox/Technical_contributors_workshop.