Jump to: content, navigation, search

Navigation menu

Communication channels analysis: Difference between revisions

some updates
(Status: Some ongoing work)
(some updates)
 
An often cited problem is that announcements made this way can easily get lost in the noise, and indeed the noise prevents many people attempting to keep up with the talk and dev main mailing lists (Harry sympathises with this viewpoint, and has ''never'' attempted to follow any mailing lists, with the result that he misses out on some announcements) Many of the other communication channels are attempts to tackle this problem.
 
A small minority of users have been known to post far too often, in breach of normal mailing list etiquette. This can be seeseen within user posting stats (''Question: user stats link?'') These users contributescontribute significantly to the noise factor, although all conversational postings add up to a net-squared effect of ever increasing chatter as more new joiners sign up to the mailing list.
 
The mailing list is also blighted by '''argumentative postings''' which is perhaps inevitable. Sadly it puts out a negative impression to any newcomers. Newbies were encouraged to move to the newbies mailing list, partly to decrease noise, but partly to attempt to present a more friendly face to these people. Sadly the newbies list is not without its arguments either.
 
The label of "trolling" is bandied around very easily, but in some cases there are accusations of deliberate and '''malicious''' attempts to undermine the effectiveness of the mailing list. It may be in some people's nature to needlessly start arguments, but clear-cut cases of malicious mailing list useabuse could be tackled with this use of blocking privileges. So far this has neverrarely been necessary, but sadlya theblocks projectwere mayused bein growingsome towardscases thatmore pointrecently. Steve's "poisonous people" post describes these problems. OneSometimes suggestedthere nextare step,calls isfor toa documentmore adetailed "code of conduct" for mailing list use.
 
Email addresses of posters are revealed. The system also requires to register with your 'from' address, which can be more difficult to set up as a throw-away address. The email addresses getgets published on the web archive although with some minimal anti-scraping obfuscation. This doesn't seem to bother many people, so presumably sp@mmers haven't figured it out yet (or don't tend to find the archives)
 
There is no integration with OSM user accounts, e.g. a way to post to mailing lists on the web via that.
 
==== announce list ====
 
http://lists.openstreetmap.org/pipermail/announce/ A mailing list just for announcements. Clearly for this to be effective, it should not involve any discussion, and postings should be important project announcements, for some definition of "important". This means that unimportant things should nonot appear there, but also important things MUST appear there. So far people seem to be using it fairly sensibly. Maybe a little too many merkaartor point release announcements, but important announcements don't always make it onto there. ''Question: Is public posting allowed?''
 
==== osmf-talkannounce ====
There is also osmf-announce for separate foundation related announcements. Not clear if this separation is needed really.
http://lists.openstreetmap.org/pipermail/osmf-talk/ Chit chat about the foundation. This may be particularly relevant to the Communications Working Group.
 
==== Otherosmf-talk ====
http://lists.openstreetmap.org/pipermail/osmf-talk/ Chit chat about the foundation. This may be particularly relevant to the Communications Working Group.
There is also osmf-announce, but this seems to be broken/decommissioned
 
===Wiki===
 
Documentation and help information. Publicly editable. Harry has been active (a bit less these days) and trying to manage some aspects of the wiki. The [http://wiki.openstreetmap.org/wiki/WikiProject_Cleanup WikiProject cleanup page] lays out some of the broad brushstroke information on the various objectives of the wiki, and goes on to provide guidelines. There is more work to do on wiki guidelines. It can be a sensible place to start, in the hope that the community of editors can then gradually shift things to conform with the guidelines. This is a better approach than attempting any silver-bullet rapid cleanup initiatives.
 
There is a need to tread carefully (discuss changes first) around some areas of content to avoid getting embroiled in disputes, but there is also a massive amount of clean-up work which can be carried out without encountering much controversy. This is true throughout the whole wiki and even within the (often controversial) tagging documentation.
==== 'Community Updates' page ====
http://wiki.openstreetmap.org/wiki/Community_Updates
The "Community Updates" page iswas a recentan initiative to post rolling news items on the wiki, including summaries of recent mailing list discussion ([http://wiki.openstreetmap.org/wiki/Things_to_do#Task:_Mailing_list_weekly-digest which iswas a good idea]) There arewere a couple of keen contributors, neither of whom can write good English. The fact that errors arewere not corrected quickly suggestssuggested low readership, but this could change. As with Template:News, the wiki allows more people to join in, which is good on the one hand, but we may encounter problems with the subjective choice of what is important news, and the stylistic/literary choices involved in summarising. However enthusiasm dried up and no further updates happened since 2011
 
=== Forum ===
 
A conventional web forum/message-board system which has been running for some time now. Run by Lambertus. It works fine as a place for discussion, and people who dislike mailing lists tend to wish that more people would move over to using it instead. Lambertus has done some technical tweaks to add RSS functionality. Integrated pretty nicely with OSM accounts. It uses it's own avatars where it could use OpenStreetMap ones (minor technical gripe) There's a [http://forum.openstreetmap.org/viewforum.php?id=8 feedback forum] for suggesting technical improvements.
 
The main use of the forum these days is by the russian community, with a fair bit of use by various other languages. Not much english.
 
It has functioned fairly well as a newbies/technical/tagging question & answer site, although this use case is now being usurped by help.openstreetmap.org
http://help.openstreetmap.org/
 
Question and answer site. It uses the Stack Overflow system, which resembles sites like "Yahoo! answers", with votable answers, but also blending in aspects of forums, wikis, and point-based badge games. It's pretty new. Launched by Tom Hughes during SOTM 2010, and so farit seems to be working really well. People new to this format may struggle to understand it. It was recently linked from the OpenStreetMap homepage (the word 'help')
 
Integrated pretty nicely with OSM accounts, although it uses avatars from gravatar.com rather than OpenStreetMap ones (minor technical gripe)
 
=== IRC ===
http://wiki.openstreetmap.org/wiki/IRC#IRC - Chat rooms. There's quite a lot of possible chat rooms listed. You can actually spawn a new chat room just beby entering a different name, so there's nothing to stop new ones being added to the list, but #osm, #osm-dev, #osm-de are the ones with some traffic. They function reasonably well as a place for newbies to ask questions, but whether newbies feel invited to do so is another question. The IRC channel seems to alternate between too much conversation traffic, and nothing at all. Some similar problems with other channels with individual users talking too much.
 
Several years ago there were some coordinated meetings held on the IRC channel, as a sort of live Q&A session to help newbies. Not sure how well they worked but they seemed to stop happening. http://wiki.openstreetmap.org/wiki/Mapping_Techniques,_Tips_and_Tricks
 
=== foundation blog ===
http://blog.osmfoundation.org/ - For foundation related news. Reviving this and keeping it up-to-date has been a focus of CWG activities
http://blog.osmfoundation.org/ - A grand total of two blog posts. We need to take a decision to revive this as meaningful blog or decommission it. At one stage there were some complaints that OpenGeoData.org was owned by Steve Coast, and this is not appropriate as the main blog of OpenStreetMap. The OSMF blog may have been set up as a reaction to that. ''Grant set it up. We should ask him about it.''
 
=== blogs.openstreetmap.org & user diaries ===
 
=== foundation wiki ===
http://www.osmfoundation.org/ Grant was asked to set up MediaWiki wasUsed as a simple CMS choice for the foundation site.website, Lookingalongside sosome similarbits towhich wiki.openstreetmap.orgare createsin confusionwordpress. WeHarry don'tdeveloped wanta mediawiki skin to confusinglymake duplicateit content ofmatch the mainwordpress wiki,theme but we also don't want to aim to grow content inon the same waysite. The Wewordpress don'tpowered reallypages want a wiki-style sprawling knowledgebase onhave the foundation site. It's moreadvantage of abeing CMStranslatable situation,via thanthe atranslations knowledgebasewordpress situationplugin.
 
We don't want to confusingly duplicate content of the main wiki, but we also don't want to aim to grow content in the same way. We don't really want a wiki-style sprawling knowledgebase on the foundation site. It's more of a CMS situation, than a knowledgebase situation.
The wiki is not openly editable. Editing access is granted to people on the foundation and working groups. The limited access can mean that updates are not as forthcoming as they could be, but it does mean we stand more of a chance of keeping the content tidy focussed. We can also have a positive spin on everything. Content doesn't need to drift towards a neutral point of view so much.
 
The wiki is not openly editable. Editing access is granted to people on the foundation and working groups. The limited access can mean that updates are not as forthcoming as they could be, but it does mean we stand more of a chance of keeping the content tidy & focussed. We can also have a positive spin on everything. Content doesn't need to drift towards a neutral point of view so much.
Maybe we should move a way from using a wiki (e.g. drupal or wordpress instead) Where wiki style collaboration is useful, we could use the main wiki. Alternatively if we stick with MediaWiki, we should at least make the wiki look very different from the main wiki (skin). Perhaps think about non-open permissions.