Hi all,

The official Druid Twitter account [1] is currently being managed by a
small group of PMC members who have direct access to the account. This
is causing a couple of issues.

- Only PMC members can access the account. However, most of the
current PMC members are developers who primarily write codes rather
than tweets.
- Because non-PMC members cannot access the account, non-developers
cannot make contributions using Twitter.
- We currently cannot invite non-developers as PMC members since we
are not acknowledging non-coding work.
- Sharing the password among many people can cause security problems.

To address these issues, I suggest making a new process for managing
the Twitter account and tweets as below.

1. Sharing the account

The official Druid Twitter account is owned by the PMC chair. Only the
PMC chair can access the account directly. Other contributors,
including PMCs, share the account using TweetDeck [2]. TweetDeck
natively allows sharing the account among different people without
sharing the password. TweetDeck also has embedded roles, i.e.,
"owner", "admin", and "contributor", that have different permissions.
As these roles are similar to the Apache PMC members and committers,
respectively, I suggest
  - The PMC chair invites PMC members as "admins" on TweetDeck.
  - The PMC chair or PMC members invite Committers as "contributors"
on TweetDeck.
  - The "admins" and "contributors" can log in with their "own"
account on TweetDeck and write tweets on behalf of the Druid account.

See [3] to learn more details of the "owner", "admin", and "contributor" roles.

2. A new review process for tweets

I suggest setting up a "review process" for tweets similar to what we
do for the code review. Every tweet should go through the review
process before being published. We should also provide guidelines for
what "good" tweets are. Good tweets should promote only the Apache
Druid brand. The review process should be done based on the
guidelines. What should be in the review guidelines would be an
interesting discussion. I would like to discuss it later if we all
agree on having the review process.

For the review tool, I suggest using GitHub. What I'm imagining is
that contributors make Pull Requests for tweets they want to publish.
We can organize tweets on GitHub in a structured way such as
organizing based on the date when they are published. I am open to
other suggestions as well if there are better alternatives.

This review process can be also useful for acknowledging non-coding
work. We can collect metrics to identify active contributors and give
them credits. For example, contributors who write tweets can be
invited as Apache committers based on their activity.

3. Metrics for the Druid account

Some metrics such as impressions for the Druid account are available
in [4]. This will be available only for the account owner which will
be the PMC chair. I'm not sure if there are other services where you
can see those metrics without accessing the account.

Love to hear from others.
Jihoon

[1] https://twitter.com/druidio
[2] https://tweetdeck.twitter.com
[3] https://help.twitter.com/en/using-twitter/tweetdeck-teams
[4] https://analytics.twitter.com

PS. I think this Twitter account issue is a small piece of the problem
of non-coding work being not acknowledged. I will start another thread
to discuss it.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
For additional commands, e-mail: dev-h...@druid.apache.org

Reply via email to