Updating our communication protocols
Jocelyn Ibarra
Public
Seen by 55
Hey peeps,
I'm moving this here to avoid having two conversations in the same place.
Given the amount of platforms we use (and the big updates in them we’ve done over the past 4-6 months– Slack and Telegram, as examples) perhaps it's time to revise our communication protocols as an organization?
I’m speaking of:
- Outlining what each platform is for,
- Collectively deciding where XYZ should be posted,
- How long to wait for a decision/reply to be made,
- A frequency to share updates like the one Fran just proposed here https://www.loomio.org/d/bLygftk9/july-2015-checkins,
- The importance of individual communication protocols (like this one http://everyoneonlinetogether.com/ :P )
- A notifications management conversation
Thoughts?
I’d be happy to coordinate this conversation and write an update somewhere hehh :)
Eugenio Battaglia Wed 2 Sep 2015 10:15PM
You did a great job with that website, and I totally agree to find a common code for this. My only concern is that all these great insights are not well understood by many. How can we agree on this?
Jocelyn Ibarra Thu 3 Sep 2015 6:12AM
Hey! Great!
We agree on this by writing them together :)
I'm doing one exercise for the Community peeps later this week, I can get started and we do a cadavre!
Albert Cañigueral Sun 6 Sep 2015 3:04PM
@jocelynibarra great topic! As part of my role of local ES coordinator I am facing the same problem and I thank you for leading this. This should be part of the "OS Hello Trello board" ..maybe even with a test? :)
@francesca ... great Ouiki compilation and explanation. I would like to help with an updated presentation in order to give a context to this effort. The best simple "story telling" I ve seen so far is here: http://intenseminimalism.com/2015/the-three-speeds-of-collaboration-tool-selection-and-culture-fit/ . Comments?
Then based on this you can introduce the different tools to cover the needs. With no "context" it might be a little bit too much to digest :)
I agree with @eugeniobattaglia1 this is poorly understood
Related to this 2 parallel topics
a) https://www.dokuwiki.org/ . @claudinerevol1 @auli can you report progress on this. Having embedded slides and screencasts will make our life so so much easier! :) #wetdream
b) As non-profit we should also be smart to access to premium versions of these tools for free. Google Tools offer them for free to accredited non-profits. ping @floreberlingen
Auli Viidalepp Wed 9 Sep 2015 11:11AM
in reply to @albertcanigueral side topics
a) update on dokuwiki: no progress. I started something at the beginning of summer but stopped for other priorities (website), and due to budget cuts there's no additional tech team / sysadmin budget for 2015 II (who was supposed to work on this, among other things). I might review what I can do on my own this year, but the greater community server project (including wiki and other tools) is postponed to 2016 / new try at the next Summit.
b) We applied for free Google NGO account via French TechSoup early 2015 with @julie6 but afaik haven't had feedback. Julie, can you comment on this when you have a moment?
Jocelyn Ibarra Thu 10 Sep 2015 4:50AM
Hey all,
@albertcanigueral I'll keep in mind these observations. Thank you.
However, I'll add another layer to the meaning of my original message. I'm sorry if it wasnt clear:
I'm happy to lead the discussion, and even structure the initial info, but this is a shared practice that requires that others join and do their part. Especially those who will also use it.
I am proposing that we do this together because we'll be able to create inclusive practices at the same time: we will structure information to inform each other, and, as we do it, we will build the structures so that any new member or Connector can add information too.
Especially when/if info starts getting translated.
Otherwise this becomes an activity that only some do, and others, who also have great insight, remain as mere observers. We will need testers too!
We can add this to the community area as a project. Since you're in it, perhaps we keep discussing in a couple of weeks?
I agree that we could use all that you mention :)
I enjoy these types of projects. They're somewhat finite and can be immediately seen online. Thanks for all those who'd find this useful.
PS. "Update" sounds better than "report", thank you Auli.
PPS. Why "wet dream"?
Francesca · Tue 21 Jul 2015 2:32AM
Thanks for bringing up this topic Joss! Actually, regarding the outline of what each platform is for, a good starting point is this wiki page that gives a pretty decent overview I think. I last updated it about 2 months ago. Maybe based on this we could discuss here which tools we think should be used differently than it is written there, move it to a separate page so its less messy, and then discuss your other bullet points?
I totally agree on the notification management conversation being important as well. We had a very good training session during the OS Germany Summit about this, which is something one could repeat (or maybe put into a tutorial video cc @albertcanigueral )!