Re: [PR] Add "why" for branding and licencing [comdev-working-groups]
rbowen merged PR #43: URL: https://github.com/apache/comdev-working-groups/pull/43 -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add "why" for branding and licencing [comdev-working-groups]
potiuk commented on code in PR #43: URL: https://github.com/apache/comdev-working-groups/pull/43#discussion_r1665557158 ## wg-advisors/why/why_branding_licencing.md: ## @@ -1,13 +1,68 @@ # Why we should look after the project's brand and licencing -TODO: - ## Summary +The Apache Software Foundation's most important asset is a combination of branding and license that is +used by all Apache projects. The license is the Apache License, Version 2.0, and the branding is based +on the project name. The licence is a permissive open source license that allows the software to be used +by anyone for any purpose, and the branding is a set of rules that ensure that the software is recognized +as an Apache project and that the project is recognized as part of the Apache Software Foundation. + +The software that ASF projects produce is released under the Apache License, Version 2.0, which is a permissive +open source license that allows the software to be used by anyone for any purpose and it is important that +we do not limit anyone from using the software in any way. And while we allow anyone to use the software, +and redistribute it, we do not allow anyone to claim that they are the "owners" of the software, or that +they are controlling the project. + +This is why it is important to ensure that the project's brand is not used in a way that could cause confusion +or mislead users on who is owning or controlling the project. This includes ensuring that the project's name +is not used in a way that could imply that another party is controlling the project - assuring +vendor neutrality. Review Comment: Good point. Added links to [Project Independence](https://community.apache.org/projectIndependence.html) -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add "why" for branding and licencing [comdev-working-groups]
potiuk commented on PR #43: URL: https://github.com/apache/comdev-working-groups/pull/43#issuecomment-2208717949 Applied comments. -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add "why" for branding and licencing [comdev-working-groups]
potiuk commented on code in PR #43: URL: https://github.com/apache/comdev-working-groups/pull/43#discussion_r1665554435 ## wg-advisors/why/why_branding_licencing.md: ## @@ -1,13 +1,68 @@ # Why we should look after the project's brand and licencing -TODO: - ## Summary +The Apache Software Foundation's most important asset is a combination of branding and license that is +used by all Apache projects. The license is the Apache License, Version 2.0, and the branding is based +on the project name. The licence is a permissive open source license that allows the software to be used +by anyone for any purpose, and the branding is a set of rules that ensure that the software is recognized +as an Apache project and that the project is recognized as part of the Apache Software Foundation. + +The software that ASF projects produce is released under the Apache License, Version 2.0, which is a permissive +open source license that allows the software to be used by anyone for any purpose and it is important that Review Comment: Yes. Merged the two. From the second paragraph I left only the "owning" part. -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add "why" for branding and licencing [comdev-working-groups]
potiuk commented on code in PR #43: URL: https://github.com/apache/comdev-working-groups/pull/43#discussion_r1665557506 ## wg-advisors/why/why_branding_licencing.md: ## @@ -1,13 +1,68 @@ # Why we should look after the project's brand and licencing -TODO: - ## Summary +The Apache Software Foundation's most important asset is a combination of branding and license that is +used by all Apache projects. The license is the Apache License, Version 2.0, and the branding is based +on the project name. The licence is a permissive open source license that allows the software to be used +by anyone for any purpose, and the branding is a set of rules that ensure that the software is recognized +as an Apache project and that the project is recognized as part of the Apache Software Foundation. + +The software that ASF projects produce is released under the Apache License, Version 2.0, which is a permissive +open source license that allows the software to be used by anyone for any purpose and it is important that +we do not limit anyone from using the software in any way. And while we allow anyone to use the software, +and redistribute it, we do not allow anyone to claim that they are the "owners" of the software, or that +they are controlling the project. + +This is why it is important to ensure that the project's brand is not used in a way that could cause confusion +or mislead users on who is owning or controlling the project. This includes ensuring that the project's name +is not used in a way that could imply that another party is controlling the project - assuring +vendor neutrality. + +Some, popular, Apache projects have a strong brand recognition, and it's important to ensure that the +brand is used consistently across all project's assets, including the website, documentation, and +marketing materials and the ASF registers the project's name as a trademark to ensure that the project's +brand is protected. + +The ASF has a set of policies that define how the Apache brand should be used, and it's important that +all projects follow these guidelines to ensure that the brand is used consistently and correctly. + +It's a PMC responsibility to ensure that the project's brand is used correctly and to take action if the +brand is used in a way that could cause confusion or mislead users. + +The foundation has legal ways to enforce the brand and license, but it's always better to resolve any +issues informally, by contacting the party that is using the brand incorrectly and asking them to correct +the issue. + +Events are a special case, as they are often organized by third parties, and it's important to ensure +that the event is recognized as an Apache event and that the event is organized in a way that is consistent +with the Apache Software Foundation's values and principles. + ## Links to relevant documents +* [The Apache Software Foundation Trademark Policy](https://www.apache.org/foundation/marks/) +* [The Apache Licences](https://apache.org/licenses/) +* [Third party event branding policy](https://www.apache.org/foundation/marks/events.html) + ## Why are we doing it? +The software that ASF projects produce is released under the Apache License, Version 2.0, which is a permissive +open source license that allows the software to be used by anyone for any purpose and it is important that +we do not limit anyone Review Comment: Right. Removed it. -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add "why" for branding and licencing [comdev-working-groups]
potiuk commented on PR #43: URL: https://github.com/apache/comdev-working-groups/pull/43#issuecomment-2185309451 As the next "why" I proposed some "why" for branding/licencing in the "advisors" working group. This is my understanding on why licensing and branding and taking care about it is the most important thing from the legal point of view for all PMC members, but I woudl love to hear what others think about it. -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Add "why" for branding and licencing [comdev-working-groups]
potiuk opened a new pull request, #43: URL: https://github.com/apache/comdev-working-groups/pull/43 (no comment) -- 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: notifications-unsubscr...@community.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
