https://quarry.wmflabs.org/ has a different scope than Tool-Database-Queries. The former requires that the user knows the SQL query string, i. e. it is meant for users who know what they are doing, but do not want to set up a Toolforge account, hassle with the command line, etc. The latter was (in the olden days) meant for users to say: "I want a list of all pages in $category that have an English counterpart, but not a French, and a external link to $somewhere", and then someone would figure out the SQL query, run it and post the results.

So I don't see a reason to archive this project, even if it is not heavily used.

However I don't think we should use Phabricator for this purpose (there're no way to transclude information of all requests in one page). This should be migrated to a pages on wiki instead (or add a "request" function in Quarry), which make requests more easy to maintain.

Displaying Phabricator query results in MediaWiki is covered by T90432. I personally prefer using Phabricator, as that was its USP: Instead of using various wikis, Bugzilla, Trello, whatever to track tasks and their resolution, there is one interface where everything that needs to be done is displayed, and I can use the same clicks and commands for all of them.

In T107699#1844789, @jcrespo wrote:

Sorry for reopening these, but who is actively attending these? I do dozens more of these being pinged by IRC and answering labs mailing list than the ones here, without a ticket, and I do not even have the time. Wouldn't be more productive to tell people to subscribe to DBA (or MediaWiki-libs-Rdbms) and tell contributors to help there if possible (maybe as a particular column "backlog (help welcome)", if needed)?

@Bugreporter, @scfc: Any comments / reply to @jcrespo's comment? ^

Yes it is better to request it at mailing list instead of creating Phabricator tasks.

I am going to be bold and create a "Backlog (help welcome)" as a column of DBA to generalize all kind of help related to MySQL/Postgres, but I do not believe it is not in the scope of official infrastructure support, like database query optimization of non-officially maintained applications, labs/tools apps going slow, etc. I welcome everybody to try to help there.

Everybody is still welcome to try to help with the general backlog, but those will be specifically the ones that do not need access/deep knowledge of our infrastructure.

For the records, creation of this project was originally requested in T51825 by @liangent (and @valhallasw).

In T107699#1502332, @Bugreporter wrote:

However I don't think we should use Phabricator for this purpose (there're no way to transclude information of all requests in one page). This should be migrated to a pages on wiki instead (or add a "request" function in Quarry), which make requests more easy to maintain.

In T107699#2025204, @Bugreporter wrote:

Yes it is better to request it at mailing list instead of creating Phabricator tasks.

Where should queries be requested instead? Would like to update the project description if we archive the Phab project.

Any comments / input to my last comment, please?

@Bugreporter: Any comments / input to my last comment, please? If not I'm going to decline this task.

See also https://en.wikipedia.org/wiki/Wikipedia:Request_a_query

Explicitly pinging @Betacommand and @Steinsplitter here as they are listed as project members. (Please add potential maintainers accordingly for such tasks.)

@Betacommand, @Steinsplitter: Could you please answer the last comment? Thanks!