[josm-dev] Commit access

Henry Loenwind henry at loenwind.info
Sat Oct 4 16:29:37 BST 2008


Dirk Stöcker wrote:

> also has some problems (see tracker). So you still need to improve the 
> quality of your patches a bit. :-)

Here I'd like to add: JOSM is some kind of special case, because our 
auto-compiled "latest" version actually is widely used. On other 
projects a broken (e.g. deleting '{0}/*' where the placeholder variable 
can be "") SVN checkin does not hurt, here it has the potential to. So 
it is better to channel all commits through some senior team members.

>> know what I am doing and I want to continue working on JOSM. I want to
>> ask what is necessary for me to get commit access to the JOSM repository
>> since creating a bug for each patch I create seems a bit of an overhead
>> to me. Especially for oneliners :-)

May I point out that 1-line patches are the most dangerous and sneaky 
kind of patch? Oh, how many times have I killed our application at work 
with just one line.... (Actually not that often---we practice peer 
review there.)

> I got write access, because Frederik was flooded with my patches and told 

BTW: SVN holds 11 patches, now.

cu
Henry




More information about the josm-dev mailing list