<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <div class="moz-cite-prefix">On 09/04/2014 22:27, Chris Tacke wrote:<br>
    </div>
    <blockquote
cite="mid:7CF48B0CB8988E45AC776D68479B1446967E624707@MBX72.ad2.softcom.biz"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
        {font-family:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
span.txt
        {mso-style-name:txt;}
p.txt1, li.txt1, div.txt1
        {mso-style-name:txt1;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If
            you take a look at the live repository for Mono, you can see
            that Xamarin employees regularly update the source code
            (there are changes from 2 hours ago).  That places the
            statement that “Xamarin are unable to work on Mono” clearly
            into the FUD column.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mono
            is actively being fixed and improved by Xamarin and others.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
      </div>
    </blockquote>
    <br>
    Many thanks for bringing clarity to this for me Chris. As we're in a
    public forum I hope hope you won't mind me referencing this
    discussion now and in future when it is suggested to me that Xamarin
    have abandoned Mono.<br>
    <br>
    <blockquote
cite="mid:7CF48B0CB8988E45AC776D68479B1446967E624707@MBX72.ad2.softcom.biz"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-Chris<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <div>
            <div style="border:none;border-top:solid #E1E1E1
              1.0pt;padding:3.0pt 0in 0in 0in">
              <p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">
                  <a class="moz-txt-link-abbreviated" href="mailto:mono-devel-list-bounces@lists.ximian.com">mono-devel-list-bounces@lists.ximian.com</a>
                  [<a class="moz-txt-link-freetext" href="mailto:mono-devel-list-bounces@lists.ximian.com">mailto:mono-devel-list-bounces@lists.ximian.com</a>] <b>On
                    Behalf Of </b>Alex J Lennon<br>
                  <b>Sent:</b> Wednesday, April 09, 2014 4:18 PM<br>
                  <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:mono-devel-list@lists.ximian.com">mono-devel-list@lists.ximian.com</a><br>
                  <b>Subject:</b> Re: [Mono-dev] ***UNCHECKED*** Re:
                  Ongoing Mono development / Mono roadmap<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <div>
            <p class="MsoNormal">On 09/04/2014 22:00, Robert Jordan
              wrote:<o:p></o:p></p>
          </div>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal" style="margin-bottom:12.0pt">Were you
              living under a stone the past couple of years? :D <o:p></o:p></p>
          </blockquote>
          <p class="MsoNormal"><br>
            Just trying to understand the realities Robert :-D<br>
            <br>
            <br>
            <o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal" style="margin-bottom:12.0pt">You're
              mixing up Mono & MonoTouch like they were the same <br>
              and don't seem to understand how these technologies <br>
              are interwoven. <br>
              <br>
              Mono is an Open Source .NET implementation, while
              MonoTouch <br>
              (now Xamarin.iOS) is a spin-off with a lot of enhancements
              <br>
              targeted to mobile development. But at its core, it's
              still <br>
              Mono and its BCL. <br>
              <br>
              Mono's death, as you put it, would imply that Xamarin were
              <br>
              sooner or later out of business. It doesn't look so. <o:p></o:p></p>
          </blockquote>
          <p class="MsoNormal"><br>
            A key component of what I was told toay is that Xamarin are
            unable to <br>
            work on Mono due to contractual obligations to Attachmate.
            As a<br>
            result they are (I am told) abandoning Mono and doing
            something <br>
            else which is the (presumably) VM underneath the Xamarin
            tooling.<br>
            <br>
            I guess I'm looking for confirmation that either this is
            true, or<br>
            is some strange new form of FUD :) This comes from a
            discussion which<br>
            was originally about Microsoft open sourcing (ish, bits of)
            .Net.<br>
            <br>
            I care, because I think Mono is pretty fantastic, it allows
            me to retarget<br>
            products my business creates to embedded devices running
            Linux, and<br>
            I want to see it continue and grow. If the "death" of Mono
            were to be a <br>
            reality I would need to rethink some objectives.<br>
            <br>
            Which is why I asked you guys, because I figure if anybody
            can give me<br>
            a categorical answer then it is the developers...<br>
            <br>
            <br>
            <br>
            <o:p></o:p></p>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal">The truth is rather that *parts* of the
              Mono framework became <br>
              less important for Xamarin, as they are solely focused on
              mobile <br>
              nowadays. <br>
              <br>
              Which parts these are, should be too hard to figure out. <br>
              <br>
              Robert <br>
              <br>
              <br>
              On 09.04.2014 21:36, Alex J Lennon wrote: <br>
              <br>
              <o:p></o:p></p>
            <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
              <p class="MsoNormal" style="margin-bottom:12.0pt">Hi, <br>
                <br>
                I became involved in a conversation today on LinkedIn in
                which a <br>
                commentator was telling me Mono is "dead", due to
                contractual <br>
                constraints imposed on Xamarin by the "legal owners" of
                Mono, Attachmate. <br>
                <br>
                A snippet of the ensuing conversation follows, <br>
                <br>
                "In July 2011, however, Novell - now a subsidiary of
                Attachmate - and <br>
                Xamarin announced that Novell had granted a perpetual
                license for Mono, <br>
                MonoTouch and Mono for Android to Xamarin, which
                formally and legally <br>
                took official stewardship of the project." <br>
                <br>
                It also says as follows: " ...the future of the project
                was questioned, <br>
                since MonoTouch and Mono for Android would now be in
                direct competition <br>
                with the existing commercial offerings owned by
                Attachmate. It was not <br>
                known at the time how Xamarin would prove they had not
                illegally used <br>
                technologies previously developed when they were
                employed by Novell for <br>
                the same work". <br>
                <br>
                In the Mono project website (<a moz-do-not-send="true"
                  href="http://www.mono-project.com">www.mono-project.com</a>),
                you have three main <br>
                offerings, Mono, Xamarin.iOS and Xamarin.Android, and
                you can find a <br>
                link (at the bottom left corner of the page) to
                Xamarin's website. <br>
                <br>
                It is clear that this is a strategy by Xamarin to offer
                MonoTouch <br>
                developers a migration path to Xamarin tools, and not
                much more than that. <br>
                <br>
                To be able to woo Mono developers to Xamarin, Novell
                (Attachmate) and <br>
                Xamarin cut this deal, because it is of mutual
                convenience to the two of <br>
                them. <br>
                <br>
                But from any real perspective of active development of
                the platform, <br>
                Mono is dead". <br>
                <br>
                ... <br>
                <br>
                This doesn't square at all for me with the near-monthly
                releases I've <br>
                been seeing with functional enhancements I've been
                needing, such as ARM <br>
                hardfp (great work, thanks). <br>
                <br>
                Would anybody care to comment on whether there's a
                kernel of truth here <br>
                or what the roadmap for Mono development currently is? <br>
                <br>
                Thanks, <br>
                <br>
                Alex <o:p></o:p></p>
            </blockquote>
            <p class="MsoNormal" style="margin-bottom:12.0pt"><br>
              <br>
              _______________________________________________ <br>
              Mono-devel-list mailing list <br>
              <a moz-do-not-send="true"
                href="mailto:Mono-devel-list@lists.ximian.com">Mono-devel-list@lists.ximian.com</a>
              <br>
              <a moz-do-not-send="true"
                href="http://lists.ximian.com/mailman/listinfo/mono-devel-list">http://lists.ximian.com/mailman/listinfo/mono-devel-list</a>
              <br>
              <br>
              <o:p></o:p></p>
          </blockquote>
          <p class="MsoNormal"><o:p> </o:p></p>
          <div>
            <p class="MsoNormal">-- <o:p></o:p></p>
            <div>
              <p style="line-height:9.0pt"><span
style="font-size:7.5pt;font-family:"Helvetica","sans-serif""><a
                    moz-do-not-send="true"
                    href="http://www.dynamicdevices.co.uk/"><span
                      style="text-decoration:none"><img id="sig-logo"
                        src="cid:part4.02020206.08030508@dynamicdevices.co.uk"
                        alt="Dynamic Devices Ltd" width="108" border="0"
                        height="61"></span></a><o:p></o:p></span></p>
              <p style="line-height:9.0pt"><span class="txt"><b><span
style="font-size:7.5pt;font-family:"Helvetica","sans-serif";color:#999999">Alex
                      J Lennon</span></b></span><span
style="font-size:7.5pt;font-family:"Helvetica","sans-serif";color:#999999">
                  / <span class="txt">Director</span><br>
                  <span class="txt">1 Queensway, Liverpool L22 4RA</span>
                  <o:p></o:p></span></p>
              <p style="margin-bottom:12.0pt;line-height:9.0pt"><span
                  class="txt"><span
style="font-size:7.5pt;font-family:"Helvetica","sans-serif";color:#999999">mobile:
                    +44 (0)7956 668178</span></span><span
style="font-size:7.5pt;font-family:"Helvetica","sans-serif"">
                  <o:p></o:p></span></p>
              <p style="line-height:9.0pt"><span
style="font-size:7.5pt;font-family:"Helvetica","sans-serif""><a
                    moz-do-not-send="true"
                    href="http://www.linkedin.com/in/alexjlennon"
                    id="linkedin-input"><span
                      style="text-decoration:none"><img
                        id="_x0000_i1026"
                        src="cid:part6.01060106.00060800@dynamicdevices.co.uk"
                        alt="Linkedin" width="16" border="0" height="16"></span></a><a
                    moz-do-not-send="true" href="skype:alexjlennon?add"
                    id="skype-input"><span style="text-decoration:none"><img
                        id="_x0000_i1027"
                        src="cid:part8.07020304.00020503@dynamicdevices.co.uk"
                        alt="Skype" width="16" border="0" height="16"></span></a><o:p></o:p></span></p>
              <p class="txt1" style="line-height:9.0pt"
                id="disclaimer-input"><span
style="font-size:7.0pt;font-family:"Helvetica","sans-serif";color:#999999">This
                  e-mail message may contain confidential or legally
                  privileged information and is intended only for the
                  use of the intended recipient(s). Any unauthorized
                  disclosure, dissemination, distribution, copying or
                  the taking of any action in reliance on the
                  information herein is prohibited. E-mails are not
                  secure and cannot be guaranteed to be error free as
                  they can be intercepted, amended, or contain viruses.
                  Anyone who communicates with us by e-mail is deemed to
                  have accepted these risks. Company Name is not
                  responsible for errors or omissions in this message
                  and denies any responsibility for any damage arising
                  from the use of e-mail. Any opinion and other
                  statement contained in this message and any attachment
                  are solely those of the author and do not necessarily
                  represent those of the company.<o:p></o:p></span></p>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <div class="preview">
        <p style="font-family: Helvetica, Arial, sans-serif; font-size:
          10px; line-height: 12px;"><a
            href="http://www.dynamicdevices.co.uk/" class="clink"><img
              src="cid:part10.03090806.06030100@dynamicdevices.co.uk"
              alt="Dynamic Devices Ltd" id="sig-logo" border="0"></a></p>
        <p style="font-family: Helvetica, Arial, sans-serif; font-size:
          10px; line-height: 12px; color: rgb(153, 153, 153);"><span
            id="name-input" style="font-weight: bold;" class="txt">Alex
            J Lennon</span> <span id="title-sep">/</span> <span
            id="title-input" style="color: #999;" class="txt">Director</span><br>
          <span id="address-input" style="color: #999;" class="txt">1
            Queensway, Liverpool L22 4RA</span> </p>
        <p style="font-family: Helvetica, Arial, sans-serif; font-size:
          10px; line-height: 12px;"> <span id="mobile-input"
            style="color: #999;" class="txt">mobile: +44 (0)7956 668178</span>
          <br>
          <br>
        </p>
        <p style="font-size: 10px; line-height: 12px; font-family:
          Helvetica, Arial, sans-serif"> <a id="linkedin-input"
            class="social" href="http://www.linkedin.com/in/alexjlennon"><img
              src="cid:part12.01070507.09080807@dynamicdevices.co.uk"
              alt="Linkedin"></a> <a id="skype-input" class="social"
            href="skype:alexjlennon?add"><img
              src="cid:part14.07040509.05060704@dynamicdevices.co.uk"
              alt="Skype"></a></p>
        <p id="disclaimer-input" style="font-family: Helvetica, Arial,
          sans-serif; color: rgb(153, 153, 153); font-size: 9px;
          line-height: 12px;width: 25%" class="txt">This e-mail message
          may contain confidential or legally privileged information and
          is intended only for the use of the intended recipient(s). Any
          unauthorized disclosure, dissemination, distribution, copying
          or the taking of any action in reliance on the information
          herein is prohibited. E-mails are not secure and cannot be
          guaranteed to be error free as they can be intercepted,
          amended, or contain viruses. Anyone who communicates with us
          by e-mail is deemed to have accepted these risks. Company Name
          is not responsible for errors or omissions in this message and
          denies any responsibility for any damage arising from the use
          of e-mail. Any opinion and other statement contained in this
          message and any attachment are solely those of the author and
          do not necessarily represent those of the company.</p>
      </div>
    </div>
  </body>
</html>