[Developers] Status of lead developer?

[Bart Matthaei]

Hi Tom,

you can mail it to me, I can put it on sshkeychain.org as a beta. :-)

Regards,

Bart

On Jan 10, 2007, at 4:06 PM, Tom Rushworth wrote:

> Hi all,
>
> I've been intending to build a universal binary for the last 3 months,
> but like Bart real life has been keeping me much busier than I would
> like.  I wasn't going to say anything until I was certain I'd have  
> the time
> to do it :), but I guess saying I will is a way to put pressure on  
> myself
> to _find_ the time.
>
> One problem I can't fix is that I have nowhere to post the binary.   
> I'm
> connected via satellite and can't run any kind of server.  Is there  
> anyone
> I can mail the binary to that can put it up somewhere?
>
> I have the svn tree from sometime in August 06 I think.  I'll try  
> to refresh
> it this weekend, apply the patch from brion at pobox.com and build the  
> binary,
> then we can all test it.  Of course, if anyone can get to it  
> sooner, by all
> means do so.
>
> Bart, I'll dig out last summer's working repository later today and  
> see if
> I can still connect.  If I can connect, I'll let you know, and you  
> can tell
> me which branch, if any, you want me to build.
>
> I use SSHKeyChain all day, every day, on several machines.  It  
> would be a
> real shame to let it rot away.
>
> On 2007-Jan-10, at 06:35 , Bart Matthaei wrote:
>
>> On Jan 10, 2007, at 6:27 AM, sshkeychain at boonstra.org wrote:
>> [snip]
>>>  (1) Keep things more-or-less as they are in the expectation that  
>>> you
>>> [Bart] will be free (at some reasonably imminent date) to be more  
>>> active,
>>> but post a universal binary of the current stable branch with  
>>> Brion's
>>> patch -- both to eliminate the apparent neglect and to help out  
>>> those
>>> need it.
>>>
>>>   (2) Start a more formal open-source project on sourceforge or  
>>> somewhere
>>> similar.  I would be willing to volunteer my meager skills to be  
>>> one of
>>> the developers, but I believe that your involvement would still be
>>> essential at some point to keep things alive.  It may be possible to
>>> find another developer or two, based on mailing list interest.   
>>> We would
>>> at least need somebody who (unlike me) owns an Intel ac, for  
>>> testing.
>>
>> Either way, we need to get a release on the rail a.s.a.p.
>>
>>> I don't have much of an opinion about which --  (1) or (2) -- should
>>> happen.  SSHKeychain is too cool to lose to bit rot, so I'm  
>>> willing to
>>> help, but only if you want it.   You are a better judge of  
>>> whether you
>>> have the time and inclination to pursue option (1).  If you don't  
>>> have one
>>> or the other, option (2) is clearly the way to go.
>>
>> Your help is greatly appreciated. I agree that we need to post a  
>> universal binary of the current stable branch.
>> But we need to test the current branch first, to see if everything  
>> is working.
>>
>> I am willing to give you write access to the svn repository if you  
>> send me a md5 hash as a password by private mail.
>> This way you can apply your patch to the SVN tree.
>>
>> After that, we can test the branch and see if it runs stable, and  
>> all the new functionality is working.
>>
>> Has anyone on this list been using the latest SVN tree?
>>
>> Regards,
>>
>> Bart
>>
>> -- 
>> Bart Matthaei                                       bart at ambrero.nl
>>
>> Ambrero Software
>> http://www.ambrero.nl/
>>
>>
>>
>> _______________________________________________
>> developers mailing list
>> developers at sshkeychain.org
>> http://www.sshkeychain.org/cgi-bin/mailman/listinfo/developers
>
> --
> Tom Rushworth
> GPG: DF93 C92A A27C 7AC7 FE06  CF14 F61C 6CFA F7E8 F81C
>
>
>
> _______________________________________________
> developers mailing list
> developers at sshkeychain.org
> http://www.sshkeychain.org/cgi-bin/mailman/listinfo/developers
>

-- 
Bart Matthaei                                       bart at ambrero.nl

Ambrero Software
http://www.ambrero.nl/