cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Upayavira ...@odoko.co.uk>
Subject Re: community input on the GSoC
Date Fri, 08 Jul 2005 05:52:10 GMT
Antonio Gallardo wrote:
> Upayavira wrote:
> 
>> Niclas Hedhman wrote:
>>
>>> On Wednesday 06 July 2005 17:57, Torsten Curdt wrote:
>>>
>>>> o work through patches
>>>> o give them limited svn access
>>>>    - give them a full address (jdoe@apache.org)
>>>>    - add a prefix to the address (gsoc-jdoe@apache.org)
>>>
>>>
>>>
>>>
>>> There is no technical need to hand out a apache.org account, unless 
>>> infrastructure insist of doing this, and AFAIK the long-term target 
>>> is the exact opposite.
>>>
>>> So, why not check with infrastructure if they would support to set 
>>> SVN user accounts to john.doe@gsoc2005.google.com or something 
>>> similar, and someone trusted can just generate a password and send them.
>>>
>>> I think infra@ would be Ok, since it will be relatively easy to 
>>> "clean-up" later.
>>
>>
>>
>> Technical need is because of commit mails, not because of SVN itself. 
>> Account might not do much, but some kind of mail account must exist, 
>> IIUC.
> 
> 
> 
> Interesting. Please expand more the idea. :-) In special, why the commit 
> mails are the problem.

Actually, it is for two reasons. (1) because they need to run svnpasswd 
to set their password. (2) because, IIUC, mail when sent must come from 
a real email account (something to do with antispam).

More than that, I can't really say ('cos I don't understand enough).

Regards, Upayavira


Mime
View raw message