You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tinkerpop.apache.org by sp...@apache.org on 2023/02/23 21:40:42 UTC
[tinkerpop] branch master updated (511dee618a -> 4f08e1984c)
This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
from 511dee618a Merge branch '3.6-dev'
new 55b129cd05 updates to media CTR
new 23df04cf1f Merge branch '3.5-dev' into 3.6-dev
new 4f08e1984c Merge branch '3.6-dev'
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/src/dev/developer/for-committers.asciidoc | 46 ++++++++++++++++++--------
1 file changed, 33 insertions(+), 13 deletions(-)
[tinkerpop] 03/03: Merge branch '3.6-dev'
Posted by sp...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
commit 4f08e1984cad2f8621b54b9356360f8c06158f5b
Merge: 511dee618a 23df04cf1f
Author: Stephen Mallette <st...@amazon.com>
AuthorDate: Thu Feb 23 16:40:39 2023 -0500
Merge branch '3.6-dev'
docs/src/dev/developer/for-committers.asciidoc | 46 ++++++++++++++++++--------
1 file changed, 33 insertions(+), 13 deletions(-)
[tinkerpop] 02/03: Merge branch '3.5-dev' into 3.6-dev
Posted by sp...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
commit 23df04cf1fdec9485a74e0bdbf112087d8f04a9f
Merge: 95335249c2 55b129cd05
Author: Stephen Mallette <st...@amazon.com>
AuthorDate: Thu Feb 23 16:40:31 2023 -0500
Merge branch '3.5-dev' into 3.6-dev
docs/src/dev/developer/for-committers.asciidoc | 46 ++++++++++++++++++--------
1 file changed, 33 insertions(+), 13 deletions(-)
[tinkerpop] 01/03: updates to media CTR
Posted by sp...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
commit 55b129cd0522eefcdc46f762b7a5ccd2403bbbf7
Author: Stephen Mallette <st...@amazon.com>
AuthorDate: Thu Feb 23 16:40:16 2023 -0500
updates to media CTR
---
docs/src/dev/developer/for-committers.asciidoc | 46 ++++++++++++++++++--------
1 file changed, 33 insertions(+), 13 deletions(-)
diff --git a/docs/src/dev/developer/for-committers.asciidoc b/docs/src/dev/developer/for-committers.asciidoc
index 9f3e9f98d9..aecf9030d3 100644
--- a/docs/src/dev/developer/for-committers.asciidoc
+++ b/docs/src/dev/developer/for-committers.asciidoc
@@ -72,21 +72,41 @@ taken and added to the <<meetings,Meetings>> section of this document using the
== 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.
+Tinkerpop hosts link:https://www.twitch.tv/apachetinkerpop[Twitch streams] for various knowledge sharing sessions and
+demos, as well as a link:https://www.youtube.com/@apachetinkerpop[YouTube channel] to upload video content.
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!
+. 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.
+. 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).
+. The proposal must achieve lazy consensus at minimum.
+. After obtaining approval from the DISCUSS thread, start planning and promoting your stream/video!
+
+The process above applies to two content models: a class of content and individual content. A class of content refers
+to a content series which would encompass several individual streams or recordings, whereas individual content would
+be a single one-off stream or recording (which presumably does not fit into an established class). Proposing either
+a class of content or individual content both require a DISCUSS thread as written above, but once a class is
+established, content makers are free to make content under the model defined by that class without having a special
+DISCUSS thread for each recording or stream. You may, of course, use the dev list to organize a particular stream or
+recording for a particular content class.
+
+The following bullets represent current content classes:
+
+* A __Contributorcast__ is like a podcast and is held by contributors to the TinkerPop project. They may or may not be
+official committers, but they should have submitted merged pull requests of significance or have some recognized
+standing in Stackoverflow, Discord or just generally the TinkerPop Community. At least one official committer must
+be on the stream and those committers are in charge of content presented and those other contributors they invite to
+join. There is no particular format for this content and it is meant to be informal in its style but informational and
+more often than not about TinkerPop itself.
+* __TinkerPop Wide__ streams are about the wider TinkerPop Community. They focus on third-party tools, libraries, graph
+system implementations and applications that are powered by TinkerPop, but might also stretch into the general graph
+world. An official committer must host the stream.
+
+All media needs to achieve a certain level of consistency and quality with existing content. Content creators and
+their guests should abide by the community guidelines for link:https://safety.twitch.tv/s/article/Community-Guidelines?language=en_US[Twitch],
+link:https://www.youtube.com/howyoutubeworks/policies/community-guidelines/[YouTube] and the
+link:https://community.apache.org/contributors/etiquette[ASF] when producing media.
== Release Notes