XSF Communications Team - 2020-04-16


  1. debacle has left
  2. Bastien has left
  3. emus has left
  4. Wojtek has left
  5. Bastien has joined
  6. SouL has joined
  7. Vaulor has joined
  8. DebXWoody has joined
  9. emus has joined
  10. emus I think they are a good way to enable community involvement from people with not so much tech-background. Translations would be great in general I think. However with the lack of ressources dunno where to go.
  11. jcbrand has joined
  12. jcbrand Link Mauve: because coordinating them takes time and energy and we're few people. It's better to be a bit less ambitious and be able to do something for longer than to burn out quickly by doing too much.
  13. jcbrand I'll never stop someone from making translations, but I don't see the point in going out of our way to accommodate them either
  14. emus has left
  15. Alex has left
  16. Alex has joined
  17. Guus +1
  18. pep. well the technical/infra stuff only has to be done once
  19. emus has joined
  20. emus > well the technical/infra stuff only has to be done once Yes, I'm happy to translate. but what burns down is transfering between the platforms. I at least that is what we should improve. And even without translations, there are still needs to transfer text back to the Wiki and someone has to merge it to the website from github. Last time also formating was not process (no offence, just to clarify about the problem). And we althought think about not using pictures anymore because of traffic or so...... I mean, ... really?
  21. emus Guus: Thanks for your help in the Monal issue btw
  22. Guus Np
  23. jcbrand has left
  24. jcbrand has joined
  25. Neustradamus has joined
  26. Neustradamus has left
  27. debacle has joined
  28. emus has left
  29. emus has joined
  30. SouL has left
  31. SouL has joined
  32. intosi has left
  33. intosi has joined
  34. Wojtek has joined
  35. Wojtek has left
  36. Wojtek has joined
  37. Wojtek has left
  38. Wojtek has joined
  39. Guus has left
  40. Guus has joined
  41. Link Mauve Something I’d like to do wrt translations is more technical ones.
  42. Link Mauve For instance the XEPs are unreadable if you don’t speak English.
  43. Link Mauve Same for xmpp.org.
  44. Link Mauve When I wrote my first XMPP client, XMPP wasn’t any more open than any proprietary protocol due to the specs being English-encrypted.
  45. Link Mauve I don’t have the time or energy to pour into doing a translation of xmpp.org, but that would be a good direction to go imo.
  46. emus Link Mauve: For that sounds like a good suggestion! I still would stick to keep the term wording english. But yes. that would be a cool project I think
  47. emus Link Mauve: For me that sounds like a good suggestion! I still would stick to keep the term wording english. But yes. that would be a cool project I think
  48. Link Mauve Depends on the language, we tend not to do that in French for instance.
  49. emus Yes, I know, you should try to translate once, eg. Last Message Correction. But afterwards stick to the english term. (My intention is, that we keep the wording in general similar)
  50. emus on an inter-cultural basis
  51. Link Mauve I still think it depends on the language.
  52. Link Mauve Languages not using a Latin alphabet will probably want to use names in their languages instead.
  53. Link Mauve French too usually.
  54. Link Mauve Except maybe for acronyms?
  55. Link Mauve German is usually fine with keeping English terms around.
  56. jcbrand emus: my issues with images was that it's not clear where they should be hosted and I'm not sure simply copying URLs from somewhere else is a good idea.
  57. jcbrand Perhaps others here have some ideas or suggestions
  58. jcbrand To host them ourselves, we need to put them in our repo, which I don't think is a good idea
  59. jcbrand But perhaps there's another way
  60. DebXWoody Why not keep the files of newsletter in a repo in md-format an deploy all within on site?
  61. DebXWoody The english is on xmpp.org, isn't it?
  62. jcbrand I'm specifically talking about images here
  63. jcbrand The newsletter is already in markdown format in the xmpp.org repo
  64. emus Ok, yes. Absolute not blaming or offending. I just wanted to show that we think about think we maybe shouldn`t about. I mean that in a positive manner
  65. emus Ok, yes. Absolutely not blaming or offending. I just wanted to show that we think about think we maybe shouldn`t about. I mean that in a positive manner jcbrand:
  66. DebXWoody Why not keep the fr, de,... at the same place?
  67. jcbrand DebXWoody: that would probably be better than having them hosted elsewhere.
  68. emus > To host them ourselves, we need to put them in our repo, which I don't think is a good idea > But perhaps there's another way Yes sure, I agree
  69. DebXWoody In a second step we can think about to generate tar.gz files to download.
  70. DebXWoody an generate some small "post records" like "The new newsletter of xmpp is avaiable on xmpp.org site.... <link>". Which can be used by others (microblog, social media,...)
  71. emus DebXWoody: If you have an open repo for this, you just fork it or? Sounds a bit complicated, or?
  72. arnaudj has left
  73. jcbrand has left
  74. DebXWoody has left
  75. jcbrand has joined
  76. arnaudj has joined
  77. Licaon_Kter has left
  78. Licaon_Kter has joined
  79. Licaon_Kter has left
  80. jcbrand has left
  81. SouL has left
  82. Wojtek has left