From 1c54e4dd07a46badfb95b207134af8babd8fbc49 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Sat, 1 Jan 2005 03:28:16 +0000 Subject: [PATCH] Discourage combining student contributions late. Talk about SourceForge. --- EXPERIENCE | 4 ---- doc/devel.texi | 12 ++++++++++++ doc/threads.texi | 18 ++++++++++++++++++ 3 files changed, 30 insertions(+), 4 deletions(-) diff --git a/EXPERIENCE b/EXPERIENCE index dd5b665..76231d1 100644 --- a/EXPERIENCE +++ b/EXPERIENCE @@ -2,10 +2,6 @@ General: - - Lots of groups only tried combining the 3 group members' parts - only in the last few hours. Emphasize that this is a bad choice. - Encourage them to use CVS/sourceforge/etc. - - Suggest where to start in each assignment? - Provide more tests! diff --git a/doc/devel.texi b/doc/devel.texi index 20af12f..86c47f4 100644 --- a/doc/devel.texi +++ b/doc/devel.texi @@ -6,6 +6,7 @@ Here are some tools that you might find useful while developing code. @menu * Tags:: * CVS:: +* SourceForge:: * VNC:: @end menu @@ -45,6 +46,17 @@ the projects. For more information, visit the @uref{https://www.cvshome.org/, , CVS home page}. +@node SourceForge +@section SourceForge + +SourceForge is a web-based system for facilitating software +development. It provides you with a version-control system (typically +CVS, as described above) and other tools for tracking your software. +You can use it to store files, track bugs, and post notes about +development progress. It's also free. You can set up your own +project in SourceForge at @uref{http://sourceforge.net, , +sourceforge.net}. + @node VNC @section VNC diff --git a/doc/threads.texi b/doc/threads.texi index eb59d8a..8e6e38d 100644 --- a/doc/threads.texi +++ b/doc/threads.texi @@ -383,6 +383,24 @@ Problems 1-3 and 1-4 won't be needed for later projects. Problem 1-4 (MLFQS) builds on the features you implement in Problem 1-3. You should have Problem 1-3 fully working before you begin to tackle Problem 1-4. + +@item +In the past, many groups divided the assignment into pieces, then each +group member worked on his or her piece until just before the +deadline, at which time the group reconvened to combine their code and +submit. @strong{This is a bad idea. We do not recommend this +approach.} Groups that do this often find that two changes conflict +with each other, requiring lots of last-minute debugging. Some groups +who have done this have turned in code that did not even successfully +boot. + +Instead, we recommend integrating your team's changes early and often, +using a source code control system such as CVS (@pxref{CVS}) or a +group collaboration site such as SourceForge (@pxref{SourceForge}). +This is less likely to produce surprises, because everyone can see +everyone else's code as it is written, instead of just when it is +finished. These systems also make it possible to review changes and, +when a change introduces a bug, drop back to working versions of code. @end itemize @node Problem 1-1 Alarm Clock -- 2.30.2