[16416] in Kerberos_V5_Development
Re: Windows future
daemon@ATHENA.MIT.EDU (Jeffrey Altman)
Thu Sep 30 12:40:38 2010
X-Envelope-From: jaltman@secure-endpoints.com
X-MDaemon-Deliver-To: krbdev@mit.edu
Message-ID: <4CA4BD76.1090505@secure-endpoints.com>
Date: Thu, 30 Sep 2010 12:40:22 -0400
From: Jeffrey Altman <jaltman@secure-endpoints.com>
MIME-Version: 1.0
To: krbdev@mit.edu
In-Reply-To: <DADD7EAD88AB484D8CCC328D40214CCD01C69A22FA@EXPO10.exchange.mit.edu>
Reply-To: jaltman@secure-endpoints.com
Content-Type: multipart/mixed; boundary="===============1835039990=="
Errors-To: krbdev-bounces@mit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1835039990==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enig647DE8739C34E94101DBAC0A"
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig647DE8739C34E94101DBAC0A
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 9/30/2010 9:55 AM, Thomas Hardjono wrote:
>=20
> Hi Jeff,
>=20
> 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.
>=20
>>> Secure Endpoints believes that it could bring KFW current in about fo=
ur
>>> calendar months with a better than full time effort. However, it wou=
ld
>>> all be for naught if the Consortium didn't have its own in-house
>>> resource to maintain the code going forward and perform interop testi=
ng
>>> with future Microsoft releases while they are in early beta. We
>>> estimate the cost of development and maintenance would be approximate=
ly
>>> $280,000 for the first year with an on-going cost of $120,000 for eac=
h
>>> subsequent year. This is assuming that the efforts Secure Endpoints =
has
>>> already put into KFW and NIM are accepted as a starting point.
>=20
> 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 askin=
g for
> on a single vendor.
>=20
> /thomas/
Thomas:
You misinterpreted what I wrote. We estimated the resources that the
Consortium would require to restart and sustain an on-going Windows
development effort (with or without our help). We can produce such
estimates because we understand the needs of the user community, the
costs of the relevant expertise, and have spoken for years about what
needs to be accomplished. If you believe our estimates are incorrect,
it would do the Consortium well to present a plan to the community and
explain the resources that would be required to execute it.
Jeffrey Altman
--------------enig647DE8739C34E94101DBAC0A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
iQEcBAEBAgAGBQJMpL15AAoJENxm1CNJffh42HkIANZjV07xOI/NCyzbLJNBl7b4
T5weAaXTMbAaB/9AGPUlXkhPY6xdnNAtrDzsZI4Srmwm9/Hs6rXW6AlR4wyEx4WQ
NW8x6glxQYUSdJuNsSMlNNqswue1PklD8Hv+8BBaCap9r36tzADiVRIGr0Mb7xzt
DI6C5muujtN/M7fW/Tnpp/8ZWZ5NJPqGdu17WITz69vuYw2AFYbu28TOcU03muzu
2bhuydzuOvVrlzQxZeqHK7cqJAIfnSS+mwEQNnoYO6Zy+Z0MVT10javaEFBlbXzv
4Tk4PMHnQfmpmdEFJSGp8LQF7DVlJjrEFsuy4t60MsbX04vJG+PH1vq69/LpRXg=
=7e+Q
-----END PGP SIGNATURE-----
--------------enig647DE8739C34E94101DBAC0A--
--===============1835039990==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
--===============1835039990==--
