<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Yes, MIT would prefer to remain the canonical framework. Our goal is to build the MIT Mobile Framework into something any school can use with ease.</div><div><br></div><div>We are eager to review and accept any patches you may have. MIT is very interested in Modo's templating work (/future) and intends to incorporate that once it is further along. We also plan to incorporate even the parts of the Harvard code which MIT does not itself use, such as TransLoc and FoodPro support, because other users of the framework may find them useful.</div><div><br><div apple-content-edited="true">Justin<br></div></div><div><br></div><div><div>On Oct 26, 2010, at 11:55 AM, David Ormsbee wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi folks,<div><br></div><div>I'm sorry to add more confusion to the situation. Let me start by saying that Harvard's /future code is not ready for immediate adoption. It's still a work in progress, the structure might shift around, and we've only just started doing QA work on it. I wanted to let people know it existed to add to the general discussion on where we all want this framework to go. I also wanted to do the development out in the open and show everyone exactly what our folks have been hard at work on.</div>
<div><br></div><div>Modo still considers the MIT repo to be the canonical one, and we hope to get our changes merged back upstream when it's stable. There are a few features that exist in the stable Harvard repo (not /future) that aren't present in the MIT version -- cross-module search, dining (using a CSV export from FoodPro), and TransLoc support for shuttles. If those are of interest, you may want to fork Harvard. Otherwise, I encourage people to fork MIT as a general rule.</div>
<div><br></div><div>Thank you.</div><div><br></div><div>Dave<br><br><div class="gmail_quote">On Tue, Oct 26, 2010 at 11:39 AM, Dave Olsen <span dir="ltr"><<a href="mailto:dmolsen@gmail.com">dmolsen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I had the same question. Is there a canonical version of the framework? It's sort of bad enough that I've already gone off on a fork (and I'm well aware that's annoying) but seeing what could be four versions a user could now choose from... Just curious if there's a preference going forward among the options released last week.<br>
<br>
Sent from my iPhone<br>
<div><div></div><div class="h5"><br>
On Oct 26, 2010, at 11:02 AM, Derek Morr <<a href="mailto:derekmorr@psu.edu">derekmorr@psu.edu</a>> wrote:<br>
<br>
> Thank, David.<br>
><br>
> We're still running the WVU 0.9 fork, but are looking to upgrade. Would<br>
> you recommend deploying the 2.2.7 branch, or the Harvard branch? Is<br>
> there a list of differences between the 2.2.7 and Harvard branches? If<br>
> want to send patches, should we generate the diffs against 2.2.7,<br>
> Harvard, or the /future tree in the Harvard branch?<br>
><br>
> -derek<br>
><br>
> --<br>
> Derek Morr<br>
> Senior Systems Programmer<br>
> Emerging Technologies, Information Technology Services<br>
> The Pennsylvania State University<br>
> <a href="mailto:derekmorr@psu.edu">derekmorr@psu.edu</a><br>
><br>
> This email was sent (at least in part) over IPv6.<br>
> _______________________________________________<br>
> I-mobile-u mailing list<br>
> <a href="mailto:I-mobile-u@mit.edu">I-mobile-u@mit.edu</a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/i-mobile-u" target="_blank">http://mailman.mit.edu/mailman/listinfo/i-mobile-u</a><br>
<br>
<br>
_______________________________________________<br>
I-mobile-u mailing list<br>
<a href="mailto:I-mobile-u@mit.edu">I-mobile-u@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/i-mobile-u" target="_blank">http://mailman.mit.edu/mailman/listinfo/i-mobile-u</a><br>
</div></div></blockquote></div><br></div>
<span><ATT00001..c></span></blockquote></div><br></body></html>