@Aklapper Thank you! I've sent the survey to all 30 authors.

Thanks, @Dvorapa for reporting the issue!

@Aklapper also added the workflow as you defined in https://phabricator.wikimedia.org/T188244#4266947 here: https://www.mediawiki.org/wiki/Gerrit/Code_review#Finding_patches_to_review. Feel free to modify!

Sent an email to faculty members at POSSE with a link to this resource: https://www.mediawiki.org/wiki/User:SSethi_(WMF)/Sandbox/POSSE:Wikimedia

In T188244#4269103, @Aklapper wrote:

If so, then, maybe it is not adding those who aren't listed on the page. If this is the case, then should we not ping folks on IRC before adding them as a reviewer to a patch?

I'm not sure I can follow. I might totally misunderstand, but the first sentence makes me think "If I do not know you then I cannot add you", the second sentence makes me think "Why would I ping folks about Gerrit on a horrible medium like IRC if I can ping folks about Gerrit in a slightly less horrible medium like Gerrit?" though I imagine that many people ignore all those noisy Gerrit spam notifications in general.

@Aklapper thank you for sharing the list! I've sent the survey to 48 new authors!

In T188244#4266947, @Aklapper wrote:

• Conclusion: We ignore queries #1 and #2 for this workflow, and either use queries #3 to #6, or use some of the queries #3 to #6 to start small and expand.

@zhuyifei1999 Sorry for the late reply! Your comment here was helpful and you were right, express receives the tool name in the URI. I am now using the express router middleware that helps mount sub-apps on a mount point. I couldn't find anything cleaner than this :P I've made the related changes to the tutorial.

@Aklapper I've documented four queries here: https://www.mediawiki.org/wiki/Gerrit/Code_review#Finding_patches_to_review.

Thanks, @sonkiki @Halfak for working on the mentoring program and for taking notes! :)

@Mh-3110 thanks for sharing your post! :)

Post-hackathon @Yug shared with me a project via email centered around text-to-speech for LinguaLibre to be promoted to new developers via the guide. Just checking if we all are on the same page here cc @Aklapper @0x010C

Yes, that's true! There isn't anything more actionable on this task.

Reminders sent to attendees about linking their blog posts here: https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2018#Event_blogging

(removing the link to the meeting notes, might be that it is for private use)

@Niedzielski Is this a session or a project? If not a project, then I would move it to a different column. Thanks!

@Anna.d92 I would be happy to help you with this at the hackathon! I am writing up a tutorial around hosting Node.js tool on Toolforge, hoping to finish it by the hackathon which you could use it as a reference: https://phabricator.wikimedia.org/T192423#4196282

The first draft of the tutorial is here: https://www.mediawiki.org/wiki/User:SSethi_(WMF)/Sandbox/My_first_NodeJS_OAuth_tool. The tool works locally, a few more tweaks to get it to work in the Toolforge environment.

@bd808 I am able to download the iso successfully, and all the files seem to be in there. I am copying them now! :)

All details are here: https://github.com/srish/gerrit-newcomer-bot

@qdinar thanks for reporting! I noticed your patchset and filed an issue here. Will add a fix soon!