Windows future

[Thomas Hardjono]

Hi Jeff,

IMHO, at the end of the day if the Kerberos user community wants
to see an on-going development of KfW as a true open-source project
then folks will need to contribute dev cycles and/or resources.
By that I mean cycles on Windows development for KfW.

>> Secure Endpoints believes that it could bring KFW current in about four
>> calendar months with a better than full time effort.  However, it would
>> all be for naught if the Consortium didn't have its own in-house
>> resource to maintain the code going forward and perform interop testing
>> with future Microsoft releases while they are in early beta.  We
>> estimate the cost of development and maintenance would be approximately
>> $280,000 for the first year with an on-going cost of $120,000 for each
>> subsequent year.  This is assuming that the efforts Secure Endpoints has
>> already put into KFW and NIM are accepted as a starting point.

I personally do not think MIT, the MIT-KC board and Members would
like to see us spend the amount of money that Secure Endpoints is asking for
on a single vendor.

/thomas/


________________________________________
From: krbdev-bounces at MIT.EDU [krbdev-bounces at MIT.EDU] On Behalf Of Jeff Blaine [jblaine at kickflop.net]
Sent: Thursday, September 30, 2010 9:31 AM
To: krbdev at mit.edu
Subject: Re: Windows future

The MIT Kerberos Consortium has no response to Jeffrey Altman's
information in the post linked below?

http://mailman.mit.edu/pipermail/krbdev/2010-August/009259.html
_______________________________________________
krbdev mailing list             krbdev at mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev