[tinkerpop] branch 3.5-dev updated: CTR - add Twitch/YouTube content submission rule per dev list DISCUSS thread

[xi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

xiazcy pushed a commit to branch 3.5-dev
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git


The following commit(s) were added to refs/heads/3.5-dev by this push:
     new fb8fcb7818 CTR - add Twitch/YouTube content submission rule per dev list DISCUSS thread
fb8fcb7818 is described below

commit fb8fcb7818644705bbd22af5acb27ab2cc8ac8cc
Author: Yang Xia <55...@users.noreply.github.com>
AuthorDate: Wed Feb 22 10:27:57 2023 -0800

    CTR - add Twitch/YouTube content submission rule per dev list DISCUSS thread
---
 docs/src/dev/developer/for-committers.asciidoc | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/docs/src/dev/developer/for-committers.asciidoc b/docs/src/dev/developer/for-committers.asciidoc
index 627175d4e0..9f3e9f98d9 100644
--- a/docs/src/dev/developer/for-committers.asciidoc
+++ b/docs/src/dev/developer/for-committers.asciidoc
@@ -70,6 +70,24 @@ On the day of the meeting, the meeting organizer will create a Google Hangout (o
 At that point, all who are interested can attend.  Meeting minutes should be
 taken and added to the <<meetings,Meetings>> section of this document using the pattern already established.
 
+== Media Content Submission
+
+Tinkerpop hosts link:https://www.twitch.tv/apachetinkerpop[Twitch streams] for various knowledge sharing and demos,
+as well as a link:https://www.youtube.com/@apachetinkerpop[YouTube channel] to upload video contents.
+Everyone in the community is welcome to submit contents to stream or upload, abiding the following process:
+
+1. Send a DISCUSS thread to the dev mailing list that describes the topic, the platform it goes to, who will present it and a date to do it.
+2. If the proposal comes from someone who isn't an official TinkerPop committer, then they must obtain a committer "sponsor",
+who is responsible for and endorses the content. (This can be asked on the DISCUSS thread).
+3. The proposal must achieve lazy consensus at minimum.
+
+In terms of content, Tinkerpop currently hosts two types, one is individual topics, for which each content would require a DISCUSS thread.
+Another is a class of topics, which is a series of related contents defined under one set of operations
+(e.g. the Contributorcast Twitch chat series running post-releases), and such class would require just one DISCUSS thread laying out
+the content and rules upfront.
+
+After obtaining approval from the DISCUSS thread, start planning and promoting your stream/video!
+
 == Release Notes
 
 There is a two-pronged approach to maintaining the change log and preparing the release notes.