@Gopavasanth, @Soda: There is both https://github.com/gopavasanth/ToolWatch/issues and https://phabricator.wikimedia.org/tag/tool-toolwatch/ . Where is the one canonical issue tracker for this codebase? https://toolsadmin.wikimedia.org/tools/id/tool-watch implies it is Phabricator, so Github issues should be switched off (or the Phabricator project archived)? Thanks in advance for avoiding duplication and fragmentation!

We will close the github issue @Aklapper, thanks :)

cc @Jnanaranjan_sahu

We plan to add a notification system to the authors once the tool gets unavailable. Lets discuss the task here before moving forward with any further implementations.

In T353573#9411419, @Reputation22 wrote:

We will close the github issue @Aklapper, thanks :)

Yay. When? :)

Hi @Aklapper, it seems like there are no issues listed on https://github.com/gopavasanth/ToolWatch/issues. To ensure centralized issue tracking, let's use the Phabricator tool under https://phabricator.wikimedia.org/tag/tool-toolwatch/. This way, all discussions and issues related to ToolWatch can be conveniently managed in one place.

@Gopavasanth Anyone ending up first on https://github.com/gopavasanth/ToolWatch/issues will likely not find your comment that you posted at https://phabricator.wikimedia.org/T353573#9431896 . :) Please ensure centralized issue tracking by switching off one of two places (e.g. for GitHub), and allowing folks who go to https://github.com/gopavasanth/ToolWatch to find out about the existence of https://phabricator.wikimedia.org/tag/tool-toolwatch/ somehow. Thanks :)

@Aklapper, thank you! All issues related to the tool can now be tracked only at this link: https://phabricator.wikimedia.org/tag/tool-toolwatch/