[09:56:27] majavah: I invite you to follow this https://wikitech.wikimedia.org/wiki/Help:Access_policies and request cloud admin access (the most elevated one) [21:41:14] bd808 how much content if any will be brought over from the test toolhub to the production toolhub? [21:43:03] @harej: at the moment I do not have any content migration plan. I haven't audited lists, but there are only 9 toolinfo records that folks have made their directly -- https://toolhub-demo.wmcloud.org/search?origin__term=api&ordering=-score&page=1&page_size=12 [21:43:39] I can't really move the user accounts because they are attached to a different OAuth grant [21:45:14] because of the inability to move accounts, if I did move content I would not be able to assign ownership back to the original user which makes it all seem not very useful [21:45:40] Can I simply resubmit them by hand into production Toolhub? [21:45:42] There's only 9 [21:46:46] @harej: Yes! It actually should be pretty easy to use the API console on both sides to get the raw json API output from the demo server and put them into the prod server. [21:47:58] But note that if you submit https://toolhub-demo.wmcloud.org/tools/firefly-linttables to the prod then your account will own the record rather than Firefly. [21:49:54] And also, don't submit mine (diffedit), because it's a duplicate - i wasn't aware it had already been imported via some tool list [21:49:57] @harej: I can take a TODO to contact those of you who have created new content in the demo server and give some instructions on how to copy that data over [21:51:25] Do the entries necessarily need to be created by the person owning the tool long term? I thought contributions directly through the Toolhub interface were editable by anyone so it didn't really matter who submitted [21:52:08] @jhobsy: yeah, that would be https://toolhub-demo.wmcloud.org/tools/metawiki-jon-harald-s%C3%B8by-diffedit which comes from https://en.wikipedia.org/wiki/Wikipedia:User_scripts/List via a scraper I built. [21:52:40] @harej: api created records are owned by the creator. Right now there is no "community" owned content. [21:52:48] I see [21:53:06] annotations are expected to be community editable, but we haven't built that yet [21:54:02] I'm open to changing api created records to be community owned if that becomes a general consensus [21:56:20] https://toolsadmin.wikimedia.org/tools/id/toolinfo-scraper is the WP:US/List scraper [21:59:48] is the idea that people edit WP:US/List and changes are picked up that way or we edit on Toolhub and it diverges over time? [22:01:29] legoktm: well... the idea is not yet well defined either way. The scraper will keep Toolhub in sync with the contents of WP:US/List, but no edits can be made to these records directly in Toolhub. [22:02:05] I would like to find better workflows, but even though I've been coding on this for a year there is a lot more to do [22:02:11] gotcha [22:03:05] WP:US/List should be rewritten in the toolinfo schema 🙂 [22:03:22] And then dynamically generated [22:03:28] @harej: very much ideally in the long run yes [22:04:26] * bd808 points to the phab board and gerrit repo and says "patches welcome" [22:06:54] T186387 & T272652 would be related tasks I think [22:06:54] T186387: Create proof of concept Toolhub gadget - https://phabricator.wikimedia.org/T186387 [22:06:55] T272652: Make a Scribunto extenstion that lets lua talk to the Toolhub API - https://phabricator.wikimedia.org/T272652 [22:08:13] Generally finding workflows to make documenting on-wiki tools (user scripts, gadgets, lua modules, complex templates) is needed [22:10:08] All you folks who make those things probably have better ideas than I do about what would make it relatively easy to document them in Toolhub. [22:11:39] some magic like a gadget or probably better an extension that we could keep in sync on all wikis writing to a slot or other discoverable location would be a neat thing [22:12:16] or a gadget/extension that somehow talks directly to the Toolhub API to do it and then show the info on both sides [22:52:42] someone want to kick the gerrit-reviewer-bot? https://gerrit-reviewer-bot.toolforge.org/ says it's another victim of The Grid [22:55:03] !log tools.gerrit-reviewer-bot Restarting in the hope of fixing LE cert issues [22:55:05] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.gerrit-reviewer-bot/SAL [22:58:28] AntiComposite: ummm... it's a python2.7 thing so I'm not sure that restarts of the job will make anything better [22:58:44] ouch [22:59:53] oh, I didn't mean the webservice, I meant the stuck job 913897 [23:00:27] !log tools.gerrit-reviewer-bot root forced the deletion of job 913897 [23:00:30] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.gerrit-reviewer-bot/SAL [23:01:40] that looks like it worked, it at least says it's running now [23:03:13] bd808, thanks, I see it adding reviewers now [23:03:20] cool [23:13:31] ah, it wasn't running, thanks for fixing that AntiComposite