> The company I'm working at is evaluating subversion and we have a
> number of successful pilots in place.
>
> There are some issues we would like to address and I'm looking to
> talk to some people with Subversion internals experience that can
> help us optimize the Subversion experience for our users.
>
> I have some tentative budget allocated and we are a large company
> so the opportunity for a good long term contract or employment
> (if interested) may be in the cards.
>
> Here are some of the issues we would like resolved:
>
> 1) Reduce the ".lock" operation when doing updates.
> When svn does most "update" or "stat" operations, it traverses the
> tree making "lock files" this causes the speed of the tool be to
> much slower than it could be. We'd like to explore options for a
> custom build that would reduce that.
>
> 2) Reduce "entries.log" operation when doing updates/checkout:
>> For instance, when doing a "svn checkout" I'll see ".svn/tmp/entries"
>> created many times, and then renamed over ".svn/entries".
>>
>> Is there any way to reduce these items when you _know_ you're going
>> to be working in isolation?
>>
>> Could this be made any faster by just updating the files in place?
>
> 3) Reduce the size of the checkout, we'd like to explore opportunities for not having copies of the files in the "svn-base" directory, either storing this on the server (as an option) or maybe just compressing it.
>
> There will be more work, and this potentially could be a long
> term contract.
>
> I would like to talk someone with some internals experience that
> _potentially_ get these sort of changes pushed upstream into the
> client.
>
> Work would very likely be open sourced.
>
> Our location is Sunnyvale CA, and the job at minimum require some
> travel to our campus to interact with developers and assist with
> deployment of features. Someone willing to relocate to Sunnyvale
> would probably work best.
>
> Please respond with a resume, cover letter and ball-park figure for
> your hourly rate or salary requirements if looking for full-time.
>
> Finally, yes, I am aware of "collab.net", however I've had trouble
> spinning up interest from them on these issues.

FWIW, your questions made it to me via your CollabNet contact last
week and I replied with answers similar to what Greg gave along with
some names of people that might be interested. That said, I suspect
they would not be interested in working from Sunnyvale. If you want
core Subversion work performed, would that really be needed? That
requirement was not communicated to me last week else I'd have not
suggested them.

I suspect that the people I suggested are being contacted about their
availability and rates so that an answer could be provided back to
you. I forwarded your email to your CollabNet contact to let them
know you were not happy about not receiving a reply back.