Hey @Halfak , thanks for the details on how and why to target technical contributors. I think that entails a different outreach campaign because the target audience and the call to action (or expected engagement) are different.

Update:

• we published the blog on the Foundation's News page and on Wikimedia Space
• we are now working to create a category on Discuss, as well as private groups. @elappen-WMF will be adding corresponding links to announcement doc and category.

In T217232#5366443, @Halfak wrote:

It just occurred to me that this work might align with @Rfarrand's work on setting up smaller, geographically distributed technical events. I wonder if there's a good way that we might both support those events and build our relationships with a variety of technical contributors who might be interested in ORES.

The call for proposals was closed on July 22.
We now have 53 accepted posters, of which we received 22 for print. We extended the deadline to July 28 for a few poster presenters that hadn't submitted their work yet.

Update on emailing affiliates: Dumisani is working on cross-checking all affiliates on the last updated list to have the affiliate agreement signed. After this, we will be able to use this list for distribution. He estimates that this process will be ready towards the end of the month.

I managed to get a contact list for affiliates from Dumi. I will use this to send the message on Monday.

How do you enable the bios for every post? I typically see it on the editor view of a post on WordPress, but now I can't find it.

In T227604#5318629, @elappen-WMF wrote:

Spoke with Hang about different ideas. We agreed that a sticker would be more pragmatic than a card or another simple type of material. Not only are they more fun for participants, but they have the added value of compounding awareness of the program when displayed publicly, and future iterations of stickers could serve for collection purposes. This sticker will be the original, with future stickers getting more complex/branded.

The initial idea is:

• A sticker that says "Wikimedia Space", along with the URL. This URL will add to the "original" element of the sticker, as the URL will change post-prototype.

I sent approval and rejection messages on June 20, July 2, and July 8. At the moment, we have 44 accepted posters, and we could receive 1 to 3 new posters this week. The deadline to submit a poster proposal closed yesterday (July 7), so now until July 21st we just need to receive the work and send it to print.

Comms gave some feedback and suggestions on the blog, and I worked to polish this piece more.
The team sent me the doc with the content for the page on Wikimania wiki, which I have created today. Still waiting to hear from the team on some clarification with regard to the deadline to register.

Hi @Billinghurst, @Eric_Luth_WMSE : can we please add the page about Learning Days under the category Activities on the sidebar? It could go below Hackathon. Thanks!

@hdothiduc I love these badges!
Considering Nichole's feedback, and your original idea, what if you try making the road a line, equally as thick as the speech bubble line, with no color filling. This will put both graphics on the same level, avoiding this perception that the speech bubble is in the background, or a secondary graphic.

@hdothiduc can you please indicate on this spreadsheet which posters have been submitted for print? Thank you!

Thank you for flagging that, @hdothiduc !
I have responded. I was behind in the poster acceptance process, but now I have gone through all submissions, and accepted most of them. You can find all accepted poster submissions on this category on Wikimania wiki. I messaged all poster authors and reminded them of the content and the deadline. I'll check back for new proposals early next week.

In T219806#5257183, @hdothiduc wrote:

This sounds great, @SandraF_WMF! Thank you for the summary! I am really looking forward to working further on the documentation and on the video later this year!

@mcruzWMF, definitely thank you very very much for your feedback and suggestions. I agree with what you said!

I reverted the h1 colors now and don't use the dark blue anymore. I will do the rest of what is listed under "Short term" by the end of the month.

In T219806#5255969, @SandraF_WMF wrote:

@hdothiduc and I checked in yesterday and went through her designs. I'm extremely happy with what Hang has produced; I understand how to apply the designs and have even learned a bit about CSS in the process :-) At this moment, in my current planning, I can get started with what we have at this moment. As for next steps, we talked about the following:

Short term (finishing this assignment)

• Hang will upload the illustrations she made to Wikimedia Commons, in svg format, so that community members can download and edit them, and translate the lines of text as needed. She will also send me brief guidelines on how anyone (I, and other community members) can create their own illustrations in the same style. I will then organize the illustrations on Commons and will create a gallery page there with explanations on their background, usage and application, and will start experimenting with integrating them into draft documentation.
• @mcruzWMF: thank you so much for pointing to those templates developed for the Wikimedia Resource Center. They indeed look excellent and extremely useful for my purposes. I will start to play around with them on draft documentation so that I get a better idea of where improvements and additions may be needed.
  • One detail @hdothiduc mentioned: it would be good to also have hover styling for the Portal Navigation template. This may be something to look at later this year, see below.

Longer term (September-December 2019)

I expect that the bulk of documentation work for GLAM and StructuredDataOnCommons will happen in September-December 2019. Hang and I discussed that it would be great if I can ask for her ongoing design input and help again during that period, for more detailed fine-tuning of the exact elements and additions we need at that point, building upon the first elements she has designed now.

1. There is currently no need (yet) to rework the workflow graphic IMO. It is very much work in progress and it is likely to change a lot - and perhaps be applied in different ways - in those upcoming months. I suggest we revisit it in September-December 2019 in that context, unless @mcruzWMF has strong opinions on restyling the current version :-)

We have signoff on the blog draft. I submitted to comms today.
We are aiming at publishing the page on wikimania wiki by the end of this week.

In T219806#5252874, @SandraF_WMF wrote:

Thanks for your feedback, María! Hang and I are checking in later today to go through feedback in person. Please note that I am the one who created the workflow graphic last year - that image is not Hang's work! That said, guidelines on how to create and improve such graphics in the future are very welcome.

In T222288#5251656, @hdothiduc wrote:

Thanks for the feedback! How about this?

I shortened the text slightly. I think this last one is my favorite.

Is your timeline still to launch tomorrow? Unfortunately, I am busy until tomorrow with an urgent task.
I could make minor changes, though if you need me to.

Hi @hdothiduc thank you for working on this. I'm providing some feedback below.

Hi @hdothiduc !
Thanks for working on these. Yes, I think more fun is needed in these flyers ;-)

Hi @hdothiduc , I added a link on the task description to the communications plan we created with @SandraF_WMF some months ago. As part of the distribution plan, there is an explainer video. Since this task is connected to that, I thought it was good to share this document as well.

I made huge progress on the blog draft. Check it out!

In T217386#5221724, @hdothiduc wrote:

Hi @mcruzWMF!

1. I've got a question from someone, if they could print the poster themselves and bring it to the conference if they can't meet the deadline?

In T223102#5205712, @mcruzWMF wrote:

In T223102#5203223, @mmodell wrote:

I've added @mcruzWMF to the #acl*phabricator group. @mcruzWMF can you edit the form now?

No, I get the same message as I describe on this message

In T223102#5222173, @hdothiduc wrote:

Thank you @Aklapper for the heads up.
For the Phab Herald rule, should I simply create a task in Phabricator?
@mcruzWMF, would you like to be included / to have the rule be set up for Community Comms requests as well?

I submitted a blog template for Comms review.

Hi @hdothiduc the goal of this communications plan is to get more people interested in the ToT curriculum. When I thought of creating a video, I was thinking of a narrative where we:

• describe what the program is (bullet 2, slide 2)
• share when it happened before (bullet 1, slide 2)
• say how satisfied people were ( pages 3 and 4)
• finish with what we hope to achieve (If you are going to Wikimania, sign up to join ToT in Stockholm, which will take place on August 15, 2019)

Hi @DMccurdy ,
when you can, please copy the template here, paste on this task description, and complete it with the information about the project.

Hi @SPatnaik !
Can you please copy and paste the template here and add it to the task description? Please complete with the information for this project. Thanks!

In T223102#5203223, @mmodell wrote:

I've added @mcruzWMF to the #acl*phabricator group. @mcruzWMF can you edit the form now?

In T223102#5201629, @Quiddity wrote:

Note: I'm an admin (and on their team) and can edit the form in the future as needed.

In T223102#5199188, @Aklapper wrote:

Hmm. For which exact URL do you get which exact error message?

In T223102#5199089, @Aklapper wrote:

In T223102#5199076, @mcruzWMF wrote:

1. Can we change the name of the form to "CommRel Design Request"?

Sure, done!

Dana will share the data from the satisfaction survey tomorrow, Tuesday May 21st.
CC'ing @hdothiduc for support with video.

@Aklapper:

1. Can we change the name of the form to "CommRel Design Request"?
2. We should also create a form that is just for community comms. It is mostly the same form, but it changes the people who are subscribed to it and the associated projects. This is the link to the pre-filled task. If you have any recommendations regarding these two forms that are very similar, I'd love to hear it.
3. Can Hang and I become form editors, in case we need to make modifications in the future?

In T223102#5185872, @Aklapper wrote:

In T223102#5185432, @mcruzWMF wrote:

We need to implement this for design and community comms requests as well. At the time, our colleagues cannot find the pre-filled task in two clicks on Phabricator, like they do with other tasks.

I am curious how exactly your colleagues try to find how and where to file a task in Phabricator under your project.

• See https://www.mediawiki.org/wiki/Phabricator/Help/Forms how anyone can add a form to their Favorites (star) menu by customizing their Favorites menu.

In T223102#5184577, @hdothiduc wrote:

Oh cool!
I think, in an effort to direct attention for the requester:

• we could hide the Status, Priority, Assigned To and Story Points fields, because we would take care of that
• is it possible to expand the description field, so the whole content is visible. So then you just scroll the whole page instead of having two scrollable areas (the description field and the page to e.g. see the preview).

And yes, I think the main advantage of a form is to have a preamble above all fields. @mcruzWMF did you have something specific in mind, when you were thinking about creating a form for the requests?