[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: Karl Fogel <kfogel_at_red-bean.com>
Date: Wed, 25 Feb 2009 17:41:26 -0500

"Hyrum K. Wright" <hyrum_wright_at_mail.utexas.edu> writes:
> Along the lines of not paying attention to users, did this arise from
> the "Speeding up workspace" thread on the users list, perchance? This
> is open source, people: if you want to have influence in the
> community, contribute. Period. (Caveat: "contribute" does not mean
> "write code". It could mean write code, but it could also mean join
> in the development discussion, fund a developer to work on your
> feature, or contribute financially to SVNCorp. But being visible in
> the community will give you a much louder voice when it comes to
> features, etc.)

I know I'm totally kibbitzing, having not been active in development
lately, but:

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.

Most users already know that increased investment of time & effort will
bring increased influence. No one thinks that's unjust or anything.
But it's still good (for the project as well as for users) to provide
important stuff in a way that's easy for non-involved users to follow.

(By the way, we've not had a really good plan for what to do with
donations to the SVN Corp. We'd probably get a lot more donations if we
did; it might work for SVN Corp to fund development, just would have to
be thought through carefully...)


Received on 2009-02-25 23:41:44 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.