Set as security due to the risk of tool deletion by the banned user — there are multiple accounts still active, i.e.,

• https://wikitech.wikimedia.org/wiki/User:Jarallah
• https://wikitech.wikimedia.org/wiki/User:Jarallah_II
• https://wikitech.wikimedia.org/wiki/User:JarBot_II
• https://wikitech.wikimedia.org/wiki/User:JarBot_III

Blocked 6 more accounts which shared the same email in LDAP.

Not sure whatt to do about the adoption request, however. None of the tools seem to have a license specified.

(when possible, please make this task public)

In T324607#8448313, @TheresNoTime wrote:

(when possible, please make this task public)

Done, as the accounts listed above are now disabled as well.

In T324607#8448306, @taavi wrote:

Not sure what to do about the adoption request, however. None of the tools seem to have a license specified.

For the records, a few weeks ago a coworker contacted its maintainer about license and source code. The maintainer's reply was that they have not made their code public yet or put it under any license yet.

Do we know where the code is located?

In T324607#8449324, @jrbs wrote:

Do we know where the code is located?

• https://admin.toolforge.org/tool/jarbot has over 200 custom pywikibot scripts in /data/project/jarbot/pyvenv/core/scripts/userscripts. 3 include license comments.
• https://admin.toolforge.org/tool/jarbot-ii has about 125 custom pywikibot scripts in /data/project/jarbot-ii/pyvenv/core/scripts/userscripts. 3 include license comments.
• https://admin.toolforge.org/tool/jarbot-iii has over 150 custom pywikibot scripts in /data/project/jarbot-iii/pyvenv/core/scripts/userscripts. 4 include license comments.
• https://admin.toolforge.org/tool/jarallah has over 200 custom pywikibot scripts in /data/project/jarallah/pyvenv/core/scripts/userscripts. 3 include license comments.
• https://admin.toolforge.org/tool/jarallah-ii has over 100 custom pywikibot scripts in /data/project/jarallah-ii/pyvenv/core/scripts/userscripts. None include license comments.

None of these tool accounts include a Striker toolinfo declaring a default license. I think all of the scripts that do include license comments were copied from elsewhere.

In T324607#8448715, @Aklapper wrote:

For the records, among this year's nominations for the Coolest Tool Award (CTA) was also a nomination for JarBot. Thus the CTA committee reviewed the nomination and contacted its maintainer about license and source code. The maintainer's reply was that they have not made their code public yet or put it under any license yet.

Technically, that was an confession to violating the Toolforge's Rules (second point, "All code in the Tools project must be published under an OSI approved open source license"). Perhaps it would make sense to remind maintainers that use Toolforge about that when CTA committee asks for the license?

@Urbanecm: T271712 or T311293 might scale better for trying to encourage Toolforge rules (but someone needs to do it). :)

Wonderful :( Based on T324607#8449385, I'd recommend we just mark the tools for deletion. And maybe in 2023 do some kind of Toolforge-wide audit of licensing compliance...🤔