[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: John Mark <johnmark_at_johnmark.org>
Date: Wed, 25 Feb 2009 15:06:17 -0800

On Wed, Feb 25, 2009 at 2:41 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:

> Neels had a good point.  For complex but important topics like the wc
> rewrite, a summary now and then would make a big difference to the many
> users who don't have time to follow the development list.
> Lots of projects keep a blog for this sort of thing.  Subversion never
> has, but it might be time to consider one.  Or if the Submerged blog at
> http://blogs.open.collab.net/svn/ is doing that job already, then link
> to it from somewhere on the front page.

I hope nobody minds if I chime in here... but I think this is a great
point and, in my opinion, one thing that's missing from Subversion. As
I put together more community days - more on that later - I'd love to
know where to send the people we meet so they can find topical info on
new developments. I'm happy to help formulate a system that we can use
for just such a purpose. One thing I'm about to implement is importing
feeds into the submerged blog. That way, whenever one of you posts
something interesting, I'll add it there.

The submerged blog *could* be something that fills this need, but
we've let it lie still for too long - not pointing fingers, because
I'm just as guilty as anybody else. I'd like to remedy that ASAP.
Considering the amount of "mindshare" grabbed by other SCM's within
various open source dev communities, I think now is past time to look
at renewed outreach efforts, with more blogging being just one.

If you'd like to brainstorm things we could do in concert, I'm happy
to drop in on IRC and have that discussion.


Received on 2009-02-26 00:06:40 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.