+1 that's a great idea
On Wed, Jul 20, 2011 at 10:19 AM, Jonathan Ellis wrote:
> I'd love to put a "Planet Cassandra" aggregator together.
>
> On Wed, Jul 20, 2011 at 12:13 PM, Ed Anuff wrote:
>> I think that what's being asked for isn't so much announcements as
>> some sort of way of communica
Edward, by "noise" I mean talk between users, or even developers, that's not
hard information about Cassandra. (I don't mean to demean talk between users
or developers, that is indeed the place to go if you want to be part of the
conversation.) I don't consider announcements about upcoming features
On Wed, Jul 20, 2011 at 12:48 PM, David Boxenhorn wrote:
> I am not going to argue the point, because it's not really the point that I
> wanted to make. Maybe I'm an atypical user.
>
> The point I wanted to make is that there should be someplace for users to
> go
> to find out what's going on with
Ed, that's exactly what I want. A blog format works for me too. Cassandra is
*far* from being a black box, and users have to be quite educated about
Cassandra internals in order to make decisions.
Here are some examples of things I'd like to know, from concrete to
abstract:
1. New releases
2. Bug
I'd love to put a "Planet Cassandra" aggregator together.
On Wed, Jul 20, 2011 at 12:13 PM, Ed Anuff wrote:
> I think that what's being asked for isn't so much announcements as
> some sort of way of communicating or summarizing roadmap. However, in
> practical matters, I'm not sure how this can
I think that what's being asked for isn't so much announcements as
some sort of way of communicating or summarizing roadmap. However, in
practical matters, I'm not sure how this can be done in a mailing list
form. Anything that gets "announced" as roadmap is either so far
along that it's not road
On Wed, Jul 20, 2011 at 12:28 PM, David Boxenhorn wrote:
> Not true. I am a user. I consider this to be effectively the same as
> deprecating supercolumns (with support for the old API for backward
> compatibility). The fact that it is in the presentation that I linked to -
> from a DataStax emplo
I am not going to argue the point, because it's not really the point that I
wanted to make. Maybe I'm an atypical user.
The point I wanted to make is that there should be someplace for users to go
to find out what's going on with Cassandra, with out all the noise of the
user and dev lists, or JIRA
You missed the point completely, then.
We recommend not using Supercolumns if you don't know what you're
doing, because almost everyone who does is doing it for the wrong
reasons.
If you are using Supercolumns for the right reasons (or even the wrong
ones) you don't need to worry because the API
Not true. I am a user. I consider this to be effectively the same as
deprecating supercolumns (with support for the old API for backward
compatibility). The fact that it is in the presentation that I linked to -
from a DataStax employee! - with essentially the same message (i.e. don't
use them if y
That's exactly the kind of thing that *shouldn't* be on an announce
list (and stay on the dev list), precisely because it deals with
internals that users don't care about.
On Wed, Jul 20, 2011 at 11:18 AM, David Boxenhorn wrote:
> I would like to see this list also used for announcing upcoming fe
I would like to see this list also used for announcing upcoming features. At
some point a decision is made that some future version will include some
important feature. I don't want that information to be buried in a JIRA
ticket or a user/dev list discussion.
For example, I was surprised to learn,
DataStax has had requests for something like this. It seems like
something that would be generally useful for the community though.
Regarding twitter, I'm not sure a twitter account should be required
to get that information. I think you can follow a twitter account as
an rss feed though, so that
On Mon, Jul 18, 2011 at 10:32 AM, Sylvain Lebresne wrote:
> That being said, I could understand that some people may find it
> cleaner to have a
> separate announce list and it is not something unheard of, so I'm ok
> with that if enough
> people thinks it's a good idea.
Ditto.
> - should it be
I have mixed feeling about that.
On the one side, I agree with Gary that it doesn't add any real value.
There is twitter,
and we use consistent tagged subjects for release email, so it's easy
to subscribe
to the user list and set up a filter.
That being said, I could understand that some people m
I think a lot of people follow cassandra on twitter. However I don't think it
would be a big deal to email both user@ and announcements@ when a new release
is out, if people don't mind the extra list.
Nick - is this from people asking about this?
On Jul 18, 2011, at 9:50 AM, Gary Dusbabek wrot
Following @cassandra on twitter or a google alert would be simple enough I
think.
Gary.
On Mon, Jul 18, 2011 at 14:26, Nick Bailey wrote:
> What do we think about having a separate mailing list for just
> cassandra related announcements. The main purpose being announcing new
> releases once the
I think this is a good idea. It would be helpful for a lot of people who
don't want to monitor dev, but they want the artifacts that come out of it.
On 7/18/11 7:26 AM, Nick Bailey wrote:
What do we think about having a separate mailing list for just
cassandra related announcements. The main pu
What do we think about having a separate mailing list for just
cassandra related announcements. The main purpose being announcing new
releases once they pass a vote and are put up on the website. I think
there is a desire for a way to be informed when new releases are
available without sifting thro
19 matches
Mail list logo
