[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Questions from the Subversion 1.6 Preview event in Berlin

From: Justin Erenkrantz <jerenkrantz_at_apache.org>
Date: Wed, 25 Feb 2009 23:00:43 -0800

On Wed, Feb 25, 2009 at 10:06 PM, Greg Stein <gstein_at_gmail.com> wrote:
> I'm assuming Justin is like myself in thinking, "shit. that woulda
> been neat to know about and possibly attend." ... NOT "damn. that
> shouldn't have happened without our permission." Your entire reply is
> as if Justin said it *should not* have happened, when I suspect is was
> more like *why couldn't the rest of us have been involved?*

As usual, Greg channels me quite well. =)

> I mean... this even has a Capitalized Name. And apparently Tuesday was
> just the first day.
> Or maybe it was just for elego and CN customers. Fine. Cool. But when
> the first line of an email talks about an Event, then my first thought
> is "huh? what event? why wasn't I invited? I like SVN. I think I could
> have contributed in some way. I woulda been interested to talk to
> these people." (and after reading the report about wc-ng, I think it
> was mischaracterized, so I *really* would have wished to have been
> there)

Exactly my feelings.

> So all that said, your email is right in that we cannot and should not
> attempt to control any happenings around Subversion. But I suspect
> you're preaching to the choir, and Justin wasn't saying that at all.
> It just seems weird when there is an event that seems/appears/sounds
> like a "community" event, and we have NO IDEA that it is happening. I
> cannot imagine any community event that would NOT want our
> participation (our == the devs), so why aren't we hearing about these
> things?

Yup yup. As I've said before, such events would only be better served
by the real community knowing about it. -- justin

Received on 2009-02-26 08:00:57 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.