search

thecodeteam / roadmap

The {code} Team Roadmap
3 stars 1 forks source link

Reword the REXray introduction and documentation #62

Closed kacole2 closed 8 years ago

kacole2 commented 9 years ago

this is to take out the "big" words and brand rexray as a pure "docker volume driver". Categorize and minimize the amount of information to develop a better first impression.

akutz commented 9 years ago

Hi @kacole2, I performed some of this surgery yesterday on the README.md at https://github.com/akutz/rexray/tree/feature/foundation. Check it out and let me know what you think.

kacole2 commented 9 years ago

@akutz looking better. i think we need to put our marketing hats on. What will gain more traction (think marketing, not tech):

1) REX-Ray provides visibility and management of external/underlying storage via guest storage introspection. Available as a Go package, CLI tool, and Linux service, and with built-in third-party support for tools such as Docker, REX-Ray is easily integrated into any workflow.

or

2) REX-Ray is a Docker Volume Driver that provides persistent storage for containers by exposing 3rd party storage volumes as folder paths. Additionally, REX-Ray provides management and visibility of multiple storage platforms as a standalone CLI tool.

akutz commented 9 years ago

Hi @kacole2,

REX-Ray is not a pure Docker volume driver, nor do I agree it should be advertised as such, especially with its roadmap. @clintonskitson, thoughts?

kacole2 commented 9 years ago

@akutz i looked at REXray 0.2 features. Think of how you want to make a splash. You always ride the coat tails of what has the most marketing power. Right now, if you go to someone and say "i've got this awesome storage introspection tool", they will have no idea what you are talking about. You should be able to sell your product without having to explain it. At the same time, what is going to be the biggest use case? Right now, it's a Docker Volume Driver.

akutz commented 9 years ago

Hi @kacole2,

That's what bloggers are for :) The REX-Ray README mentions Docker right there in the intro. This isn't my first dance, and while I'm intrigued by your tango, I think you missed that they played a waltz. I'm all about selling an idea and product, but I'm also about consistency and avoiding rebranding. I know where REX-Ray is going, and what it's purpose will be moving forward with regards to Docker, Mesos, etc. I don't wish to brand it strictly as a Docker tool today only to have to minimize that or alter people's perception of that later. How about this:

REX-Ray is a storage management platform available as a Docker volume driver, a Go package, a CLI tool, and a Linux service. REX-Ray provides visibility and management of external/underlying storage via guest storage introspection and is easily integrated into any workflow. For example, here's how to list storage for a guest hosted on Amazon Web Services (AWS) with REX-Ray:

kacole2 commented 9 years ago

then i guess the rest of the team is left out on the roadmap and where this is going.

and no i'm not dancing. I'm stating what I know.

akutz commented 9 years ago

Hi @kacole2,

Perhaps this type of conversation is better held via voice because the tact and tone of the above messages with regards to thinking how I want to make a splash, or putting on my marketing hat come across as condescending. I was trying to ignore the implied undertones and took a similar approach to condensing nuance to witticisms with my remark about dancing, but I guess it offered the same offense I took.

FWIW, I meant no offense, but I'd offer that what you're stating is your opinion. Just as I'm stating my opinion mine. I am free to disagree with yours, just as you are with mine. Please note that I did attempt to meet you in the middle with an offered suggestion.

No one is leaving anyone out. I am referring to what @clintonskitson and I have discussed about REX-Ray and how it will work in the future with regards to libstorage, Mesos, and other ideas about which we've chatted that will likely coalesce or fit into future roadmaps.

@clintonskitson, what are your thoughts? I know that you've discussed with Josh that even once Libstorage becomes our focal point of storage integration into Docker he sees REX-Ray as having a life beyond into Mesos and other integration points. That's the tack I'm taking on trying to come up with wording that, while highlighting Docker, doesn't position REX-Ray as solely a Docker tool.

kacole2 commented 9 years ago

@akutz no offense taken.

clintkitson commented 9 years ago

We're on the right track here. Yes we want to make sure people 1) understand the value of it 2) tag along with big brands. The don't believe these things are mutually exclusive.

REX-Ray is a storage management tool providing advanced and consistent volume management across many storage platforms. It is easily integrated into any workflow and provides visibility and management of external/underlying storage via Docker Volume Driver, HTTP/JSON API, a Go package, and CLI tool. At its core REX-Ray performs abstraction, orchestration, and guest storage introspection which pushes storage management to the edge. For example, here's how to list storage for a guest hosted on Amazon Web Services (AWS) with REX-Ray: