If you are interested about Apache Ozone please see https://ozone.apache.org

If you are interested about how this Twitter account is used, please continue to read.

Follow us on Twitter at @ApacheOzone.

Disclaimer

The goal of the Apache  Ozone Twitter account is to help early adopters and users to get information about Ozone as an Apache project. We would like to tweet about developments in Ozone and big data community.

The Twitter account is handled by individuals: committers and PMC members which means that individual views can be noticed behind tweets (similar to the progress of the project based on individual contributions).

The tweets are not voted one-by-one by the PMC, the tweet contributors, who handle the project Twitter account, do the best to follow the “Apache way”.

Account usage

We believe that tweets are an important way to communicate with the community, and helps to build a stronger base for “community over code”.

We also realize the importance of an official Twitter account: It becomes a de-facto face of the project.

As all the tweets are tweeted from the name of the project, all the comments and communication should follow the guidelines of ASF and should be inside the boundaries of the project which is governed by the PMC and the ASF.

To achieve this, we propose to do the following:

• Write down guidelines we would like to follow with the Apache Hadoop Ozone account.
• Name the individuals who contribute to write new tweets.
• Provide easy way to give feedback or address an issue.
• Maintain and improve this page after any issues to improve the quality of the communication in the future. (Adding good and bad examples).

Guidelines

There are a few guiding principles that we will use before going down into specific usage guidelines.

1. Twitter account is not a substitute

The apache mailing lists, JIRAs and Github are where the core Apache communications happen. Twitter is not a substitute for those tools. So, while Twitter is a useful tool for disseminating information it is not considered as a substitute for any of the primary collaboration tools. In short, The project related information (roadmap, features) and other discussions should and will happen as it does today.

2. Conversations on Twitter

Twitter is a two-way communication medium. People will respond to your tweets. Not all responses will be civil.
In most cases, it would be best to engage in a conversation via a personal account.

3. Protecting and honoring Apache brand.

Many Apache projects are backed by commercial entities. It is easy to blurr the difference between the commercial entity and Apache project. Extreme care should be taken to make sure that tweets from this account reflect the true Apache brand, and the open nature of the project. This account should not promote companies and other commercial activites, or things like hiring.

This does not mean that links to companies, or talks or other interesting things cannot be shared. We trust that Apache committer is someone that will act in the best interest of Apache Ozone and will have enough judgement to make sure that his/her integrity is not compromised in this regard.

An operational advice; if in doubt, use your personal account to tweet. If some others feel that it should be tweeted via Apache Ozone, then they can always retweet it.

4. Topics of Interest

The topics of Apache Ozone twitter account will primarily be of technical nature. However, Twitter is a place where human beings interact. So use your judgement in tweets. Off-topic, and controversial things are best avoid.
For example, something like “I support/oppose the current president” or something like “great game Rams, but what a win Seahawks” are great examples of topics which are best expressed via a user’s personal account.

But a human story that involves Ozone or Hadoop or technology is very powerful way and welcome.

Some examples of the content that is good for this account to tweet will be:

• Share links from the companies if they represent good, technical content (A good technical blog post about any new features is acceptable).

• Mention presentation from commercial events, presentation recordings if they are available freely and are technical.

• Share any news about development and community activities. The right level of the information sharing is not defined by this document and judged mainly by the followers (tweet only releases? Or ask feedback for design docs?)

So please use your discretion.

5. Apache code of conduct

We would like to promote the core ideas of Apache via this account. All Hadoop committers are welcome to tweet via this account. We would like to emphasize that if a tweet is inappropriate and invites objections, we will remove that tweet.

Anyone can report the content of a tweet, to the ozone-dev or private lists.

Initial committers that is interested in Tweeting about Ozone

As of now the following committers will handle the twitter account:

• Dinesh Chitlangia
• Anu Engineer
• Márton Elek
• Wei-Chiu Chuang

We will add any Ozone  committers who are interested in tweeting about Ozone to this list by sharing the password.

Feedback

As nobody is perfect, any feedback is more than welcome. If you found any issues with any tweets please report it (in the following order).

1. Reply to the tweet and express your concerns.
2. If you concerns are not addressed write to the PMC list (private@ozone.apache.org)
3. If your concerns are not addressed, write the contacts of the Code of conduct