% This file was created by tufte_periodical_2.xsl, which is licensed under the Apache License 2.0.

\documentclass[twoside,symmetric,justified]{tufte-handout} % Also supports option a4paper.

% https://tex.stackexchange.com/questions/202142/problems-compiling-tufte-title-page-in-xelatex
\usepackage{ifxetex}
\ifxetex
  \newcommand{\textls}[2][5]{%
    \begingroup\addfontfeatures{LetterSpace=#1}#2\endgroup
  }
  \renewcommand{\allcapsspacing}[1]{\textls[15]{#1}}
  \renewcommand{\smallcapsspacing}[1]{\textls[10]{#1}}
  \renewcommand{\allcaps}[1]{\textls[15]{\MakeTextUppercase{#1}}}
  \renewcommand{\smallcaps}[1]{\smallcapsspacing{\scshape\MakeTextLowercase{#1}}}
  \renewcommand{\textsc}[1]{\smallcapsspacing{\textsmallcaps{#1}}}
  \usepackage{fontspec}
\fi

\usepackage{fontspec}
\setmainfont{ETBembo}

\title{Monthly Wrap}
%\author[]{}
\date{}

%\geometry{showframe} % display margins for debugging page layout

\usepackage{graphicx} % allow embedded images
  \setkeys{Gin}{width=\linewidth,totalheight=\textheight,keepaspectratio}
  \graphicspath{{graphics/}} % set of paths to search for images
\usepackage{amsmath}  % extended mathematics
\usepackage{booktabs} % book-quality tables
\usepackage{units}    % non-stacked fractions and better unit spacing
\usepackage{multicol} % multiple column layout facilities
\usepackage{fancyvrb} % extended verbatim environments
  \fvset{fontsize=\normalsize} % default font size for fancy-verbatim environments
\usepackage{xurl} % hard-wrap URLs in the side margins
\usepackage{mparhack} % put margin notes onto the correct side for twoside layout
\usepackage{morefloats}

\raggedbottom
\maxdeadcycles=1000

% Generates the index
\usepackage{makeidx}
\makeindex

\begin{document}

\maketitle% this prints the handout title, author, and date

%\printclassoptions

\setcounter{footnote}{0}
\section{Peeragogy Monthly Wrap: 2019-03}
You’re reading the summary of our first meeting of a series conducted in Q1 and Q2\sidenote{\url{https://en.wikipedia.org/wiki/Calendar\_year\#Quarters}}. Our fun work included reviewing each other’s blog posts, introducing a newcomer to the project, revising an abstract, and hearing how Nepalese peers help one another!

Following the vernal equinox\sidenote{\url{https://en.wikipedia.org/wiki/March\_equinox}} we held four meetings discussing peeragogy (check out our latest Peeragogy Handbook\sidenote{\url{https://peeragogy.github.io}} to learn more! There is also an earlier version of the Handbook on Wikibooks\sidenote{\url{https://en.wikibooks.org/wiki/Peeragogy\_Handbook\_V1.0}}), which is our way to describe how peer learning\sidenote{\url{https://en.wikipedia.org/wiki/Peer\_learning}} and production\sidenote{\url{https://en.wikipedia.org/wiki/Peer\_production}} work. In an effort to drink our own champagne\sidenote{\url{https://en.wikipedia.org/wiki/Eating\_your\_own\_dog\_food\#Alternative\_terms}}, we’re implementing our wrapper pattern (see Peeragogy Wrapper Pattern\sidenote{\url{https://peeragogy.github.io/pattern-wrapper.html}} description in the Peeragogy Handbook) by creating this meeting artifact you’re now reading: “Someone involved with the project should regularly create a wrap-up summary, distinct from other project communications, that makes current activities comprehensible to people who may not have been following all of the details.”

If you have any questions about these notes and/or the project in general, dear reader (this is an old technique in fiction where the author directly address the reader, which we’re using to make this a conversation! We want to know what you think!! Cliff Notes has a nice write up\sidenote{\url{https://www.cliffsnotes.com/literature/a/adam-bede/critical-essays/the-dear-reader-technique-in-adam-bede}} about how the technique was used in Adam Bede\sidenote{\url{https://en.wikipedia.org/wiki/Adam\_Bede}}. “The technique, then, is first of all a convention. Eliot pretends throughout that Adam Bede is a true story. She takes the pose of one who is merely recording events which she has heard recounted. … The ‘dear reader’ technique also serves some practical functions. Because the author pretends to be ‘outside’ her own story, she is free to comment in her own voice upon the characters and events she creates.”), please reach out by emailing peeragogy@googlegroups.com\sidenote{\url{mailto:peeragogy@googlegroups.com}}!

\subsection{March Meeting}
When we last met in December\sidenote{\url{https://github.com/Peeragogy/Peeragogy.github.io/wiki/Monthly-Wrap:-December-2018-by-Charlie}}, we defined some 2019 first quarter goals:

\begin{itemize}
\item Write a blog post (no more than three paragraphs) on a learning topic they find interesting and relate it to peeragogy
\item And/or if you don’t have time to write, you can proofread,
\item Meet again in March to share work and outline next steps, and
\item Keep in touch via our public email group.
\end{itemize}
Aside from the fact that some of our writings exceed three paragraphs, I feel like we made good progress towards our Q1 goals. Lisa published a Medium\sidenote{\url{https://en.wikipedia.org/wiki/Medium\_(website)}} blog post “Peeragogy: An Introduction (draft)\sidenote{\url{https://medium.com/@snowinla/peeragogy-an-introduction-draft-d229fb951ba2}}” (later she put out a revised PDF version\sidenote{\url{https://authorlisasnow.com/wp-content/uploads/2019/05/Understanding-Peeragogy-to-Maximize-Resources-and-Efficiencies.pdf}}), Joe wrote a draft of a new article on our PubPub\sidenote{\url{https://www.pubpub.org/about}} (it’s a tool for collaborative writing) instance, I compiled a submission to the Anticipation\sidenote{\url{http://anticipationconference.org}} conference (“Anticipation 2019 is a unique, radically interdisciplinary forum for exploring how ideas of the future inform action in the present. It brings together researchers, policy makers, scholars and practitioners to push forward thinking on issues ranging from modelling, temporality and the present to the design, ethics and power of the future. This conference includes attention to design amongst other domains.”), we met in March, and we sent some emails to the public group (including introducing a newcomer to our fun world – Joe welcomed him\sidenote{\url{https://groups.google.com/d/msg/peeragogy/1GNDuzXuQv0/nJVhI0mACQAJ}} by implementing our newcomer pattern\sidenote{\url{https://peeragogy.github.io/pattern-newcomer.html}} in our Google Group\sidenote{\url{https://en.wikipedia.org/wiki/Google\_Groups}}).

During that March meeting our discussion topics included:

\begin{itemize}
\item Siblings
\item Paola’s research and exciting upcoming presentation
\item Simplifying buddhism and applying it to modern times (similar books read by Joe \& Lisa)
\item Quote about time for change\sidenote{\url{https://twitter.com/mmay3r/status/1108118141941374976}}
\item Community Organizers: animal management advocates ManuMitra (the group has a Facebook page\sidenote{\url{https://www.facebook.com/KMCMANUMITRA}} and this description is from a Global Alliance for Rabies Control article\sidenote{\url{https://rabiesalliance.org/resource/manumitra-tackles-nepals-urban-street-dogs-one-ward-time}}: “It was a risk to design a project which hinges entirely on the community. But we found no shortage of local people willing to work voluntarily for street dogs. Even (or perhaps especially) in the most underprivileged communities, there are individuals who resolve human-dog conflict or unofficially act as a font of knowledge on dogs. They are the experts in their local dogs and local humans, and they are permanent residents. It would be inappropriate for us to come and attempt to do their job – the only question we should ask is, ‘how can we help these people?’” queried Basanta Gautam, ManuMitra’s community coordinator) in Nepal being more helpful for accomplishing dog management than traditional hierarchical aid organizations
\begin{center}
\includegraphics[width=1\linewidth]{../media/resource_1.jpg}
\end{center}
\noindent{}\ignorespacesafterend{}\ifhmode\unskip\fi
\end{itemize}
The community organization chat reminded us of the community lifting itself up by its bootstraps story we quoted in our first paragogy paper (Corneli, J. and Danoff, C. 2011. Paragogy\sidenote{\url{http://ceur-ws.org/Vol-739/paper\_5.pdf}}. Proceedings of the 6th Open Knowledge Conference. “Paragogy is a theory of peer learning: we endeavor to say how it works, and how it works best. This paper outlines paragogy’s contemporary relevance and expounds its principles, showing their connections to other theories. We present an extended example of paragogy in practice, where we use it to evaluate our experiences working at the Peer 2 Peer University (P2PU).”):

\begin{quote}

A. T. Ariyaratne’s essay on Rural Self Help, one of the foundational writings of the Sarvodaya Shramadana\sidenote{\url{https://www.sarvodaya.org}} movement in Sri Lanka 6, begins:


“Nobody needs to teach rural communities about ‘group effort’ and ‘self-help’. […] The real question, therefore, is to examine what are the constraints that exist inhibiting the expression of their group effort and self-help qualities designed to improve food and nutrition levels, clothing,shelter, health, sanitation, education and cultural life?”


We approach peer learning in a similar spirit: it is something we all know how to do, but can’t always do well. Intuitively, there are bound to be difficulties for a group of peers studying a subject together, outside a traditional classroom or without a teacher. Indeed, peer learning is different from other forms of group effort, the proverbial “barn raising” for example, in which the persons involved can be presumed to know how to build barns – or at least to know someone who knows, and stand ready to take orders.


\end{quote}
Coming out of the meeting, we defined some action items:

\begin{itemize}
\item Meet in April
\item Review manuscript in progress doc and add links to more work
\item Collect success stories
\end{itemize}
\subsection{Licensing of this Resource}
This work has been released into the public domain\sidenote{\url{https://en.wikipedia.org/wiki/Public\_domain}} by its author, Charlie Danoff\sidenote{\url{https://en.wikiversity.org/wiki/User:Charles\_Jeffrey\_Danoff}}. This applies worldwide. In some countries this may not be legally possible; if so: Charlie Danoff\sidenote{\url{https://en.wikiversity.org/wiki/User:Charles\_Jeffrey\_Danoff}} grants anyone the right to use this work for any purpose, without any conditions, unless such conditions are required by law.

This file is licensed under the Creative Commons\sidenote{\url{https://en.wikipedia.org/wiki/Creative\_Commons}} CC0 1.0 Universal\sidenote{\url{https://creativecommons.org/publicdomain/zero/1.0}} waiver. The author of this work has dedicated it to the public by waiving all of his or her rights to the work under copyright law and all related or neighboring legal rights he or she had in the work, to the extent allowable by law. Legal Code\sidenote{\url{https://creativecommons.org/publicdomain/zero/1.0/legalcode}}


\bibliography{\jobname}
\bibliographystyle{plainnat}

\newpage
\begin{fullwidth}
~\vfill
\thispagestyle{empty}
\setlength{\parindent}{0pt}
\setlength{\parskip}{\baselineskip}
Layout: Copyright \copyright\ 2007-\the\year\ Kevin Godby, Bil Kleb, Bill Wood, Stephan Kreutzer

\par The layout is licensed under the Apache License, Version 2.0 (the “License”); you may not
use this layout except in compliance with the License. You may obtain a copy
of the License at \url{http://www.apache.org/licenses/LICENSE-2.0}. Unless
required by applicable law or agreed to in writing, layouts distributed
under the License are distributed on an “AS IS” BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations
under the License.

“ET Book” font: Copyright \copyright\ 2015-\the\year\ Dmitry Krasny, Bonnie Scranton, Edward Tufte

Permission is hereby granted, free of charge, to any person obtaining a copy of the “ET Book” font and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\\
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\\
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
\end{fullwidth}

\end{document}
