[11:14:38] I want you to fuck me hard. My profile on the site --->>> http://gg.gg/d1bmr [15:03:09] !help [15:03:10] ylevental: If you don't get a response in 15-30 minutes, please create a phabricator task -- https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=wmcs-team [15:03:53] ylevental: hi there [15:05:28] gtirloni: I was running https://tools.wmflabs.org/relgen and inputted a filename "DC_Miedzianik_&_J_Mitchell_1992.jpg" [15:06:38] It generated the link https://commons.wikimedia.org/wiki/File:DC_Miedzianik_&_J_Mitchell_1992.jpg, but it redirected to https://commons.wikimedia.org/wiki/File:DC_Miedzianik_&_J_Mitchell_1992.jpg [15:07:13] This was from the "release email" [15:08:58] gtirloni: Will you look into this? It's not a big deal but it's still a bug [15:09:33] Looks like there's an encoding problem with the URL in the email.. it's replacing "&" by "&" (this is HTML for &) [15:09:55] I'm not the owner of that tool.. I'd suggest you open a task in phabricator for it [15:10:40] Okay, thank you [15:11:46] https://phabricator.wikimedia.org/tag/otrs/ [15:11:53] you're welcome [15:13:44] just for reference, they should be replacing the ampersand with "%26" for the correct URL encoding... It's probably the templating engine doing its job at the wrong time :) [17:13:27] gtirloni: FDMS4 owns the tool [19:59:39] hello! when creating a new Toolforge tool, what do I put for the software license if the software has a custom, unnamed FOSS license? [20:19:49] I've gone with MIT, which resembles the custom license https://github.com/rahiel/open_nsfw--/blob/master/LICENSE.txt Hopefully we can change it later in the toolsadmin interface, if need be [22:46:57] musikanimal: you have to use a OSI-approved license -- https://wikitech.wikimedia.org/wiki/Help:Toolforge/FAQ