XSF Editor Team - 2022-12-15


  1. jonas’

    FTR: https://github.com/xsf/xeps/issues?q=is%3Aopen+is%3Aissue+label%3A%22Editor+Tooling%22

  2. jonas’

    I also put that in the topic of this room now

  3. emus

    👍

  4. MattJ

    emus, were you in the board meeting? :) Kev and stpeter will be stepping up to perform editor duties

  5. MattJ

    I feel like we settled loads of stuff in the meeting, and all I keep hearing is that we need to settle stuff

  6. emus

    > MattJ: > 2022-12-15 04:49 (GMT+01:00) > emus, were you in the board meeting? :) Kev and stpeter will be stepping up to perform editor duties I didnt understood it like this tbh

  7. ralphm

    Peter literally said this, Kev said he'd help out

  8. MattJ

    Exactly

  9. emus

    ok

  10. MattJ

    In case it was also missed: MSavoritias volunteered to write stuff too, on the condition it doesn't require interacting with Github (they were shown several tasks that do not require Github interaction). Also, Guus has already been doing some more work on the XEP linter (another part of the tooling). Things are moving.

  11. MattJ

    And Jonas and I agreed to be the technical leads for anyone working on tooling (so we can provide guidance, answer questions). Between the two of us we have a good handle on what's required.

  12. ralphm

    yay

  13. MattJ

    However I also appreciate the point raised by multiple people during the meeting, which is that people doing the editor work once Jonas stops should also have the most input into the tooling.

  14. MattJ

    Once Jonas leaves, building out the workflow that suited Jonas may not be ideal :)

  15. MattJ

    I actually think this doesn't apply the majority of tasks we have specified currently, so I'm not too worried about it, but it's something to bear in mind as we move forward

  16. MattJ

    Also stpeter raised the good point about working on the problem from the other direction: simplifying the current process, if we identify points where it can be simplified

  17. Kev

    TBH, I think the vast majority of the current workflow can be automated such that it won't cause too much pain, even without refining the process.

  18. Kev

    (Not that I'm arguing against simplifying process)

  19. MattJ

    Yeah, I don't see any simplification removing the desire for a linter, or removing the desire for something that displays and informs about the results of a merge, for example

  20. emus

    > MattJ: > 2022-12-15 05:04 (GMT+01:00) > In case it was also missed: MSavoritias volunteered to write stuff too, on the condition it doesn't require interacting with Github (they were shown several tasks that do not require Github interaction). Also, Guus has already been doing some more work on the XEP linter (another part of the tooling). Things are moving. Yeah, I wanted to remind that too

  21. emus

    > MattJ: > 2022-12-15 05:05 (GMT+01:00) > And Jonas and I agreed to be the technical leads for anyone working on tooling (so we can provide guidance, answer questions). Between the two of us we have a good handle on what's required. btw I think that was not clear in the meeting minutes in the end right?

  22. MattJ

    I haven't reviewed the minutes yet, but if these things are not clear then of course they should be

  23. ralphm

    Let's just get on with the tasks at hand. I think what and who has been spelt out now.