Should we keep drone?

[aucampia]

Should we keep drone running? I guess it does not hurt, but I'm not sure it helps that much either, probably something we should think about.

CC: @ashleysommer @nicholascar

[nicholascar]

This is definitely one for @ashleysommer who set drone up! It was a replacement for Travis which was going to start to cost , but if we’ve emulated Drone’s actions without it, we should remove it as we have a lot of moving parts in the RDFlib testing system so would be good to simplify.

[ashleysommer]

I didn't know we added GitHub Actions. What was the reasoning behind that? When we had to move from Travis, we discussed alternatives and decided on Drone because it was very close in features and functionality to Travis, and we could host it ourselves, and have more control over it. We were worried about vendor lockin with GitHub-specific tooling.

If we have really decided to go back on that and go with GitHub Actions, then we can probably retire our drone server.

[aucampia]

Any update on this? I made #1815 - this is basically what I would say is the only remaining thing stopping us from disabling drone.

[nicholascar]

Let's schedule a quick maintainers call. I think we all have good intentions to be in sych here but we are missing thing by not actually communicating synchronously!

How does a virtual meeting on Friday 22nd April, a week from now, at 10:00 UTC (https://www.timeanddate.com/worldclock/converter.html?iso=20220422T100000&p1=47&p2=1440&p3=37) sound? We need only meet for a short time but we can just tick off a few things we should all agree on, like this, potential release timing etc.

[aucampia]

Time works for me.

[aucampia]

Any time other than 01h00 -> 07h00 CET (09h00 -> 15h00 AEST) is really fine by me, just depends on whether I have something on my schedule already.

[nicholascar]

OK @white-gecko and @ashleysommer , does this time work for you?