Community contact page -Who owns what?

Mozillians
#1

Hello,

One of the recurrent problems we have is figuring out who owns what inside a specific community.

For example, Community Ops team trying to reach people in charge of a community website, Community Marketing trying to reach the person leading marketing efforts in this other community.

So, I open this topic to know: Are communities listing this information? If so, how, where?

And a second question: How can we maintain this list across communities to be able to access it in a easy (centralized?) way?

Thanks!

#2

there is https://docs.google.com/spreadsheets/d/1GasFyOZ9cGczocZiUSNyyl3VL7K49i91C2fkxmx9RQQ/edit#gid=2 for comms channel if all the communities are using this info we can easily add the info in the document.

#3

It should be easy for communities to update their lists anytime and for external people to have a place to see the updated information.

One idea could be a wiki page listing all communities and a link to their community structure on their sites.

#4

We can take a silimar structure as L10n:Teams on wiki.
Actually, I think there would be a duplicate of some info already inside it.

Also, is there exist any problem for a centralized community liaison structure? Any info should able to go through the one who take charge of dispatching inquiry.

#5

Do you mean communities with just one person in charge of acting as a bridge?

The problem we want to solve here is to avoid a single point of failure, so if we just have one person in charge of the website or marketing and this person is busy, on vacations, away or not anymore contributing we don’t know where/who to ask.

If we have a page listing all people, it would be easier to avoid bottle necks and bus factors.

#6

Another structure we’re practicing at Taiwan is, we don’t use a single person’s mail for contact, but an alias of all core contributors (admin (a) moztw.org). We can easily add or remove people to the alias while people go or join, and you don’t have to worry about who to contact for what.

We also had a practice rule that when we send out or reply a mail as community’s position or discuss cooperation with other parties, we’ll cc to this the mailbox to let every other know what is going on.

This can also prevent single failure point and also hydra-headed problem.

1 Like
#7

Yes that’s interesting. For example at Mozilla Hispano we use alias for external communications with different areas (l10n, QA, marketing…).