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

Re: RFC: simple proposal for Internet-scoped IDs

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Wed, 5 Dec 2012 10:18:24 +0100

On Wed, Dec 5, 2012 at 1:54 AM, Eric S. Raymond <esr_at_thyrsus.com> wrote:
> Ben Reser <ben_at_reser.org>:

...

>> 3) You keep assuming that email addresses are immutably owned by
>> someone. That is fundamentally not true for the vast majority of
>> people and frankly is never absolutely not true.
>
> So? Does this make it any less a good idea to support that case
> properly? I think not - especially since committers to public
> repositories are quite likely to be in the (admittedly minority)
> group who do maintain stable addresses.

Just to be clear, this entire proposal / discussion is about a feature
that only makes sense for public repositories, forges, open source
projects, etc, ... right? AFAIU, there is no need for something like
this in corporate repositories, where you normally have a closed set
of users, with centrally managed accounts (usually in a central
directory), where SVN is just one of several IT services based on this
same user account.

I'm not downplaying the issue / proposal / discussion (public
repositories are certainly an important "market" for SVN), but bear in
mind that SVN also has high penetration in the corporate world, where
this is not an issue (quite the contrary, my company wouldn't want me
to claim my commits into their repository with
"jcorvel{_AT_}gmail.com", they want it associated with my company
account or company email address).

So I guess what I'm saying is: whatever comes out of this shouldn't in
any way hinder the usage in corporate environments. I think it would
be bad if any of this would be enabled by default, or if configuration
directives would generate doubt with sysadmins (unsure whether they
should enable such features). I'd hope a sysadmin would be able to
centrally block "the feature" (because they might not want attribution
ids in their repositories, no matter what their users think).

Also (but I guess that has already been said): if it ends up being
some client-side configuration, it should obviously be settable per
repository (so I can work with some forge with a certain attribution
id, and with the corporate repository without one, all from the same
pc).

-- 
Johan
Received on 2012-12-05 10:19:24 CET

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