[OpenAFS] Re: [AFS3-std] Re: IBM will not re-license OpenAFS .xg files
Ted Creedon
tcreedon@easystreet.net
Fri, 31 Aug 2012 06:59:59 -0700
--bcaec51b98cd2c814f04c89035c0
Content-Type: text/plain; charset=ISO-8859-1
For what its worth, while at Mentor Graphics, I retained Scott Myers and an
intern to write C++ header files for the IBIS specification.
IBIS specifies how to model complex electronic circuits and interconnect
(i.e. as in Intel motherboards).
Equivalent complexity. I built a special room with 36 ft of whiteboard,
Scott would layout the design and the intern would spend a week coding.
So that is my level of effort estimate, once the spec is written, which
took an industry committee of experts a wear to agree on.
Interestingly, the header files spotted several ambiguities in the spec
which is left unresolved guaranteed that multiple vendor IBIS
implementations would be incompatible.
Ted
On Thu, Aug 30, 2012 at 8:56 PM, Derrick Brashear <shadow@gmail.com> wrote:
> > Maintaining OpenAFS involves, among other things:
> >
> > * Kernel code as well as userspace code for various UNIXes.
> > * Mac OS X development (with quite a bit of OS internals involvement).
> > * Windows kernel file system development.
> > * High-performance threaded code with a complex lock model.
> > * A custom network protocol with substantial complexity.
> > * Cryptographic network security models.
> >
> > Some of those things (such as the Windows kernel file system work) no
> > other project, open source *or* commercial, does at the level that
> OpenAFS
> > does. This is a level of complexity *far* beyond the typical open source
> > project. The only open source projects I can think of with equivalent
> > complexity are primarily maintained by full-time, professional developers
> > whose job is to work on that software, and whose salaries are paid by
> > companies like Red Hat, Novell, IBM, Google, or Oracle.
>
> Indeed, it has come back to me through 3rd party channels that Apple
> has told developers
> "OpenAFS is doing it, so clearly it can be done ..." as outsiders.
>
> [...]
>
> > * A coherent mobile story for how mobile devices and applications are
> > going to access data in AFS, including how they can authenticate
> without
> > using user passwords (which are increasingly a bad authentication story
> > anywhere but are particularly horrible on mobile devices).
>
> Apple has made this somewhat harder by removing developer access to the
> hardware
> device identifier.
>
> Largely I find myself in agreement with the rest of this.
>
>
> --
> Derrick
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>
--bcaec51b98cd2c814f04c89035c0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
For what its worth, while at Mentor Graphics, I retained Scott Myers and an=
intern to write C++ header files for the IBIS specification. <br><br>IBIS =
specifies how to model complex electronic circuits and interconnect (i.e. a=
s in Intel=A0 motherboards).<br>
<br>Equivalent complexity.=A0 I built a special room with 36 ft of whiteboa=
rd, Scott would layout the design and the intern would spend a week coding.=
<br><br>So that is my level of effort estimate, once the spec is written, w=
hich took an industry committee of experts a wear to agree on.<br>
<br>Interestingly, the header files spotted several ambiguities in the spec=
which is left unresolved guaranteed that multiple vendor IBIS implementati=
ons would be incompatible.<br><br>Ted<br><br><div class=3D"gmail_quote">On =
Thu, Aug 30, 2012 at 8:56 PM, Derrick Brashear <span dir=3D"ltr"><<a hre=
f=3D"mailto:shadow@gmail.com" target=3D"_blank">shadow@gmail.com</a>></s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">> Maintaining OpenAFS i=
nvolves, among other things:<br>
><br>
> * Kernel code as well as userspace code for various UNIXes.<br>
> * Mac OS X development (with quite a bit of OS internals involvement).=
<br>
> * Windows kernel file system development.<br>
> * High-performance threaded code with a complex lock model.<br>
> * A custom network protocol with substantial complexity.<br>
> * Cryptographic network security models.<br>
><br>
> Some of those things (such as the Windows kernel file system work) no<=
br>
> other project, open source *or* commercial, does at the level that Ope=
nAFS<br>
> does. =A0This is a level of complexity *far* beyond the typical open s=
ource<br>
> project. =A0The only open source projects I can think of with equivale=
nt<br>
> complexity are primarily maintained by full-time, professional develop=
ers<br>
> whose job is to work on that software, and whose salaries are paid by<=
br>
> companies like Red Hat, Novell, IBM, Google, or Oracle.<br>
<br>
</div>Indeed, it has come back to me through 3rd party channels that Apple<=
br>
has told developers<br>
"OpenAFS is doing it, so clearly it can be done ..." as outsiders=
.<br>
<br>
[...]<br>
<div class=3D"im"><br>
> * A coherent mobile story for how mobile devices and applications are<=
br>
> =A0 going to access data in AFS, including how they can authenticate w=
ithout<br>
> =A0 using user passwords (which are increasingly a bad authentication =
story<br>
> =A0 anywhere but are particularly horrible on mobile devices).<br>
<br>
</div>Apple has made this somewhat harder by removing developer access to t=
he hardware<br>
device identifier.<br>
<br>
Largely I find myself in agreement with the rest of this.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
--<br>
Derrick<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________=
__________________________<br>
OpenAFS-info mailing list<br>
<a href=3D"mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a><br=
>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info" target=
=3D"_blank">https://lists.openafs.org/mailman/listinfo/openafs-info</a><br>
</div></div></blockquote></div><br>
--bcaec51b98cd2c814f04c89035c0--