<HTML>
<HEAD>
<TITLE>Re: [I-mobile-u] Documentation for Mobile Web Project</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Dave,<BR>
<BR>
Thanks for your questions and thoughts.<BR>
<BR>
The MIT Mobile projects (mobile web, SMS, native applications – prototype for iPhone only for now) are currently using SVN. We plan on setting up the SVN on SourceForge (hopefully in the next two weeks) after we had a chance to play with the structure of the 2.0 code. We are leaning towards creating separate branches for each school that’s participating. The intent would be to create a shared SVN space without introducing the complexity of managing contributors. <BR>
<BR>
I see this as a 3 phase process:<BR>
Phase 1 (today): Distribute the source code as is (we hope to have the 2.0 ready for SourceForge by early next week)<BR>
Phase 2 (mid-November): Set up SVN with the revised 2.0 code base and allow for each school to set up its own branch. This should allow everyone to provide contributions within their own environment. Whoever is interested in grabbing the specific functionality can do so from these branches.<BR>
Phase 3 (2010): Set up a Generic/Common branch or a new SVN that works as for a “generic” mobile web site. <BR>
<BR>
I welcome any suggestions, but I thought this would allow us to proceed with minimal “administrativia” during the first 2 phases. It will also allow all of us to see what each school is doing individually as well as being able to access their contributions directly from the SVN branch that they are responsible for maintaining.<BR>
<BR>
Cheers,<BR>
<BR>
Andrew<BR>
<BR>
On 10/30/09 2:46 PM, "Dave Olsen" <<a href="dmolsen@gmail.com">dmolsen@gmail.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Is there a version control system that people feel comfortable with?<BR>
I'm most familiar with Subversion and Git. Downloading a zip file<BR>
isn't exactly the most sustainable way to either deliver code or<BR>
accept changes back.<BR>
<BR>
In a similar vein, one of the things I played around with is trying to<BR>
have each part of the site be essentially a standalone module. Maybe<BR>
finding a standard that people feel comfortable with would make it<BR>
easier to expand the Mobile Web project. I don't know how much work it<BR>
would be in the v2 environment of MIT Mobile Web but it wasn't<BR>
terribly difficult to set-up in the v0.9.<BR>
<BR>
<BR>
--<BR>
<BR>
Proud supporter of DC United<BR>
_______________________________________________<BR>
I-mobile-u mailing list<BR>
<a href="I-mobile-u@mit.edu">I-mobile-u@mit.edu</a><BR>
<a href="http://mailman.mit.edu/mailman/listinfo/i-mobile-u">http://mailman.mit.edu/mailman/listinfo/i-mobile-u</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
________________________________<BR>
Andrew Yu<BR>
Mobile Platform Manager & Architect<BR>
Information Services & Technology<BR>
Massachusetts Institute of Technology<BR>
Phone: 617-324-8985<BR>
Email: <a href="andrewyu@mit.edu">andrewyu@mit.edu</a><BR>
<BR>
*** MIT Mobile Web and MIT SMS (beta) ***<BR>
Visit <a href="http://m.mit.edu">http://m.mit.edu</a> from your mobile device, or<BR>
Text "help" to 648338<BR>
</SPAN></FONT>
</BODY>
</HTML>