XSF Editor Team - 2017-09-25

  1. Guus has left

  2. winfried has left

  3. Guus has left

  4. Guus has left

  5. Tobi has left

  6. SamWhited has left

  7. Tobi has joined

  8. Guus has left

  9. Guus has left

  10. Guus has left

  11. Guus has left

  12. SouL has joined

  13. SamWhited has left

  14. Guus has left

  15. Guus has left

  16. Guus has left

  17. Guus has left

  18. winfried has joined

  19. Guus has left

  20. Guus has left

  21. Guus has left

  22. Guus has left

  23. Flow has joined

  24. Guus has left

  25. Guus has left

  26. Guus has left

  27. winfried has joined

  28. winfried has left

  29. jcbrand has joined

  30. jcbrand has left

  31. Guus has left

  32. Guus has left

  33. Guus has left

  34. Guus has left

  35. Guus has left

  36. winfried has joined

  37. Guus has left

  38. Guus has left

  39. jcbrand has left

  40. SamWhited has joined

  41. winfried has joined

  42. SamWhited has joined

  43. Guus has left

  44. Guus has left

  45. jonasw has left

  46. Guus has left

  47. Guus has left

  48. Guus has left

  49. Flow has joined

  50. SamWhited

    We already have a Trello for boards, FYI, please do not use GitHub boards. I don't really care between the two, but let's not duplicate info and everyone was already using Trello.

  51. SamWhited

    I have closed the GitHub boards.

  52. SamWhited

    Feel free to rearrange or rename columns in the trello board if you need to. If you can't, let me know and I'll fix permissions (but I think everyone can)

  53. jonasw

    I don’t like trello.

  54. SamWhited

    Me neither.

  55. jonasw

    any good reason not to move to github "projects"?

  56. jonasw

    they’re nicely integrated.

  57. SamWhited

    Everyone was already using Trello

  58. jonasw

    there’s no tight coupling between the boards, is there?

  59. SamWhited

    If the council has a thing on Trello, they can move it directly to the editor board. Let's not try to change our entire process just because I don't love something.

  60. SamWhited

    It works and is "good enough".

  61. jonasw

    right, maybe I don’t know trello well enough

  62. SamWhited


  63. jonasw

    what I liked about the github things is that you can see right on the PR what the status in council etc. is

  64. Guus

    (github has a Trello-like feature?)

  65. jonasw

    Guus, yeah, they added that a few months ago I think

  66. SamWhited

    Guus: I think they call it "Projects", it's fairly recent.

  67. jonasw

    I used it to track PRs through council

  68. SamWhited

    I assume Trello has a GitHub integration we could enable, but I haven't tried it; it was never really a problem.

  69. SamWhited

    I just don't want info ending up in two places with council looking at our Trello and half the stuff being on GitHub.

  70. jonasw

    I put the stuff on council trello whenever needed.

  71. jonasw

    SamWhited, what do you suggest as a means of communication so that work I do on the xeps repo (e.g. with respect to tooling) is seen by all active editors?

  72. jonasw

    I tried PRs on the xeps repository which apparently didn’t really help.

  73. jonasw

    I can ping the editors list, do you think that’d be more useful?

  74. jonasw

    also it’d have been nice to get some notice before you simply close the boards -- they are referenced in the current readme

  75. jonasw

    and I currently don’t have the time to re-work the readme

  76. jonasw

    also it is a bit demotivating to get my work (thought put into a process I can work efficiently with, given that there was only sparse documentation, the timezone issue noone of us can do something about and the huge backlog) reverted without a word of discussion.

  77. Guus has left

  78. SamWhited

    jonasw: the email list would be good for communication

  79. jonasw

    right, let’s try that

  80. SamWhited

    Sorry if it's demotivating, but please don't just duplicate work that's already been done.

  81. Guus has left

  82. jonasw

    SamWhited, I understand.

  83. Guus has left

  84. SamWhited

    Reworked the readme: https://github.com/xsf/xeps/pull/519

  85. SamWhited

    If we want to change in the future that's fine, but for now let's not make the editor process require any more steps than it already does.

  86. SamWhited

    And let's discuss before changing the process.

  87. Guus has left

  88. jonasw

    SamWhited, okay, fair

  89. jonasw

    I’m composing an email with an overview of what I did in the last month besides working on XEP updates.

  90. Guus has left

  91. jonasw

    thanks for the fix to the readme

  92. SamWhited

    Sure thing; thanks for all the work you've been doing?

  93. SamWhited

    !, even.

  94. Guus has left

  95. jonasw

    email sent, have fun reading it :)

  96. Guus has left

  97. Guus has left

  98. Guus has left

  99. SamWhited has joined

  100. Guus has left

  101. Guus has left

  102. Guus has left

  103. Guus has left

  104. Guus has left

  105. Guus has left

  106. Guus has left

  107. Guus has left

  108. soul has left

  109. soul has joined

  110. Guus has left

  111. Guus has left

  112. Tobi has left

  113. Guus has left

  114. Guus has left

  115. Guus has left

  116. Guus has left

  117. winfried has left

  118. Guus has left

  119. winfried has left

  120. SamWhited has left

  121. Guus has left

  122. SamWhited has joined

  123. SamWhited has joined