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

Re: [SVN-DEV] Re: [PATCH] complete: APR-ized svn_parse_date replacement

From: Brian Behlendorf <brian_at_collab.net>
Date: 2001-08-28 22:55:06 CEST

On Tue, 28 Aug 2001, C. Scott Ananian wrote:
> On 28 Aug 2001 kfogel@collab.net wrote:
>
> > An idea for making this work better than it does with the FSF (where
> > long delays in getting copyright papers from contributors are the
> > norm): send people self-addressed stamped envelopes and printouts of
> > the papers to sign. This makes it much more likely that they will be
> > returned in a finite amount of time. :-)
>
> and accept *faxes*! The FSF is playing it safe, even at the expense of
> contributors, because it fully expects to have to fight the court case one
> day. It's hard to imagine a violation of SVN's license, liberal as it is,
> so the greater flexibility of faxed signatures should definitely be in.

I'll pass this note on to our in-house counsel who'll be setting it up. I
would believe we could accomodate this, at least so we don't have to wait
on accepting contributions (even if we need the actual doc later on).

> and provide an easy way to see the *status* of the paperwork. many FSF
> contributors sent in their paperwork and then waited around
> for a confirmation notice or some such before finishing their patches.
> No notice is ever sent by the FSF, and so people assume that the paperwork
> got lost, or something, and eventually give up on their getting patches
> committed.

It's probably a file we could maintain under revision control somewhere.
=)

> Finally: with an adequate version control system, it ought to be possible
> to commit patches *immediately* pending paperwork. The commit can always
> be reverted if the paperwork doesn't come through. You should be careful
> to specially flag/lock further modification of lines where a patch is
> still 'pending' to avoid messy reverts in the abort case, but such a lock
> could provide a powerful incentive to all involved to deal with the
> paperwork expeditiously. You don't want to leave potential contributors
> hanging in paperwork limbo while their enthusiasm drains.

Yep, agreed 100%

> And the implementation of this system with SVN may be an excellent test
> case for the flexibility of the access control mechanism.

Heh, true!

Thanks for the ideas,

        Brian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:37 2006

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.