XSF Editor Team - 2019-09-12


  1. pep.

    jonas’, please do tell me when you've got time to spare. I can probably adapt more easily. I'll be at a conference sunday to tuesday, wednesday I should be in dresden (from the afternoon). I'm still considering going to Berlin for the weekend, 19-22 (There's All Systems Go!), and after that I'm back to Dresden for a few days. until the 24th maybe. I'll be back maybe a week after that :P

  2. pep.

    We obviously don't have to do that IRL, online is perfectly fine. Dresden is just going be a place I've got time to do stuff :P

  3. pep.

    (I mean nothing planned in particular. I obviously have lots of bugs to fix in different projects)

  4. pep.

    https://github.com/xsf/xmpp.org/pull/599 this should have been accepted a while back :P

  5. pep.

    I suggest you reupdated it(?) < jonas’

  6. pep.

    I can't review it btw

  7. jonas’

    whoops

  8. pep.

    reupdate*

  9. jonas’

    thanks

  10. pep.

    Also the strophe update seems legit

  11. jonas’

    this is the wrong venue by the way

  12. pep.

    editor@ ?

  13. jonas’

    yes

  14. pep.

    That's not editor stuff?

  15. jonas’

    no

  16. pep.

    ok

  17. jonas’

    the website has nothing to do with the editor

  18. pep.

    oh

  19. pep.

    Is there a venue for that even

  20. jonas’

    xsf@

  21. pep.

    ok, sure

  22. jonas’

    pep., did you check out this one already? https://github.com/xsf/xeps/#gardening-issue-triaging-by-non-editors

  23. pep.

    nope, thanks

  24. jonas’

    that’s a good way to get your hands dirty

  25. jonas’

    for the last bullet point, always assign me

  26. jonas’

    there is no other editor at the moment :)

  27. jonas’

    (or, assign yourself and get your hands dirty with that ;))

  28. jonas’

    in more detail: https://github.com/xsf/xeps/#triaging-a-pr

  29. pep.

    I don't know you but I generally don't like having issues assigned randomly (by an outsider), especially in a team. It's certainly easier when it's a team of 1 :P

  30. pep.

    At least at work, I didn't like it

  31. jonas’

    pep., having anyone assigned is a good sign for "this has been completely triaged"

  32. jonas’

    we may change the procedure if you’re not fine with it, but for me it’s OK

  33. pep.

    I see

  34. pep.

    nah, if it has proper meaning associated to it it's fine. That sounds good

  35. pep.

    I don't like it when it's "hey you, deal with it" :)

  36. jonas’

    I’ll do some minor cleanup to the triaging section

  37. jonas’

    pep., https://github.com/horazont/xeps/tree/feature/readme-triage-update#triaging-a-pr

  38. pep.

    Thanks, I didn't mean to rush you

  39. jonas’

    oh, this was more like the "uh, this is wrong I need to fix it now" thing :)

  40. pep.

    heh

  41. pep.

    "Does the PR add a revision block? If no, add the Needs Version Block label." is that always necessary now?

  42. jonas’

    yes

  43. pep.

    ok

  44. jonas’

    updated it once more

  45. pep.

    You forgot 2. in 1. Sanity Checks ?

  46. jonas’

    no, moved it elsewhere

  47. pep.

    Ah, markdown doesn't care about numbering I see

  48. jonas’

    yeah

  49. pep.

    Just that they are numbers

  50. pep.

    It doesn't even check that they're increasing numbers :x

  51. jonas’

    cleaned that up

  52. pep.

    "2. If the PR does not a revision block" *add

  53. pep.

    /contain

  54. jonas’

    thanks, fixed

  55. pep.

    Same error below, in 5., sorry

  56. jonas’

    should be fixed there too

  57. jonas’

    did a s/// for that one :)

  58. pep.

    k

  59. pep.

    looks good otherwise

  60. jonas’

    thanks

  61. jonas’

    hitting the green button

  62. jonas’

    that should get you started until I can make time :)

  63. jonas’

    I have vacation starting tomorrow, that should help

  64. pep.

    k