XSF Communications Team - 2018-02-16

  1. Nÿco has left
  2. Nÿco has joined
  3. Daniel_W has left
  4. Seve One of my questions is if this can be done from the XSF or it has to be done as something independent/
  5. jcbrand has joined
  6. jcbrand has left
  7. jcbrand has joined
  8. jcbrand Do you guys have any suggestions for the name of the newsletter?
  9. jcbrand About online copies, I'm thinking of creating a Jekyll blog/website, with each blog entry being the newsletter instalment. AFAIK this can be done, so we'll then get a website (which we control) and a newsletter.
  10. Seve My question is related to that. Because if it was under the XSF, we could have it somewhere like xmpp.org/newsletter
  11. Seve but if it's not related to the XSF at all, then we have to set up something smewhere
  12. Nÿco has left
  13. Nÿco has joined
  14. jcbrand Well, when it was asked whether the Comms team should be resurrected as an official team, Kev (IIRC) said no (at least for now)
  15. SaltyBones Guus said he would happily take pull request for xmpp.org
  16. SaltyBones Guus said he would happily take pull requests for xmpp.org
  17. SaltyBones Guus said he would happily take pull requests for xmpp.org ( https://github.com/xsf/xmpp.org )
  18. jcbrand I'll talk to Guus about it
  19. jcbrand The XSF is quite bureaucratic sometimes
  20. jcbrand I'm not sure I want to make a pull request every time a newsletter is sent out
  21. jcbrand Especially if the newsletter gets generated from the blog post
  22. SaltyBones jcbrand, neither do I think you should, just wanted to relay the information
  23. jcbrand sure, it's good to know
  24. Nÿco has left
  25. Nÿco has joined
  26. Guus has joined
  27. Guus jcbrand will have xmpp.org commit rights in three, two, one...
  28. Guus or, perhaps, the entire comms team?
  29. Seve o/
  30. jcbrand xmpp.org uses a static site generator (Pelican) to generate its content.
  31. jcbrand I'd like to check out the xmpp.org repo and see whether I can generate posts under /newsletter which will then be the newsletter installments
  32. jcbrand I think it might even be possible to have tinyletter.com send out HTML emails based on content from xmpp.org/newsletter
  33. jcbrand That way, we have the newsletter hosted on xmpp.org and sent out via emails
  34. Seve That would be nice if it can be automated, so just write the post and be sent :D
  35. jcbrand I think it can, I'm just wary of HTML emails, since it's apparently very difficult to test that they render properly in all clients
  36. jcbrand So the emails' HTML must be very simple IMO
  37. jcbrand So you'd need to render one set of HTML for xmpp.org/newsletter, and different HTML for the email
  38. jcbrand Guus will help us officially ressurrect
  39. Guus To facilitate this effort (and hopefully other efforts related to the XSF providing outwards communication) I suggest that you guys ask Board for the Communications Work Team to be (re)created. It was disbanded, if I recall correctly. When we have a CommsWT again, we can easily define that its members should have access to the tools needed for their activities (permission on the corresponding github repos, access to our social media accounts, etc).
  40. jcbrand Guus: how do we ask?
  41. Seve I agree, yes.
  42. Guus The most pragmatic way to do this is to request this on the members mailing list - including a charter that defines the mission statement.
  43. SaltyBones Seems easier to just give rights to jc and make changes go through him.
  44. SaltyBones #cuttheredtape
  45. Guus That will give other members the ability to pitch in on the idea (maybe others have suggestions), and will give me an explicit request to bring for the board.
  46. Seve SaltyBones, that's lazy!
  47. Seve :P
  48. Seve Guus, do you know why the previous team was disbanded?
  49. Seve And what were their 'goals'?
  50. SaltyBones Seve, no, that's pragmatic and efficient. :p
  51. Guus SaltyBones: although I agree that the tape is annoying, there are many members that feel comfortable with it. On top of that, I don't want to depend on any one person, if I can.
  52. Guus Seve, it was disbanded for a lack of activity, iirc. I think at one point, it was just nyco, who didn't get any support.
  53. Guus SaltyBones: to prevent endless discussions of why we need or need not have red tape, the pragmatic approach in XSF sadly is to follow the tape. :)
  54. SaltyBones Guus, ...I can't even. ;)
  55. Guus also, I'm perfectly willing to assist here - should be fairly straightforward.
  56. SaltyBones We don't XMPP2 we need XSF2. :p
  57. Seve I'm lost now. What does the tape expression mean?
  58. Seve (sorry for the offtopic)
  59. SaltyBones Seve, "red tape" is an expression for annoying processes that have to be followed
  60. SaltyBones It's an even more negative term for bureaucracy ;)
  61. Guus red tape is a metaphore for 'annoying bureaucratic processes'
  62. Guus my advice on that within the XSF: go with it. It's actually not so bad if you avoid the discussions on why we have them in the first place.
  63. jcbrand I agree that's it's better to have a team instead of relying on one person
  64. jcbrand It helps with transferring knowledge and avoiding a low bus factor
  65. jcbrand And it helps prevent burnout if the load is shared
  66. Guus exactly. That said, you can formally define whatever set of work teams that you want: the entire effort stands or falls with having people actually doing the legwork.
  67. jcbrand Also, if multiple people have access to the newsletter source, they can help craft it before it gets sent out
  68. Seve Well, based on my experience on struggling to find time to do something else except work and personal stuff, I know jcbrand will not be able to do it always, so the more people that can help out the better, I think.
  69. jcbrand Don't skip leg day
  70. jcbrand yes
  71. jcbrand I also don't want to be solely responsible
  72. Guus I think we're in agreement?
  73. jcbrand We can wait a bit for others in the list to state objections if they have any
  74. jcbrand in the MUC I mean
  75. Guus here's the old wiki page for comms: https://wiki.xmpp.org/web/CommTeam
  76. Guus jcbrand, I'd take this to the members list, and let people object to a specific proposal to reinstate the work team.
  77. jcbrand yes, are you saying literally you, or are you suggesting that it be done?
  78. jcbrand I agree with writing to the members list, I just thought we might want to hear from Daniel_W and nyco
  79. Guus I'd be happy to draft the text with you, but I think it'd be good if we have someone else than me spearheading this.
  80. jcbrand I'm happy to send out the email
  81. jcbrand so we're all happy
  82. jcbrand which is good ;)
  83. Guus I shall make my bliss complete by getting another cup of coffee then! :)
  84. jcbrand I agree it should come from someone within the proposed comms team
  85. Guus ok, lets do it :)
  86. Seve I have a question but I was not sure if I should say this out loud. I wanted to do something like 'In today's What can I do with XMPP?: Message corrections' and explain a little bit the XEP in a practical way, (maybe just for users, not sure yet), and including maybe clients supporting this and that. Would thes be possible under the XSF and would this fit this team or...?
  87. Seve Because I thought the CommTeam would be something to promote XMPP in some way
  88. Seve But this is not clear for me
  89. Seve `The team's mission is to continuously improve the editorial quality of written, spoken, and visual materials produced by the XMPP Standards Foundation. `
  90. SaltyBones Seve, I think that would be great.
  91. SaltyBones Since this is going to be mostly links you can actually do anything as long as you do it somewhere else. Then we can just link to it.
  92. SaltyBones Linking to a "why gajim is trash" post would not even mean that we support this position or anything.
  93. Guus (note that there's no requirement to retain the previous charter. If you want to change it for the new team, go for it)
  94. SaltyBones So I think it's safe and any content you want to produce would be awesome.
  95. Seve I just say that because I wanted to see how this goes in order to understand if I could fit in the team or not. I would like to help on something but I'm a very very bad communicator. My skills for that are not good (starting with my english), so that's why I was afraid at saying "Count me in". But depending on what...
  96. guus.der.kinderen has joined
  97. guus.der.kinderen Seve, don't worry
  98. guus.der.kinderen Go for it
  99. Guus hey, mobile me
  100. Guus has left
  101. Guus has joined
  102. Guus there, we are one now.
  103. Seve Well, what do you guys think about it, then?
  104. Seve How do you guys see the Work team? What would be the goal? I would like to understand this, if possible. Do you see it as a group of people that promotes XMPP? Do you see it as what the previous work team said `improve the editorial quality of materials`? Or how do you see it?
  105. Guus I'd suggest something like this: "The Communcation Work Team primary goal is to facilitate the production and distribution of audio/visual media on behalf of the XSF and its mission. This can includes, but need not belimited to, management of the XSF Blog, website, newsletter and social media accounts."
  106. Guus that probably can be improved upon
  107. jcbrand Seve: I'm writing the email to the members list now
  108. jcbrand IMO the goal is informing the people who are interested in XMPP news about what's happening within the XMPP world
  109. jcbrand Simple as that
  110. jcbrand How it's done can be left up to the comms team members
  111. Seve jcbrand, please count me in
  112. jcbrand But there are some obvious tools, like the newsletter, social media, blogging etc.
  113. jcbrand Seve: ok!
  114. Seve Greaat! :D
  115. Guus it's good to see this springing back in action guys! thanks!
  116. jc has joined
  117. jcbrand I've sent out the email
  118. mathieui has joined
  119. Guus has left
  120. Guus has left
  121. jc has left
  122. jc has joined
  123. jc has left
  124. jc has joined
  125. Seve Thank you very muc for writing the email, jcbrand :)
  126. Guus has left
  127. SaltyBones class xmpp saying
  128. SaltyBones thank you very muc
  129. Seve laughs :D
  130. Guus has left
  131. Guus I didn't even spot that... :)
  132. jc has left
  133. jc has joined
  134. jcbrand has left
  135. jcbrand has joined
  136. jc has left
  137. jc has joined
  138. jcbrand has left
  139. SaltyBones has left
  140. jcbrand has joined
  141. jcbrand has left
  142. jc has left
  143. jc has joined
  144. jc has left
  145. jc has joined
  146. jc has left
  147. jc has joined
  148. jc has left
  149. jc has joined
  150. Guus has left
  151. SaltyBones has left
  152. Guus has left
  153. Guus has left
  154. Guus has left
  155. Guus has left
  156. SaltyBones has left
  157. jc has left
  158. jc has joined
  159. jcbrand has joined
  160. jcbrand has left
  161. Guus has left
  162. Guus has left
  163. Guus has left
  164. Guus has left
  165. Guus has left
  166. jc has left
  167. jc has joined
  168. jc has left
  169. jc has joined
  170. jcbrand has joined
  171. jc has left
  172. jc has joined
  173. Guus has left
  174. jc has left
  175. jc has joined
  176. Guus has left
  177. SaltyBones has left
  178. jc has left
  179. jc has joined
  180. SaltyBones has joined
  181. jc has left
  182. jc has joined
  183. jc has left
  184. Guus has left
  185. jc has joined
  186. Guus has left
  187. jc has left
  188. jc has joined
  189. Neustradamus has joined
  190. Neustradamus Whaouuuuu jc jcbrand, good news to read you ;)
  191. Guus has left
  192. Guus has left
  193. jc has left
  194. jc has joined