Skip to content

Commit 375216f

Browse files
committed
Merge copilot/sub-pr-175: resolve conflicts, move hybrid meeting info to margin note
- Merge PR #176 from copilot/sub-pr-175 - Resolve conflict in lab meetings section - Move hybrid meeting info to margin note for consistency with document style - Remove duplicate hybrid meeting info from intro paragraph - Recompile PDF
2 parents 7ce3562 + fb15313 commit 375216f

2 files changed

Lines changed: 22 additions & 10 deletions

File tree

lab_manual.pdf

479 Bytes
Binary file not shown.

lab_manual.tex

Lines changed: 22 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -732,19 +732,31 @@ \subsection{Authorship guidelines}
732732
\noindent Effective lab communication requires forums for communicating. We use \href{http://www.slack.com}{Slack} to
733733
facilitate remote communications, and encourage
734734
in-person interactions as often as possible---ideally several times a
735-
week for group projects. All of our meetings are hybrid: you can attend in person in Moore 416 or via Zoom. The Zoom link is posted in the \texttt{\#general} Slack channel at the start of each term and is used for all lab Zoom meetings unless otherwise noted. We have the following regularly scheduled
735+
week for group projects. We have the following regularly scheduled
736736
meetings:
737737

738+
\marginnote{\texttt{NOTE:} All lab meetings are hybrid: in person in
739+
Moore 416 or on Zoom. A Zoom link is provided in the \texttt{\#general}
740+
Slack channel at the start of each term, to be used for all lab Zoom
741+
meetings unless otherwise noted.}
742+
738743
\begin{itemize}
739-
\item \textbf{Lab meetings.} We hold weekly lab meetings. During the first week of each term,
740-
we schedule meeting times via a When2Meet poll shared on Slack. Once finalized,
741-
the schedule is posted and pinned to the \texttt{\#general} channel. If you are an active
742-
lab member, you are expected to attend our lab meetings unless you
743-
let \director~know that you have a conflict (e.g., a course that meets
744-
at the same time, another commitment that comes up, etc.). Prioritizing lab meeting attendance helps build
745-
and maintain a lab culture of collaboration and ongoing participation.
746-
747-
During lab meetings, we typically focus on things that project teams want input on beyond their immediate group. We also use lab meetings to discuss logistics, give feedback on upcoming talks or poster presentations, and share project updates that might be of interest beyond one project team. Generally we spend most of the time going around the room and having each person give a brief informal update about something they are working on, planning to work on, or thinking about.
744+
\item \textbf{Lab meetings.} We hold weekly lab meetings.
745+
During the first week of each term, we schedule meeting times via a When2Meet poll
746+
shared on Slack. Once finalized, the schedule is posted and pinned to the
747+
\texttt{\#general} channel. If you are an active lab member, you are expected to
748+
attend our lab meetings unless you let \director~know that you have a conflict
749+
(e.g., a course that meets at the same time, another commitment that comes up,
750+
etc.). Prioritizing lab meeting attendance helps build and maintain a lab culture
751+
of collaboration and ongoing participation.
752+
753+
During lab meetings we typically focus on things that project teams want input
754+
on beyond their immediate group. We also use lab meetings to discuss logistics,
755+
give feedback on upcoming talks or poster presentations, and/or share project
756+
updates that might be of interest beyond one project team. Generally we spend
757+
most of the time going around the room and having each person give a brief
758+
informal update about something they are working on, planning to work on, or
759+
thinking about.
748760

749761

750762

0 commit comments

Comments
 (0)