XSF Communications Team - 2019-11-20

  1. Guus has left
  2. Guus has joined
  3. debacle has left
  4. LNJ has joined
  5. emus has joined
  6. LNJ has left
  7. jcbrand has joined
  8. Nÿco doing it right now
  9. Nÿco btw, next week, I'm gonna cover:
  10. Nÿco Newsletter open process XMPP on Social Media
  11. Nÿco maybe I should add the SCAM sprints
  12. jasonervin has joined
  13. winfried has left
  14. winfried has joined
  15. winfried has left
  16. winfried has joined
  17. LNJ has joined
  18. debacle has joined
  19. winfried has left
  20. winfried has joined
  21. Nÿco oops: https://github.com/xsf/xmpp.org/pull/641
  22. Nÿco good point by Guus
  23. Guus As someone who recently lost all his bookmarks, I don't mind having a list of "XSF-internal" MUC rooms.
  24. Guus But on our public website, I'd focus on rooms that are of interest to the intended audience.
  25. Guus I don't think that the SCAM and Communication Teams MUCs are that.
  26. Guus mabye create the list on the wiki instead?
  27. SouL If that list is required, I would maybe keep it in the wiki and not in the website. I would rather keep workteams as something internal for the XSF, I don't see the value of random internet people joining this room
  28. SouL I see Guus was faster than me
  29. Guus Well, I don't mind showing that we're an open organisation but I don't think that listing them helps the intended audience finding the correct place to find help.
  30. raspbeguy has left
  31. raspbeguy has joined
  32. debacle has left
  33. Nÿco I find these arguments relevant, still I remain hesistant
  34. Nÿco anyway, that twice -1 vs only one 0
  35. SouL Nÿco, what about you?
  36. Nÿco "hesitant", would vote 0 (not +1 not -1)
  37. Guus What would be the benefit of having these MUCs listed on the public website, for the intended audience?
  38. Nÿco as you said, transparency I'd love to have audience feedback, qualitative rather than quantitative
  39. Nÿco it lowers the barrier of entry
  40. Nÿco someone who would want to suggest just drops a short message on our MUC
  41. Guus As an alternative to the alternative that I've suggested on Github (which would still work for me): Maybe add the MUCs to the pages of the individual Work Teams?
  42. Guus and/or do both.
  43. Nÿco easier than getting an account to modify the wiki, easier than creating a PR or reporting an issue on GitHub
  44. Guus I'd not add them to https://xmpp.org/community/chat.html without making it very clear that these rooms are mostly 'internal' (I prefer to not have them listed at all on that page)
  45. Nÿco right, forgot that
  46. Guus You don't need an account to read the wiki
  47. Guus only to change it.
  48. Nÿco read, but not write
  49. Nÿco still, providing feedback to the XSF is difficult
  50. Nÿco generally
  51. Nÿco not only comm
  52. Guus giving people more options isn't always an improvement.
  53. Nÿco I'm diverging
  54. Guus regardless, I'm not feeling very strongly about this either way.
  55. Guus I'd personally not add them, but I'm fine with them being added.
  56. Guus gets back to work
  57. SouL Hmm
  58. SouL It would maybe fit best on the contact page
  59. SouL like if workteams where specific departments (Human resources, public relations, etc)
  60. Nÿco https://github.com/xsf/xmpp.org/pull/641 closed, wontfix
  61. Nÿco thx!
  62. Guus I like how you're putting things like this up for discussion. Thanks!
  63. Nÿco real of humour?
  64. SouL Real!
  65. Nÿco cool
  66. Guus I actually appreciate the way you're doing this - no irony intended.
  67. Nÿco ok, clear, thx
  68. Nÿco I appreciate how this discussion happened
  69. Nÿco regarding social media content:
  70. Nÿco this week: Gajim tomorrow, Conversations next day
  71. Nÿco next week: call for content for the newsletter, newsletter process, our social media accounts, SCAM sprints
  72. debacle has joined
  73. Nÿco we have analytics on Twitter but nothing on Mastodon, that's gonna be manual :'(
  74. Nÿco oops, https://github.com/conversejs/converse.js/releases/tag/v5.0.5
  75. Nÿco so maybe I'd do Conversations Thu and Converse Fri?
  76. Guus v5.0.5 fixes a very nasty bug that effectively silently drops messages. If we're going to mention the release, doing it sooner rather than later is good.
  77. Nÿco like "now"?
  78. Guus I'm still not sold on the idea that we're publishing content for other projects in the first place, but I'll leave that to you for now 🙂
  79. Nÿco I'd rather relay JC's announces
  80. Guus nah, no need to rush-rush things
  81. Guus but I'd suggest moving it up to the pile of scheduled things.
  82. Nÿco I know you're not convinced, I am not yet either to be completely honest this is only experimentation we'll see the reception
  83. Guus as this update being deployed will benefit the XMPP ecosystem as a whole
  84. Guus fair enough
  85. Nÿco btw, I'll deploy it rght away :)
  86. Nÿco deployed
  87. Nÿco CDNs rock
  88. Guus Yeah, for Openfire we need a small wrapper
  89. Guus I'm trying to get anyone-but-me to do that, to reduce the bus factor of that
  90. Nÿco https://wiki.xmpp.org/web/Twitter_and_Mastodon_content for transparency and co-construction
  91. Nÿco https://wiki.xmpp.org/web/index.php?title=CommTeam/Newsletter_Twitter_campaign&redirect=no#Draft_tweets are still usefull
  92. Nÿco otherwise, still talking about sharing and building together, how about we sync the CommTeam on a Trello board?
  93. SouL Perfect!!
  94. Guus Although I don't have an immediate better alternative, I'd not use the term 'diverse' as is done in those templates. These days, 'diverse' mostly refers to diversity in context of race, ethnicity, gender, sexual orientation.
  95. Guus Although I don't immediately have a better alternative, I'd not use the term 'diverse' as is done in those templates. These days, 'diverse' mostly refers to diversity in context of race, ethnicity, gender, sexual orientation.
  96. Nÿco where do you see "diverse"?
  97. Guus Draft tweets, last one
  98. Guus > XMPP is Diverse - you will never get "locked in" when using XMPP technologies. As an example, you have plenty of options to choose from when looking for a XMPP client. https://xmpp.org/software/clients.html
  99. Guus Maybe re-use these terms? https://xmpp.org/about/technology-overview.html
  100. Guus lunch!
  101. Nÿco https://trello.com/b/dkhCQCOE/commteam
  102. Nÿco ok
  103. Wojtek has joined
  104. emus has left
  105. emus has joined
  106. winfried has left
  107. winfried has joined
  108. LNJ has left
  109. Wojtek has left
  110. Wojtek has joined
  111. winfried has left
  112. winfried has joined
  113. winfried has left
  114. winfried has joined
  115. LNJ has joined
  116. winfried has left
  117. winfried has joined
  118. raspbeguy has left
  119. jasonervin has left
  120. raspbeguy has joined
  121. LNJ has left
  122. jasonervin has joined
  123. Nÿco https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/Dcs2Ri8s6822WXzyWG8SiQySQExvUwZKNX1oyOhA/Capture_d_e_cran_2019-11-20_a__16.37.27.png
  124. emus nice!
  125. emus has left
  126. emus has joined
  127. LNJ has joined
  128. jcbrand has left
  129. jcbrand has joined
  130. LNJ has left
  131. LNJ has joined
  132. jasonervin has left
  133. winfried has left
  134. winfried has joined
  135. winfried has left
  136. winfried has joined
  137. Wojtek has left
  138. LNJ has left
  139. debacle has left
  140. raspbeguy has left
  141. debacle has joined
  142. DebXWoody has left
  143. DebXWoody has joined
  144. DebXWoody has left
  145. DebXWoody has joined
  146. DebXWoody has left
  147. DebXWoody has joined
  148. jasonervin has joined
  149. DebXWoody has left
  150. DebXWoody has joined
  151. emus has left
  152. emus has joined
  153. emus has left
  154. emus has joined
  155. emus has left
  156. raspbeguy has joined
  157. emus has joined
  158. emus has left
  159. jcbrand has left
  160. debacle has left