XSF Communications Team - 2024-03-29


  1. gnemmi

    Hello everyone!

  2. gnemmi

    Hope you are all enjoying a beautiful Friday

  3. gnemmi

    If I may .. is there a way to get in touch with the Summits, Conferences & Meetups Work Team?

  4. gnemmi

    I did take a look at the wiki, but there's no MUC address listed =/

  5. MattJ

    Just invited you there

  6. gnemmi

    Hey! Thank you MattJ !!

  7. Mari0

    SCAM, at your own risk 😂️

  8. gnemmi

    LOL 😅️

  9. emus

    Dear all,

  10. emus

    .

  11. emus

    Dear all, the XMPP Newsletter "turns 50" 🙂 🎉️ That means the next release will be the 50. release. Many thanks all ready for your support so far. I am happy to hear if you have suggestions. I will post the PR soon. It's maybe also time to introduce changes if we have any. I'd would love to see more direct translations on the XSF website. at least for this release. We can also advertise to have more people translating.

  12. emus

    Btw, who were the initator of the XMPP Newsletter?

  13. Licaon_Kter

    👍

  14. MattJ

    Possibly Nyco

  15. MattJ

    But I don't recall for certain

  16. emus

    I asked JC

  17. TheCoffeMaker

    will try to make es translation, I think that will have time 🤞

  18. emus

    Great

  19. emus

    The pad has been closed for March 2024

  20. emus

    The PR is open: https://github.com/xsf/xmpp.org/pull/1366

  21. Mari0

    there are some errors, can't still have access to correct

  22. emus

    what do you mean by access?

  23. cal0pteryx

    Mari0: you have to contribute via your fork

  24. cal0pteryx

    That's how the github fork and merge workflow works

  25. Mari0

    ok

  26. Kris

    I think the git workflow is an unnecessary barrier to contribution and also prevents people from making quick corrections if they see mistakes.

  27. Kris

    and it's not really designed for collaborative document editing anyways

  28. MSavoritias (fae,ve)

    +1

  29. Mari0

    I synched my fork but can't see the March newsletter

  30. roughnecks

    > I think the git workflow is an unnecessary barrier to contribution and also prevents people from making quick corrections if they see mistakes. I agree, anyway here's a simple tutorial for pull requests: https://www.youtube.com/watch?v=rgbCcBNZcdQ

  31. roughnecks

    (not mine)

  32. Mari0

    https://share.sabatino.pro/upload/ssZ2aZTHRLfsSEdXynlbzcl1/Schermata%20del%202024-03-29%2017-36-58.png

  33. MSavoritias (fae,ve)

    personally i just create a new fork every time because i cant be bothered to understand how git works

  34. MSavoritias (fae,ve)

    if i dont i somehow dont have the changes

  35. Mari0

    I decided to start a wiki using git causa i want to learn how to use it

  36. Mari0

    I decided to start a wiki using git cause i want to learn how to use it

  37. MSavoritias (fae,ve)

    fair. i want at some point to

  38. Mari0

    > > I think the git workflow is an unnecessary barrier to contribution and also prevents people from making quick corrections if they see mistakes. > I agree, anyway here's a simple tutorial for pull requests: https://www.youtube.com/watch?v=rgbCcBNZcdQ thx roughnecks, :-)

  39. roughnecks

    👍️

  40. cal0pteryx

    As emus pointed out, there is the Pad for general contributions, which is open until some days before the github PR is opened. Editing the pad is easy and possible for everyone. It's not necessary to know any git until this point. Then, the review process starts. During review, it is best to be able to track changes, and git offers the tools for this. In fact, you don't even need to know Git during this step, because you can just use github's web interface for that.

  41. cal0pteryx

    As soon as the PR is merged and you want to correct anything after that, you need to use git(hub). But you can go through github's web interface without touching git as well.

  42. cal0pteryx

    It's as simple as: go to the website, click "Edit on GitHub", edit the file, Commit, make a pull request

  43. cal0pteryx

    > I think the git workflow is an unnecessary barrier to contribution and also prevents people from making quick corrections if they see mistakes. I don't see any better way. Do you, Kris?

  44. Kris

    I don't think you can edit other peoples pull requests on github

  45. Kris

    maybe I am overlooking something though

  46. cal0pteryx

    Sure you can

  47. cal0pteryx

    _but_ that not necessary, is it? During review, you leave a comment. That's how I do it, at least. Then, the original author applies comments

  48. Kris

    I am not sure what a better way would be, maybe a wiki? but I sure have seen it multiple times here that errors ended up in the published news letters and people running into issues with the git based workflow, me included and I know basic git stuff

  49. Kris

    I guess the issue might be that once you ask for review it is already in git and then people are turned off by the complicated workflow?

  50. Kris

    maybe a review step before doing the git PR would help?

  51. Kris

    fixing typos and stuff in git is tedious

  52. cal0pteryx

    Kris, as I said, you don't even need to understand any of this fork and merge workflow if you just leave comments on the github PR. comments as in: you click a line, write text, click comment

  53. Kris

    yeah that might be an option, but that feature is pretty hidden in github

  54. Kris

    also more and more people don't have github accounts on purpose...

  55. cal0pteryx

    well, what we could do is a call for review before moving stuff to github, so that there are two days of review in the pad. but I think we did that before

  56. Kris

    lets try that next time, maybe it helps

  57. cal0pteryx

    alright!

  58. emus

    I am also happy to have more support on the preparations. I am happy to just put a quite final version to github

  59. emus

    Even its really great (muy bien todos!) - how many people working on their own spanish translation have we? 2 groups? 😄

  60. emus

    TheCoffeMaker, gnemmi, Mari0:

  61. gnemmi

    yo

  62. gnemmi

    Im done over here

  63. gnemmi

    just finished the spanish translation

  64. gnemmi

    was just about to git add the file

  65. TheCoffeMaker

    gnemmi: Great!

  66. gnemmi

    😁️

  67. gnemmi

    [gnemmi@e490 blog]% git add 2024-04-05-newsletter-ES.md

  68. emus

    gnemmi, TheCoffeMaker: Mari0 just did push his translation

  69. gnemmi

    ok .. should I throw mine away?

  70. emus

    Nope, please align what to do now. You can check and see who has the better formulations

  71. gnemmi

    Ok ... so .. What I can do is send my translation so any other translation can review it/ compare / merge / etc ..

  72. gnemmi

    I just can figure out the right command =/

  73. gnemmi

    git clone -b newsletter-mar24 https://github.com/xsf/xmpp.org.git

  74. gnemmi

    that's how I got the source

  75. gnemmi

    then git add my file

  76. gnemmi

    now, how the heck do I make the commit to that branch??

  77. TheCoffeMaker

    gnemmi: you need to fork the repo and use it as working project

  78. gnemmi

    🫠️

  79. TheCoffeMaker

    😅

  80. emus

    Well, you could push you version against the one fron mario and see the differences and then discuss

  81. Kris

    git diff for translations isn't going to do so well I fear 😅️

  82. gnemmi

    https://files.xmpp.social/upload/72890ba3e7e6bc7f1b993e487d3d149fd09e3184/Yidrniq1LcrxgkoTZFhSlHtcCTAyhtaNz4ngm1uw/2024-04-05-newsletter-ES.md

  83. gnemmi

    and theeeeeeeeeeeeeere we go ..

  84. gnemmi

    [gnemmi@e490 blog]% git push remote: Support for password authentication was removed on August 13, 2021.

  85. gnemmi

    I tried on every imaginable way but I was 1 commit ahead of master so I had to do a push but push was removed ..

  86. gnemmi

    so .. there's the spanish translation

  87. gnemmi

    TheCoffeMaker, Please, do take a look at the whole thing when you can

  88. gnemmi

    TheCoffeMaker, here's the file with Mari0's changes https://github.com/xsf/xmpp.org/pull/1368

  89. gnemmi

    just 2 lines

  90. gnemmi

    https://files.xmpp.social/upload/72890ba3e7e6bc7f1b993e487d3d149fd09e3184/JmOnPGhj4W9DGfe0oRJv1mqO0VMUntbDYgfhUexv/2024-04-05-newsletter-ES.md

  91. gnemmi

    there .. with Mario's patch

  92. gnemmi

    😁️

  93. gnemmi

    just add that file to the tree so we can take a look at the rich text 👍️

  94. TheCoffeMaker

    gnemmi: there are a few changes that must be addressed, check past spanish translations for standardized names

  95. gnemmi

    Will do

  96. TheCoffeMaker

    will be on my puter later, ping u on xmpp:es-translators@conference.cyberdelia.com.ar?join as soon as I get ready