Re: License for text content
Thank you! Using Apache License 2.0 as the single license makes sense to me. Best, tison. Shane Curcuru 于2024年5月2日周四 19:55写道： > (Moving general@incubator and dev@community to BCC since this is really > a legal question about ASF licensing) > > tison wrote on 5/1/24 11:25 PM: > > Hi, > > > > IIUC, the Apache License 2.0 is mainly to license code and related stuff > > that constructs the final software. > > > > However, projects may also create text content like documents. Is it > > appropriate to use Apache License 2.0 for them (since quite a few terms > > may not be applicable)? Or what licenses shall we use? > > The ASF uses the Apache-2.0 license for our projects' own content that > is put into any releases, immaterial of type of content: > > https://apache.org/legal/src-headers.html#faq-docs > > Using a single license reduces complexity, and makes it simpler for > users to understand the issues around re-using ASF products. > > -- > - Shane >Member >The Apache Software Foundation > >
Re: License for text content
(Moving general@incubator and dev@community to BCC since this is really a legal question about ASF licensing) tison wrote on 5/1/24 11:25 PM: Hi, IIUC, the Apache License 2.0 is mainly to license code and related stuff that constructs the final software. However, projects may also create text content like documents. Is it appropriate to use Apache License 2.0 for them (since quite a few terms may not be applicable)? Or what licenses shall we use? The ASF uses the Apache-2.0 license for our projects' own content that is put into any releases, immaterial of type of content: https://apache.org/legal/src-headers.html#faq-docs Using a single license reduces complexity, and makes it simpler for users to understand the issues around re-using ASF products. -- - Shane Member The Apache Software Foundation - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: License for text content
Hi, The CC BY 4.0 is not compatible with the Apache license, so I would avoid it if you can. While the Apache license is intended for code, it’s OK to use for documentation as well. Kind Regards, Justin > On 2 May 2024, at 1:25 pm, tison wrote: > > Hi, > > IIUC, the Apache License 2.0 is mainly to license code and related stuff > that constructs the final software. > > However, projects may also create text content like documents. Is it > appropriate to use Apache License 2.0 for them (since quite a few terms may > not be applicable)? Or what licenses shall we use? > > For example, a website repo can contain both code and docs. In my personal > site, I wrote: > >> Code is licensed under Apache-2.0, words and images are licensed under CC > BY 4.0. > > But I don't know if we can write the same to a site repo of an ASF project. > > Best, > tison. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
License for text content
Hi, IIUC, the Apache License 2.0 is mainly to license code and related stuff that constructs the final software. However, projects may also create text content like documents. Is it appropriate to use Apache License 2.0 for them (since quite a few terms may not be applicable)? Or what licenses shall we use? For example, a website repo can contain both code and docs. In my personal site, I wrote: > Code is licensed under Apache-2.0, words and images are licensed under CC BY 4.0. But I don't know if we can write the same to a site repo of an ASF project. Best, tison.
