Hello Jetlo,

I want to support the idea expressed by my fellow volunteers that this
decision does not adequately support the community's use-cases. I fully
understand that Etherpad was designed as a temporary collaboration tool,
but:
* it is not only used by the tech community, so such an announcement *must*
go out as widely as possible, especially on the lists dedicated to
conference organizers  and wikimedia-l
* *17 days is not enough* heads up for the community to organize and
sort/backup decades of meeting minutes. I believe that for the first
cleanup, *3 months* would a more realistic timeline
* future purges should also have a *predictable schedule and be announced*
at least a month in advance, to allow people to save their work

I hope your team will reconsider their decision to cater for the needs of
the wider community.

Best,
  Strainu

În mar., 10 feb. 2026 la 14:57, Jelto Wodstrcil via Wikitech-l <
[email protected]> a scris:

> Hello everyone
>
> If you don't use etherpad, you can ignore this message.
>
> We will *delete all pads after 1st March 2026*! If you need any of your
> pads, please make a local backup. We will not be able to recover the data
> after 1st March.
>
> The pad cleanup helps to reduce the size of the database and the footprint
> on our infrastructure. After the cleanup, etherpad can still be used for
> real-time collaboration but please do not expect long term storage.
> Additional cleanups might happen after that unannounced.
>
> See also https://phabricator.wikimedia.org/T415237 for more information.
>
> Greetings and thank you
>
> Jelto
>
> _______________________________________________
> Wikitech-l mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
_______________________________________________
Wikitech-l mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

Reply via email to