XSF Editor Team - 2017-09-25

  1. 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.

  2. SamWhited

    I have closed the GitHub boards.

  3. 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)

  4. jonasw

    I don’t like trello.

  5. SamWhited

    Me neither.

  6. jonasw

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

  7. jonasw

    they’re nicely integrated.

  8. SamWhited

    Everyone was already using Trello

  9. jonasw

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

  10. 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.

  11. SamWhited

    It works and is "good enough".

  12. jonasw

    right, maybe I don’t know trello well enough

  13. SamWhited


  14. jonasw

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

  15. Guus

    (github has a Trello-like feature?)

  16. jonasw

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

  17. SamWhited

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

  18. jonasw

    I used it to track PRs through council

  19. SamWhited

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

  20. 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.

  21. jonasw

    I put the stuff on council trello whenever needed.

  22. 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?

  23. jonasw

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

  24. jonasw

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

  25. jonasw

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

  26. jonasw

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

  27. 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.

  28. SamWhited

    jonasw: the email list would be good for communication

  29. jonasw

    right, let’s try that

  30. SamWhited

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

  31. jonasw

    SamWhited, I understand.

  32. SamWhited

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

  33. 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.

  34. SamWhited

    And let's discuss before changing the process.

  35. jonasw

    SamWhited, okay, fair

  36. jonasw

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

  37. jonasw

    thanks for the fix to the readme

  38. SamWhited

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

  39. SamWhited

    !, even.

  40. jonasw

    email sent, have fun reading it :)