parshimers commented on issue #8984: URL: https://github.com/apache/texera/issues/8984#issuecomment-6375732808
Luis, Meng and I caught each other in the hall, so we ended up having a little chat about this. We talked a bit about the history of each operator's icons. Meng mentioned the main way these icons came in was very distributed. A typical immigration project for many new contributors was to create an operator, and as part of that they had to add an icon for it. At that time the licensing was not being closely scrutinized. So, for these icons, they are certainly suspect- people would likely just look on Google Images or something. Then we discussed a bit about what to do about it. We discussed the complications of using a model to create the icons. I mentioned that it isn't out of the question, but it is kind of a grey area. I pointed out that the very same thing can happen with LLMs when coding (e.g. it could produce more or less verbatim some well known implementation of an algorithm). This was for the purpose of highlighting that it could be acceptable just as it is for code, but you always must scrutinize the output of any generated asset and clearly mark that it is one (and hopefully information about how it was generated) Based on all of this, I mentioned that my general preference for addressing the remaining icons that we don't know the copyright status of is something like this (from most preferred to least): 1. If we can find icons used in other Apache projects that represent similar things (e.g. database operations) we can use them. This might not be a ton of work, because a lot of them are in the same category, so some other project may have either made the icons themselves or clearly stated the license of it. The same thing applies if we can find some icon set with a compatible license. 2. If we cannot find anything, it may be permissible to generate some of the icons. It needs to be closely scrutinized and marked as such though. 3. We can DISCLAIMER-WIP, but I stated that this is "kicking the can"; it's only really something that can unblock the release but it doesn't get us any closer to actually solving the problem. If anyone has other thoughts about it please chime in. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
