XSF Editor Team - 2020-03-02


  1. debacle has left
  2. ابو صهيب اصدارات has left
  3. ابو صهيب اصدارات has joined
  4. ابو صهيب اصدارات has left
  5. winfried has left
  6. winfried has joined
  7. lnj has joined
  8. winfried has left
  9. winfried has joined
  10. debacle has joined
  11. ابو صهيب اصدارات has joined
  12. ابو صهيب اصدارات has left
  13. ابو صهيب اصدارات has joined
  14. debacle has left
  15. winfried has left
  16. winfried has joined
  17. ابو صهيب اصدارات has left
  18. winfried has left
  19. winfried has joined
  20. pep. jonas’, do you have a list of things you'd like to see done by editors, I'm thinking tooling mostly
  21. jonas’ registry
  22. pep. Or infra
  23. jonas’ registry
  24. pep. yeah registry
  25. jonas’ xeps themselves are manageable
  26. jonas’ it’s currently blocking on iteam
  27. jonas’ AFAIK
  28. pep. I know, so it's not in my power really :/
  29. jonas’ you can do editorial work on the registries
  30. jonas’ like checking the content of the XMLs against the XEPs
  31. jonas’ they haven’t been updated in at least three years
  32. pep. Ok so tooling for that would be a thing to do
  33. jonas’ I don’t think you can do tooling for that
  34. jonas’ but go ahead
  35. pep. Just curious
  36. jonas’ one could try to scrape the registry submissions from the documents
  37. jonas’ but that sounds error-prone
  38. pep. What else?
  39. jonas’ do it manually
  40. pep. I mean what else could use tooling
  41. jonas’ I don’t think one can create tooling for this which won’t fail silently or have lots of false positives
  42. jonas’ I don’t know
  43. jonas’ I’m happy with the current tooling
  44. pep. k
  45. jonas’ except that I’d like to automate email sending, but that mostly requires infrastructure
  46. jonas’ or faster build processes, but that also requires infrastructure
  47. jonas’ I fix most pain points in the tooling myself
  48. jonas’ I should proablby commit my scripts to create tags though
  49. jonas’ there are a few nice-to-haves
  50. jonas’ I guess
  51. jonas’ like a bot which analyses new PRs and automatically assigns labels (ProtoXEP, Needs Council, Needs Author, Needs Board)
  52. pep. Yeah that's also something I wanted
  53. jonas’ something which creates and maintains a todo list for editors, because it’s not always clear what needs to be done
  54. jonas’ and my attempt at introducing Github Projects for that was shot down
  55. pep. yeah
  56. jonas’ which is a shame, because they even got more automation for those nowadays
  57. pep. shot down by whom?
  58. jonas’ someone from the Editor team
  59. jonas’ check the commit history
  60. jonas’ of README.md
  61. pep. ok
  62. pep. Well now that you're managing editors almost by yourself..
  63. pep. I'm not personally against it
  64. jonas’ I also effectively was back then
  65. pep. That would tie us even more to github, but I don't see us moving any time soon as much as I would like it
  66. jonas’ for what reason?
  67. pep. me wanting to move?
  68. jonas’ yes
  69. pep. I had that clear in mind some time ago. I'd say one of the biggest reason now is because I'm generally not fond of big hubs
  70. jonas’ we don’t have the resources to host our own.
  71. pep. I'm aware of that, which is why I'm saying I don't see us moving to that
  72. jonas’ so there’s no reason to not make use of the platform we currently have
  73. pep. We agree
  74. jonas’ right
  75. winfried has left
  76. winfried has joined
  77. Kev jonas’: The XSF is in GSoC this year. I wonder if one could wrangle a XEP management platform as a project
  78. Kev The email automation thing I think can be done with 'moderate' ease (hours of coding rather than weeks), by recording the last-announced versions of everything and the current versions, and sending emails on container startup if they differ. But I'm not volunteering, I'm afraid.
  79. lnj has left
  80. pep. I don't think that's a good idea. GSoC takes quite some time for mentors if done properly, more than if we were to do it ourselves
  81. jonas’ Kev, the email thing is essentially just a webhook and two lines of code. or one line of code if you do it on the XSF server which knows when stuff has happened either way.
  82. jonas’ but frankly, email sending is least of my concernsn
  83. lnj has joined
  84. ابو صهيب اصدارات has joined
  85. ابو صهيب اصدارات has left
  86. winfried has left
  87. winfried has joined
  88. winfried has left
  89. winfried has joined
  90. stpeter has joined
  91. winfried has left
  92. winfried has joined
  93. winfried has left
  94. winfried has joined
  95. winfried has left
  96. winfried has joined
  97. debacle has joined
  98. winfried has left
  99. winfried has joined
  100. winfried has left
  101. winfried has joined
  102. winfried has left
  103. winfried has joined
  104. winfried has left
  105. winfried has joined
  106. winfried has left
  107. winfried has joined
  108. winfried has left
  109. winfried has joined
  110. lnj has left
  111. Tobi has left
  112. winfried has left
  113. winfried has joined
  114. winfried has left
  115. winfried has joined
  116. winfried has left
  117. winfried has joined
  118. winfried has left
  119. winfried has joined