commit 1354f2b9a07ed0187451992314b542ae86e61379 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Wed Dec 14 10:53:39 2022 -0500 Updates diff --git a/group-writing.md b/group-writing.md index e705483..dcf05f5 100644 --- a/group-writing.md +++ b/group-writing.md @@ -26,11 +26,13 @@ section of writing written by a teammate, be objective and not hyper-critical. A "complete" chapter has: + - All content in place. - Everyone has edited (shared ownership, unified voice). - Professionally written. When complete: + - Make sure format is 11pt or 12pt font - Make spacing 1.5 or double spaced to allow room to make comments - Provide version number in filename (e.g,. `background-v1.pdf`) commit f3b0ded6d9f5e0a4f605e6236bae89e6bcb62244 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Wed Dec 14 10:13:05 2022 -0500 Updates diff --git a/group-writing.md b/group-writing.md index f3cc8b2..e705483 100644 --- a/group-writing.md +++ b/group-writing.md @@ -1,20 +1,23 @@ --- pagetitle: Group Writing -version: 1.2 +version: 1.3 --- # Group Writing -+ Work in section-sized chunks or even chapter-sized chunks. A - chapter is a good sized chunk to deliver to your advisor, too, for - feedback. +Work in section-sized chunks or even chapter-sized chunks. A +chapter is a good sized chunk to deliver to your advisor, too, for +feedback. -+ You can divide up writing as best fits the team. Authorship does - not need to be noted. +Outline every section/chapter before writing it. Go over the outline +as a group to get con census on the outline. (See outlining one pager) -+ Regardless of who wrote first (or second) drafts, *everyone* edits - the report. This provides shared ownership of the writing and gives - it a unified "voice". +You can divide up writing as best fits the team. Authorship does +not need to be noted. + +Regardless of who wrote first (or second) drafts, *everyone* edits +the report. This provides shared ownership of the writing and gives +it a unified "voice". *Important:* keep your ego out of writing and editing. Know that if a team-mate provides criticism and corrects prose, they do it to improve @@ -22,15 +25,15 @@ the work. Similarly, if you provide criticism/corrections to a section of writing written by a teammate, be objective and not hyper-critical. -+ A "complete" chapter has: - - All content in place. - - Everyone has edited (shared ownership, unified voice). - - Professionally written. +A "complete" chapter has: +- All content in place. +- Everyone has edited (shared ownership, unified voice). +- Professionally written. -+ When complete: - - Make sure format is 11pt or 12pt font - - Make spacing 1.5 or double spaced to allow room to make comments - - Provide version number in filename (e.g,. `background-v1.pdf`) - - Format as PDF +When complete: +- Make sure format is 11pt or 12pt font +- Make spacing 1.5 or double spaced to allow room to make comments +- Provide version number in filename (e.g,. `background-v1.pdf`) +- Format as PDF Then, send me an email with the chapters as an email attachment. commit 9b7330c5f435a7c28724e2d93a9143c76a9beb91 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Mon Aug 15 07:17:55 2022 -0400 Updates diff --git a/group-writing.md b/group-writing.md index 2da3a5c..f3cc8b2 100644 --- a/group-writing.md +++ b/group-writing.md @@ -16,11 +16,11 @@ version: 1.2 the report. This provides shared ownership of the writing and gives it a unified "voice". - *Important:* keep your ego out of writing and editing. Know that if - a team-mate provides criticism and corrects prose, s/he does it to - improve the work. Similarly, if you provide criticism/corrections - to a section of writing written by a teammate, be objective and not - hyper-critical. +*Important:* keep your ego out of writing and editing. Know that if a +team-mate provides criticism and corrects prose, they do it to improve +the work. Similarly, if you provide criticism/corrections to a +section of writing written by a teammate, be objective and not +hyper-critical. + A "complete" chapter has: - All content in place. @@ -32,4 +32,5 @@ version: 1.2 - Make spacing 1.5 or double spaced to allow room to make comments - Provide version number in filename (e.g,. `background-v1.pdf`) - Format as PDF - - Send as email attachment + +Then, send me an email with the chapters as an email attachment. commit a262d8201a5895c7251c935b937c58e2506228c5 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Tue Aug 9 09:17:35 2022 -0400 Updates diff --git a/group-writing.md b/group-writing.md index ee465e2..2da3a5c 100644 --- a/group-writing.md +++ b/group-writing.md @@ -30,6 +30,6 @@ version: 1.2 + When complete: - Make sure format is 11pt or 12pt font - Make spacing 1.5 or double spaced to allow room to make comments - - Provide version number in filename (e.g,. background-v1.pdf) + - Provide version number in filename (e.g,. `background-v1.pdf`) - Format as PDF - Send as email attachment commit 0a3a035cc794a63af63c86c0c68decfdb2d808f2 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Mon Aug 8 13:58:58 2022 -0400 Updates diff --git a/group-writing.md b/group-writing.md index 6ab33c0..ee465e2 100644 --- a/group-writing.md +++ b/group-writing.md @@ -1,5 +1,9 @@ -# MQP Group Writing Guidelines -v1.1 +--- +pagetitle: Group Writing +version: 1.2 +--- + +# Group Writing + Work in section-sized chunks or even chapter-sized chunks. A chapter is a good sized chunk to deliver to your advisor, too, for commit 385f82b8934327afa719a97fb9e7900893906afc Author: Mark Claypool <claypool@cs.wpi.edu> Date: Wed Sep 25 14:28:05 2019 -0400 Updates diff --git a/group-writing.md b/group-writing.md index 5fac0d6..6ab33c0 100644 --- a/group-writing.md +++ b/group-writing.md @@ -1,9 +1,9 @@ # MQP Group Writing Guidelines -v1.0 +v1.1 + Work in section-sized chunks or even chapter-sized chunks. A -chapter is a good sized chunk to deliver to your advisor, too, for -feedback. + chapter is a good sized chunk to deliver to your advisor, too, for + feedback. + You can divide up writing as best fits the team. Authorship does not need to be noted. @@ -19,13 +19,13 @@ feedback. hyper-critical. + A "complete" chapter has: - - All content in place. - - Everyone has edited (shared ownership, unified voice). - - Professionally written. + - All content in place. + - Everyone has edited (shared ownership, unified voice). + - Professionally written. + When complete: - - Make sure format is 11pt or 12pt font - - Make spacing 1.5 or double spaced to allow room to make comments - - Format as PDF - - Provide version number in filename (e.g,. background-v1.pdf) - - Send as email attachment + - Make sure format is 11pt or 12pt font + - Make spacing 1.5 or double spaced to allow room to make comments + - Provide version number in filename (e.g,. background-v1.pdf) + - Format as PDF + - Send as email attachment commit ca7404caee84b3ca8f6f1f8c8a78765f9be05418 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Sun Feb 25 19:54:24 2018 -0500 Added presentations diff --git a/group-writing.md b/group-writing.md new file mode 100644 index 0000000..5fac0d6 --- /dev/null +++ b/group-writing.md @@ -0,0 +1,31 @@ +# MQP Group Writing Guidelines +v1.0 + ++ Work in section-sized chunks or even chapter-sized chunks. A +chapter is a good sized chunk to deliver to your advisor, too, for +feedback. + ++ You can divide up writing as best fits the team. Authorship does + not need to be noted. + ++ Regardless of who wrote first (or second) drafts, *everyone* edits + the report. This provides shared ownership of the writing and gives + it a unified "voice". + + *Important:* keep your ego out of writing and editing. Know that if + a team-mate provides criticism and corrects prose, s/he does it to + improve the work. Similarly, if you provide criticism/corrections + to a section of writing written by a teammate, be objective and not + hyper-critical. + ++ A "complete" chapter has: + - All content in place. + - Everyone has edited (shared ownership, unified voice). + - Professionally written. + ++ When complete: + - Make sure format is 11pt or 12pt font + - Make spacing 1.5 or double spaced to allow room to make comments + - Format as PDF + - Provide version number in filename (e.g,. background-v1.pdf) + - Send as email attachment