XSF Editor Team - 2020-03-02

jonas’, do you have a list of things you'd like to see done by editors, I'm thinking tooling mostly

registry

Or infra

registry

yeah registry

xeps themselves are manageable

it’s currently blocking on iteam

AFAIK

I know, so it's not in my power really :/

you can do editorial work on the registries

like checking the content of the XMLs against the XEPs

they haven’t been updated in at least three years

Ok so tooling for that would be a thing to do

I don’t think you can do tooling for that

but go ahead

Just curious

one could try to scrape the registry submissions from the documents

but that sounds error-prone

What else?

do it manually

I mean what else could use tooling

I don’t think one can create tooling for this which won’t fail silently or have lots of false positives

I don’t know

I’m happy with the current tooling

k

except that I’d like to automate email sending, but that mostly requires infrastructure

or faster build processes, but that also requires infrastructure

I fix most pain points in the tooling myself

I should proablby commit my scripts to create tags though

there are a few nice-to-haves

I guess

like a bot which analyses new PRs and automatically assigns labels (ProtoXEP, Needs Council, Needs Author, Needs Board)

Yeah that's also something I wanted

something which creates and maintains a todo list for editors, because it’s not always clear what needs to be done

and my attempt at introducing Github Projects for that was shot down

yeah

which is a shame, because they even got more automation for those nowadays

shot down by whom?

someone from the Editor team

check the commit history

of README.md

ok

Well now that you're managing editors almost by yourself..

I'm not personally against it

I also effectively was back then

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

for what reason?

me wanting to move?

yes

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

we don’t have the resources to host our own.

I'm aware of that, which is why I'm saying I don't see us moving to that

so there’s no reason to not make use of the platform we currently have

We agree

right

jonas’: The XSF is in GSoC this year. I wonder if one could wrangle a XEP management platform as a project

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.

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

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.

but frankly, email sending is least of my concernsn