Page MenuHomeSoftware Heritage

Create mailing list swh-maintenance for SWH clients
Closed, ResolvedPublic

Description

A mailing list dedicated to SWH clients and users.
In this list, the following can be announced and discussed:

  • down time while migrations and service outage
  • errors that where observed by clients

This dedicated channel will be for clients.
For example with HAL, it will help moderators on HAL to program their moderation time and even communicate when an error occurs.

I'm putting it SWORD deposit project, but it should be in SAVtype of project.

Event Timeline

moranegg triaged this task as Normal priority.
zack added a subscriber: zack.Jun 19 2019, 12:23 PM

There are two separate use cases here, so I'll comment on them separately:

errors that where observed by clients

We already have a tool for this one, which is our forge. Is there a reason why it is not good enough for this use case?
There might be valid reasons, of course. But note that adding another tool to address those reasons will mean that someone of us will then need to be a back-and-forth proxy between issues raised on the list and our forge. That is going to be *a lot* of *tedious* work. So we need to think twice before going there.

down time while migrations and service outage

We have http://status.softwareheritage.org/ for this, but we are not using it.
I suggest we start using it and make it a habit of doing so, developing the needed integrations.

We have http://status.softwareheritage.org/ for this, but we are not using it.
I suggest we start using it and make it a habit of doing so, developing the needed integrations.

Wow this is awesome !!
We need to add deposit.softwraeheritage.org to it and it is really great.

But it is not enough to tell moderators there will be down time.

About the errors, we did create deposit@softwareheritage.org mail for these particular users, but it still Jozefina mailing only me when something wrong,
which means:
moderator X has problem -> mails Jozefina -> Jozefina checks -> Jozefina mails me -> I check on IRC or ask @ardumont directly -> I answer Jozefina -> Jozefina answers moderator X

and I don't know how to improve this work-flow.

We have http://status.softwareheritage.org/ for this, but we are not using it.

I completely forgot we had that. I even forgot what email account i had subscribed with...

I suggest we start using it and make it a habit of doing so, developing the needed integrations.

yes.

We need to add deposit.softwraeheritage.org to it and it is really great.

done

T1917 has been opened to discuss the communication policy we want to convey from that status.io page.

If we agree that the status page is the way forward (and that clients interested in swh can use it to subscribe to update), i think we could close this current task now.

zack added a comment.Tue, Jul 16, 12:06 PM

If we agree that the status page is the way forward (and that clients interested in swh can use it to subscribe to update), i think we could close this current task now.

As I understand it, this task was about two-way communication:

  1. swh → users (downtime announcement)
  2. users → swh (bug reports)

T1917 (will) cover (1), but not (2).

I've already argued above that (2) already exists, and is our forge.

I agree this task can be closed (provided that there're no objections on the forge appropriateness for downtime-related bug reports).

ardumont closed this task as Resolved.Tue, Jul 16, 1:35 PM
ardumont claimed this task.

I've already argued above that (2) already exists, and is our forge.

Yes, i agreed with this statement (albeit implicitely).
And that's why i proposed to close it as well since both (1) and (2) are addressed.

I agree this task can be closed (provided that there're no objections on the forge appropriateness for downtime-related bug reports).

No objection on my part.


Closing as "resolved". The needs (1) and (2) are addressed differently than with the proposed mailing list implementation.
They are addressed nonetheless.

Note:
If someone objects, they can always reopen it.