Topic on Talk:Wikimedia Audiences

Apply same structure also on team pages? No Comm-Tech section?

8
AKlapper (WMF) (talkcontribs)

I like a lot what I see on this page. Thanks to everybody who worked on this!

I especially love the consistent structure (list of Phab projects + boards, name of lead, list of updates, links to team goals). I'd love to see this structure (plus a "Contact" section) also reflected or applied on each dedicated team wiki page and then maybe transclude sections - One place less to keep updated and more likely that users find such info when accessing team wiki pages not via "Wikimedia Product". Would this make sense in the long run, and do I miss some negative aspects on this early morning?

I see sections for Discovery, Editing, Fundraising Tech and Reading. The header of https://www.mediawiki.org/wiki/Wikimedia_Engineering also lists Community Tech. For consistency, is there a reason CT does not have their own section here (yet?) with the same structure like for all other teams?

WMoran (WMF) (talkcontribs)

We have had a few discussions with the Community Tech team and the current structure is what they prefer reporting wise so they remain under the reading audience. We did give the wish list a special call out and reading can post status updates specific to community tech in their section. I'd love to see more as it comes and I am sure we will.

Jdforrester (WMF) (talkcontribs)

I strongly disagree about adding yet more reporting burden to each of the teams of the departments here. The whole point of this is to give a consistent over-view; rolling it out to other teams is just makework.

For Comm Tech, they are part of Reading and not reported distinctly.

AKlapper (WMF) (talkcontribs)

@Jdforrester (WMF): I'd also disagree with more reporting burden, hence I proposed to reuse the data and structure already available on the Wikimedia Product page to be also displayed and used on each actual team page. And I'd hope that my additional request of having a "Contact" section is long-lived enough to not create too much burden either. :)

Jdforrester (WMF) (talkcontribs)

The structure of the page is not the burden; expectations of filling it in every day/week/month/quarter is.

AKlapper (WMF) (talkcontribs)

If I get you right then that's a topic to discuss about the structure and content of this very page itself, and not about my proposal to re-use the content of this page also on each dedicated team page. :)

WMoran (WMF) (talkcontribs)

Each team has a landing page, lead and phab board listed. These are all core interaction points. On the landing pages of it is not already there a mailing list or lead should also be listed for contact. Are you suggesting somethings else?

AKlapper (WMF) (talkcontribs)

@WMoran (WMF): I'm suggesting that each team page like Wikimedia Discovery, Fundraising tech, or Reading have a similar consistent structure like Wikimedia Product (Team head, contact info via IRC and mailing lists, relevant Phab boards, potential subteams, updates, goals), as interested people might not always have visited Wikimedia Product before ending up on each team page.

Plus I'm suggesting not to duplicate work, by not having such info manually inserted in two places (each team page and Wikimedia Product) but using transclusion so teams would only have to keep one place up-to-date.

Hope I made it a bit clearer now, sorry for any potential confusion. :-/