Tue 24 Jun 2014 8:48AM


JAP João Azevedo Patrício Public Seen by 322

Effective communication is not as simple as it may seem, the link that is needed to create between the sender and the receiver is not linear and it's dependent of lot's of variables that go from interest in the matters communicated, to the way it's communicated or simply the frequency.

Regarding this issue I want to start a discussion on, for a start, blog communication, and the decentralization and planning of communication. One aspect that can't be denied is that almost all the communication in blog is done by one person or two persons, and focuses in general on aspects that orbit around the distro but don't go deep or have a understandable frequency for a reader.

Regarding this I suggest that we define communication in blog in 3 main aspects (not strict): Cooker issues, workshop issues, associative issues. The blog post should be (as we are going to have another tools for fast com and have the social networks) to be a more comprehensive and planned communication. So we should define that each of this aspect should have at least 1 blog post per month, can have more.

For that we will need: 1 - blog planning responsible; 2- something to post about :-)

this person should contact cooker and workshop and understand what is being done, who works normally on what, and also check for suggestion on blog posts, an example:

  1. Person A could write a blog post about it's work on kernel, or how to do something with the kernel that is on omlx.
  2. Person B can write something about packaging or using something,
  3. Person C can write something on how to do something using krita,

also, progress blog post could be written.

the planner should check what can be done, and with the people that could write them prepare the blog post and define the release dates. Those blog post will be published by those people, showing the community that oma is a multitude of people, and not concentrated.

Also communication about previous releases should be: "look what we can do with it"; and for new releases "look what we are doing, implementing, for you".

this is not to be strict but a way to involve people.

I hope we could start a good discussion here about this issues.


Anurag Bhandari Tue 24 Jun 2014 2:40PM

+1 for all the highlighted points. Once we have our own microblogging platform installed (as was discussed on Workshop), it'd be good to do a max 1-2 blog posts per month and write out all experiences and informal posts on the microblog.


jclvanier Wed 25 Jun 2014 8:30AM

Though I cannot involve myself in this domain, I agree with this proposal.


Kate Lebedeff Thu 26 Jun 2014 5:17PM

Sounds like very sane system, which should be indeed effective