Thanks so much @Tim_WMDE!
We really, really appreciate the work you put behind this and we at the Team Ideenförderung are very lucky to have you as our bannerman! (Excuse the bad pun, too tempting not to...)

Hey @Tim_WMDE thanks for the nice in person meeting we just had. For documentation purposes, I would sum up what we did.

@Christine_Domgoergen_WMDE completed this task and figured out where the tool should be embedded:

Re-assigning this task because the texts/ links are ready to be implemented!

@Cirdan I've got an update! Our collective efforts have brought forth the following Hilfeangebote for the right hand column. The idea behind this is that we're offering 3 different levels of support/ help: guided tutorials, self-study via on-wiki help sites and concrete questions.

As we discussed during out last meeting:

I am closing this task as the tool is self explanatory.

Hey @Cirdan, I edited www/python/src/static/mitmachen.js on github with our proposed texts.

@Cirdan I wanted to close this task as resolved, but I guess it's not resolved until you've had a chance to implement it :)

Happy to announce the result of our team's collective brainpower:

Update: @Stefan_Schneider_WMDE will follow up with this task, to gauge options of how we're going to proceed regarding this matter.

I got the text for the template from @Jan_Dittrich. Thank you Jan!

@Cirdan, a practical question:

Adding the protocol from a meeting with Software engineering on August 15th:

Update after meeting with Software Engineering Team at WMDE on August 15th:

Regarding Bug reports:
We talked to Jan from our UX department, and he suggested to link to a Google Form for bug reports, and that he has a template for such a form which you could use. Would you like me to ask for this template, so you could use it?

Thanks for this suggestion! I personally can not tell how complex this would be to implement. With Cirdan on vacation, could you, @RazShuty, help in giving us an idea whether this would be a small or large addition/ alteration to the existing code? (Not asking you to do it, just asking you to get an idea of how much work it would be, if you can estimate it. :))

On Wikipediaday in October, ask community for their expertise on where to embed / link the tool.

Also it would be nice, if the link of every task would use the Wartungsbaustein or the unchecked link as an anchor. Like this the user is guided to the specific place where he or she is expected to edit and does not get lost in scrolling and searching for the unchecked link etc.

Since Cirdan is on vacation right now, let's work with these 4 tasks for now:

Hey @Christine_Domgoergen_WMDE, thx for you input! In this project we use only the materials we already have, it's out of scope to develop something new. But if we have something new in the future, I am sure we can update the links and videos embedded in the tool as well.

For both these points:

@Christine_Domgoergen_WMDE and @Stefan_Schneider_WMDE I would ask for your help here, again: Where in our current onboarding materials should the tool be linked?

Sounds good - does this mean, the task can be resolved?

I like it as it is, it is very descriptive and tells you what you'll have to do to solve the task!

Thanks Jan! The next time we use this tool in a campaign, we will consider these points for tracking/ analysis:

@Christine_Domgoergen_WMDE and @Stefan_Schneider_WMDE, I would kindly ask you to check whether the language we use here on the website https://tools.wmflabs.org/mitmachen/ is congruent with the language and terms we use in all our other tutorials/ onboarding materials.

@Christine_Domgoergen_WMDE and @Stefan_Schneider_WMDE do you have any ideas? What would be a good and descriptive name ("sprechender Name") and a descriptive, short but informative tagline (Unterüberschrift) for this tool?

I would not suggest that we offer support for the use of the tool.
This is out of scope of our resources. You are doing such great work that I am sure the tool will be mostly self-explanatory! :)

@Christine_Domgoergen_WMDE Your expertise is needed here:

@Jan_Dittrich can you lend your expertise here? Which of the solutions that Cirdan suggested would you prefer?
Or would there be something else?

So perhaps @Stefan_Schneider_WMDE or someone else from the team can give us an estimate of how many visitors reach the end of the tutorials/will get a chance to click the link to the tool?

Update on this task: Since we are currently not running the tool as part of a banner campaign, the need for special care/ maintenance during the day the focus on this shifted, and this task is currently not needed. When we run this tool as part of a campaign in the future, and expect an increased amount of people using it intensely for a limited time, the Ideenförderung (IF) Team will re-open this task!

Hey, just a quick update: I have taken this task into our IF team, and we will work on it as part of our next 2 week sprint, starting August 9th.

Looks good, thank you very much for getting this fixed so quickly. Until next time! 🎉

Wow, it looks crispy as a bag of chips now on my Mac.

Hey, I was working from home and now have a meeting right away, so will be with you at 15:45 - thx for being so spontaneous. Laters!

Hey, thanks - would you be up for a quick IRL meeting today around 15:45, if I just quickly came up to you to the 3rd floor, to say hi? Maybe quicker to do it in person :)

Hi @Tim_WMDE, thx for the implementation! Looks good :)
If I may add a minor thing about the graphics in the middle, they look a tiny bit pixelated. The outline of the circle, the logo-ball and the question mark is quite not as crisp as the graphics in the 1200px banner that the agency sent over.

Hi, thx for the update. I am out of office rn but will be back on the project next Monday (July 30th) and will get on it.

Hi @Stefan_Schneider_WMDE thx a lot for getting this done.
@kai.nissen, thx for pointing out the inconveniences/ flaws of the design. Is this something we need to get fixed by the agency, or can you work with it?

I attached the final designs in the zip file above.
This zip file includes a file with the information requested above ("color codes etc.rtf"), but I will copy & paste it here, too.

Thank you!

Follow up from the last call: Option B is preferred.

After we got feedback from the pretests, our design agency had to update the banner design, because the old one was received rather badly.

Find 1-3 people from WMDE SWE team to maintain operation of the tool.

Notes from call with Cirdan:
Track how many people clicked the link to the tool in the tutorial
and then count how many search requests the tool got.

I added my session recap and feedback here in this etherpad: https://etherpad.wikimedia.org/p/mentormeeting

Thank you very much! I enjoyed working on this so much, it's hard for me to stop.

List added here: https://www.mediawiki.org/wiki/Hackathons/Handbook/Event_week#Make_a_packing_list
If possible, please add new items to the wiki page directly so we don't lose information.
Thank you! :)

... and I will make sure to put it there. :)

I'd put it under "during the event", in a section called "packing list", and/or under "venue + wifi".