XSF Communications Team - 2020-04-03


  1. winfried has left

  2. winfried has joined

  3. peetah has left

  4. peetah has joined

  5. jcbrand has joined

  6. peetah has left

  7. peetah has joined

  8. peetah has left

  9. peetah has joined

  10. DebXWoody has joined

  11. emus has joined

  12. peetah has left

  13. peetah has joined

  14. peetah has left

  15. debacle has joined

  16. peetah has joined

  17. peetah has left

  18. peetah has joined

  19. winfried has left

  20. winfried has joined

  21. jcbrand

    emus: I'm not sure that we should link to you existing pull request

  22. jcbrand

    Are we always going to use this PR? Otherwise we need to always immediately create a new or PR and then update the MUC subject.

  23. emus

    jcbrand: Hmm, you mean for the people? I dont understand yet why to creat new PR? ahh you mean for muc. Then we can davise to the PR general site and look for the recent month?

  24. emus

    jcbrand: Hmm, you mean for the people? I dont understand yet why to creat new PR? ahh you mean for muc. Then we can advise to the PR general site and look for the recent month?

  25. emus

    Anyway, do you have all information you need for the release?

  26. jcbrand

    I think we can create a newsletter label for the PR and mark it with that. Then we can probably fine a URL which will link to the latest PR via there label.

  27. jcbrand

    I think we can create a "newsletter" label for the PR and mark it with that. Then we can probably fine a URL which will link to the latest PR via there label.

  28. jcbrand

    I think we can create a "newsletter" label for the PR and mark it with that. Then we can probably find a URL which will link to the latest PR via there label.

  29. jcbrand

    About the images, they can be added to a folder in the site, and then you link to them in the text. I don't think that can be done via the GitHub interface though.

  30. jcbrand

    I can do that manually, just put the URLs to the messages in a comment in the PR.

  31. jcbrand

    I'll look into merging the PR and sending it the newsletter tonight

  32. jcbrand

    I'll look into merging the PR and sending out the newsletter tonight

  33. emus

    > I think we can create a "newsletter" label for the PR and mark it with that. Then we can probably find a URL which will link to the latest PR via there label. Yes taht works

  34. emus

    jcbrand: Alright, ping me if I can do anything

  35. arnaudj has left

  36. arnaudj has joined

  37. debacle has left

  38. jcbrand has left

  39. debacle has joined

  40. jcbrand has joined

  41. DebXWoody has left

  42. jcbrand

    emus: I left a message on github regarding images, perhaps others here can also have a look there.

  43. jcbrand

    TL/DR: On 2nd thought I'm not convinced that we should upload newsletter images to the xmpp.org repo, given that it bloats the repo for IMO negligible benefit.

  44. jcbrand

    So we need to find a proper solution here and I think we should just leave images this time. I'll admit that I personally don't care much for images in emails in any case.

  45. emus

    jcbrand: I only uploaded it there because I didnt knew where to put those. You can delete the comment. However, I think its part of hightlighting things which is always good in a newsletter to let people have an glimpse over the horizon. I would continue on putting at least one or two pictures

  46. jcbrand

    I'm not referring to you uploading them there

  47. jcbrand

    My point is they need to be hosted somewhere

  48. jcbrand

    And originally I thought we'll put them in the repo, but now I think we shouldn't.

  49. emus

    jcbrand: but how have you processdd them before?

  50. peetah has left

  51. emus

    ok. so you uploaded those to the repo?

  52. peetah has joined

  53. emus

    I think there is a way to work around storing in the repo

  54. emus

    you can send the newsletter without this time

  55. jcbrand

    We never included images in the newsletter before, at least not when I sent it out

  56. emus

    🤔 thats wrong, all the recent ones had images? Or what do I not understand?

  57. emus has left

  58. debacle has left

  59. peetah has left

  60. peetah has joined

  61. Wojtek has joined

  62. emus has joined

  63. DebXWoody has joined

  64. DebXWoody has left

  65. emus has left

  66. emus has joined

  67. debacle has joined

  68. jcbrand

    I didn't work on the recent ones. I see that the last one simply points to an image on someone else's blog.

  69. jcbrand

    I'm not sure that this is a good idea. We have no guarantee that the images will remain hosted and available and we're leeching off of other people's bandwidth

  70. emus

    jcbrand: You mean working with links?

  71. jcbrand

    If you include an image by simply pasting a link that points to someone else's domain, then you're using their bandwidth and you're dependent on them keeping on hosting the image for you

  72. jcbrand

    In any case, I've merged the newsletter now

  73. jcbrand

    Once it's live I'll send out the email

  74. jcbrand

    hmmm... I checked locally and I see there are a bunch of broken links... for example to the translations

  75. jcbrand

    I'll have to fix that first... but I have to go now

  76. emus

    jcbrand: Can I do something?

  77. emus

    yes I understand about the domain

  78. DebXWoody has joined

  79. DebXWoody has left

  80. DebXWoody has joined

  81. jcbrand

    No worries, I've now pushed a commit to fix various links

  82. DebXWoody has left

  83. jcbrand

    Ok, I've sent out the newsletter. Fingers crossed it's all OK

  84. winfried has left

  85. winfried has joined

  86. winfried has left

  87. winfried has joined

  88. peetah has left

  89. peetah has joined

  90. DebXWoody has joined

  91. DebXWoody has left

  92. emus

    Came to my mailbox. What about the website?

  93. winfried has left

  94. winfried has joined

  95. jcbrand has left

  96. Licaon_Kter has left

  97. Licaon_Kter has joined

  98. jcbrand has joined

  99. jcbrand has left