From 54b1e1835a320103baec57a3d9d2805084adb9bc Mon Sep 17 00:00:00 2001
From: "Peter J. Keleher" <keleher@cs.umd.edu>
Date: Tue, 21 Sep 2021 08:46:22 -0400
Subject: [PATCH] auto

---
 groupProject/README.md | 42 +++++++++++++++++++++---------------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/groupProject/README.md b/groupProject/README.md
index 26bc773..6d0fca4 100644
--- a/groupProject/README.md
+++ b/groupProject/README.md
@@ -70,27 +70,6 @@ in class**. The ARKit and machine learning libraries are expansive
 enough that I encourage you to build on what we discuss in
 class, if we get there. FireBase may or may be considered novel, depending on how you are using it.
 
-## Artifacts to be turned in
-1. **Due 10/7**: 1-2-page PDF document with/
-   - Project Name
-   - Group Name
-   - Group Members (names)
-   - Minimal product goals  (1 paragraph)
-   - Stretch goals  (1 paragraph)
-   - Projected timeline, w/ milestones and assignment of work to group members.
-   - Sample [here](sampleSemesterProjectWeek1.pdf)
-1. [Weekly updates](sampleSemesterProjectWeekly.pdf) of current progress will be submitted
-   each Sunday night starting by midnight 4/12, possibly via Google Forms. Exact format of this will be
-   defined once we find out how many groups we have.
-1. **What to Turn in  12/1**: Final project, including video, due.
-- write a five-ten page report describing the evolution of your ideas,
-  the process you went through to end up at the final app, and of
-  course the app project itself.
-- A five-minute screen-capture video (with audio desribing the
-  app's features). I will choose among these for the last full week of
-  classes. Each such team gets a 10% bonus.
-- Turn in the app. It must compile and work as in the video/presentation.
-
 # Project Ideas
 
 These are ideas, you can either choose one of them to build on, or define your
@@ -121,6 +100,27 @@ before proceeding.
     online information and links for those recognized objects.
 1. Something else.
 
+## Artifacts to be turned in
+1. **Due 10/7**: 1-2-page PDF document with/
+   - Project Name
+   - Group Name
+   - Group Members (names)
+   - Minimal product goals  (1 paragraph)
+   - Stretch goals  (1 paragraph)
+   - Projected timeline, w/ milestones and assignment of work to group members.
+   - Sample [here](sampleSemesterProjectWeek1.pdf)
+1. [Weekly updates](sampleSemesterProjectWeekly.pdf) of current progress will be submitted
+   each Sunday night starting by midnight 4/12, possibly via Google Forms. Exact format of this will be
+   defined once we find out how many groups we have.
+1. **What to Turn in  12/1**: Final project, including video, due.
+- write a five-ten page report describing the evolution of your ideas,
+  the process you went through to end up at the final app, and of
+  course the app project itself.
+- A five-minute screen-capture video (with audio desribing the
+  app's features). I will choose among these for the last full week of
+  classes. Each such team gets a 10% bonus.
+- Turn in the app. It must compile and work as in the video/presentation.
+
 ## Grading
 
 You grade for this project will be composed of:
-- 
GitLab