[FFmpeg-devel] [PATCH] [RFC] doc/community: Add a policy about using FFmpeg name in public events

[Vittorio Giovara]

---
Here are some initial talking points, I wasn't sure where to put this so I
thought community.texi was ok, please let me know your thoughts.
Ideally we should have the GA vote on this when we reach consensus (or get
close to it).
Thanks
Vittorio

 doc/community.texi | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)

diff --git a/doc/community.texi b/doc/community.texi
index 97a49f15ed..852db9a197 100644
--- a/doc/community.texi
+++ b/doc/community.texi
@@ -179,4 +179,37 @@ instead and point them in the right direction.
 Finally, keep in mind the immortal words of Bill and Ted,
 "Be excellent to each other."

+ at anchor{Brand}
+ at chapter Brand
+
+FFmpeg is a legally protected trademark. This means that it is not
possible to
+act on behalf of FFmpeg without explicit permission from the community.
+
+Here are some key points to remember:
+
+* To represent FFmpeg in any product, conference, or tradeshow, you must
obtain
+permission from the FFmpeg community. This typically requires just sending
a
+request on the mailing list, and waiting for an approval.
+
+* The FFmpeg community, specifically the General Assembly (GA), has the
final
+say in resolving any disputes or conflicts related to the use of the
FFmpeg name.
+In particular or public events, the community may require additional
information
+to ensure alignment with FFmpeg's goals and values.
+
+* Failure to follow the proper procedures for representing the FFmpeg name
can
+result in severe consequences, including:
+  - Denial of future permission to use the FFmpeg name.
+  - Exclusion from the FFmpeg community.
+  - Potential legal action.
+
+If you're considering using the FFmpeg name in any capacity, it's crucial
+to adhere to these guidelines:
+
+* Consult the FFmpeg Community: reach out to the community through the
mailing
+list to discuss your specific use case and obtain necessary permissions.
+* Be Transparent and Honest: provide clear and detailed information about
your
+event or product, including its goals, participants, and how it relates to
FFmpeg.
+* Respect the Community's Decisions: The GA's decisions regarding the use
of the
+FFmpeg name are final and should be respected.
+
 @bye
-- 
2.45.2