← Back to context

Comment by SamuelAdams

1 year ago

So if they add “credit to raphaelrobert”, or a copy of your license to their code somewhere, Kagi will be compliant?

I’ve never had any of my open source software used, and I typically license it with MIT, so I’m curious how other groups and organizations actually comply with the license.

They are compliant, the code being used is under the MIT license.

  • Yeah I'm as big of a FOSS fan as the next guy on here but you really can't complain about how someone uses your code if you used the MIT License...one of the most permissive licenses in existence.

    If someone wants attribution or something then they should use a license that requires that thing.

    • There’s a gap between what is legally required and what is common courtesy.

      I’m under no obligation to thank someone for holding a door for me; if I fail to do so it does not mean that person should switch to a different door-holding license in the future. It just means I’m a bit of a jerk.

      When lifting an entire (permissive licensed) implementation it’s good form to say thanks.

      5 replies →

    • You can if they don't include the copyright header: "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."

      Which, as far as I can tell they haven't done. Their MIT licence claims their own copyright. No reference to the library used in readme.

      https://github.com/kagisearch/privacypass-lib/blob/main/LICE...

      https://github.com/kagisearch/privacypass-lib/blob/main/READ...

      Usually when using apps that use MIT licensed libs they also implement a notice in a user-facing way. Google maps for instance has a (albeit hidden) section in their settings menu referencing at least one MIT licensed library.

      1 reply →

  • MIT licence explicitly requires maintaining the original copyright header, and licence.

    >Copyright (c) <year> <copyright holders>

    >Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

    >*The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.*

    >[...]