Project 2: Panel Activity
Key dates
| What | When |
|---|---|
| Summary proposal due | 2026-10-23, 9:00 a.m. |
| Panel recordings (Tuesday and Thursday class suspended) | sign up for 2026-10-27, 28 or 29 |
| Feedback released | 2026-11-03 |
| Revised proposal due | 2026-11-10 |
Overview
You’ll take part in a recorded panel of three students. Each panelist brings their own topic: a public issue you care about, which you will carry forward into Project 3.
Project 1 asked you to analyze language on the page. Project 2 asks you to do it live, in unscripted talk, including your own.
How it works
- Panels are recorded privately on Tuesday 2026-10-27 and Thursday 2026-10-29 (9:00 to 11:15 a.m. both days), and Wednesday 2026-10-28 (9:00 a.m. to 12:00 p.m.). Each panel is 25 minutes, with 10 minutes between panels. Only the three panelists and I are in the room. (So classes are essentially cancelled for the week.)
- Each panel runs 25 minutes: 5 minutes of questions from me to each panelist (15 minutes), then 10 minutes of open discussion among all four of us.
- Recordings are posted to a private TRU Media site for your review.
Part 1: Summary proposal (before the panel)
Write a short proposal for the topic you’ll bring to the panel and continue in Project 3. It should:
- Name the public issue and the text(s) or discourse you’ll be looking at
- Name the course concepts (SFL and/or CDA) you expect to apply, and why they fit
- Say what you want to find out, or argue, in Project 3
Length: 250 words
We’ll draft these in the 2026-10-20 workshop and swap feedback in panel trios. They will be submitted on 2026-10-23 to Chris and your co-panelists.
Part 2: The panel
During the panel, you must:
- Name at least one course concept and apply it to something actually said in the panel, by you or by a co-panelist
- Engage at least once with a co-panelist’s contribution, using conceptual language
As in Project 1, naming a concept is not analysis. “That’s modality” earns nothing on its own. Saying what the modality in your co-panelist’s claim does, and who it positions how, does.
Part 3: Revising your proposal
After I release feedback on 2026-11-03, revise your summary proposal using my feedback on your panel contribution. Submit your revised proposal through the same Moodle link by 2026-11-10.
Complete / Redo
This project is graded Complete or Redo, consistent with the course’s ungrading approach.
Complete requires:
- Summary proposal submitted before the panel
- At least one course concept named and applied to something actually said in the panel
- At least one engagement with a co-panelist’s contribution using conceptual language
- Proposal revised in response to my feedback
- Written in your own words except where quoting relevant texts
Redo is assigned when:
- No concept is applied to something actually said, or concepts are named but not applied, or
- There is no engagement with a co-panelist’s contribution, or
- The revised proposal doesn’t show use of the feedback
A Redo means revising your summary proposal again, based on my feedback on your panel contribution. You do not re-record the panel.
If your revised proposal is still marked Redo when Project 3 is due (2026-11-27), you don’t submit another revision. Instead, your Project 3 annotation must show how you addressed the outstanding feedback, and I’ll make the Project 2 call from that.
Borderline work is marked Redo, with feedback on what to change.
Redo attempts for this project are unlimited (though you will need to get on with Project 3 at some point!)
Submission
- Summary proposal: PDF, uploaded to Moodle under Project 2 and emailed to your two co-panelists, by 2026-10-23 at 9:00 a.m. Exchange email addresses with your co-panelists before then.
- Revised proposal: PDF, same Moodle link, by 2026-11-10.