Learning patterns/Publication policy

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
A learning pattern fororganizational
Publication policy
problemWe have multiple communication channels
solutionPublish a clear policy about what goes to which channel
creatorSylvain WMFr
endorse
created on14:12, 26 March 2015 (UTC)
status:DRAFT


What problem does this solve?[edit]

A chapter usually has multiple communication channels for its actions: internal wiki, websites of the various Wikimedia projects, meta.wikimedia.org, its website, its blog, its accounts on various social networks ... If it is sometimes possible reduce the number of channels (e.g. merger site and blog), this is not always the case, so you have to determine what deserves to be published and where.

What is the solution?[edit]

It is appropriate to have a single place to find all the actions held or supported by the chapter. In our case, we use the Wikimembers. This is our main tool of organization and internal communication, all members and employees having access to this space of exchange. This tool allows us to inform everyone of all the association's actions but also to list our various working groups. Always aiming to communicate internally, we use mailing lists. These allow us to have an email list to exchange without having to log into a forum or other external platform.

As for our external communication we use our website for all corporate and non-updatable information. To set the news of the association, we go through different communication channels support as a blog for important information which should be detailed. For more specific news, we use our social networks such as Facebook and for spontaneous news, Twitter.

The most complex part is the communication with the rest of the movement: if it is tempting to duplicate information in various locations, it highly complicates the work update. For each action, we must determine whether it relates to a specific project and put the pages for participants above (e.g. for a editathon, put the explanation page on Wikipedia, for a photo weekend put the page on Commons ...) This does not provide communication on other projects, but you just have to point to one and only one resource.

Things to consider[edit]

  • Have a place containing every action, private or public
  • Have a single place for public information about an action, and only links to it elsewhere

When to use[edit]

Endorsements[edit]

See also[edit]

Related patterns[edit]

External links[edit]

References[edit]