XSF Editor Team - 2023-03-09


  1. stpeter has joined

  2. winfried has left

  3. stpeter has left

  4. snow has left

  5. snow has joined

  6. winfried has joined

  7. Tobi has joined

  8. Tobi has left

  9. winfried has left

  10. Tobi has joined

  11. Tobi has left

  12. larma has left

  13. MSavoritias (fae,ve) has joined

  14. Tobi has joined

  15. snow has left

  16. Tobi has left

  17. Tobi has joined

  18. Tobi has left

  19. Tobi has joined

  20. wurstsalat has joined

  21. emus has joined

  22. soul has left

  23. soul has joined

  24. winfried has joined

  25. winfried has left

  26. Kev has joined

  27. pep.

    Is there a way to include commit information when building xeps? Last commit to have modified the file.

  28. jonas’ has left

  29. pep.

    I find this useful when serving new changes to be discussed

  30. pep.

    (stuff I build locally and upload somewhere for everyone to see)

  31. pep.

    But I'd also find useful to have this info available in XEPs in general anyway

  32. flow has left

  33. flow has joined

  34. larma has joined

  35. Guus has joined

  36. Guus

    I've dutifully followed TRIAGING and applied the "Needs Editor Action" label to https://github.com/xsf/xeps/pull/1214 - but is there anything that I can do to move this along?

  37. tmolitor

    Guus: I guess adding a commit putting the xep back into experimental (if that's the only editor action needed)

  38. tmolitor

    jonas': ist that correct? --^

  39. Guus

    tmolitor: yeah, if it's something easy like that, I'm happy to. I'm just not sure exactly what's needed.

  40. Guus

    Apart from processes to be completed, is there stopping something from this being moved to council?

  41. tmolitor

    no, no stoppers...it is not even needed to move that to council because it's an experimental xep and the original author already gave his okay, so it's fine to just be merged and published afaik

  42. tmolitor

    speaking of publishing the xep: XEP-0353 is merged, but not yet published, right? (the update announcement on standards@ and the update of the html rendering on xmpp.org is still missing)

  43. tmolitor

    Guus: --^

  44. Kev

    > Guus: I guess adding a commit putting the xep back into experimental (if that's the only editor action needed) I don't have time to look right now, but if the only thing blocking on triage is that it needs to bump to experimental again from deferred, adding that block speeds things up, yes.

  45. Guus

    I don't know anything about publishing, tmolitor

  46. Kev

    > speaking of publishing the xep: XEP-0353 is merged, but not yet published, right? (the update announcement on standards@ and the update of the html rendering on xmpp.org is still missing) I've merged some things but not done the corresponding publish, yes.

  47. Guus

    Does the move to experimental require a new revision block?

  48. Kev

    Moving to experimental requires changes to the XEP, and changes to the XEP require a new version block.

  49. tmolitor

    but only if the current version block was already published

  50. tmolitor

    which it was not in case of XEP-0388

  51. tmolitor

    > Moving to experimental requires changes to the XEP, and changes to the XEP require a new version block.

  52. tmolitor

    so changing just the status to experimental should suffice for XEP-0388

  53. Guus

    This is my attempt: https://github.com/xsf/xeps/pull/1214/commits/7615b5070526cc2a36a65f4ef9411cfc4ebb5815

  54. Guus

    note that I'm casually identifying myself as an editor here.

  55. Guus

    (which I am not)

  56. Kev

    That's not right.

  57. tmolitor

    and because the newest commit of a xep should always contain a revision block, adding the "experimental" to my pull request branch and then doing a squashing merge of that branch should be fine

  58. tmolitor

    Kev: why?

  59. Kev

    Because Guus has pushed a 0.4.1 change that does nothing but change from Deferred to Experimental, when there was never a published 0.4.0

  60. tmolitor

    yes, I thought you meant my comment about just changing the 0.4.0 to also include the change back to experimental...

  61. Kev

    I'm saying that Guus's commit is wrong.

  62. Guus

    I'll remove the revision block and add a LI on the last one.

  63. tmolitor

    okay, so Guus should do what I suggested above (create a new commit containing that change but without a version block, then squash merge the whole branch)?

  64. Tobi has left

  65. Guus

    how's this?

  66. Kev

    Guus shouldn't merge anything. But if that branch contains a single commit that both adds the right version block and changes it from Deferred to Experimental, I believe it'll be ready to merge.

  67. tmolitor

    okay, that's nearly the same, just Guus stopping processing before merging that and someone different (you, Kev?) doing the squashing merge...

  68. Tobi has joined

  69. Tobi has left

  70. Tobi has joined

  71. emus

    Shouldnt we just try it? I mean, if triage fails (?) we can manually revert and correct the script?

  72. emus

    sorry wrong movie

  73. Kev

    I have no idea what you're talking about, sorry.

  74. snow has joined

  75. Kev

    And I'm sorry I'm not being as patient as I should today. If anyone has a spare ten or twenty hours in the day, please send them, I need them.

  76. Guus

    Hey, don't start hogging spare hours all by yourself!

  77. Guus

    it's fine, Kev. We've all been there.

  78. Guus

    as for me: trying to walk that balance between being helpful and causing more work is tricky.

  79. Guus

    now: dinner.

  80. snow has left

  81. winfried has joined

  82. tmolitor

    I hope your dinner is no work :)

  83. winfried has left

  84. winfried has joined

  85. snow has joined

  86. Tobi has left

  87. Tobi has joined

  88. Tobi has left

  89. Tobi has joined

  90. Tobi has left

  91. Tobi has joined

  92. Tobi has left

  93. Tobi has joined

  94. Tobi has left

  95. Tobi has joined

  96. Tobi has left

  97. Tobi has joined

  98. Tobi has left

  99. Tobi has joined

  100. Tobi has left

  101. Tobi has joined

  102. Tobi has left

  103. Tobi has joined

  104. Tobi has left

  105. Tobi has joined

  106. Tobi has left

  107. Tobi has joined

  108. snow has left

  109. Tobi has left

  110. Tobi has joined

  111. Tobi has left

  112. Tobi has joined

  113. Tobi has left

  114. Tobi has joined

  115. Tobi has left

  116. Tobi has joined

  117. Tobi has left

  118. Tobi has joined

  119. Tobi has left

  120. Tobi has joined

  121. Tobi has left

  122. Tobi has joined

  123. winfried has left

  124. emus

    > Kev: > 2023-03-09 05:32 (GMT+01:00) > I have no idea what you're talking about, sorry. I thought it was about automation stuff

  125. Kev has left

  126. larma has left

  127. larma has joined

  128. Guus has left

  129. MSavoritias (fae,ve) has left

  130. Link Mauve has joined

  131. Tobi has left

  132. Tobi has joined

  133. winfried has joined

  134. Tobi has left

  135. Tobi has joined