hey folks, quick update to say you’ve probably noticed our new community icons.

these icons were lovingly crafted by @UrLogicFails@beehaw.org, who posted them a couple of days ago over in Creative. we took notice of them and obviously–because they’re our community icons now–really, really liked them.

thanks to his generosity in working things out with us, we’re pleased to announce we can use his icons under a Creative Commons license for the site! until further notice they’ll be our site icons, with credit to him on our sidebars. we’ll also be adding attribution to the community sidebars over the rest of day as time permits.

we’re also pleased to report that, thanks to your generosity, we’ve been able to reasonably compensate him for all 33 of the icons he’s made for the community! the agreed to rate is $5 per icon, for a total of $165 that’s been paid out to him as of today. this expense has been reflected on our Open Collective. (we’ve also agreed to, as possible, commission him for any future community icons until further notice, which will be subject to that same rate.)

hopefully you enjoy the new icons, and please thank UrLogicFails for the work here! thanks for using the site again folks!

  • alyaza [they/she]@beehaw.orgOPMEnglish
    5·
    1 year ago

    So either way that icon has to be changed to be in compliance with the usage guidelines (@alyaza, @Gaywallet and @UrLogicFails ), since I believe the Beehaw-community does not want to infringe on such a point. I am also then not sure if @UrLogicFails can release the icon under a license as is done here, since the keyhole logo is trademarked (see the OSI Trademark Guidelines). See for instance how !opensource@lemmy.ml has solved this. They use the icon with the ® symbol as well as attributing the OSI in the sidebar:

    can now also speak on this point: we have an alternative in the works, ETA to its completion is tonight/tomorrow. given the short turnover we’re expecting here i think we’ll just leave the current icon in place for today–our backup and previous icon would infringe on the same principle in any case so it’s just trading one icon issue for another, lol.