Thanks for filing this, and with detail, @Aklapper . In my opinion, as only @JAufrecht was truly involved in maintaining this, the project simply won't get any further attention. Since he's no longer with the org (and probably disinclined to do anything with WMF anymore, given the abruptness of that), I would hope there is a process or protocol for sunsetting these sorts of things. For instance, archiving the board, closing the tasks, notifying admins of wmflabs instances, tagging MW pages, etc.

As far as I know, @aezell and @Niharika had interest in the data from the reports, and @JAufrecht added them into the project with a hope to have someone else maintain it, or even rewrite it in Ruby instead of R. Otherwise, I don't think they are connected...?

Correct. I expressed interest in helping Joel out with the project a few years ago but I did not really find myself having the time that project needs.

@Charlotte: Hi, I am wondering if my statement above "If I get it right, the only team which might be using Phlogiston seems to be the Android team?" is correct.
Do you know if Phlogiston is used by the Android team (or if you're not the right person to ask, who would know)? Thanks in advance!

Also giving a heads-up to @ggellerman, as Phlogiston is listed under "Tools, Practices, and Presentations we like" on https://www.mediawiki.org/wiki/Wikimedia_Product/Technical_Program_Management - should it still be listed there?

@Aklapper

@ggellerman is on holiday right now, but I am happy saying that we can remove it from the page you linked. Thanks for the heads up! :)

@MBinder_WMF: Aren't you also supposed to be on holiday for today? :P More seriously speaking, thanks a lot for the quick reply and the edit! Appreciated.

In T253964#6386271, @Aklapper wrote:

@Charlotte: Hi, I am wondering if my statement above "If I get it right, the only team which might be using Phlogiston seems to be the Android team?" is correct.
Do you know if Phlogiston is used by the Android team (or if you're not the right person to ask, who would know)? Thanks in advance!

I didn't even know this existed. So no, we don't use it.

I don't know if the public dump of phabricator is being created using phlogiston or not, I couldn't find anything in puppet or codesearch pointing to how this dump is being created. I just want to mention that I use this dump and I'm planning to depend on it even more so please keep that if possible.

I emailed WMF's Tech and Product teams, in case there might be other users not aware of (unlikely, but better safe than sorry).

@Ladsgroup: Phlogiston is only a consumer of the dump, so should be fine.

Dump code itself is at https://phabricator.wikimedia.org/diffusion/PHTO/browse/master/public_task_dump.py

Config / cronjob is https://phabricator.wikimedia.org/source/operations-puppet/browse/production/modules/phabricator/manifests/tools.pp and https://phabricator.wikimedia.org/source/operations-puppet/browse/production/modules/profile/manifests/phabricator/main.pp

In T253964#6396663, @Ladsgroup wrote:

I couldn't find anything in puppet or codesearch pointing to how this dump is being created

I think the deeper fix here is either "add diffusion repos to codesearch" or to migrate code out of diffusion/differential over to Gerrit (T191182)

It has been nearly four weeks since contacting WMF's tech and product mailing lists in T253964#6399539 and no new comments have been added to this task.
Hence I will proceed and sunset Phlogiston within the next days.