eWEEK Hosts Tweetchat on Big Data Analytics in Cloud Jan. 16

On Wednesday, Jan. 16 at 11am Pacific Standard Time/2pm Eastern Standard Time/7pm Greenwich Mean Time, eWEEKnews will host its first Tweetchat event. The topic will be "Big Data Analytics in the Cloud: Is the Future Now?"

eWEEK is moving into some new-media interactive events, and you are invited to participate.

On Wednesday, Jan. 16 at 11 a.m. Pacific Standard Time/2 p.m. Eastern Standard Time/7 p.m. Greenwich Mean Time, eWEEKnews will host its first Tweetchat event. The topic will be "Big Data Analytics in the Cloud: Is the Future Now?" It will be moderated by The Station, who also serves as eWEEK's editor of features and analysis.

The Station has some experience in this genre. Last August, I was invited to be the first guest moderator for an IBM Tweetchat, entitled "Cloudchat: What Level of Resiliency Is Right for Your Cloud?" From most reports, it was highly successful.

Quick facts:

Topic: "Big Data Analytics in the Cloud: Is the Future Now?"
Date/time: Jan. 16, 2013 @11 a.m. PST/2 p.m. EST/7 p.m. GMT
Hosted by: @eWeekNews
Moderator: Chris Preimesberger: @editingwhiz
Tweetchat handle: Use #eWeekChat to follow/participate in the chat
Chatroom link: http://tweetchat.com/room/eweekchat

Here's how a Tweetchat works:

Who: All those interested in the topic who also have a Twitter ID. Use this chatroom link: http://tweetchat.com/room/eweekchat

What: A tweetchat is an online conversation held at a prearranged time following a specific hashtag. In eWEEK's case, we will be using #eWeekChat for all or most of our Tweetchats. Chatroom link: http://tweetchat.com/room/eweekchat

When: Wednesday, Jan. 16 at 11 a.m. Pacific Standard Time/2 p.m. EST/7 p.m. GMT.

Where: The chat can be followed on Twitter using the hashtag #eWeekChat. A link to the recap (so you can see a record of what everybody Tweeted) will be posted on this blog the following Friday, Jan. 18.

Why: The whole idea is to facilitate additional industry dialogue and provide a forum for questions, idea sharing and problem solving. We also want your input on what you'd like to discuss during future chats, so please leave a comment on this post or tweet @eweeknews with topic ideas.

All participants need to do is to check in to use #eWeekChat to follow and/or participate in the chat. Again, the chatroom link is http://tweetchat.com/room/eweekchat.

Participants will be able to ask questions of eWEEK staff members and other participants or simply add their thoughts to the conversation. The only restrictions are that we stay on topic and that you say what you need to say succinctly (140 characters).

You may not have participated in a Tweetchat previously. They generally move pretty fast, but you can learn a lot. We'll also post a record of all the comments so that you can refer to it afterward.

Please note that to maintain a semblance of order, please prefix your question or comment with the number of the question we are currently discussing. As an example, the moderator may post: "Q1: Are you now using, or planning to use, a cloud-based business analytics service in the next 12 months?"

To which you might answer: "A1: Yes, I want to, but my boss is a little skeptical. We work for the CIA."

To see an example of what this looks like, here is a transcript of the IBM cloudchat from August.

Particularly welcome for the Jan. 16 event would be comments on how people are using or planning to use cloud-service business analytics, a rapidly ramping-up sector of cloud computing—especially in midmarket and small enterprises.

A Tweetchat is a venue that is easy to use on any type of device, too. By the way, did you know that eWEEK is the only mainstream IT trade publication that has specific apps for Android and iOS devices?

You can add this to your calendar via Eventbrite. Hope to connect with you Jan. 16.

Chris Preimesberger

Chris J. Preimesberger

Chris J. Preimesberger is Editor-in-Chief of eWEEK and responsible for all the publication's coverage. In his 13 years and more than 4,000 articles at eWEEK, he has distinguished himself in reporting...