Thanks Andrew. I think many people take attribution as something more distinct, like having to say ‘powered by Swagger!’, and this is definitely not the case. As you mentioned, it doesn’t need to be painfully out there to give attribution.
From: <[email protected]> on behalf of Andrew Todd <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, 17 May 2017 at 11:01 To: "[email protected]" <[email protected]> Subject: Re: Attribution I'm not a lawyer, either, but if there is Apache-licensed JavaScript/HTML/CSS sent from your server to a Web browser on the public Internet, that is probably distribution of that specific code, and it would seem appropriate to provide attribution and information as detailed in section 4 of the license -- although I don't see why that necessarily has to be in the UI; it could be part of the site's source code. I'm basing this on my understanding of the FSF/GNU Project's definition of distribution, cf. RMS's expression of concern over this -- https://www.gnu.org/philosophy/javascript-trap.html I'm not really sure why you'd want to hide the fact that you're using an open standard from your users, though. On Tue, May 16, 2017 at 5:06 PM, Ron Ratovsky <[email protected]> wrote: Disclaimer: I’m not a lawyer. In general, anything under Swagger is licensed using APL2. Would highly recommend reading it - http://www.apache.org/licenses/LICENSE-2.0. In general, you don’t have to attribute anything if you host it. If you distribute it (see the relevant section), I believe you need to attribute it, but it doesn’t need to be in a prominent way. From: <[email protected]> on behalf of Alexey Akimov <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Sunday, 14 May 2017 at 12:39 To: Swagger <[email protected]> Subject: Attribution Hello community, Does anybody know what kind of attribution is required on a Swagger-powered documentation website according to its License Agreement? Is it mandatory to have a visible URL to swagger.io on the front page, or it is voluntary and just supports the community effort? Is there any difference in case of using Swagger UI vs. not-using it? And more specifically, if my documentation website would be all custom-made and built in-house, would it be also necessary to display any attribution to the Open API specification, if it is being used internally as a format to store API descriptions? I would appreciate any ideas and links on this matter. Thank you in advance! -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
