commit 0a3a035cc794a63af63c86c0c68decfdb2d808f2
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Mon Aug 8 13:58:58 2022 -0400

    Updates

diff --git a/future.md b/future.md
index de0263c..a55c874 100644
--- a/future.md
+++ b/future.md
@@ -1,6 +1,9 @@
-# Future Work Writing Guidelines
+---
+pagetitle: Writing the Future Work
+version: 1.3
+---
 
-v1.2
+# Writing the Future Work
 
 The Future Work sections has continuing work that a project
 immediately following yours would undertake.

commit d4128661ee0785908dc7548a8b4ee9b53509e7fe
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Tue Feb 25 06:22:58 2020 -0500

    Updates

diff --git a/future.md b/future.md
index 3fa9e56..de0263c 100644
--- a/future.md
+++ b/future.md
@@ -1,6 +1,6 @@
 # Future Work Writing Guidelines
 
-v1.1
+v1.2
 
 The Future Work sections has continuing work that a project
 immediately following yours would undertake.
@@ -18,6 +18,9 @@ you started.
 goals of the project space, but is probably beyond the scope of even
 another whole project.
 
+You do not necessarily need to break them up by tiers, but you can
+certainly think of them that way.
+
 For most reports, the Future Work chapter would include a half-dozen
 such items total.
 

commit adb9bdbbda09e0c5d86f168072609acd2a2236dd
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Wed Feb 27 00:02:38 2019 -0500

    Updates

diff --git a/future.md b/future.md
index 1c0088e..3fa9e56 100644
--- a/future.md
+++ b/future.md
@@ -1,6 +1,6 @@
 # Future Work Writing Guidelines
 
-v1.0
+v1.1
 
 The Future Work sections has continuing work that a project
 immediately following yours would undertake.
@@ -18,15 +18,15 @@ you started.
 goals of the project space, but is probably beyond the scope of even
 another whole project.
 
-For most report, the future work chapter would include a half-dozen
+For most reports, the Future Work chapter would include a half-dozen
 such items total.
 
-For each future work idea above, write a short paragraph providing a
-few details on what the work entails.  A general "formula" for this
+For each future idea above, write a short paragraph providing a few
+details on what the work entails.  A general "formula" for this
 paragraph that works well is:
 
 1. Open with the future work item itself.  e.g., "Future work includes
-   doing *XYZ*..."
+doing *XYZ*..."
 
 2. Say *why* that item is interesting.  e.g., "Doing *XYZ* would
 allow someone to do or know *ABC* ..."
@@ -35,3 +35,8 @@ allow someone to do or know *ABC* ..."
 item yourself, should you have to do so.  This is typically brief,
 just a quick sentence or two.
 
+Overall, the future work should *not* make it look like the best and
+most interesting parts of the work are yet to come - the project
+itself should be viewed as cool and significant (e.g., in the
+Conclusion chapter).
+

commit e5cfe6bf704f9f36d0c26fae9e94d6228e50907b
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Tue Feb 26 12:53:28 2019 -0500

    Updates

diff --git a/future.md b/future.md
new file mode 100644
index 0000000..1c0088e
--- /dev/null
+++ b/future.md
@@ -0,0 +1,37 @@
+# Future Work Writing Guidelines
+
+v1.0
+
+The Future Work sections has continuing work that a project
+immediately following yours would undertake.
+
+Generally, include a few (2-3) topics along three different tiers:
+
++ *Short term* - immediate parts of the work that would be started, such
+as continuing with development or analysis that was not quite
+completed.
+
++ *Medium term* - work over a few months that continues the project work
+you started.
+
++ *Long term* - more extensive work that fits in with the overall
+goals of the project space, but is probably beyond the scope of even
+another whole project.
+
+For most report, the future work chapter would include a half-dozen
+such items total.
+
+For each future work idea above, write a short paragraph providing a
+few details on what the work entails.  A general "formula" for this
+paragraph that works well is:
+
+1. Open with the future work item itself.  e.g., "Future work includes
+   doing *XYZ*..."
+
+2. Say *why* that item is interesting.  e.g., "Doing *XYZ* would
+allow someone to do or know *ABC* ..."
+
+3. Briefly sketch out how you would go about tackling this future work
+item yourself, should you have to do so.  This is typically brief,
+just a quick sentence or two.
+