- From: Markus Lanthaler via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Jan 2019 21:34:32 +0000
- To: public-hydra-logs@w3.org
> Thanks for voicing your concerns, @lanthaler. I understand your reasoning around usage that have little or nothing to do with Hydra. To avoid that, we could require affiliation with Hydra of some sort, such as membership of the CG. Would that help, you think? No, I don't think so as the CG is open to everyone and membership doesn't mean much by itself. > Regarding the first part of the sentence, say someone created a FOSS implementation of Heracles in Python and wanted to use the Hydra logo in a derived form for it there. Would you oppose this? Almost certainly not but I'd like to reserve the right to do so. I'd prefer if the Hydra logo would be reserved for Hydra itself and would like to avoid diluting the brand or implying official endorsement by the use thereof (or a slight derivation thereof). Under fair use that tool could obviously advertise its Hydra-compliance by using the official logo (and that shouldn't require to change it in any way). I hope this clarifies things. Let's discuss it again when the first case that doesn't fall under fair use comes up. I think there are more important discussions to be had right now to move Hydra forward ;-P -- GitHub Notification of comment by lanthaler Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/181#issuecomment-457365344 using your GitHub account
Received on Thursday, 24 January 2019 21:34:33 UTC