XSF Editor Team - 2022-12-14


  1. larma

    .

  2. jonas’

    larma, so you're saying merge as-is (except for the revision block?)

  3. jonas’

    larma, so you're saying merge as-is (except for the revision block)

  4. jonas’

    larma, so you're saying merge as-is (except for the revision block)?*

  5. jonas’

    larma, so you're saying merge as-is (except for the revision block)?

  6. larma

    Nicoco told me that he's still some changes pending on that one, so it makes sense to wait for those first.

  7. larma

    I think https://github.com/xsf/xeps/pull/1188 would be ready to merge though.

  8. larma

    Nicoco also wanted to change a few bits on #1251, so waiting also makes sense there.

  9. Kev

    Reading through the triaging workflow at the moment, which of the tooling relies on the naming of a PR being "ProtoXEP: Title..."?

  10. Kev

    (Or XEP-XXXX for non-protos)

  11. jonas’

    no tooling, but human

  12. jonas’

    when multiple PRs are affecting the same document, one might want to group them together.

  13. Kev

    Ta.

  14. Kev

    And that only affects the PR title, not the commit title?

  15. jonas’

    correct

  16. jonas’

    just for overview in the PR list really

  17. jonas’

    we can also drop that with a workflow which requires less manual work

  18. jonas’

    but as long as you have to process PRs manually as currently, it's immensely helpful to see if multiple PRs touch the same document

  19. Kev

    Do we have any policy about Editors doing the work on commits, where the issuer ticks that box?

  20. Kev

    version blocks, etc.

  21. jonas’

    I do that

  22. jonas’

    if I'm in the mood anyway and it saves me round-trips

  23. jonas’

    (to the point where I'll --amend commits)

  24. Kev

    By amending the original commit, or another com...

  25. Kev

    K.

  26. Kev

    Are the other instructions (processing particularly) believed current?

  27. jonas’

    https://github.com/xsf/xeps/blob/master/docs/PROCESSING.md

  28. jonas’

    this applies, *except* for the docker build thing

  29. jonas’

    because that broke, you have to do it locally, push it manually and pull it manually on eos2

  30. jonas’

    except that I don't bother with the labels at all anymore

  31. jonas’

    and I suspect you saw https://github.com/xsf/xeps/blob/master/docs/TRIAGING.md

  32. Kev

    Yes ta.

  33. emus

    jonas’, Kev, MattJ: Do you want me to organise a separate meeting on the topic? Hope I did not forget anyone offering support here (I leave volunteers to do the actual work out here for the moment, so we can arrange and come up with a plan)

  34. Kev

    I'd have thought if people need to talk about how to get things done in the short term they can just talk here, as Jonas and I did earlier.

  35. emus

    Well, I meant to meet here and discuss at the same time and also get together on.the topic at the same time

  36. Kev

    As Jonas has very kindly offered to hang around and offer advice after retiring, my inclination would just be to see how things roll out, and take corrective action if it doesn't work out, but if Jonas/Peter/anyone else inclined to do Editor legwork past or presents wants a meeting I'll go along with whatever.

  37. Kev

    As Jonas has very kindly offered to hang around and offer advice after retiring, my inclination would just be to see how things roll out, and take corrective action if it doesn't work out, but if Jonas/Peter/anyone else inclined to do Editor legwork past or present wants a meeting I'll go along with whatever.

  38. emus

    > we need: (1) an acting editor (2) people to write the tooling those were the points to discuss