inline ----- Original Message ----- > From: "Dave Lester" <[email protected]> > To: "mesos" <[email protected]> > Cc: "Jie Yu" <[email protected]> > Sent: Wednesday, September 3, 2014 3:54:31 PM > Subject: Re: updating website copy > > Just seeing this now, a few minutes after going live with the post. If > folks are OK with Ben's initial draft I can update the website copy this > afternoon. >
+1 from me. > I don't anticipate the project description and website copy will be static, > so perhaps we can organize a small group to discuss future improvements and > also be responsible for keeping it up to date in the future. If you're > interested in that (I know Joe chimed in with some thoughts about tweaks we > could make) maybe we can form a small working group to think more-deeply > about this and report back to the dev list. > This could probably done on an as-needed basis. > Moving forward, I think positioning the project (including messaging on the > website) will be important for communicating what Mesos is and for > increasing adoption. Most Apache project websites have done an abysmal job > at this, and left it to vendor websites to demonstrate their value > proposition. +1 > In the case of Mesos, I think there's a great opportunity for > the Apache community to work together to make progress on the project > website itself. Let me know if you're interested in digging deeper into > this. > Absolutely. > Dave > > > On Wed, Sep 3, 2014 at 6:44 AM, Tim St Clair <[email protected]> wrote: > > > I figured I would retouch this thread given that Jie will be adding a blog > > soon, I think the timing would be right for the website also. > > > > Cheers, > > Tim > > > > ----- Original Message ----- > > > From: "Benjamin Hindman" <[email protected]> > > > To: "dev" <[email protected]> > > > Sent: Monday, August 18, 2014 10:47:54 AM > > > Subject: updating website copy > > > > > > I believe it's high time to update the our website with some new copy > > (what > > > we have presently hasn't been updated for a while), and I wanted to reach > > > out to you for feedback in the hopes of making some improvements before > > > MesosCon (and my talk!). > > > > > > While I've always felt the most apt description for Mesos was as a > > "kernel" > > > in order to emphasize the power of the primitives for building new > > > distributed systems, in the earliest days I tended on the conservative > > side > > > with my choice of language as I felt it was easier for folks to grasp > > Mesos. > > > > > > But I feel like our project is at a level of maturity where that is less > > of > > > a concern, and my gut is that we should really embrace the kernel > > messaging > > > in order to leave folks with the right first impressions about the > > > technology, especially with respect to what it facilitates today and what > > > we hope it will facilitate tomorrow. > > > > > > I've pasted some new copy below that I'd love feedback on. We haven't > > > really done much of a review process for the website in the past, but I > > > thought I'd share this more widely in order to get any feedback before > > > making any updates. > > > > > > Looking forward to seeing many of you at MesosCon this week! > > > > > > > > ------------------------------------------------------------------------------------------------ > > > > > > Headline: > > > > > > Program against your datacenter like it’s a single pool of resources. > > > > > > Subhead: > > > > > > Apache Mesos abstracts CPU, memory, storage, and other compute resources > > > away from machines (physical or virtual), enabling fault-tolerant and > > > elastic distributed systems to easily be built and run effectively. > > > > > > > > > Distributed Systems Kernel > > > > > > > > > Mesos is a distributed systems kernel built using the same principles as > > > the Linux kernel, only at a different level of abstraction. The Mesos > > > kernel runs on every machine and provides applications (e.g., Hadoop, > > > Spark, Kafka, Elastic Search) with API’s for resource management and > > > scheduling across entire datacenter and cloud environments. > > > > > > > -- > > Cheers, > > Timothy St. Clair > > Red Hat Inc. > > > -- Cheers, Timothy St. Clair Red Hat Inc.
