Hello, this is a provocative approach to migration! * Clarification Q: The timeline was finalized on November 28, and any tools and cronjobs w/ no response from maintainers will stop working on the same day on December 14th, regardless of how actively they are used? Is there anything that users of those tools can do to delay this? It might be worth posting in places where active /users/ of tools hang out, not just the maintainers, as they will be inconvenienced and may be able to share maintainership where needed.
* Can you share stats on how many tools remain to be migrated, how many will stop in December, and which are the most-used? This phab board has ~460 open tasks https://phabricator.wikimedia.org/project/board/6135/query/open/ , some created this week by the maintainers after receiving a recent ping https://phabricator.wikimedia.org/T352564 , while https://grid-deprecation.toolforge.org/ lists only 447 tools still running on GE -- scores of which seem quite popular. * When "grid infrastructure is deleted" on March 14, will there be backups of the tools for people who want to migrate them in the future? * At least Maarten and Albin asked to be unassigned from migration tasks for their tools (but remain assigned). If they can't unassign themselves, and users need to coordinate finding migrators for their tools to keep working: is there some other way to flag in Phab which tools need someone to work on migration? Ideally a way visible from taskboard overviews... Cordially, Sam _______________________________________________ Cloud mailing list -- [email protected] List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
