Manual de las Carpentries¶

Las Carpentries enseña habilidades básicas en programación y análisis de datos a investigadores de todo el mundo. Los talleres de Software Carpentry, Data Carpentry, y Library Carpentry están basados en nuestras lecciones. Organizadores, instructores y aprendices en dichos talleres deben de seguir nuestro Código de conducta.

Código de Conducta¶

The Carpentries: Código de conducta¶

Código de Conducta (vista resumida)¶

A continuación, se encuentra un resúmen del Código de Conducta de The Carpentries. Para mayor detalle del CoC continúa leyendo.

Para más información, por favor revisa nuestra:

Guía para la Respuesta a Incidentes
Guía para el Reporte de Incidentes
Procedimiento de Respuesta a Incidentes
Guía para la suspensión temporal.

Nos dedicamos a brindar un ambiente acogedor y de apoyo dirigido a todas las personas, independientemente de su conocimiento, experiencia, o identidad. La participación en esta comunidad, implica que los participantes aceptan el Código de Conducta de The Carpentries y los procedimientos por los cuales cualquier incidente referido al Código de Conducta será resuelto. Cualquier comportamiento para excluir, intimidar, o causar incomodidad es una violación del Código de Conducta. Con el objeto de fomentar un ambiente de aprendizaje positivo y profesional recomendamos los siguientes tipos de comportamiento en todas las plataformas y eventos:

Usa lenguaje inclusivo y amistoso (receptivo)
Sé respetuoso con los diferentes puntos de vista y experiencias
Acepta amablemente las críticas constructivas.
Enfócate en lo que es mejor para la comunidad.
Muestra cortesía y respeto hacia los otros miembros de la comunidad.

Si crees que alguien está violando el Código de Conducta, te pedimos que lo reportes al Comité del Código de Conducta de The Carpentries completando este formulario, quien tomará las acciones apropiadas para manejar la situación.

Código de Conducta (Vista detallada)¶

Parte 1. Introducción

The Carpentries es una comunidad liderada por proyectos. Valoramos la participación de cada miembro en la comunidad. Estamos comprometidos en crear un espacio amigable y respetuoso para aprender, enseñar y contribuir. Esperamos que todos los participantes a nuestros eventos muestren respeto y cortesía con los demás.

Para dejar claro que es lo que se espera, cada uno de los participantes de las actividades de The Carpentries debe dar conformidad al Código de Conducta. Este aplica a todos los espacios manejados por The Carpentries incluidos, pero no limitados a, talleres, listas de correos, y foros online como GitHub, Slack y Twitter. Se espera que los anfitriones de los talleres ayuden a hacer cumplir el Código de Conducta.

El Comité del Código de Conducta de The Carpentries es responsable de hacer cumplir el mismo. Dicho Comité puede ser contactado enviando un correo a coc@carpentries.org. Todos los reportes serán revisados por el Comité y serán confidenciales.

Parte 2. Código de Conducta de The Carpentries

The Carpentries está dedicado a brindar un ambiente acogedor y de apoyo dirigido a todas las personas, independientemente de su conocimiento, experiencia o identidad. Como tal, no toleramos comportamientos que sean irrespetuosos con nuestros maestros o alumnos o que excluyan, intimiden, o causen disconformidad a otros. No toleramos la discriminación o el acoso basado en características que incluyen, pero no limitadas a, la identidad y expresión de género, la orientación sexual, la discapacidad, la apariencia física, el tamaño corporal, la ciudadanía, la nacionalidad, el origen étnico o social, el embarazo, condiciones familiares, condición de veterano, información genética, religión o creencia (o falta de ella), pertenencia a una minoría nacional, edad, educación, condiciones socio-económicas, elecciones técnicas, y nivel de experiencia.

Cada uno de los participantes de las actividades de The Carpentries debe dar conformidad al Código de Conducta. Este aplica a todos los espacios manejados por The Carprentries incluidos, pero no limitados a, talleres, listas de correos, y foros onlines como GitHub, Slack y Twitter. Se espera que los anfitriones de los talleres ayuden a hacer cumplir el Código de conducta. Mediante la participación, los participantes indican que aceptan los procedimientos por los cuales The Carprentries resuelven cualquier incidente referido al Código de Conducta, los cuales quizás incluyan el almacenamiento y procesamiento de información personal.

Parte 2.1 Comportamiento esperado

Se espera que todos los participantes a nuestros eventos y comunicaciones muestren respeto y cortesía con los otros miembros. Todas las interacciones deberán ser profesionales independientemente de la plataforma: ya sea online o en persona. Con el objetivo de fomentar un ambiente de aprendizaje positivo y profesional alentamos a seguir este tipo de comportamientos en todos los eventos y plataformas de The Carpentries:

Usa lenguaje inclusivo y amistoso (receptivo)
Sé respetuoso con los diferentes puntos de vista y experiencias
Acepta amablemente las críticas constructivas.
Enfócate en lo que es mejor para la comunidad.
Muestra cortesía y respeto hacia los otros miembros de la comunidad.

Nota: Consulte las cuatro reglas sociales para obtener más recomendaciones.

Parte 2.2 Comportamiento inaceptable

Ejemplos de comportamientos inaceptables de parte de los participantes en cualquier evento/plataforma de The Carpentries incluyen:

realizar comentarios escritos o verbales que tengan el efecto de excluir a las personas sobre la base de la pertenencia a cualquier grupo específico
hacer que alguien tema por su seguridad, por ejemplo, a través del acecho, el seguimiento o la intimidación
amenazas o lenguaje violento dirigido contra otra persona
la exhibición de imagenes sexuales o violentas
atención sexual no deseada
contacto físico no consensuado o no deseado
interrupción sostenida de charlas, eventos o comunicaciones
insultos o humillaciones
chistes sexistas, racistas, homófobos, transfóbicos, excluyentes o que discriminan contra las personas con discapacidad
maldecir en exceso
incitar a la violencia, al suicidio o a la auto-lesión
continuar iniciando interacción (incluidas fotografías o grabaciones) con alguien después de que se le solicite que deje de hacerlo
publicación de comunicaciones privadas sin consentimiento

Parte 2.3 Consecuencias de los Comportamientos inaceptables

Se espera que a los participantes a quienes se les pida que detengan cualquier comportamiento inapropiado, cumplan inmediatamente. Esto aplica a cualquier evento y plataforma de Carpentries, ya sea online o en persona. Si un participante se involucra en un comportamiento que viola este Código de Conducta, los organizadores pueden advertir al agresor, pedirle que abandone el evento o la plataforma (sin reembolso), o involucrar al Comité del Código de Conducta de Carpentries para que investigue la violación del Código de Conducta e imponga las sanciones apropiadas.

Registro de actualizaciones¶

2019-02-28 Adición del proceso de apelación, procedimiento para el seguimiento de la persona reportada, terminología, procedimiento de respuesta a incidentes del Código de Conducta, lista de verificación de suspensión temporal, y cláusulas ampliadas para conflictos de intereses.
2018-09-11 Código de Conducta revisado para proveer ejemplos de comportamiento beneficial y no deseado. También incluye cambios relacionados al intento de evaluación. Han contribuido: Ethan White, Kari L. Jordan, Karin Lagesen, Malvika Sharan, Samantha Ahern, y Simon Waldman.
2018-09-11 Se revisaron la Guías de reportes para incluir puntos de contactos alternativos. Colaboradores: Ethan White, Kari L. Jordan, Karin Lagesen, Malvika Sharan, Samantha Ahern, y Simon Waldman.
2016-11-21 Se ha publicado el Código de Conducta, las pautas para la presentación de Reportes y el Manual de Cumplimiento. Los documentos se adaptaron de las guías escritas para el Proyecto Django, las cuales a su vez se basan en la plantilla de la Iniciativa de Ada y en el procedimiento para manejar incidentes de acoso de la Pycon 2013. Colaboradores: Adam Obeng, Aleksandra Pawlik, Bill Mills, Carol Willing, Erin Becker, Hilmar Lapp, Kara Woo, Karin Lagesen, Pauline Barmby, Sheila Miguez, Simon Waldman, Tracy Teal.

Acerca de este documento¶

Este documento se adaptó de las pautas escritas para el Proyecto Dyango, las cuales a su vez se basan en la plantilla de la Iniciativa Ada y en el procedimiento para manejar incidentes de acoso de la Pycon 2013. Colaboradores en este documento: Adam Obeng, Aleksandra Pawlik, Bill Mills, Carol Willing, Erin Becker, Hilmar Lapp, Kara Woo, Karin Lagesen, Pauline Barmby, Sheila Miguez, Simon Waldman, Tracy Teal. Otter Tech agregó un idioma adicional del Código de conducta de PyCon U.S. 2018 (con licencia CC BY 3.0)

Guía de Respuesta del Código de Conducta ante Incidentes¶

La información sobre cómo reportar un incidente del Código de Conducta (CoC) se encuentra descrito en nuestra Guía para el Reporte de Incidentes del Código de Conducta.

Las listas de verificación a continuación describen los pasos que puede tomar cualquier miembro de la comunidad (anfitrión del taller, instructor, ayudante, etc.) durante un posible incidente del Código de conducta antes de informar al Comité del Código de Conducta. Puede que te encuentres con situaciones desafiantes y que tengas poca experiencia o capacitación para sentirte cómodo haciendo cumplir el CdC. Estas pautas tienen la intención de guiarte a través del proceso de apoyo a otros miembros de la comunidad y a ti mismo durante un incidente.

Todos los miembros de la comunidad de Carpentries deben sentirse facultados para hacer cumplir el Código de Conducta.

Idealmente, todos deberíamos ser capaces de contribuir a evitar un incidente. En la práctica, tenemos un nivel de comodidad distinto en función de nuestra experiencia y ambiente que nos rodea. A continuación se detallan las formas en que puedes brindar apoyo y los pasos que puedes seguir durante o luego de un incidente.

Si puedes, pasa de ser un espectador a ser primer respondiente del Código de conducta. Si ve que sucede algo inapropiado, hable. Si no te sientes cómodo interviniendo, pero crees que alguien debería hacerlo, por favor reporta el incidente en persona a un anfitrión o instructor del taller, o mediante el formulario de Reporte de Incidentes del Código de conducta al comité del Código de conducta.

Respuesta Inmediata¶

La respuesta inicial a un incidente es muy importante y definirá el tono para la comunidad de Carpentries. Dependiendo de la severidad y/o detalles del incidente, una respuesta inmediata podría ser necesaria. Si un incidente implica daño físico o una amenaza a la seguridad de alguien (por ejemplo, una amenaza de violencia), cualquier miembro de la comunidad puede – y debería – actuar inmediatamente para proteger la seguridad de todos. Esto puede incluir contactar a los recursos de emergencia o crisis.

Incidentes en curso¶

Si un incidente está en curso, ya sea en persona o en línea, cualquier miembro de la comunidad (anfitrión del taller, instructor, ayudante) puede actuar independientemente y emplear cualquiera de las herramientas disponibles para el miembro de la comunidad para pacificar la situación. En situaciones donde un individuo de la comunidad actúa inmediatamente, dicho individuo debe informar al anfitrión del taller lo antes posible y reportar sus acciones al Comité de Código de Conducta para revisión dentro de las 24 horas de ocurrido el incidente. En caso de ser necesaria una respuesta inmediata, por favor refiérete a la Lista de verificación para Respuesta Inmediata.

Listas de verificación para responder a un incidente¶

Lista de verificación para Respuesta Inmediata

Evalúa si necesitas un personal de primera respuesta (policía, etc.) para responder inmediatamente al incidente. Si es así, pídele al reportador del incidente que se quede contigo y marca el número de emergencia apropiado.
Si hay una amenaza general hacia todos los participantes y/o a la seguridad de cualquiera persona que haya asistido al evento de Carpentries, contacta al número de emergencia establecido.
Si los individuos están físicamente seguros, contacta a un agente de la ley o de seguridad únicamente ante la solicitud de quién reportó el incidente.
Sigue cualquier lineamiento local para el manejo de incidentes, incluso si tienes un rol legal como reportador.

Lista de verificación para eventos en persona (Talleres de Carpentries, CarpentryCon, CarpentryConnect, Entrenamiento de Instructores de Carpentries)

Asegúrate que los participantes estén seguros.
En caso contrario, refiérete a la Lista de verificación para Respuesta Inmediata.
Escucha a quién reporta la situación y escribe tantos detalles como sea posible.
Pídele al reportador que informe el incidente mediante el Formulario de Reporte de Incidentes de Código de Conducta. Si el reportador prefiere que tu completes el reporte, complétalo con su asistencia.
Informa al anfitrión del taller que ha habido un incidente y que un reporte fue enviado mediante el formulario de reporte de incidentes. Si el incidente involucra al anfitrión del taller, reporta el incidente directamente al comité de Código de Conducta mediante el formulario de reporte de incidentes.

Lista de Verificación para Eventos en Línea y Canales de Comunicación (Demostraciones de enseñanza, Discusiones de la Comunidad, Entrenamiento de Instructores de Carpentries, Canales de Slack, TopicBox)

Informa al anfitrión del evento/facilitador de la reunión que ha habido un problema y envía un reporte mediante el formulario de reporte de incidente.
Si el incidente involucra al anfitrión del evento/facilitador de la reunión, por favor completa el formulario de reporte de incidente, y ten por seguro que tanto la confidencialidad como tu experiencia en nuestra comunidad es nuestra primera prioridad.

Si un miembro de la comunidad ha violado el CdC a través de un evento en línea, el comité de CdC puede emitir una Suspensión por Término por un período corto, y los privilegios del reportado en todos los canales de comunicación de Carpentries podrían verse suspendidos hasta que el Comité de Código de Conducta haya concluido la investigación del incidente reportado.

Los individuos reportados usualmente se enojan, se ponen a la defensiva, o niegan el reporte. Permíteles que den detalles adicionales acerca del incidente. Sin embargo, recuerda:

No importa si su intención no era la de lastimar a nadie; su comportamiento de todas formas impactó negativamente en los participantes.
No es tu trabajo tranquilizarlos o perdonarlos.
No permitas que la persona reportada se disculpe con el reportador o la persona afectada. Usualmente una disculpa se centra en los sentimientos de la persona reportada y no en la persona que fue afectada. Puedes aceptar la disculpa y ofrecer pasarla a la persona afectada, pero no estás obligado a hacerlo si consideras que esto podría afectar negativamente al reportador.

Guía de Informe de Incidentes del Código de Conducta¶

Reportar un Potencial Incidente de Código de Conducta¶

Si estás asistiendo a un taller de Carpentries, a un evento en persona, o participando en uno de nuestros eventos en línea o de nuestros canales de comunicación y crees que alguien está en peligro físico, por favor pídele al anfitrión de tu taller, instructor(es), u otro miembro de la comunidad que contacte al servicio de emergencia apropiado (policía, línea de emergencia, etc.). Previamente al taller de Carpentries o evento en persona, los organizadores del evento deberán determinar los números de emergencia y procedimientos locales.

Si crees que alguien violó el Código de Conducta durante un evento de Carpentries o en uno de los espacios en línea de Carpentries, te pedimos que lo reportes. Si no estás segura si el incidente sucedió en un espacio gobernado por Carpentries, te pedimos que de todas formas reportes el incidente. Te recomendamos que envíes tu reporte completando el Formulario de Reporte de Incidente del Código de Conducta. El formulario puede ser completado anónimamente, o si los deseas, puedes incluir tu información de contacto.

Enviar un Reporte de Incidente del Código de Conducta

El Comité del Código de Conducta toma en serio todos los informes de incidentes y los revisará de acuerdo con nuestras pautas de cumplimiento. Un informe de incidente garantiza revisión, pero no necesariamente que se tomará una acción.

Formas de contacto alternativas¶

Si prefieres contactarnos por otros medios, un correo electrónico a coc@carpentries.org será visto por todo el comité de Código de Conducta. Si no te sientes cómoda informando al comité del Código de Conducta, los incidentes también se pueden reportar a Cam Macdonell, el defensor del pueblo designado para The Carpentries, en confidential@carpentries.org.

También puedes contactar a la directora ejecutiva de The Carpentries (Tracy Teal) por teléfono al +1-530-341-3230 o por correo electrónico a tkteal@carpentries.org.

Confidencialidad¶

Siempre puedes reportar un incidente de manera anónima. Sin embargo, si deseas que alguien te haga un seguimiento sobre el progreso de tu reporte de incidentes, deberás proporcionar información de contacto.

Todos los informes se mantendrán confidenciales y los detalles se compartirán solo con los miembros del comité del Código de Conducta. En caso tal que algún miembro del comité del CdC esté involucrado en un informe, se le pedirá a dicho miembro que se recuse de las conversaciones en curso, y se le prohibirá el acceso a los informes una vez que se haya tomado la decisión de cumplimiento. Las acciones de resolución también pueden incluir la expulsión del miembro del comité de CdC.

En casos excepcionales, el comité de CdC puede suspender a un miembro de la comunidad. En tales casos, se informará al Consejo Ejecutivo y al personal de Carpentries para evitar daños a la comunidad en el futuro, y se empleará la Lista de Verificación de Respuesta Inmediata del Personal de Carpentries.

Algunos incidentes ocurren en interacciones uno a uno, y aunque los detalles sean anonimizados, la persona reportada puede llegar a identificar a quién hizo el reporte. Si temes por posibles represalias o por tu seguridad personal, por favor comunícalo en tu reporte. Te invitamos a reportar el incidente para que podamos ayudarte a la vez que velamos por la seguridad de los otros miembros de nuestra comunidad. En algunos casos, podemos compilar varios informes anonimizados para resaltar un patrón de comportamiento y poder tomar medidas sobre él.

El comité del Código de Conducta puede decidir que se debe hacer una declaración pública sobre el incidente y/o la acción tomada. Si ese es el caso, las identidades de todos los reportados y reportadores se mantendrán confidenciales a menos que esas personas instruyan al comité de CdC de lo contrario.

Datos del Informe¶

Los reportes se pueden presentar de forma anónima con detalles mínimos. Si crees no poder proporcionar detalles, nos gustaría de todas formas saber que ocurrió un incidente. Sin embargo, nuestra capacidad de actuar se verá afectada por la cantidad de información que nos puedas proporcionar.

La información sobre un incidente puede ser comunicada al personal relevante de Carpentries en casos en los cuales un miembro esté suspendido de participar en la comunidad de Carpentries. En esos casos, se empleará la Lista de Verificación de Suspensión.

Seguimiento con Quien Realizó el Reporte¶

Una vez presentado un informe a través del Formulario de Informe de Incidente del Código de Conducta u otros canales de comunicación, el comité del Código de Conducta manejará la revisión y el seguimiento de acuerdo con los procedimientos establecidos en las Pautas de Cumplimiento.

Procedimiento de Respuesta a Incidentes y Pautas de Cumplimiento del Código de Conducta.¶

Este documento describe el Procedimiento de Respuesta a Incidentes y Pautas de Cumplimiento seguidas por el Comité de Código de Conducta (CoCc) de The Carpentries, una vez que se reporta un incidente a través del formulario de informe correspondiente u otros canales. Estas pautas se utilizan cuando el CoCc revisa y resuelve incidentes para garantizar la coherencia, la transparencia y la imparcialidad. The Carpentries tiene acceso a asistencia legal a través de su patrocinador fiscal, iniciativas Comunitarias, en caso de ser necesaria.

El comité de CoC intentará garantizar su seguridad y la ayuda correspondiente en el momento que se solicite la misma, especialmente en eventos presenciales. El (los) informante(s) del incidente recibirán un correo electrónico del Comité del Código de Conducta confirmando recepción del mismo dentro de las 24 horas posteriores a la presentación del reporte, nuestro objetivo es el mismo tiempo de respuesta a través de otros canales.

Si hay un incidente en curso o una amenaza a la seguridad física, la prioridad inmediata del comité será proteger a todos los involucrados. Esto significa que podemos demorar una respuesta «oficial» hasta que creamos que la situación ha terminado y que todos están físicamente seguros.

El comité hará todo el esfuerzo posible para reunirse dentro de los siguientes dos días hábiles para revisar el incidente y determinar los próximos pasos. Una vez que el comité tenga una descripción completa de los eventos, tomará una decisión sobre cómo responder. Los ejemplos de posibles respuestas a incidentes se detallan en las Pautas de Cumplimiento de The Carpentries. El comité responderá dentro de una semana al informante/denunciante original, ya sea con una resolución o con una explicación de por qué la situación aún no se ha resuelto.

Una vez que el comité haya llegado a una resolución, se contactará con el informante/denunciante original para informarle qué acción (si correspondiese) se tomará. El comité tendrá en cuenta los comentarios del informante sobre la veracidad de su respuesta, pero puede decidir no tomar ninguna acción sobre estos.

Finalmente, el Presidente del Comité del Código de Conducta y el Enlace del Consejo Ejecutivo redactarán un informe de transparencia para los incidentes informados a través del formulario de reporte de incidentes u otros canales. Los nombres del reportero y de las personas involucradas en el incidente no se incluirán a menos que la resolución resulte en una suspensión temporal. El Consejo Ejecutivo puede optar por hacer un informe público del incidente mientras mantiene el anonimato de los involucrados.

Terminología¶

Informante/Denunciante: Persona que reporta un incidente.
Reportado/Denunciado: Persona que ha sido reportada.
Grupo de Respuesta a Incidentes (GRI): Grupo de personas quienes trabajan en un incidente en particular. Existe un mínimo de tres personas del Cómite del Código de Conducta por cada GRI.
Responsable de Respuesta a Incidentes (RRI): Persona del Cómite del Código de Conducta que lidera el GRI. Esta persona es elegida por el GRI para un incidente específico.

Procedimiento de Respuesta a Incidentes elaborado por el Comité de Código de Conducta de The Carprentries.¶

El siguiente es un resumen de los pasos que realiza el Comité del Código de Conducta para responder a un incidente reportado mediante el formulario de reporte de incidentes. Para más información al respecto a continuación se proporciona un resumen.

Si se necesita una respuesta inmediata (peligro físico, interrupción en un taller, conversación en línea de manera continua) a un incidente informado a través de cualquiera de los canales, el CoCc, Comité del Código de Conducta, puede activar la lista de verificación para la suspensión temporal.
Para respuestas no inmediatas enviadas a través del formulario para informar/reportar un incidente, se envía un correo electrónico automático al comité del Código de Conducta el cual indica la recepción del mismo.
Una respuesta automática se envía al denunciante para informarle que el reporte del incidente fue recibido a través del formulario seguro.
La primera persona del Comité del Código de Conducta en recibir el informe lo revisa y proporciona una respuesta inicial al informante/denunciante dentro de las 24 horas posteriores a la presentación del informe o de manera inmediata, en caso de que la seguridad sea un problema.
Esta respuesta incluirá un detalle de las acciones que espera realizar el Comité del Código de Conducta para proporcionar una resolución al informe presentado.
La primera persona del Comité del Código de Conducta en recibir el informe, completa un formulario de recolección de datos de incidentes para compartirlo con el Comité de CoC.
Un mínimo de tres miembros del Comité del Código de Conducta (Grupo de Respuesta a Incidentes (GRI)) se reúne para discutir el incidente. El documento del informe del incidente se comparte con el GRI antes de dicha reunión.
Un Responsable de respuesta a Incidentes (RRI) es designado por el GRI, Grupo de Respuesta de Incidentes.
El GRI, Grupo de Respuesta de Incidentes, determina si el incidente ocurrió en un espacio de The Carpentries y, por lo tanto, si es apropiado revisarlo.
El GRI, Grupo de Respuesta de Incidentes, revisa toda la información incluida en el reporte del incidente y determina si es necesario solicitar más datos. Si es así, la misma se solicita al informante/denunciante.
El RRI, Responsable de respuesta a Incidentes, se comunica con el(los) informantes/denunciantes para programar una reunión, si fuese necesario. Al menos dos miembros del GRI, Grupo de Respuesta de Incidentes, deben estar presentes en la reunión.
Puede llevarse a cabo una reunión, la cual es opcional, con el informante para obtener más información. Al menos dos miembros del GRI, Grupo de Respuesta de Incidentes, deben estar presentes en la misma.
Después de una recopilación y revisión exhaustiva de la información, si fuera necesario, el GRI, Grupo de Respuesta de Incidentes, determina una resolución. Las posibles resoluciones al incidente se encuentran en esta documentación e incluyen, pero no se limitan a, una amonestación privada, una amonestación pública y una suspensión temporal.
El RRI, Responsable de respuesta a Incidentes, informa al denunciante y solicita su opinión sobre la resolución del incidente. Esta retroalimentación puede ser usada o no para modificar la misma.
The IRL updates the reportee(s).
El personal determina con la Lista de Verificación de Suspensión Temporal, si esta debería ser empleada o si se deben tomar otras medidas.
El personal prioritario es notificado para así implementar las acciones correspondientes a la resolución del incidente. Los detalles del informe permanecen confidenciales.
Las decisiones y los resultados se registran en el repositorio privado de GitHub del Comité de Código de Conducta.
El Presidente del Comité del Código de Conducta y el Enlace del Consejo Ejecutivo redactan un informe de transparencia.

Informe de Reconocimiento.¶

Cuando se recibe un informe, cualquiera de los miembros del Comité del Código de Conducta responderá al informante para confirmar la recepción del mismo. Esta respuesta se enviará dentro de las 24 horas posteriores a la notificación del incidente, sin embargo, el CoCc, Comité del Código de Conducta, hará todo lo posible por responder antes de dicho plazo.

Para obtener detalles sobre lo que debe contener el reporte de un incidente, consulte la Guía para Reportar Incidentes. Si un informe no contiene suficiente información, el comité intentará obtener toda la información relevante para resolver el incidente. El Comité tiene la facultad para actuar en nombre de The Carpentries y contactar a cualquiera de las personas involucradas, a menos que el informante solicite no hacerlo, ya que proteger la seguridad del informante es prioritario en cualquier reporte o revisión de incidente. El comité también está facultado para actuar si alguno de sus miembros se da cuenta que un comportamiento, prolongado a lo largo de tiempo, es inapropiado.

Evaluación de Respuesta a Incidentes.¶

Al recibir un informe de un incidente, al menos tres miembros del CoCc, Comité del Código de Conducta, formarán parte del Grupo de Respuesta a Incidentes (GRI). Éste, se reunirá para:

Asignar un Responsable de Respuesta a Incidentes (RRI).
Revisar la documentación del informe para definir el contenido y contexto del incidente.
Consultar la documentación de incidentes pasados para establecer patrones de comportamiento (si la misma estuviese disponible y fuese aplicable).
Discutir cuáles serían las resoluciones más apropiadas al incidente.
Determinar las acciones a seguir por el informante, el denunciado y cualquier otra persona nombrada en el informe que pueda haber sido afectada.

Las deliberaciones de la evaluación de Respuesta al incidente se almacenarán en el repositorio privado de GitHub del Comité del Código de Conducta.

El Comité intentará dar una respuesta consensuada dentro de la siguiente semana de haber recibido el formulario de Respuesta a Incidente. En el caso de que no sea posible, el RRI, Responsable de Respuesta a Incidentes, responderá al (los) denunciante(s) con un informe y un cronograma definido para llegar a la resolución del mismo.

Siguiendo con el Informe.¶

Cuando se continúa con el informe, los representantes de CoCc, Comité del Código de Conducta:

Explicarán que se reportó un incidente que involucra al denunciado.
En esta explicación, el enfoque estará en el impacto de su comportamiento, y no en su intención.
Reiterarán el Código de Conducta y explicarán que su(s) comportamiento(s) fue(ron) considerado(s) inapropiado(s).
Proporcionarán al denunciado ejemplos concretos de cómo pueden mejorar su comportamiento.
Darle al(los) denunciado(s) la oportunidad de expresar su opinión sobre el incidente.
Recuérdeles las consecuencias de su comportamiento, o las futuras consecuencias si el mismo se repite.
Explique las posibles resoluciones que pueden ser impuestas por el CoCc, Comité del Código de Conducta, si se determina que hay una infracción/o violación al Código de Conducta.

Resoluciones¶

El comité debe acordar una resolución con la mayoría de los miembros que investigan el incidente en cuestión. Si el comité no llega una a decisión mayoritaria y existen tiempos muertos durante más de una semana, se pasará el asunto al Consejo Ejecutivo para su resolución.

Los siguientes son ejemplos de posibles resoluciones a un Incidente reportado. Esta lista no es exhaustiva, y el Comité de Código de Conducta de The Carpentries se reserva el derecho de tomar cualquier acción que considere necesaria para resolver el mismo. Las posibles soluciones a un incidente incluyen:

No sé tomará ninguna acción, si el comité del Código de Conducta determinó que no hubo incumplimiento del mismo.
Una advertencia/reprimenda verbal privada del comité a la(s) persona(s) involucrada(s).
Esta conversación puede ocurrir de manera presencial, por videoconferencia o por teléfono.
El RRI, Responsable de Respuesta a Incidentes, escribirá un breve informe de la conversación que se compartirá con el reportado con fines de verificación y luego se compartirá con el CoCc, Comité del Código de Conducta, y se mantendrá un registro en el repositorio privado de GitHub.
Una amonestación privada por correo electrónico del comité a la(s) persona(s) involucrada(s).
El RRI, Responsable de Respuesta a Incidentes, enviará una amonestación a la(s) persona(s) por correo electrónico, con copia al Comité del Código de Conducta.
Solicitando que el reportado/denunciado evite cualquier interacción y proximidad física con cualquier otra persona por el resto del evento de The Carpentries.
Rechazando la compras de bebidas alcohólicas por parte del reportado en eventos de The Carpentries.
Finalizando cuanto antes una charla que viola el Código de Conducta.
No publicando el vídeo o las diapositivas de una charla dada por una persona que violó el Código de Conducta.
No permitiendo que un orador que violó el Código de Conducta con anterioridad brinde (más) charlas en los talleres o eventos de The Carpentries ni ahora ni en el futuro.
Requiriendo que el denunciado no sea voluntario en futuros eventos de The Carpentries, ya sea por tiempo indefinido o por un período de tiempo determinado por el CoCc, Comité del Código de Conducta.
Requiriendo que el denunciado reembolse cualquier subsidio de viaje que haya recibido.
Requiriendo que el reportado/denunciado abandone inmediatamente un evento y no regrese.
Poniendo fin de inmediato a las responsabilidades y privilegios que el reportado/denunciado tiene por ser voluntario.
Dar a conocer el incidente públicamente, idealmente en el mismo lugar donde ocurrió el hecho (por ejemplo, en el servidor de listas cuando la violación al código de conducta tuvo lugar en la misma lista; GitHub para una violación al código realizada en dicha plataforma, etc.).
El CoCc, Comité del Código de Conducta, puede optar por publicar en el futuro este mensaje en otro lugar.
Una suspensión impuesta (es decir, pedirle a alguien que «se tome una semana de descanso» de un servidor de listas o de los repositorios de GitHub de The Carpentries).
El RRI, Responsable de Respuesta a Incidentes, comunicará esta suspensión al reportado. Se le pedirá que voluntariamente acceda a la suspensión , pero en caso contrario, se puede imponer una prohibición temporal para hacer cumplir esta suspensión.
Una prohibición permanente o temporal en algunos o todos los espacios de The Carpentries (listservs, GitHub, eventos presenciales, incluyendo talleres, etc).
El comité del CoC mantendrá registros de todas las prohibiciones para que puedan ser revisadas en el futuro, extendidas a los nuevos foros de comunicación de The Carpentries, e incluso mantenidas de alguna otra manera.
Asistencia al demandante con un informe dirigido a otros organismos, por ejemplo, a las oficinas institucionales o agencias apropiadas para la aplicación de la ley.

Una vez que se ha llegado a una resolución sobre el incidente reportado, pero antes de su promulgación, el RRI, Responsable de Respuesta a Incidentes, se pondrá en contacto con el informante/denunciado y con cualquier otra parte afectada para explicar la resolución propuesta. El RRI consultará a ambas partes si dicha resolución resulta aceptable debiendo registrar los comentarios hechos al respecto. Sin embargo, no se requiere ningún tipo de acción por parte del Comité del Código de Conducta sobre esta retroalimentación.

Proceso de Apelación¶

Cualquier persona(s) involucrada(s) en un informe/denuncia de un incidente respecto al Código de Conducta manejado por el Comité del CoC (CoCc) tiene derecho de apelar cualquier decisión tomada por éste. Para esto, se puede presentar una apelación directamente al CoCc (correo electrónico: coc@carpentries.org) o al ombudsperson (correo electrónico: confidencial@carpentries.org) enviando un correo electrónico con el asunto «Código de Conducta Apelación de Incidentes».

El correo electrónico debe incluir documentación relacionada con el incidente para respaldar la apelación. La documentación mencionada puede incluir, pero no se limita a:

Información del reporte que justifique la acción de la apelación.
Cartas de apoyo de miembros de la comunidad.
Declaraciones de otras personas involucradas en el incidente para apoyar la apelación.

Las apelaciones se pueden solicitar hasta 30 días después de haberse definido una resolución.

Responsabilidad¶

El comité del CoC, Código de Conducta, presentará un informe al Consejo Ejecutivo y al Director Ejecutivo de The Carpentries en caso de que la resolución en curso, sea una suspensión o prohibición.

El comité del CoC, Código de Conducta, no discutirá públicamente los detalles de un incidente; cualquier declaración pública será hecha por el Consejo Ejecutivo de The Carpentries.

Al final de cada trimestre, el Consejo Ejecutivo publicará un resumen de los incidentes revisados por el Comité del Código de Conducta, indicando cuántos informes recibió, cuántos incidentes investigó de forma independiente, cuántas veces actuó de manera unilateral, y para cada uno de ellos, cuál parte del Código de Conducta tuvo en cuenta para clasificar el incidente.

Conflictos de intereses.¶

En el caso de un conflicto de intereses (cuando un miembro del comité, un miembro de su familia o alguien con quien dicho miembro tenga una relación académica o de empleo cercana esté involucrado en una queja), el miembro del comité debe notificar inmediatamente a los otros miembros y recusarse si fuera necesario.

En el caso de que un miembro del CoCc, Comité del Código de Conducta, participe en un informe, se le pedirá que se recuse de las conversaciones en curso y no tendrá acceso a los informes finales una vez que se haya tomado la decisión de cumplimiento. La definición de la resolución también puede incluir la eliminación de ese miembro del comité del Código de conducta.

Código de Conducta Guía para la Suspensión Temporal¶

Lista de Verificación para la Suspensión Temporal de The Carpentries¶

Como parte de las opciones de aplicación, el comité de Código de Conducta (CoC) de Carpentries, puede dejar a un miembro de la comunidad en Suspensión Temporal, siendo el miembro de la comunidad removido de todos sus compromisos en Carpentries por un período de tiempo.

El objetivo de una Suspensión Temporal es: 1) limitar la participación de una persona en los espacios de Carpentries virtuales y presenciales por un período de tiempo determinado para crear un espacio seguro para la comunidad, y 2) para dar tiempo y oportunidad al individuo para revisar sus respuestas al incidente, y evidenciar inmediatamente cambios demostrables, en curso, para ser evaluados por el comité de CoC para una posterior posible reincorporación.

En la mayoría de los casos, una Suspensión Temporal sólo será promulgada después de ser revisado por el comité CoC y alcanzado una resolución. Sin embargo, en situaciones severas, en particular donde hay acoso activo, el comité CoC puede aprobar una inmediata Suspensión Temporal de corto plazo, mientras el incidente esté bajo revisión.

Si existe una decisión para una Suspensión Temporal, la siguiente lista de verificación es seguida por el personal apropiado, para aprobar la Suspensión Temporal. En concordancia con la guía de confidencialidad de CoC sólo el personal necesario se involucrará en la implementación de estas acciones.

Comunicaciones en línea y Comunidades¶

Revocar acceso desde los siguientes canales de comunicación y comunidades:

Listas de correo en TopicBox
Listas de correo sobre Google Groups incluyendo, pero no limitado a:
- Grupo de gobierno de Library Carpentry
- Mantenedores en curso de Library Carpentry
- Comité de Código de Conducta
- Grupos de Mentoreo de Carpentries
Twitter:
Blogs
GitHub (incluyendo pero no limitado a carpentries, datacarpentry, swcarpentry, librarycarpentry, data-lessons, carpentrieslab)
Gitter - Library Carpentry Lobby
Slack
Facebook
LinkedIn Carpentries y LinkedIn Instructors

Además, no estará permitido al miembro de la comunidad asistir a discusiones de la comunidad.

Talleres de Enseñanza¶

El miembro suspendido, por el tiempo de su suspensión:

Se le solicitará no registrarse en talleres de la Planilla de Instructores.
No podrá participar como ayudante en ningún taller.
Sera removido del acceso para ingresar a Eventbrite
No se le permitirá planificar talleres.
No se le permitirá solicitar o ser anfitrión de talleres coordinados centralmente.
No se le listará como instructor en la página web de «instructores».
Será removido de la lista de email de instructores.

Organizando talleres¶

Si la integrante suspendida es una Coordinadora Regional o trabaja en otro rol donde organizar talleres para The Carpentries, durante la suspensión no tendrá acceso a:

LastPass
AMY
Email regional
Asana
HelpScout
Zoom
Canal de Slack de Coordinadores Regionales
Lista de Email de Coordinadores Regionales

Entrenamiento de Instructores¶

El miembro suspendido será removido, por la duración de la suspensión, de la página web «Nuestros Entrenadores». Además, el miembro suspendido no podrá:

Enseñar en Entrenamiento de Instructoras o dirigir sesiones de demostración de enseñanza. La Directora Adjunta de Entrenamiento de Instructores (DDIT) verificará el Etherpad de la demostración de enseñanza para asegurarse que la integrante suspendida no esté registrada para dirigir demostraciónes de enseñanza y buscará una entrenadora de reeemplazo si es necesario.
Unirse a los encuentros de entrenadoras. El DDIT verificará el Etherpad del encuentro, y si la integrante suspendida se registró para participar, enviará un email a quienes participan para confirmarles que no asistirá
Publicar pull requests (PRs), problemas, o comentarios en el repositorio GitHub de Entrenamiento de Instructoras. Será eliminada la posibilidad de grabar o administrar acceso a repositorios por el período de suspensión
Publicar en los canales de Slack de entrenadoras o en las listas de mail. La integrante suspendida será eliminada de estas listas por el período de suspensión.
Participar en la revisión de solicitudes para capacitaciones abiertas de entrenadoras o participar como estudiante en entrenamiento de instructoras.

Entrenamiento de Entrenadores¶

La integrante suspendida no podrá participar en Entrenamientos de Entrenadoras (si está enrolada en ese momento), y no se aceptará como entrenadora de entrenadoras (si aplica durante el período de suspensión). Además, no podrá continuar un entrenamiento actual. Pordrá presentarse o volver a presentarse a nuevas rondas de Entrenamientos de Entrenadoras.

Organización de Miembros y Actividades Locales¶

La integrante suspendida no podrá participar en los talleres oficiales con la marca de Carpentries o en actividades en el sitio local o de una organización miembro por el período de suspensión. Esperamos que la integrante suspendida declare que llevará a cabo esta suspensión y que notifique al comité del CoC si esta suspensión interferirá con sus obligaciones laborales.

Si la suspensión afecta las obligaciones laborales o la integrante suspendida es un contacto clave para un sitio miembro, el miembro trabajará con la Directora Ejecutiva de Carpentries para determinar un curso de acción.

Desarrollo de Lecciones y Mantenimiento:¶

La integrante suspendida no podrá publicar PRs, problemas o comentarios en ningún repositorio de Carpentries, incluyendo, pero no limitado a, organizaciones de datacarpentry, swcarpentry, library carpentry, data-lessons, y carpentrieslab. Serán eliminados los privilegios de administrar o grabar a repositorios de estas organizaciones por el tiempo que dure la suspensión.

Si el miembro suspendido en un mantenedor, el nombre será removido de las páginas de lecciones y no aparecerán en la página de Mantenedores por la duración de la suspensión.

Consejo Ejecutivo:¶

Si la integrante suspendida es parte del Concejo Ejecutivo, no participará de las responsabilidades del Concejo Ejecutivo y será removida de los repositorios del Concejo Ejecutivo y de la lista de integrantes del Concejo Ejecutivo en el sitio web por el tiempo que dure la suspensión. El Concejo Ejecutivo revisará el incidente respecto al CoC para determinar si la suspensión afectará su posición en el Concejo Ejecutivo a largo plazo.

Comités, Grupos de Trabajo y Otras Interacciones¶

Se suspenderá la participación en todos los comités, comunidades y grupos de trabajo (African Task Force, Carpentries en LatinoAmérica, etc.).

Otras Interacciones¶

La capacidad de los miembros suspendidos de iniciar sesión en AMY para administrar sus propios perfiles u otras tareas se revocará durante la duración de su suspensión.

A continuación se presentan los recursos principales necesarios en varias facetas de la comunidad de las Carpentries.

EVALUACIÓN¶

Evaluación del estudiante¶

La evaluación desempeña un papel clave para garantizar el éxito, la longevidad y la evolución de los talleres de The Carpentries. El objetivo principal de nuestros esfuerzos de evaluación es evaluar el impacto que estamos teniendo enseñando habilidades de datos en toda nuestra comunidad global. Nuestros esfuerzos de evaluación están destinados a guiar el desarrollo, implementación e instrucción de nuestros talleres. Estamos comprometidos a proporcionar realimentación dirigida a nuestra comunidad con respecto a nuestros objetivos de evaluación y usar la información recopilada de la evaluación para mejorar la forma en que enseñamos habilidades de datos y construimos comunidades de aprendizaje.

Nuestras herramientas de evaluación cubrirán el conocimiento del contenido, la autoeficacia y las estrategias metacognitivas. Además, la evaluación se realizará al final de cada taller y 6 meses después de un taller. Los datos se publican cada dos años, y se publicará una revisión anual de nuestro impacto en nuestro sitio web. El código fuente, los datos y la información adicional también están disponibles en este repositorio de GitHub.

Estamos comprometidos a apoyar a nuestros estudiantes, acomodar sus diferencias y alentarlos a crecer individualmente y convertirse en parte de nuestra comunidad de práctica. También los alentamos a comprender, reflexionar y controlar su propio aprendizaje.

Evaluamos a nuestros alumnos midiendo los cambios en sus actitudes, motivación y autoeficacia. Nuestra encuesta previa al taller incluye preguntas sobre las actitudes de los alumnos sobre el contenido cubierto en su taller y sus objetivos (es decir, lo que esperan aprender).

También hacemos preguntas para medir la mentalidad de los alumnos (crecimiento vs. fijo). Nuestro objetivo es medir su confianza en su capacidad de aprender, no necesariamente ejecutar tareas específicas.

Además, medimos la percepción de los alumnos sobre el crecimiento de sus habilidades y si planean recomendar nuestros talleres a sus colegas.

Nuestras encuestas previas y posteriores al taller se pueden ver aquí:

Encuesta previa al taller de Software Carpentry
Encuesta posterior al taller de Software Carpentry
Encuesta previa al taller de Data Carpentry
Encuesta posterior al taller de Data Carpentry
Encuesta previa al taller de Library Carpentry
Encuesta posterior al taller de Library Carpentry
Encuesta de impacto a largo plazo de Carpentries

Evaluación programática¶

En mayo de 2018, comenzamos a publicar regularmente informes de evaluación programática. Estos informes proporcionan una visión general de nuestras actividades en el taller y del instructor. Puede encontrar más información, incluidos los informes publicados, en nuestro sitio web.

Red de Evaluación¶

Acerca de¶

La Red de Evaluación se estableció en octubre de 2016 como un espacio para aquellos que trabajan en la evaluación dentro de los espacios de computación de código abierto o de investigación para colaborar y compartir recursos.

Lo que hacemos¶

La Red de Evaluación se reúne trimestralmente para discutir las mejores prácticas y proyectos en torno a la evaluación de resultados en computación científica. Para obtener información sobre reuniones anteriores, consulte las actas en el repositorio de la Red de evaluación.

Participa¶

Para unirse a la red de evaluación, envíe un correo electrónico a Kari Jordan a kariljordan@carpentries.org.

COMUNICACIÓN¶

The Carpentries Style Guide¶

This guide aims to provide a standard reference point when questions arise about style for The Carpentries - how we would prefer people to reference us, how best to render dates and times for a global community, when to use what capitalisation, and other questions of style.

We will adhere to a similar style on our website and in other material we make widely available such as blog posts, but not necessarily in lessons. To ensure that the style guide is as widely applicable as possible, UK English spellings and usage will be used in favour of American spelling.

The guide is a work in progress and additions are welcome. This version, compiled by Belinda Weaver, is a first draft.

Please note, as outlined in section C: The Carpentries, while sounding plural, is a singular entity. Therefore, when referring to The Carpentries, verbs should also be singular, e.g., ‘The Carpentries is …’. The full and correct title for the merged organization is The Carpentries. However, terminology such as ‘A Carpentries workshop …’ is acceptable.

A¶

abbreviations and acronyms¶

Generally use all capitals for initialisms, e.g., NSF, CEO, BIDS. When writing about an organisation or event within text, provide the acronym in brackets on first use, and use the acronym to refer to the organisation or event from then on. For example, ‘She was the chair of the National Science Foundation (NSF) … The NSF … ’

If an organisation is mentioned only once within a piece of text, say, in a blog post, it is not necessary to provide its acronym. Do not use acronyms without spelling these out first as country-specific acronym may be unfamiliar to members of our community.

accents¶

Use on non-English words when known. People’s names, in whatever language, should also be given appropriate accents where known, e.g., ‘Arsène Lupin was a jewel thief who never got to Bogotá or Angoulême.’

adverbs¶

Hyphens are not needed after adverbs ending in -ly, e.g. a hotly argued topic, a constantly evolving career, a recently published program, etc. Hyphens are needed with short and common adverbs, e.g., ever-faithful follower, ill-written script, much-quoted speech.

ampersand¶

In text and blog posts, use the ampersand in organisations’ names when the organisation does so, e.g., P&O, AT&T.

apostrophes¶

Indicates either a missing letter or letters (can’t, we’d, hadn’t) or a possessive (Siobhan’s script). The correct use of the apostrophe is important, as a misplacement or omission can alter a sentence’s meaning. Apostrophes are not needed in dates. Preferred form is 1990s, not 1990’s; the 70s, not the 70’s.

B¶

bullet points¶

Should ideally include a full stop after each one if it is not just a list of terms, i.e:

This is the first bullet point that covers a range of ideas.
This is the second that also ranges quite widely.
And this is the third and these are just examples.

But

Instructors
Trainers
Mentors

C¶

capital letters and capitalisation¶

titles
Render these with initial capitals, e.g., President Abraham Lincoln, Facebook’s CEO, Pope John Paul II, the Secretary-General Ban-Ki Moon.

government departments initial capitals, e.g., Department of Industry, Department of Health. Use lower case when not referring to a department by its proper name, e.g., ‘Senator Carr first led the Department of Industry. The department is now led by … ’

government agencies, public bodies, quangos
Render these with initial capitals, e.g., District Attorney’s Office, Human Rights Commission, the University of Florida. Use lower case when not referring to an organisation by its proper name, e.g., ‘She worked for the National Society of Coders. The society was founded … ’

lesson titles and episode names
Lesson titles and episodes within lessons should be rendered in Title case, i.e. all major words capitalised, e.g., Introduction to Data; Project Organization and Management for Genomics.

names of institutions
Render these with initial capitals, e.g., Gordon and Betty Moore Foundation, Smithsonian Institute, the United Nations, the European Union.

roles
Roles within The Carpentries are always capitalised. Therefore we use Instructor, Trainer, Maintainer, Mentor, and Curriculum Advisor. Helper and host are not capitalised as these are not official roles.

Carpentries¶

The Carpentries, while sounding plural, is a singular entity. Therefore, when referring to The Carpentries, verbs should also be singular, e.g., ‘The Carpentries is …’. The full and correct title for the merged organization is The Carpentries. However, terminology such as ‘A Carpentries workshop …’ is acceptable.

commas¶

Use commas to separate clauses in long sentences. ‘If the judges truly reflected on their decisions regarding the non-award of prizes in 2010, they would not find it hard to see why people objected to their choices.’

Commas can be used definitively. For example, in this sentence: ‘The developer, Sue Miller, is a keen coder,’ the use of commas indicates that there is only one developer.

Where no such definition is needed, e.g., ‘PyCon speaker Mary Clough won the award,’ no commas are needed since there are many speakers at PyCon, not just one.

A comma is also crucial to avoid ambiguity in examples such as this: ‘The report criticises the judges who have been accused of favouritism.’ A comma after ‘judges’ would have made it clear that all judges have been accused of favouritism. Without the comma, the sentence implies that only some judges have been criticised.

See also Oxford comma.

company names¶

Company names are always singular, e.g., ‘Twitter is …’, ‘Amazon Web Services is …’

D¶

dates¶

Our style is 21 July, 2011 (day month year).

Other renderings: ‘In the 21st century’ but ‘21st-century science’.

Use figures for decades, e.g., the 1990s, the radical 60s, etc. Do not add an apostrophe to decades, i.e. 1990s, not 1990’s; the 70s, not the 70’s.

See also times.
See also seasons.

E¶

e.g.¶

include full stops, and always follow with a comma, whether you are using the abbreviated form, e.g., or the written-out version, for example.

etc.¶

Include final full stop.

F¶

figures¶

Always spell out in writing the numbers from one to nine. Use numerals for numbers 10 to 999,999, and thereafter go back to writing numbers out in full, e.g., one million readers, eight billion people, but when the first number is above nine, you can go back to figures for that first part, e.g., 20 million lines. Spell out ordinals from the first to the ninth, e.g., third, fifth, and thereafter use 10th, 31st, etc.

first name, forename, given name¶

These terms to be used in preference to the term ‘Christian name’, which might offend non-Christians. Use first names the first time someone is mentioned, but not subsequently, e.g., ‘Mary Brown came late to programming … Brown later went on to develop several well-known programs.’

Avoid using initials rather than a name, unless that is how a person is best known, e.g., J. K. Galbraith.

foreign accents¶

If possible, use the correct accents on people’s names in any language, e.g., Sven-Göran Eriksson (Swedish), Béla Bartók (Hungarian), Phượng Nguyễn (Vietnamese).

foreign names¶

The French (or French origin) de, d’, des, la, les or le and the Dutch van are normally lowercase when the name is fully written out, e.g., Marianne d’Alpuget, Erik van der Walden, but capitalised when written without forenames, e.g., D’Alpuget, Van der Walden.

foreign words and phrases¶

Italicise these and provide accents where applicable, e.g., bête noire. In the case of frequently used foreign terms in accepted English usage, e.g., avant garde, vis a vis, vice versa, you do not need to italicise.

fractions¶

Render as two-thirds, three-quarters, etc., but two and a half needs no hyphens.
See also figures.

H¶

honorifics and titles¶

Honorifics which denote occupations, e.g., Doctor, Professor, can initially be used within text or in blog posts. Drop honorifics and first names after the first mention and use surname only from then on, e.g., ‘Professor Gillian Kramer teaches … Kramer has spent a lot of time…’

Honorifics such as FRCS should not include full stops.

I¶

initials¶

Separate initials in names from each other with spaces and full stops, e.g., J. K. Galbraith.

-isation¶

not –ization, e.g., organisation, characterisation.

-ise¶

not -ize at end of word, e.g., characterise, sympathise, organise. One exception is capsize.

italics¶

Foreign words and phrases, and scientific names, e.g., Macropus rufus, Bufo marinus.

N¶

names¶

Do not use the terms Christian name, first name, or forename. Instead use given name or personal name. We will defer to people”s chosen spelling, choice of given name, punctuation, capitalisation, and name order (when known or obtainable).
See also foreign names.

numbers¶

Always spell out in writing the numbers from one to nine. Use numerals for numbers 10 to 999,999, and thereafter go back to writing numbers out in full, e.g., one million readers, eight billion people, but when the first number is above nine, you can go back to figures for that first part, e.g., 20 million lines. Spell out ordinals from the first to the ninth, e.g., third, fifth, and thereafter use 10th, 31st, etc.

When starting a sentence with any number, the number should be written out as words, e.g., ‘Twenty-five people attended the workshop.’ ‘Nineteen-ninety-five was not a leap year.’

O¶

Oxford comma¶

A comma before the final ‘and’ in lists. Straightforward lists (he wrote books, short stories and poetry) do not need the extra comma, but sometimes it can help the reader to know which bits go together, e.g., ‘she wrote in these genres – horror, mystery, cloak and dagger, and fantasy’, and sometimes it is essential for clarity and meaning, e.g.,

I spoke to my sisters, Olga Petrova, and Susanne De Vries (means I spoke to my sisters AND to Olga Petrova and Susanne De Vries)

I spoke to my sisters, Olga Petrova and Susanne De Vries (this wrongly implies that Olga Petrova and Susanne De Vries are the sisters in question.)

Carpentries style is to use the Oxford comma.

P¶

per cent¶

Please spell this out in text, e.g., not as %, and write as two words, not one.

Q¶

quotation marks¶

Use single quotes at the start and end of a quoted section, with double quotes for quoted words within that section. Place full stops and commas inside the quotes for a complete quoted sentence; otherwise the full stop comes outside, e.g.,

‘Anna said: “Your style guide needs updating,” and I said: “I agree.”’ ‘Anna said updating the guide was “a difficult and time-consuming task”.’

For parentheses inside direct quotes, use square brackets, e.g., The judges said, ‘We very much liked the work of Goran [Kovacs] from Croatia’.

quotations¶

Colons, rather than commas, should be used to introduce quotations from speeches or writings that run longer than a single sentence, e.g., Brown said: ‘Winning the Nobel Prize was a highlight. It will change my life. I can’t believe my luck.’

To introduce phrases or single sentence quotations, a comma is preferable, e.g., Brown said, ‘Winning the Nobel Prize was a highlight.’

R¶

roles¶

Roles within The Carpentries are always capitalised. Therefore we use Instructor, Trainer, Maintainer, Mentor, and Curriculum Advisor. Helper and host are not capitalised as these are not official roles.

S¶

scientific names¶

Render these in italics, with the first name, which denotes genus, having an initial capital, with the second, which denotes species, written in lower case, e.g., Aedes aegypti (yellow fever mosquito), Crocodylus porosus (Saltwater crocodile), Macropus rufus (Red kangaroo).

seasons¶

Avoid using seasons when discussing or announcing events, as seasons vary from hemisphere to hemisphere. What is Fall in the USA is spring in Australia. Use a month range instead, e.g., January to March, or use halves or quarters, e.g., ‘This happened in the first quarter of 2018’, ‘This is planned for the second half of the year.’
See also dates.

singular or plural?¶

Corporate entities take the singular: e.g., ‘The NSF has announced … ’ In subsequent references, use a singular pronoun: ‘It will cover the Olympics.’ The Carpentries is always singular.

square brackets¶

In text, square brackets are used for interpolated words in quotations, e.g., Olav Jonsson said, ‘Matthew [Brown] went to Capetown to address a conference.’

T¶

times¶

Times should be rendered in UTC in a 24-hour format, e.g., 12:00 UTC, 17:30 UTC, 09:00 UTC. Do not use local zones, e.g., PDT, AEST. If you want to make times meaningful for people in a range of time zones, use the Event Time Announcer (using your UTC time and date as the basis to create the event) to create a linkable time that will render locally for each person who uses it, e.g., 20 August, 2018 22:00 UTC: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Carpentries+Mentoring+Committee+Meeting+2&iso=20180820T22&p1=%3A&ah=1

Getting your news out there¶

The Carpentries have a number of mechanisms for pushing out news. These include:

Our newsletter, Carpentry Clippings, which appears every two weeks.
Our Facebook page, which community members are welcome to follow and comment on.
Twitter feeds for The Carpentries, Software Carpentry, Data Carpentry, and Library Carpentry.

If you would like us to post an event, a job vacancy or a new publication of interest to the community in our newsletter, on Twitter, or on Facebook, email team@carpentries.org with For Newsletter, For Twitter, or For Facebook as the subject line.

Submitting blog posts¶

The Carpentries welcomes blog posts from our community members including workshop host sites, instructors, learners, and more.

How to Contribute a Blog Post to The Carpentries blog¶

If you wish to contribute a blog post, please work in https://github.com/carpentries/carpentries.org, which can be viewed at https://carpentries.org/blog/.
Posts go in the _posts folder.
Posts need to be created in Markdown and named according to this convention:

YYYY-MM-DD-filename.md

e.g.

2018-04-29-book-review-teaching.md

In order to render correctly, posts need to have a header block, which should be created like this example, e.g.

---
layout: page
authors: ["Tracy Teal", "Belinda Weaver"]
teaser: "New website for access to all things Carpentries"
title: "Launching The Carpentries Website"
date: 2018-04-25
time: "09:00:00"
tags: ["Website", "Communications"]
---

Separate the header block from the post text by inserting a new line.

All fields should be filled in. If there is more than one author, separate the author names like this: ["Name 1", "Name 2"].
Images should be uploaded to the images folder. Images should be linked using Markdown, and paths to the image should be relative.

Example:
```
![Image Description]({{ site.filesurl }}/images/myimage.jpg)
```
A web link should be used for images hosted elsewhere. Please be sure you have rights to use this image before including it.

Example:
```
![Image Description](https://web_address/pathway_to_full_image_filename)
```
If you are not sure how to add images in Markdown format, look at an existing post with a locally hosted image and copy the formatting from there.
Once you have previewed your file, commit the Markdown file to your fork and start a Pull Request. We automatically run tests using TravisCI on your Pull Requests. Please review your pull request a few minutes after you”ve submitted it to make sure those tests have passed. These tests look for valid YAML headers and make sure that the post will build properly. Once tests have passed, Carpentries staff will review and merge your Pull Request or reach out to you with more questions.

Alternative Ways to Post¶

If you are new to GitHub and want to submit a blog post without using this workflow, you can submit it through this form and we will post it to the blog for you.

If you wish to submit a blog post about a favourite tool or research workflow, you can submit the post through this form and we will post it on the blog for you.

How to Contribute a Blog Post to Data Carpentry¶

If you wish to contribute a blog post, please work in https://github.com/datacarpentry/datacarpentry.github.io, which can be viewed at http://www.datacarpentry.org/blog/.
Posts go in the _posts folder.
Posts need to be created in Markdown and named according to this convention:

YYYY-MM-DD-filename.md

e.g.

2017-07-10-assess_report.md

In order to render correctly, posts need to have a header block, which should be created like this example, e.g.

---
layout: post
subheadline: "Lessons"
title: Data Carpentry Genomics and Asssessment Hackathon
teaser: "Announcing a Data Carpentry Genomics and Assessment Hackathon"
header:
   image_fullwidth: "light-blue-wood-texture.jpg"
categories:
   - blog
comments: true
show_meta: true
authors: ["Tracy Teal", "Belinda Weaver"]
---

Separate the header block from the post text by inserting a new line.

Subheadline is an optional field, as is teaser, but the other fields should be filled in. If there is more than one author, separate the author names like this: ["Name 1", "Name 2"].
Images should be uploaded to the images folder. Images should be linked using Markdown, and paths to the image should be relative.

Example:
```
![Image Description]({{ site.filesurl }}/images/myimage.jpg)
```
A web link should be used for images hosted elsewhere. Please be sure you have rights to use this image before including it.

Example:
```
![Image Description](https://web_address/pathway_to_full_image_filename)
```
If you are not sure how to add images in Markdown format, look at an existing post with a locally hosted image and copy the formatting from there.
Once you have previewed your file, commit the Markdown file to your fork and start a Pull Request. We automatically run tests using TravisCI on your Pull Requests. Please review your pull request a few minutes after you”ve submitted it to make sure those tests have passed. These tests look for valid YAML headers and make sure that the post will build properly. Once tests have passed, Carpentries staff will review and merge your Pull Request or reach out to you with more questions.

Alternative Ways to Post¶

If you are new to GitHub and want to submit a blog post without using this workflow, you can submit it through this form and we will post it to the blog for you.

If you wish to submit a blog post about a favourite tool or research workflow, you can submit the post through this form and we will post it on the blog for you.

How to Contribute a Blog Post to Library Carpentry¶

If you wish to contribute a blog post, please work in https://github.com/LibraryCarpentry/librarycarpentry.github.io, which can be viewed at https://librarycarpentry.org.
Posts go in the _posts folder.
Posts need to be created in Markdown and named according to this convention:

YYYY-MM-DD-filename.md

e.g.

2018-09-12-data-in-the-desert.md

In order to render correctly, posts need to have a header block, which should be created like this example, e.g.

---
layout: page
authors: ["Tracy Teal", "Belinda Weaver"]
title: "Data in the desert"
teaser: "Library Carpentry workshop at the University of Arizona"
date: 2018-09-12
tags: ["University of Arizona", "Library Carpentry", "The Carpentries", "Workshop"]
category: ["blog"]
---

Separate the header block from the post text by inserting a new line.

All fields should be filled in. If there is more than one author, separate the author names like this: ["Name 1", "Name 2"].
Images should be uploaded to the images folder. Images should be linked using Markdown, and paths to the image should be relative.

Example:
```
![Image Description]({{ site.filesurl }}/images/myimage.jpg)
```
A web link should be used for images hosted elsewhere. Please be sure you have rights to use this image before including it.

Example:
```
![Image Description](https://web_address/pathway_to_full_image_filename)
```
If you are not sure how to add images in Markdown format, look at an existing post with a locally hosted image and copy the formatting from there.
Once you have previewed your file, commit the Markdown file to your fork and start a Pull Request. We automatically run tests using TravisCI on your Pull Requests. Please review your pull request a few minutes after you”ve submitted it to make sure those tests have passed. These tests look for valid YAML headers and make sure that the post will build properly. Once tests have passed, Carpentries staff will review and merge your Pull Request or reach out to you with more questions.

Alternative Ways to Post¶

If you are new to GitHub and want to submit a blog post without using this workflow, you can submit it through this form and we will post it to the blog for you.

How to Contribute a Blog Post to Software Carpentry¶

If you wish to contribute a blog post, please work in https://github.com/swcarpentry/website, which can be viewed at https://software-carpentry.org/blog.
Posts go in the _posts folder, which is divided up first by year, e.g. 2017, and then by month, e.g. 07. Be sure to start creating your file in the correct folder.
Posts need to be created in Markdown and named according to this convention:

YYYY-MM-DD-filename.md

e.g.

2017-07-10-assess_report.md

In order to render correctly, posts need to have a header block, which should be created like this example, e.g.

---
layout: post
subheadline: "Assessment"
title: "Analysis of Software Carpentry Workshop Impact"
date: 2017-07-10
time: "08:00:00"
authors: ["Tracy Teal", "Belinda Weaver"]
category: ["surveys", "workshops", "impact", "assessment"]
---

Separate the header block from the post proper by a new line.

Subheadline is an optional field, as is time, but the other fields should be filled in. If there is more than one author, separate the author names like this: ["Name 1", "Name 2"]. Separate any categories the same way.
Images should be uploaded to the appropriate year in the files/<year>/<month> folder. Images should be linked using Markdown, and paths to the image should be relative.

Example:
```
![Image Description]({{ site.filesurl }}/2017/07/myimage.jpg)
```
A web link should be used for images hosted elsewhere. Please be sure you have rights to use this image before including it.

Example:
```
![Image Description](https://web_address/pathway_to_full_image_filename)
```
If you are not sure how to add images in Markdown format, look at an existing post with a locally hosted image or one with a web link and copy the formatting from there.
Once you have previewed your file, commit the Markdown file to your fork and start a Pull Request. We automatically run tests using TravisCI on your Pull Requests. Please review your pull request a few minutes after you”ve submitted it to make sure those tests have passed. These tests look for valid YAML headers and make sure that the post will build properly.

Alternative Ways to Post¶

If you are new to GitHub and want to submit a general blog post without using this workflow, you can submit it through this form and we will post it to the blog for you.

If you wish to submit a blog post specifically about a favourite tool or research workflow, you can submit the post through this form and we will post it on the blog for you.

Troubleshooting¶

The most likely reason posts fail to build is because of “rogue” characters in the YAML header. Rogue characters generally occur because material has been pasted in directly from programs like Word or Google documents. The most common rogue characters that cause issues are smart quotes (curly quote marks as opposed to plain ones), but others might be em or en dashes, mathematical or other symbols, or other characters that cannot be rendered in plain text by typing on a keyboard. Replace smart quotes with plain quote marks and smart em or en dashes with plain hyphens to avert any problems.

Boletín informativo (Newsletter)¶

Nuestro Newsletter, Carpentry Clippings, aparece cada dos semanas.

Publicación del Newsletter¶

Esta información está destinada al personal o miembros de la comunidad que han asumido la responsabilidad de publicar el Newsletter.

Cada Newsletter es una campaña en MailChimp

Para crear un Newsletter, inicie sesión en MailChimp y haga clic en Campaigns. Haga una copia del último boletín y cambie el nombre de la copia para reflejar la fecha actual (por ejemplo, Carpentry Clippings, 27 de marzo de 2018).

Verifique que el campo Para (To) esté configurado correctamente ya que va a x suscriptores del Newsletter.

Verifique que el campo De (From) esté configurado correctamente como proveniente de The Carpentries.

Asegúrese de que la fecha en la línea Asunto (Subject) se cambie a la nueva fecha del Newsletter.

Seleccione editar diseño para agregar contenido al newsletter. Cuando abra el newsletter, haga clic en el ícono del lápiz en el Newsletter de la izquierda para abrirlo y editarlo. (La edición se realiza dentro del panel derecho; el panel izquierdo muestra la vista pública a medida que se edita).

Elimine el contenido anterior y péguelo en el nuevo, dejando los encabezados para que el formato no se vea afectado.

Asegúrese de actualizar la fecha en la parte superior del correo electrónico también.

Resalte cada párrafo y haga clic en Borrar estilos si todo lo que está copiando aparece en negrita cuando no lo desee.

Agregue imágenes haciendo clic en el ícono Imagen en la ventana de edición. Las imágenes deben tener menos de 550 px de ancho para renderizarse correctamente. Se pueden redimensionar dentro de MailChimp trabajando con el estilo de imagen (image styling) y la ubicación de la imagen.

Vaya a Vista previa y prueba (Preview and Test) para obtener una vista previa del Newsletter antes de enviarlo. Esto incluye una vista previa de la versión de escritorio y móvil. Envíe un correo electrónico de prueba para obtener una vista previa en su cliente de correo electrónico.

Save and Close and schedule the newsletter to be sent. This should be set for Wednesday at 9 am Eastern time. Be sure it is set for AM, not PM. A confirmation message saying «Rock On! Your campaign has been scheduled» will be displayed, and a link to a published view of the newsletter will be displayed. Paste this link into the staff channel so staff have a chance to review the newsletter before it goes out.

The newsletter will now be locked. If any changes need to be made after ther newsletter has been scheduled, you will need to pause the campaign, make changes, and restart the campaign.

After a campaign has been paused and then restarted, it is important to doublecheck that the date and time for sending out the newsletter is still correctly set as this will often default to the current time, rather than the original scheduled time.

As soon as the newsletter has been sent out, move it to the Carpentry Clippings folder. This adds it to the searchable online archive findable through our website. To move it, check the box next to the newsletter and select the Carpentry Clippings folder when the Move to option appears.

Tips and Tricks¶

The Mailchimp editor is not entirely user-friendly. Formatting changes may appear in the edit window but not in the preview document. The easiest workaround for this is to:

Copy and paste text in the Mailchimp editor.
Select all text in the Mailchimp editor and click Clear Styles.
Select all text and set font to Arial 12 point.
Select the title («Carpentries Clippings, ») and set font to 18 pt bold.
Select each subheading one by one (Highlights from the Carpentries Community Calendar, Community News, etc.) and set font to 16 pt bold.
Select each item heading one by one and set font to 14 point regular.

Mailchimp customer service chat is hard to find on their website but quite responsive to requests for help.

Slack and Mailing Lists¶

There are many ways in which you can join our conversations:

The Discuss email list, which community members are welcome to join and post to.
Our other email lists are a combination of regional and topic-specific lists.
Our Slack channel, which community members are welcome to join. Click on «Channels» in the left panel to view all existing channels.

Carpentries Commons¶

El repositorio GitHub de Carpentries Commons es un lugar para compartir abiertamente material reutilizable, como texto para convocatorias de financiación (grants), redacción para solicitudes de empleo o de contrato indefinido (tenure track), diapositivas para conferencias, descripciones de talleres, copias promocionaled, etc.

El personal de The Carpentries tendrá acceso de escritura para agregar, editar y cargar material aquí. Otros miembros de nuestra comunidad deberán bifurcar el repositorio y someter pull requests.

Presentations¶

It”s great for community members to give presentations on The Carpentries! Include your work with The Carpentries in a presentation, or you”re more than welcome to give talks or discuss the organization in general.

There are some general Google slide decks as well as ones more tailored to particular topics or events. The General slide deck is CC0, so you”re welcome to use it how you wish. Please just keep attributions on individual figures or photos if they are there.

Scheduling Online Community Events¶

The Carpentries offers three Zoom rooms for public community events. Zoom rooms are available for events such as discussion sessions, teaching demos, and committee meetings.

General Room Usage and Links¶

Rooms are generally used as follows. However, any room can be used for other purposes if it is available. Links below will open Zoom and enter the respective room.

Room 1: Instructor Training
Room 2: Instructor Training backup
Room 3: Community events (teaching demos, discussion sessions, committee meetings, etc.)

Each room can have a host who will have privileges to mute people, create breakout rooms, etc. Please contact team@carpentries.org if you would like host privileges for an event.

Zoom Manual¶

The Carpentries online community events are held on Zoom. The Carpentries staff will set up host access to our Zoom rooms for people leading community events. No login is needed for event guests; however a browser plug in may be required.

If you are leading an event, you will be given host acccess to the event. This will give you extra privileges including the ability to mute participants and assign participants into breakout rooms. Only one person can be logged in as host at a time, and another person logging in as host will kick the original offline. However, the host can transfer host privileges to other participants if you need to trade host status with co-facilitators during the event.

All Carpentries online events are set up such that participants can enter the room without the host being present. If you ever get an error message saying you can’t join the room because you’re not the host, please contact The Carpentries staff immediately.

Host abilities:¶

“Mute” is in the lower left. To mute other participants, the host can go to “Manage Participants”, hover over a participant’s name, and click “mute”.
When the room host clicks “End Meeting” a dialogue box appears with three options: “Cancel”, “Leave Meeting” and “End Meeting for All”. Be careful not to end the meeting if you are leaving the room while the event is still active.
Only the host has the ability to create “Breakout rooms”. The button for this is on the lower left. Breakout rooms can be assigned automatically. By default, participants will be assigned to the same groups each time breakout rooms are used. You can change participants assignments manually if desired.
The host can move between breakout rooms and can send messages to all rooms simultaneously.

General tips:¶

“Gallery view” in the upper right toggles the display to show more participants videos.
“Share screen” is at the bottom middle of the screen. To end “share screen” you click the red button that will appear at the top middle of the screen when you are in screen sharing mode.
When you screen share, you have the option to share individual apps or your entire desktop. The default is the full desktop.
The Zoom chat is not stable (it is not saved across sessions or after going into breakout rooms). We highly recommend using the Etherpad or Google Doc chat instead.
If a trainee is using Linux and gets the error message «Can not start share, wayland has not been supported yet, please use x11 instead», have them log out of Zoom and log back in. On the login screen there is a gear with a dropdown menu there choose the option with x11.

Viewing Zoom Room availability¶

Zoom room calendar views are public - anyone can view whether a room is available. Only Carpentries staff members can actually book a room. If a room is available, please contact a staff member or team@carpentries.org if you would like to make a room reservation.

Room availability can be viewed below.

Red: Room 1
Orange: Room 2
Green: Room 3

Placeholder: Embedded Zoom Room Calendar

Adding an Event to the Community Calendar¶

Note while anyone can view room availability, only Carpentries staff members may book events or reserve a Zoom room.

To add an event to the Community Calendar and book a Zoom Room for it:

Give the event a meaningful title («Demos» is not as good as «Instructor Training Teaching Demos»)
List the time zone in UTC - not your local time zone. Events set in local time zones do not always correctly adjust for daylight savings time.
Add a description, including a link to the relevant etherpad or other document.

Event Setup

Select a room.

View Rooms
- Each available room will be listed. If you are scheduling a recurring event, any future conflict will prevent a given room from being listed as available.
- Multiple rooms can be selected for a single event.
- Click on a room to select it. The Zoom link will now appear in the location.
Reserved Room
- If you select a room and immediately remove it, it may not appear as available again until you close out the edit event screen and enter it again.
- Save the event.
- The event will now show up on the Carpentries Community Calendar and the Zoom Rooms Calendar.

Be sure to complete the above steps in order (i.e., do not select a room before setting the exact date and time).

Creating a Zoom Room Option on Google Calendars¶

This will only need to be done once for each new room. This is already done for Zoom Rooms 1, 2, and 3. If additional Zoom rooms are added, they will need to be set up here. This must be done by someone with admin access to The Carpentries” Google console.

Go to the Google admin console. Click on «Buildings and Resources» and then click «Edit Resources» under «Resource Management.»

You will see all existing buildings and rooms listed. This feature is meant for physical buildings; we are using it for virtual videoconferencing rooms. One «building» is set up, called «Zoom Rooms» that contains three resources – Zoom Room 1, Zoom Room 2, and Zoom Room 3.

To add a new «room» in this «building» - click on the yellow plus sign next to «Resources.» Fill out the following information:

Category: (no category set)
Type: leave blank
Building: Undefined
Floor: Undefined
Floor section: leave blank
Resource name: Link to the Zoom Room
Capacity: 100 (standard for all Zoom rooms)
Features: leave blank
User visible description: Note what this room is used for.

When done, click «ADD RESOURCE» and this new room should be on your list of rooms. This room will now be available for scheduling events as described above.

Etherpads¶

Uso General¶

The Carpentries ofrece el uso de nuestros etherpads como una herramienta colaborativa para tomar notas durante los talleres, eventos de capacitación y otros eventos relacionados con The Carpentries.

Se puede crear un nuevo etherpad agregando un nombre descriptivo a la url https://pad.carpentries.org/, por ejemplo https://pad.carpentries.org/committeename.

Los etherpads se sincronizan a medida que se escribe, de forma que todos pueden ver el mismo documento. Esto permite a todos colaborar sin problemas en los documentos.

El uso de este servicio está restringido para los miembros de la comunidad de The Carpentries; no para uso general (para eso, visite etherpad.wikimedia.org).

Se espera que los usuarios sigan nuestro código de conducta. Todo el contenido está disponible públicamente bajo la Licencia Creative Commons Attribution.

Puede encontrar una lista de todos los Etherpads de uso común en nuestro pad de pads. Esta lista se crea manualmente y, por lo general, solo incluye pads de interés para la comunidad en general. No incluirá pads específicos para eventos individuales o grupos.

Solución de Problemas¶

Mientras que los etherpads son generalmente confiables, se puede encontrar un etherpad que no cargue como se esperaba. En este caso, puede intentar agregar/exportar /html a la url de un etherpad. Por ejemplo, si https://pad.carpentries.org/committeename no carga, es posible recuperar su texto yendo a https://pad.carpentries.org/committeename/export/html. Este contenido de texto se puede copiar y pegar en un nuevo etherpad. Tenga en cuenta que esto no preservará la historia del etherpad. El chat a menudo seguirá activo en el etherpad que no funcionó, por lo que se recomienda que se vincule al nuevo etherpad en el chat del etherpad qu no funcionó.

Si surgen otros problemas con el etherpad, contáctenos a team@carpentries.org y un miembro del equipo lo ayudará a solucionar el problema.

Logos¶

Los nombres «The Carpentries», «Software Carpentry», «Library Carpentry» y «Data Carpentry», y sus logotipos asociados, todos están registrados.

No se necesita aprobación para usar estas marcas comerciales en algunos casos. Es permitido siempre que se declare con precisión que un taller es un taller de The Carpentries, o que un taller está basado en materiales de The Carpentries. Es aceptable usar la marca registrada si se reconoce o acredita The Carpentries en artículos de revistas, presentaciones de conferencias y conferencias, convocatorias de financiación (grants) y similares. En estos casos se puede usar el término «The Carpentries» o los logotipos sin alterar, sin necesidad de nuestra aprobación previa.

Si tiene dudas sobre el uso previsto de las marcas comerciales, escríbanos a team@carpentries.org y uno de los miembros de nuestro equipo lo asesorará.

Links para los logos¶

PARA INSTRUCTORES¶

Este material es para Carpentries Instructors actuales y aspirantes. Aquí puedes encontrar material sobre cómo convertirte en Instructor, cómo desarrollarte en este rol y sobre oportunidades para establecer vínculos que ofrece nuestra comunidad.

¡Gracias Instructores!

¡Estamos muy agradecidos con nuestra comunidad de Instructores! Desde las que enseñan una o dos veces al año hasta las que organizan programas completos, desde las que recién comienzan a involucrarse hasta las que están profundamente integradas como mentoras, organizadoras de discusiones, miembros del comité y de las Task Force, y entrenadoras de Instructores: CADA Instructora ayuda a hacer the Carpentries lo que es. ¡Gracias!

Para quienes ya son instructores de Carpentries¶

Desarrollo profesional para Instructores¶

Dando la bienvenida y orientando a nuevos Instructores de nuestra comunidad, y enriqueciendo y construyendo habilidades y comunidad entre quienes ya son Instructores, tenemos alternativas para acompañarte.

Mentoreo y desarrollo¶

El Comité de Desarrollo de Instructores (formalmente conocido como Mentoring Subcommittee) gestiona el programa de mentoreo, que acompaña a los Instructores a medida que avanzan en su entrenamiento, habilidades de enseñanza, desarrollo de curriculum y otras actividades relacionadas con la comunidad.

Discusiones de la comunidad¶

Estas sesiones de una hora de duración están organizadas por el Comité de Desarrollo de Instructores y cumplen una serie de propósitos. Los Instructores entrenados las utilizan en la etapa final de su entrenamiento. Allí pueden hacer preguntas sobre la enseñanza de talleres y otras cuestiones, y obtener consejos de Instructores más experimentados. Todos los encuentros son llevados adelante por voluntarios. Los Instructores que se están preparando para enseñar pueden asistir para hacer preguntas, obtener recomendaciones y conocer ejemplos o analogías que podrían serles útiles. Instructores que han tenido una experiencia reciente de enseñanza pueden asistir para contar acerca de qué funcionó bien y qué podría haber funcionado mejor, para así planificar mejor la siguiente oportunidad. Las sesiones son coordinadas a través del etherpad.

Grupos de mentoreo¶

El mentoreo es una oportunidad de desarrollo profesional que The Carpentries pone a disposición a su creciente conjunto de Instructores para ayudar a los miembros de la comunidad a aprender y crecer. No importa si eres un Instructor nuevo preparándote para enseñar tu primer taller, un Instructor experimentado deseando ofrecer talleres en una comunidad nueva, o un Instructor interesado en involucrarse con el desarrollo y mantenimiento de lecciones, los grupos de mentoreo te ayudarán a ganar la confianza, habilidades técnicas y de enseñanza que necesitas para alcanzar tu objetivo. Los grupos de mentoreo se organizan a intervalos regulares. Ve a la sección de Grupos de mentoreo para obtener más información.

Campeones de Carpentries¶

Si estás interesada en construir una comunidad local, entonces considera unirte a los Campeones The Carpentries. Las teleconferencias para Campeones se organizan trimestralmente, y allí puedes oír de miembros de la comunidad más experimentados sobre estrategias que puedes utilizar para construir las bases de una comunidad. Ya existe un manual de Carpentries Community (“Carpentries Community Cookbook”), con “recetas” que puedes adaptar a las necesidades de tu entorno local. Hay una lista de correo electrónico de Campeones y también puedes unirte al canal #champions en Slack.

Lista de encuentros¶

Si asistirás a una conferencia o evento y quieres establecer vínculos con otros miembros de la comunidad Carpentries, por favor añade los detalles del evento y tus propios datos de contacto al etherpad de encuentros.

Perfil del Instructor¶

Mantenemos un registro de la información de cada instructor en nuestro sistema de base de datos AMY. Para mantener tu perfil AMY al día puedes acceder al sistema usando tu cuenta de GitHub. Si no puedes acceder a AMY, por favor envía tu nombre de usuario de GitHub a team@carpentries.org, y el equipo administrativo actualizará tu perfil permitiéndote el acceso. Los perfiles nos ayudan a identificar instructores para los talleres, y a llevar un registro de cuándo y dónde dieron talleres. Adicionalmente solicitamos información social, tu cuenta en ORCID y sitios web personal. Si consientes, toda esta información será publicada en la página de instructores en nuestro sitio web. Ser incluido en nuestro sitio web es estrictamente opcional. Para ello debes ingresar a tu perfil de instructor y tildar el casillero «consent to publish profile», de otra forma tu información no será incluida en tu perfil público.

Enseñanza¶

Preparando un taller¶

Diríjase a la sección Teaching and Hosting para obtener instrucciones en la preparación y ejecución de un taller. Ahí encontrarás enlaces a nuestas listas de control y descripciones de las encuestas que utilizamos para evaluar las experiencias de estudiantes e instructores. También echa un vistazo a nuestra sección de administración de talleres.

Creación del sitio web de un taller¶

Para instrucciones acerca de cómo crear el sitio web de un taller consulte la página de inicio de la plantilla de talleres.

Otras formas de colaborar¶

Existen muchas otras manera en las que puedes colaborar con The Carpentries además de enseñar en talleres. Esto incluye ayudar a mantener las lecciones actualizadas convirtiéndote en mantenedor; coordinar talleres Carprentries, ayudando así a que crezca la oferta de instructores haciendo la tarea de Entrenador; participar en listas de correo electrónico como Discuss o de temas o regiones particulares; participar en los comités, por ejemplo, de Desarrollo de Instructores; participar en alguna de las TaskForces como CarpentryCon; colaborar traduciendo nuestras lecciones a otros idiomas; llevar adelante un grupo de mentoreo; coordinar sesiones de discusión, y la lista sigue. Puedes encontrar contactos para áreas específicas de trabajo en la página Involúcrate. Por favor envíanos un correo electrónico si quieres colaborar pero no estás seguro con quién contactar.

Conviértete en instructor Carpentries¶

¡Siempre estamos felices de dar la bienvenida a nuevos Instructores a nuestra comunidad!

Un Instructor Carpentries es una persona que ha completado nuestro taller de entrenamiento de 2 días, y ha cumplido con las tareas que se requieren para finalizar su entrenamiento («checkout process») para convertirse en un instructor certificado («badged»). Nuestro entrenamiento de instructores tiene los siguientes objetivos generales:

Introducir a los participantes a prácticas de enseñanza basadas en evidencia.
Enseñar a los participantes a crear un ambiente positivo para los estudiantes en los talleres.
Brindar oportunidades para que los participantes practiquen y construyan habilidades de enseñanza.
Ayudar a los participantes a que se integren a la comunidad The Carpentries.
Preparar a los participantes para usar estas habilidades de enseñanza en los talleres Carpentries.

¿Quiénes son los instructores?¶

Nuestra comunidad de Instructores incluye investigadores, editores, científicos de datos y muchos otros de un rango amplio de contextos, disciplinas, etapas de formación y países. Muchos de nuestros instructores son gente que asistió a un taller Carpentries y que fueron estimulados a participar y entrenarse como Instructores para compartir las habilidades aprendidas y que hoy usan en sus trabajos.

¿Qué conocimiento previo se requiere?¶

Algunos aspirantes a instructores se preocupan por cuánto conocimiento deberían tener sobre el material que enseñarán para poder convertirse en Instructores. Si bien nuestros Instructores tienen experiencia en al menos alguna de nuestras áreas de contenido como shell, git, SQL, Python, R, OpenRefine o software de planilla de cálculo, algunos son relativamente nuevos en estas habilidades.

Algunos pueden sorprenderse al escuchar que sentirse un «experto» en cuanto al contenido ¡no es necesario para convertirse en Instructor! Alentamos a nuevos estudiantes a que sean Instructores. Esto es debido a que:

a) often the best people to teach a novice level curriculum are not experts, but rather people who have recently been novices themselves (we”ll discuss why this is so in the training!) b) teaching is actually an excellent way to become more familiar with the material.

Y debido a que los Instructores Carpentries nunca enseñan solos ¡si te trabas siempre contarás con ayuda!

Muchos Instructores van aumentando gradualmente la cantidad de lecciones que se sienten cómodos enseñando. No conocer el material no debería impedirte de postular a ser Instructor. Sin embargo, si quieres postularte te será de utilidad haber participado de un taller Carpentries, como estudiante o ayudante, y estar familiarizado con al menos alguno de los temas. De esa forma sabrás más sobre lo que implica ser Instructor y podrás evaluar si el estilo y método de enseñanza de taller es adecuado para ti. Si decides postularte, el haber participado de un taller será considerado positivamente en nuestra rúbrica de puntaje.

Motivación para entrenarse como Instructor¶

Las personas se entrenan para ser Instructores por muchas razones:

Para mejorar sus vidas. Al enseñar a colegas cómo construir y compartir mejor software los Instructores ayudan indirectamente a crear elementos que ellos también podrán usar.
Para construir una reputación. Enseñar un taller es una excelente forma de presentarse a lugares en los que eventualmente se querría trabajar, y de entrar en contacto con potenciales colaboradores.
Para practicar enseñar. Entrenamos más instructores cada año y les damos la oportunidad de enseñar, lo que es útil para aquellos que planean carreras académicas.
Para ayudar a participar a personas de diferentes entornos. Algunos de nuestros Instructores se involucran en parte porque desean que la ciencia computacional incluya personas en rangos más amplios de contextos.
Enseñar te hace aprender cosas nuevas, o cosas que ya sabías pero en un mayor detalle. Mira este trabajo científico: «Graduate Students” Teaching Experiences Improve Their Methodological Research Skills».
Para hacer del mundo un lugar mejor.
Para adquirir nuevas habilidades para sus carreras. Los instructores desarrollarán un conjunto de habilidades. Puedes usar y reformular este texto para usar en pedidos de subvenciones, postulaciones laborales y para tu CV.
Para incorporarse a una comunidad interesada por la enseñanza inclusiva de habilidades computacionales.
Para divertirse. ¡Es realmente divertido!

Lee más acerca de las motivaciones para ser Instructor en el informe de la Dra. Beth Duckles: Value of Software Carpentry to Instructors.

Pasos para convertirte en Instructor¶

Cualquiera que comparta los objetivos de The Carpentries es bienvenido a postularse al entrenamiento de Instructores. Sin embargo, no podemos garantizar entrenar a todos los postulantes. A pesar de que nos encantaría poder ayudar a todos, debemos priorizar las personas que forman parte de nuestras organizaciones miembro, quienes han proveído fondos para asegurar que puedan desarrollar Instructores en sus organizaciones.

Es así que, si no perteneces a una institución afiliada a The Carpentries, puede que debas esperar un largo tiempo para ser entrenado como Instructor.

Periódicamente revisamos y calificamos las postulaciones que nos envían. Cuando existen plazas para entrenamiento que no son ocupadas por miembros de las instituciones miembro, invitamos a postulantes según el orden de puntaje, para completar todas las plazas vacantes.

¿Cómo calificamos a los postulantes? Mira nuestra rúbrica de puntajes.

Para solicitar entrenamiento de Instructor, por favor completa este formulario.

Ocasionalmente se ofrecen eventos de entrenamiento abiertos al público, que pueden ser anunciados por la lista de correo electrónico, newsletter, Carpentry Clippings o por nuestra cuenta de Twitter. Para todos los demás eventos, a medida que se habilitan plazas los postulantes que forman parte de la lista de espera son personalmente invitados a asistir.

GOVERNANCE¶

The Carpentries Bylaws¶

1. Propósito¶

Mission: The Carpentries builds global capacity in essential data and computational skills for conducting efficient, open, and reproducible research. We train and foster an active, inclusive, diverse community of learners and instructors that promotes and models the importance of software and data in research. We collaboratively develop openly-available lessons and deliver these lessons using evidence-based teaching practices. We focus on people conducting and supporting research.

2. Lesson Program Membership¶

Overview¶

Lesson Programs are collections of lessons which comprise one or more Carpentries workshops and the leadership guiding their development and implementation. The following requirements outline the general expectations associated with Lesson Programs; additional detail can be found in the Lesson Program Policy.

Eligibility for Lesson Program Membership¶

The Executive Council is responsible for assessing a prospective Lesson Program for acceptance into The Carpentries, which requires a majority vote. The Executive Director will be responsible for developing and implementing policies related to Lesson Program incubation and assessing the ability of the staff and community to meet obligations associated with new Lesson Programs.

Roles and Responsibilities of Lesson Programs¶

A Lesson Program within The Carpentries should possess the following characteristics:

Intention and purpose for lessons that align with The Carpentries mission and vision
Goals and objectives for lessons and/or workshops that are distinct from other Lesson Programs
Service to a particular audience of learners and instructors
Evidence of community member commitment to Lesson Program governance (see below), lesson maintenance, and curriculum development

Governance of Lesson Programs¶

Each Lesson Program will have a Lesson Program Committee to serve as community governance organization and act as a point of contact with The Carpentries Executive Council and staff. The Lesson Program Committee will provide the Executive Council with an annual report of Lesson Program operations.

Resignation and Termination of Lesson Programs¶

In the event that either the Lesson Program or The Carpentries is not fulfilling its obligations under the Lesson Program Policy, or the mission and vision of The Carpentries and the Lesson Program no longer align, the relationship between the Lesson Program and the Carpentries can be terminated. The Executive Council may decide to retire the Lesson Program through a majority vote, or the Lesson Program Committee can choose to discontinue the Lesson Program”s association with the Carpentries. In either case, notice must be given to the other organization to arrange for separation of responsibilities and resources.

3. Organizational Membership¶

Eligibility, Rights, and Termination of Organizational Members¶

Member Organizations have committed to supporting the maintenance and growth of the Carpentries community according to the specific details outlined in each institution”s Membership Agreement. In general, Member Organizations financially support The Carpentries in exchange for priority access to instructor training and guidance in building training capacity at their organization.

4. Individual Voting Membership¶

The Carpentries community includes many opportunities for involvement representing variable levels of commitment. All individuals participating in community activities are required to conform to the Code of Conduct. Individuals may choose to commit to serving in one or more formal roles in the community, such as instructor, trainer, or maintainer, as defined by The Carpentries Handbook.

Eligibility, Rights, and Termination for Voting Members¶

Individuals who satisfy at least one of the following conditions are eligible for Voting Membership, as assessed in a yearly timeframe associated with the dates of the election (Dec 1 to Nov 30):

Every individual who has completed instructor or trainer certification in the past year
Every individual who has completed their instructor certification in the last two years and has taught at least one workshop of The Carpentries
Every individual who is a certified instructor and has taught at least two workshops of The Carpentries in the past two years
Any individual who has participated on a committee, served as a mentor or maintainer, or otherwise made a significant contribution, to any Lesson Program or The Carpentries organization in the past year, as determined on a case-by-case basis by the Executive Council, and thus is considered active in the community

The Executive Director is not eligible for Voting Membership.

All individuals who satisfy conditions for 1-3 above are automatically tracked and will receive Voting Membership. Any individual who only satisfies condition 4 may receive Voting Membership by contacting The Carpentries staff within a reasonable timeframe prior to release of ballots to confirm their participation, as dictated by the Election Policy.

Any individual who no longer wishes to be affiliated with The Carpentries or included as a Voting Member must inform The Carpentries staff for removal from membership lists. Voting Membership may be terminated by a majority vote of the Executive Council for individuals who are recommended for termination by the Code of Conduct committee or Executive Director for non-compliance with The Carpentries policies or violation of the core values of The Carpentries.

5. Executive Council¶

General Powers¶

As the highest leadership body of the organization, the Executive Council is responsible for:

determining the mission and purposes of the organization
selecting the Executive Director and evaluating their performance
strategic and organizational planning
ensuring strong fiduciary oversight and financial management
identifying revenue streams and resource development
approving and monitoring The Carpentries programs and services
enhancing The Carpentries public image
assessing its own performance as the governing body of The Carpentries

Responsibilities of Executive Council Members¶

Each Member of the Executive Council is responsible for:

knowing the organization’s mission, policies, programs, and needs
reading and understanding the organization’s financial statements
serving as active advocates and ambassadors for the organization necessary for The Carpentries to advance its mission
leveraging connections, networks, and resources to develop collective action to fully achieve the Carpentries’ mission
helping identify personal connections that can benefit the organization’s fundraising and reputational standing, and can influence public policy
preparing for, attending, and conscientiously participating in Executive Council meetings

Number, Tenure, Requirements, and Qualifications¶

The Executive Council will be composed of nine (9) Members, each serving a two-year term, without limit on the number of terms. Member terms will begin on February 1st, except when filling between-election vacancies (see below). Five (5) Members of the Executive Council will be elected by the Executive Council (hereafter referred to as «Council-elected Members»). The other four (4) Members will be elected by the Membership of the organization («Community-elected Members»). No employer may have more than two elected or appointed representatives on the Executive Council, and Carpentries staff are not eligible to serve as Executive Council Members. The Executive Council has the final say in determining whether people are working for the same employer. If more than two people who are working for the same employer are elected, they must step down one by one to be replaced by other nominees in order of the number of votes received.

Regular Meetings and Quorum¶

The Executive Council must meet at least ten (10) times per year, either in person or online. Quorum for meetings of the Executive Council is five Members, including at least one Council-elected and one Community-elected Member.

Compensation¶

Members of the Executive Council shall not receive compensation from the Organization for their service, with the exception of administrative support, travel, and accommodation costs related to their duties on the Executive Council.

Confidentiality¶

Members of the Executive Council will sometimes discuss or be made aware of information or activities that may be sensitive to share publicly (e.g. salary information). Executive Council Members are expected to treat such information confidentially and to disclose such information to those outside the Executive Council only when the Executive Council has agreed that such dissemination is appropriate.

Removal¶

If a Member of the Executive Council consistently fails to meet the obligations outlined above, they may be removed by a vote of three-quarters (3/4) of the other Members of the Executive Council. A vote to remove a Member must be announced in writing to the entire Executive Council at least ten (10) days in advance of the vote. A vacated Executive Council seat will be filled following the Between-election vacancies procedure outlined in the Nominations and Elections section.

6. Nominations and Elections¶

Overview¶

Four (4) to five (5) of the nine (9) Members of the Executive Council will be elected each year, either by the community (Community-elected) or by the Executive Council (Council-elected). A general timeline for elections will occur annually as follows:

Mid-October: Executive Council announces election, soliciting self-nominations for Community-elected Members and recommendations for Council-elected Members, and identifying areas of expertise desired by the Council
Late November: Self-nominations and recommendations close and the Executive Council hosts Community Calls to discuss the election and introduce candidates for Community-elected Members
Early December: Voting Members vote for Community-elected Members
Mid-December: Executive Council elects Council-elected Members and announces the Executive Council Members for the following year
February 1: Responsibility for governance is transferred to the new Executive Council

Community-elected Members¶

Two (2) Community-elected Members will be elected each year by the Voting Members of The Carpentries. Any Voting Member of The Carpentries may stand for election by announcing their candidacy as dictated by the Election Policy; Carpentries staff may not stand for election. If there are fewer than two candidates for the election, the current Community-elected Members will decide amongst them who will remain in office.

Elections will take place once every calendar year and no later than 30 days before the new Executive Council becomes active (February 1). Each Voting Member may vote for as many candidates as there are Community-elected Member seats to be filled. The candidates who receive the highest number of votes will be elected into the Executive Council.

Council-elected Members¶

Two (2) or three (3) of the Council-elected Members will be elected each year. The Executive Council must consider at least one more candidate than the number of Council-elected Member seats to be filled. Anyone may recommend candidates for Council-elected positions.

Executive Council selects, by anonymous vote, the Council-elected Members from among the recommended candidates. Appointed Members will abstain from voting when they themselves are recommended for reappointment. Each Executive Council Member may vote for as many individuals as there are Council-elected Member seats to be filled. The individuals with the highest number of votes will be appointed. This vote will not take place until after the voting results for Community-elected Members are known and no later than December 15th.

Between-election vacancies¶

If an Executive Council seat of a Community-elected Member becomes vacant after the beginning of the year but before the first of October, the Executive Council will strive to fill the seat with one of the non-elected nominees from the previous year’s election, in the order of the number of votes they received. If this effort fails, the Executive Council may appoint a Voting Member to fill the seat.

If an Executive Council seat of a Council-elected Member becomes vacant after the beginning of the year but before the first of October, the Executive Council will strive to fill the seat with another eligible Voting Member.

In both of these cases, the vacancy will be filled by the new Executive Council Member for the remainder of the original term only.

7. Officers¶

Responsibilities of each officer of the Executive Council are as follows:

Chair¶

Oversee regularly scheduled Executive Council meetings and call special meetings as necessary
Work in partnership with the Executive Director to make sure that resolutions are carried out and issues addressed by the Executive Council as needed
Prepare the agenda for Executive Council meetings
Oversee the search for a new Executive Director (when applicable)
Coordinate the Executive Director”s annual performance evaluation

Vice-Chair¶

Understand the responsibilities of the Executive Council Chair and be able to perform these duties in the chair”s absence
Participate in leadership of the Executive Council by chairing special committees and carrying out assignments as requested by the Chair
Ensure the circulation of agendas, minutes, and other communications to the Executive Council
Ensure that any Executive Council members who have been given tasks know what it is they have been asked to do
Check that action has been taken following decisions at previous meetings

Secretary¶

Ensure that someone is assigned to and takes minutes during all official EC meetings
Revise minutes for publication
Report decisions, policy, and action items in formal minutes published publicly (when applicable)
Receive all communication from community to Executive Council and relay as necessary

Treasurer¶

Assist the Executive Director in preparing financial reports for both the Executive Council and community at large
Assist the Executive Director in preparing the annual budget and presenting the budget to the Executive Council for approval
Answer Executive Council Members’ questions about the budget and finances

Election of Officers¶

All officers must be members of the Executive Council. Officers will be selected via majority voting of the Executive Council at the first regular meeting of the year.

Removal of Officers¶

If an officer steps down, is removed from the Executive Council, or is otherwise unable to meet their obligations as determined by the Chair and/or Vice Chair, a new officer will be elected from the remaining Executive Council Members.

8. Committees¶

Committee Formation¶

Committees are organized by the Executive Council to carry out specific tasks as delegated on an ongoing basis. Task forces are similar in that they perform specific tasks, but on a short-term basis (e.g., a year or less) and may be organized by staff. Both committees and task forces are overseen by staff, although the Executive Council may request quarterly reports on each group’s activities.

9. Staff¶

Executive Director¶

The Executive Director acts as the Chief Executive Officer of The Carpentries in accordance with its vision and mission as overseen by the Executive Council. The Executive Director provides oversight and overall management, planning, vision and leadership for all aspects of The Carpentries including programs, finances, resource development, human resources, member services, communications, and Executive Council development. The Executive Director assumes a leadership role in partnering with collaborating organizations, businesses, universities, foundations, government agencies, other nonprofits and supporters. The Executive Director works with the Executive Council to establish vision, policies, strategic focus, priorities, and general scope of programs The Carpentries will deliver, and communicates on progress towards these goals via an annual report.

The Executive Council is responsible for advertising and interviewing for the position of Executive Director. A majority vote of the Executive Council is required to hire or remove the Executive Director from their position.

10. Amendments¶

Bylaws¶

Any changes to these bylaws require a majority vote of the Executive Council. The Executive Council must re-approve these rules or an amended version every two years.

Update log:

Approved 2018-11-01 by the Executive Council

Lesson Programs¶

The Carpentries supports and maintains Lesson Programs. Lesson Programs are collections of lessons comprising one or more Carpentries workshops, serving distinct goals and audience, and the leadership guiding their development and implementation.

From The Carpentries Bylaws:*A Lesson Program within The Carpentries possesses the following characteristics:

Intention and purpose for lessons that align with The Carpentries mission and vision
Goals and objectives for lessons and/or workshops that are distinct from other Lesson Programs
Service to a particular audience of learners and instructors
Evidence of community member commitment to Lesson Program governance (see below), lesson maintenance, and curriculum development*

Adoption as an official The Carpentries Lesson Program is the last step of Lesson Program incubation as outlined in the Lesson Program Incubation Roadmap

This Policy outlines the Roles and Responsibilities of the Lesson Programs and The Carpentries.

Lesson Program Policy¶

Roles and Responsibilities of Lesson Programs¶

The Lesson Program maintains a Lesson Program Committee of a minimum of 3 members to serve as community governance body and act as a point of contact with The Carpentries Executive Council and staff.
The Lesson Program Committee provides the Executive Council with an annual report of Lesson Program operations based on a template provided by The Carpentries.
The Lesson Program follows all general policies as outlined by The Carpentries, including, but not limited to, the Code of Conduct.
The Lesson Program workshops are conducted and administered as outlined in The Carpentries handbook, including tracking activities and using at least one certified instructor per workshop.
Assessment of Lesson Program workshops and activities are conducted through, and in coordination with, The Carpentries assessment efforts.
Lesson Program workshops follow The Carpentries instructor training procedures and guidelines as outlined in the instructor training curriculum.
The Lesson Program has at least one articulated, established core curriculum for a workshop and guidelines on what is required for it to be called a Lesson Program workshop.
The Lesson Program maintains documentation with information about its goals, workshops and curriculum.
The Lesson Program coordinates with The Carpentries to release and publish lessons with permanent identifiers on a regular basis.
The Lesson Program develops all content collaboratively and openly with a Carpentries approved open license.
The Lesson Program maintains and develops lessons in accordance with Carpentries guidelines as outlined in The Carpentries Curriculum Development Handbook.
The Lesson Program uses Carpentries templates and curricular guidelines for workshops and lessons.
The Lesson Program has a workshop fee structure and Member Organisation engagement plan consistent with The Carpentries.
The Lesson Program promotes its curriculum so that workshops are taught regularly.
The Lesson Program will follow the procedures and guidelines of The Carpentries administrative and financial management structure.

Roles and Responsibilities of The Carpentries¶

The Carpentries staff and affiliates will coordinate Lesson Program workshops in accordance with standard workshop coordination practices as outlined in The Carpentries Handbook.
The Carpentries will enable the Lesson Programs to make use of all The Carpentries infrastructure, including workshop coordination tools and database.
The Carpentries will provide the Lesson Programs access to all lesson and workshop templates. The Carpentries will include representatives from the Lesson Program on task forces or committees tasked with updating and maintaining these templates.
The Carpentries will support development opportunities for the Lesson Program, including grants, donations and other revenue opportunities. Funds brought in for Lesson Program activities will go to support that work.
The Carpentries will include Lesson Programs in the regular lesson release and publication cycle, coordinating between the Lesson Program maintainers and The Carpentries staff and affiliates.
The Carpentries will include the Lesson Programs in assessment efforts, including survey development and data analysis.
The Carpentries will ensure the instructor training program addresses the training needs of the Lesson Program, incorporating examples and exercises targeted towards the communities served by the Lesson Program.
The Carpentries will prepare Trainers to work with trainees from the Lesson Program.
The Carpentries Instructor Training recruitment and retention strategies will include building communities of InstructorsIinstructors in communities and domains served by the Lesson Program.
The Carpentries will include the Lesson Program in all community efforts, including but not limited to the activities of the Instructor Development committee, Mentorship program and BugBBQs.
The Carpentries programmatic and assessment reports will include Lesson Program activities. The Lesson Program will also have access to data specific to its activities.
The Carpentries Organisational Membership program will include The Lesson Program.
The Carpentries will provide an annual financial report to the Lesson Program Committee, including an assessment of the financial stability and sustainability of The Carpentries.
The Carpentries general revenue through Memberships, workshop coordination fees and general grants or donations, will support the ongoing work of the Lesson Program - running workshops, diversity and inclusion efforts, instructor training, lesson maintenance and community engagement.
The Carpentries maintains and documents an administrative and financial management structure that supports the Lesson Program.

Update log:

Approved 2018-11-01 by the Executive Council

INSTRUCTOR DEVELOPMENT¶

Instructor Development Committee¶

Instructor Development Committee Roles¶

Co-Chairs¶

Responsibilities¶

The Co-Chairs of the Instructor Development Committee are responsible for:

Scheduling monthly committee meetings.
- Meetings held monthly, twice in one day with each co-chair hosting one meeting to accommodate time zones.
Working with fellow co-chair to plan and share the monthly meeting agenda in advance (i.e. 1 or 2 weeks ahead of time).
Leading one of the monthly committee meetings (or delegate when absent).
Delegating tasks that come up each month.
- This can be done through a co-chairs meeting after monthly committee meeting.
Following up with other committee members regarding their duties/concerns.
Gathering feedback from community and other committee members about desired instructor development efforts and/or outcomes.
Adding/modifying new committee roles as necessary.
Evaluating committee roles on a yearly basis.

Time Commitment¶

1-2 hours/week
1 year term beginning 1-May

Requirements¶

Certified Carpentries Instructor

Secretary¶

Responsibilities¶

The Secretary of the Instructor Development Committee is responsible for:

Recording notes and attendance at IDC Leadership Meetings and IDC Meetings.
Adding notes to the Instructor Development GitHub Repository after each meeting
Emailing a summary of notes to the instructor-development list on TopicBox.
Updating IDC Etherpad with meeting connection information and details
Monitoring the Instructor Development Topicbox for ideas/issues to bring back to the committee.

Time Commitment¶

1-2 hours/week
1 year term beginning 1-May

Requirements¶

Certified Carpentries Instructor

Communications Chair¶

Responsibilities¶

The Communications Chair of the Instructor Development Committee is responsible for:

Adding IDC Meetings to the Carpentries Community Calendar
Actively recruiting participants to join IDC meetings and projects by sending out communications via Slack, Topicbox, Twitter (with the help of the Community Engagement Lead) and the Carpentries Blog.
Creating communications around IDC projects or other initiatives.

Time Commitment¶

1-2 hours/week
1 year term beginning 1-May

Requirements¶

Certified Carpentries Instructor

Mentoring Chair¶

Responsibilities¶

The Mentoring Chair of the Instructor Development Committee is responsible for:

Using the Mentoring Groups Workflow to recruit mentors/mentees and managing the Carpentries Mentoring Groups.
Reporting back to IDC Leadership and Carpentries Staff Liaison about Mentoring Group metrics and any concerns or revisions to the mentoring groups.
Maintaining the Carpentries Mentors” Etherpad and Mentoring Groups” Etherpad
Updating the Mentoring Groups section of the handbook as necessary.
Managing the #mentoring channel in The Carpentries Slack.
Coordinating with the Communications Chair on communications campaigns around mentoring.

Time Commitment¶

1-2 hours/week
1 year term beginning 1-May

Requirements¶

Certified Carpentries Instructor

Discussion Session Coordinator¶

Responsibilities¶

The primary responsibilities of the Discussion Session Coordinator are:

Organizing Themed Discussion Sessions and #CarpentriesConversations that come in on the Call for Community Discussion Facilitators form
Inviting instructors to attend pre and post-workshop discussions
Recruiting discussion hosts
Maintaining the discussion hosts mailing list
Maintaining the community discussions Etherpad with upcoming dates
Adding Community Discussions to the Community Calendar
Checking in with hosts the week of their discussion sessions

Time commitment¶

1-2 hours a week
1 year term beginning 1-May

Requirements¶

Certified Carpentries Instructor

Special Projects Chair¶

Responsibilities¶

The Special Projects Chair of the Instructor Development Committee is responsible for:

Facilitating the formation of task forces/committees as appropriate to accomplish desired project outcomes.
Supporting any of the other Chairs/Leaders in their roles as needed.

Time Commitment¶

1-2 hours/week
1 year term beginning 1-May

Requirements¶

Certified Carpentries Instructor

Community Discussions¶

The Instructor Development Committee leads and organizes Community Discussions. This document describes how community discussions are organized and conducted. Checklists for the Hosts and Discussion Session Coordinator are here.

The Carpentries Community Discussions are designed for everyone in The Carpentries community interested in learning, educating and advocating for teaching foundational coding and data science skills globally. Discussion topics range anywhere from teaching workshops and developing curricula to building local communities and assessing the impact of our workshops globally. There are three types of Community Discussions:

Pre- and Post-Workshop Discussions These discussions are designed for those getting ready to teach or having recently taught to come discuss their workshop with the community.
Themed Discussion Sessions These discussions are centered around a particular topic ranging anywhere from teaching your first workshop to community building strategies.
Carpentries Conversations These Conversations are hosted by one of our Committees or Task Forces to provide the community with the opportunity to learn about and discuss new developments and programs in our organisation. Our committees and task forces include:

African Task Force
Carpentries en Latinoamérica
CarpentryCon Task Force
Code of Conduct Committee
Instructor Development Committee
Lesson Infrastructure Committee
The Carpentries Executive Council

Terminology¶

Community Discussion: an online meeting where instructors share experiences from teaching and obtain information while preparing to teach.
Discussion Session Host: member of the Carpentries community who facilitates a community discussion.
Discussion Session Coordinator: a volunteer from the Instructor Development Committee whose responsibilities include updating the scheduling Etherpad and emailing invitations to instructors. For more information about this role, see the role description.

Motivation¶

The Carpentries is a community based project and the community needs opportunity to interact.
The Carpentries believes in jugyokenkyu, or «lesson study», and evidence-based education so instructors need opportunity to share experiences.
The Carpentries is continuing to increase the number of instructors and develop new lessons. New instructors would like to hear from experienced teachers who have recently taught to help prepare for upcoming workshops.

Who Can Host?¶

Hosting community discussions is a great way to meet more people in the Carpentries community, to get to know the organisation better, to learn from the experiences of others and to share your own knowledge and experience with an even greater number of people.

Any instructor with experience of organising/teaching workshops and a good knowledge of the Carpentries as an organisation is welcome to host a discussion session. Sessions are coordinated by the Instructor Development Committee and hosts are encouraged to join the meetings of this committee. Committee meetings include an update on community discussions and an opportunity to discuss the format, to ask questions about hosting a session, and to get to know other hosts. To receive messages relating to discussion sessions and hosting, make sure that you”re subscribed to the discussion hosts mailing list.

A great way to get into hosting these sessions is to first attend as an observer or co-host. An experienced host will be happy to talk you through it, and may return the favour when you host for the first time, so that you don”t have to «fly solo» in your first session.

Signing up to Host or co-Host a Community Dicussion¶

If you”d like to host a pre/post-workshop session:

Identify a session you’d like to host OR co-host on the Community Discussions etherpad: http://pad.carpentries.org/community-discussions
Type your name in the “Host” or “Co-host/notetaker” slot for the session you’ve chosen (email next to your name optional, however, if you provide your e-mail it may help facilitate communication before and after the discussion)
Add the time/date details of the discussion session you’re going to be a “Host” or «Co-host/notetaker» for on your calendar
Copying the etherpad link in your calendar event is a good idea, too!
Make sure that you”re subscribed to the discussion-hosts mailing list.

If you”d like to host a pre/post-workshop session:

Complete this form.

Host Expectations¶

Primary role is to facilitate the community discussion using the agenda at the bottom of the Etherpad.
While it’s the co-hosts main responsibility to take notes, please take notes in the Etherpad when the co-host/notetaker is speaking.
Maintaining focus on the main goal of the session, which is to share ideas, support each other, and keep instructors excited about teaching.
Ensuring instructors teaching in the near future have urgent questions or concerns addressed.
Collecting feedback from instructors who have recently taught.
Engaging newly trained instructors and evaluating their participation using a subset of questions described in the checkout procedure here: http://carpentries.github.io/instructor-training/checkout/.
Encouraging attendees to create issues or pull requests to correct problems.

Co-Host Expectations¶

Primary role is to assist with note-taking while the Host leads the discussion
Take accurate notes of discussion on the Etherpad
At the beginning of the callI, introduce yourself as the co-host/notetaker
Co-hosts/notetakers do not have to be the very active in the conversation
If a co-host/notetaker does want to chime in, it is welcome!
NOTE: if the session is mostly instructor checkouts, it is highly recommended that you, as the co-host, contribute to the discussion with your experience helping out with workshops.

Checklists - Community Discussions¶

Community discussions are organised and conducted through this Etherpad.

Discussion Session Coordinator¶

Before the Discussion Session¶

The Instructor Development Committee is responsible for organizing the community discussions so that

each month has at least eight discussion sessions, and
each session has at least one host (preferably two) to conduct the discussion.

The Discussion Session Coordinator is responsible for scheduling the events and inviting instructors who are about to teach and who have recently taught.

Meeting scheduling will be coordinated via this Etherpad.

The dates of community discussions are also listed in the Carpentries community calendar.

Invitations for checkout participants are tracked through two spreadsheets - one for instructors doing a post-workshop debriefs, sent weekly, and one for instructors doing a pre-workshop discussion session, sent every other week.
Use the email templates for the respective discussion invitation. Replace the variables in brackets with the appropriate information for that session.
Log in to AMY. Go to the reporting section to the «List of instructors by time period» section. Filter for instructors in the relevant time period. Download this list as CSV to easily read each instructor”s email address.
Send the templated email to all participants as bcc, and copy the Instructor Development Committee Co-Chairs as well as team@carpentries.org.
Email team@carpentries.org with any instructors with missing or invalid emails.

Host and Co-Host¶

Leading the Discussion Session¶

Meetings will be hosted on a Zoom videoconference, linked via the community discussions Etherpad.

Each session must have at least one host (although two hosts are preferred). Any experienced instructor is welcome to host, but hosts are encouraged to join the Instructor Development Committee.

Sign on as close to the start time as you can.
Confirm that your fellow host is present (if there is one) and who will be leading/taking notes
(Optional) If a group is very large and you have a co-host, you can split the group in two, using the Breakout Rooms feature in Zoom.
Copy the agenda from the bottom of the etherpad to the space under your time slot
Lead the discussion
- We recommend following the main points of the agenda, but feel free to let discussion go where people want. Not all the questions need to be answered by everyone.
- Don”t feel like you have to answer all the questions as the host - draw on the other discussion participants to answer each other”s questions.
- If someone is attending as part of their training checkout, prompt them to ask a question.
- Try to leave enough time at the end for the final agenda item.

The agenda should be similar to the following:

Welcome, introductions, and reminder of Code of Conduct (5-10 minutes depending on number of participants)
- Code of Conduct Link: https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html
- Host introduction
- Co-host/notetaker introduction
- Attendee introductions
  - Name, affiliation/position, purpose for attending
Report from previous workshops (10-25 minutes: 2-3 minutes per workshop plus about 5-10 minutes for questions)
- Share some significant accomplishments and obstacles.
- Any changes or additions to lesson material?
Preparing for upcoming workshops (10 minutes)
- Specific questions about teaching and/or lessons?
- How are instructors sharing roles/responsibilities? Is there a designated «lead instructor» or will you act as co-instructors?
Discussion Questions [Use Zoom Breakout Rooms for large groups] (15 minutes)
- Hosts: Choose 1-3 of these questions, or add your own.
- What additional resources would be useful to you in teaching or preparing for a workshop?
- Do you find the instructor notes helpful? How do you use them? How could they be more useful?
- What are you most excited about for teaching with The Carpentries?
Preparing for instructor training checkout (2 minutes)
- Questions about checkout procedure, lessons, or workshop organization?
- Have you asked a question here yet?
Closing (Main Room) (3 minutes)
- Reports from breakout rooms
- Q&A
- Reminders to discussion session participants
- Export the etherpad (button at top right) if you”d like to save notes from our session. Notes will be removed (but available in the archives) soon after the discussion ends!
- For small typos in lessons, submit pull request to appropriate lesson

(A copy of this agenda is kept at the bottom of the instructor discussion Etherpad.)

Based on discussion among the Instructor Development Committee, temporary questions may be added to the agenda for a month of sessions, in order to collect data on specific issues.

Take notes

If there are more than 5 workshops represented by attendees, the discussion session should be split into two groups, to make sure everyone has enough time to share. When dividing attendees into two groups, try to balance the number of people who are de-briefing, who are there for pre-workshop help, and who are instructor trainees. If there are exactly 5 workshops represented, it is at the discretion of the host whether to split the group.

After the Discussion Session¶

Archive the Etherpad by clicking on the star in the top right corner.
Fill out the host questionnaire
- Note: Please copy the list of attendees (including all attendees but removing no-shows) and paste it into question 7 of the questionnaire.
- This questionnaire will automatically send an email to the Instructor Development Committee Co-Chairs and to checkout@carpentries.org.
Clear the information from your session (date/time, attendees, notes) from the Etherpad.
(Optional) write a blog post about interesting points that came up in discussion.

Email Templates¶

Pre-workshop Discussion¶

Subject: Carpentries Pre-Workshop Discussions

Dear instructors,

If you are receiving this message, you are scheduled to teach a Carpentries workshop over the next several weeks.

The Carpentries Instructor Development Committee hosts community discussions every week to share ideas and experiences among instructors. If you have any questions or concerns about your upcoming workshop, or are interested in chatting with other instructors about your or their own experiences teaching, we encourage you to attend!

Upcoming discussions will occur on [Date 1], [Date 2] and [Date 3]. Each date has two time slots to accommodate time zones. You can sign up for the most convenient time on this Etherpad:

http://pad.carpentries.org/community-discussions

We hope to see you in the next few weeks!

Cheers, [Your name] Carpentries Instructor Development Committee

Post-workshop Debriefing¶

Subject: Carpentries Workshop Debriefing

Dear instructors,

If you are receiving this message, you have recently instructed at a Carpentries workshop.

The Carpentries Instructor Development Committee hosts community discussions every week in order to hear how workshops have gone, and we invite you to attend a discussion in the next few weeks to share about your recent workshop. Even if you have attended a debriefing discussion before, we would appreciate feedback on any workshops you have done since then - we value hearing about your experiences.

Upcoming discussions will occur on [Date 1], [Date 2] and [Date 3]. Each date has two time slots to accommodate time zones. You can sign up for the most convenient time on this Etherpad:

http://pad.carpentries.org/community-discussions

In addition to participating in the general discussion, we also welcome past instructors to co-host future discussions. Co-hosting a community discussion is a great way to share your expertise with both new and experienced instructors and is a lot of fun! To co-host a future discussion, just sign up on the same Etherpad above, or complete this form if you”d like to host a themed discussion session.

We hope to see you soon!

Cheers, [Your name] Carpentries Instructor Development Committee

Call for Instructors (to Instructor Development Committee)¶

Subject: Call for Hosts - Carpentries Community Discussions

Hello,

The Discussion Host Coordinator has posted new community discussion dates on the Community Discussions Etherpad: http://pad.carpentries.org/community-discussions

The following discussion sessions are in need of discussion hosts!

[Date 1, UTC time, time zones - example below]
Tuesday, May 1, UTC 21:00 UTC (Wed 7am AEDT, 5pm NYC, 2pm LA) - Aus/S. America/N. America

Please feel free to browse other community discussion sessions to see if there is a date/time that works for you to sign on as a host! If you have questions about hosting, please visit the Instructor Development Committee onboarding document”s section about host expectations: https://docs.carpentries.org/topic_folders/mentoring/mentoring-subcommittee-roles.html#discussion-hosts

We hope to see you soon!

Cheers, [Your name] Carpentries Instructor Development Committee

Community Discussions Workflow¶

This workflow was established for the Instructor Development Committee Discussion Session Coordinator to organise The Carpentries Community Discussions.

Scheduling Community Discussions¶

Review responses from the Call for Community Discussions Facilitators form.
- The Call for Community Discussions Facilitators form includes an integration which, when a form response is received, an e-mail is sent to The Carpentries Discussion Session Coordinator who should then open the attachment and review its contents.
Add potential Community Discussions to the Etherpad.
If the Community Discussions Facilitator proposed a day/time for the community discussion they”ll be hosting, add that day/time to the Etherpad as TBD in this format:

Themed Discussion Sessions/#CarpentriesConversation
DAY OF WEEK, MONTH DAY TIME
TIME UTC 
Click here for your time zone:
Topic:
Description
Host (name & email):
Host questionnaire to be completed at the end of call: https://goo.gl/forms/iXkMQABmO6HROfCy1
Co-host/notetaker (name & email): 
Attending (Name/Affiliation/Twitter): 
  Sharing an upcoming or past workshop? Please add the link to your workshop website along with your name.
  Attending as part of the instructor checkout requirement? Please add your e-mail address and checkout along with your name.
    1.
    2.
    3.
Attendee questionnaire to be completed at the end of call: https://goo.gl/forms/uCeESfUUWsX5dpPu2 

Add potential Community Discussion to the community calendar
- If the Community Discussions Facilitator proposed a day/time for the community discussion, add that day/time to the community calendar in UTC and assign the Zoom Room carpentries room 2 for the call. If they did not provide a time, include that question in your e-mail to them.
Add potential Community Discussion to the Community Discussions Page on the website
- Submit a PR to update the Community Discussions page on The Carpentries website
- The appropriate GitHub repository to submit your Pull Request to is here. Add the new community discussion in the upcoming discussions section.
Contact potential Community Discussions Facilitator
- Send a version of the following templated e-mail to the individual who completed the form. Once the e-mail has been sent, highlight the row in the spreadsheet yellow indicating that you”ve contacted the individuals.
Communications Tasks
- Inform the Carpentries Staff Liaisons about the Community Discussion by emailing community@carpentries.org.
- Draft tweets for Community Discussion
- Make a copy of this template and draft tweets to spread the word about the Community Discussion.
  - Send the tweet template to the Community Engagement Lead on serah@carpentries.org.
Request Blog Post to Promote Community Discussion
- Remind facilitator to write a blog post to get the word out about the community discussion. Here”s a handy blog post drafting guide to help them get started

Preparing to Host a Carpentries Community Discussion¶

[Optional] Identify a Community Discussion Moderator
- Identify someone to moderator the Community Discussion. This individual will:
- Introduce the facilitator
- Remind participants that we are following the Carpentries CoC
- Request permission from attendees to record the session.
- Take notes during the discussion
- Moderate Q&A
- Facilitate breakout rooms
- Serve as timekeeper
- Thank attendees for participating
- Remind attendees to complete the questionnaire
- Ensure we recognize those attending the discussion for checkout and facilitate Q&A for checkout participants.
Share Zoom Room Credentials & Practice Breakout Rooms
- Contact the Community Engagement Lead on serah@carpentries.org in case you need alternative Zoom Room Credentials shared.
[Optional] Review The Carpentries Community Discussions Host Onboarding slide deck

Community Discussion Wrap-Up¶

Add Community Discussions Slide Deck to Google Drive
- Add the slide deck to either the Themed Discussion Session folder or the #CarpentriesConversation folder on Google Drive.
Upload Community Discussion Recording to YouTube
- Contact the Community Engagement Lead on serah@carpentries.org to have the recording of the Community Discussion uploaded to The Carpentries YouTube Channel.
Add Community Discussion to the Past Calls section of the Community Discussions page on The Carpentries website.
Send thank you notes to the Community Discussion Facilitator & Moderator using this template email as a starting point if need be.
Review Discussion Questionnaire Results
- Request access to the results of the Community Discussion Questionnaire. Review the results and share your notes with the rest of the Instructor Development Committee Leadership Team.
Review the Community Discussion blog post and ask Community Engagement Lead to merge by emailing serah@carpentries.org or tagging @serahrono in the PR.
- If the discussion host wrote a blog post, review the blog post and the results of the questionnaire. Add/edit blog post content and be sure to include any responses from the survey that are valuable/interesting before requesting the Community Engagement Lead to merge.

Mentoring Groups¶

Mentoring is a professional development opportunity that the Carpentries offers our growing instructor pool to help community members learn and grow.

Mentoring Groups support instructors in a variety of ways. Whether you are a new instructor preparing to teach your first workshop, a seasoned instructor hoping to launch workshops in a new community, or an instructor excited about getting involved with lesson development and maintenance, mentoring groups will help you gain the confidence, technical skills, and teaching skills you need to reach your goal.

Mentors guide small groups of no more than five mentees toward a particular outcome. Outcomes might be anything from teaching a specific lesson (i.e. Version Control with Git) to making a meaningful contribution to one of our lessons.

Mentoring Groups Outline¶

Groups are encouraged to set SMART goals to be achieved. The following are sample mentoring group outlines. Groups are free to decide how to spend their time.

Sample Mentoring Group Outline: Lesson Maintenance¶

Introductions, review the Carpentries community culture, and communication channels.
Review and discussion lesson objectives.
Meeting with Lesson Maintainers to discuss challenges and opportunities.
Review, discuss, and comment on lesson issues. Identify a representative to attend the mid-way touch base.
Review, discuss, and comment on lesson pull requests.
Discuss current challenge questions. Write new challenge questions to be added to the pool of challenge questions.
Submit new challenge questions as pull requests. Draft one slide for the mentoring group showcase.
Finish slide for mentoring group showcase. Attend mentoring group showcase.

Sample Mentoring Group Outline: Teaching Workshops¶

Introductions, review the Carpentries community culture, and communication channels.
Review and discuss instructor notes.
“Tag-team” teaching each module of the lesson. Provide feedback to group members.
First mock quarter/half day workshop with group members. Identify a representative to attend the mid-way touch base.
Second mock quarter/half day workshop with group members. Draft one slide for the mentoring group showcase.
Finish slide for mentoring group showcase. Attend mentoring group showcase.

Sample Mentoring Group Outline: Organizing Workshops¶

Introductions, review the Carpentries community culture, and communication channels.
Introduce existing workshop resources. Identify challenges for organizers.
Walkthrough of workshop set up using checklists. Discuss workshop planning tools, e.g. Eventbrite, spreadsheets.
Identify potential issues and how to resolve them, e.g. ‘no shows’, CoC violations, refunds. Identify sources of help.
Draft one slide for the mentoring group showcase. Identify a representative to attend the mid-way touch base.
Identify resource gaps, e.g. issues that are not covered by existing checklists and procedures.
Finish slide for mentoring group showcase. Attend mentoring group showcase.

Sample Mentoring Group Outline: Community Building¶

Introductions, review the Carpentries community culture, and communication channels.
Discuss desired local outcome. Discuss existing community, if any. Identify stakeholders and potential supporters.
Discuss community building methods used elsewhere (e.g. ResBaz, Hacky Hours, MeetUps, communities of practice).
Discuss the use of communication tools such as Slack and Gitter channels.
Identify a representative to attend the mid-way touch base.
Draft one slide for the mentoring group showcase. Identify a representative to attend the mid-group touch base.
Draft a plan for a local community building event that includes a marketing strategy.
Review plans collectively. Identify gaps or further resources needed.
Finish slide for mentoring group showcase. Attend mentoring group showcase.

Mentoring Groups Highlights¶

Participants can choose the type of mentoring group they”d like to belong to:

Lesson Maintenance
- Contributing to current lesson development
- Contributing to lesson maintenance
Teaching Workshops
- Developing confidence and skill in teaching
- Preparing to teach a specific lesson (i.e. Python)
Organizing Workshops
- Logistics of organizing a workshop (e.g. marketing, registration)
- Logistics of running a workshop (e.g. recruiting instructors, distributing tasks)
Community Building
- Strategies to build local communities
- Tried-and-true events that help foster local communities

An additional highlight includes the opportunity to participate in in-person mentoring groups.

During the final week of the mentoring groups, we will host a virtual mentoring groups showcase. During this event, the community can hear about the projects on which the mentoring groups worked.

Lastly, both mentors and mentees will receive a certificate!

Mentor Agreement¶

I agree to follow the Code of Conduct in all communications and interactions with The Carpentries community and to promptly report any violations of the CoC that I become aware of.

When interacting with my mentoring group, I agree to

communicate The Carpentries community values to mentees and model that behaviour myself in how I mentor,
provide a welcoming and supporting environment for mentees,
avoid dismissive language, question my expert blind spot, and model error-making as a vital part of the mentoring process.

I understand that it is important to keep in touch with The Carpentries community so that my mentorship will reflect current practices. I agree to:

stay active in one or more Carpentries communication channels,
keep up-to-date with changes to the lesson(s) I teach, and
provide feedback to the Mentoring Subcommittee and Carpentries staff to help continue improving our mentoring groups.

Mentor Onboarding¶

Mentor Onboarding Recording

Mentoring Groups Recruitment Strategy¶

Recruitment
- Mentoring groups are open to any individual who has completed Carpentries instructor training.
- Community members who have taught fewer than two workshops (or no workshops at all yet) are invited as mentees.
- Certified Carpentries instructors who have taught three or more workshops are invited to lead mentoring groups.
Activities & Timing
- Mentoring groups run for between eight and 12 weeks.
- Kari Jordan will hold a mentoring groups “touch base with mentors” halfway through the 8-12 week period.
- Mentors and mentees will be asked to complete a short survey halfway through the 8-12 week period.
- The 8-12 week period will end with a virtual showcase.
- Mentors and mentees will be asked to complete asecond short survey at the end of the mentoring group period.
Exposure
- A mentoring page will be added to The Carpentries” website with information on how to join a mentoring group.
- Members will be added to groups, and new groups will be formed, on a rolling basis as needed, at the discretion of Kari Jordan.
- The Mentoring Subcommittee will be instrumental in getting the word out about mentoring groups.

Mentoring Groups: Guidelines for Certificates¶

Mentors¶

Attend a mentoring onboarding session.
Attend regular meetings with your mentees.
Attend the virtual showcase.
Attend the power check-in.
Complete the post-program survey.

Mentees¶

Attend at least two mentoring meetings.
Attend the virtual showcase.
Complete the post-program survey.

Mentoring Groups Roles¶

Mentees¶

Responsibilities¶

Communicate with your Mentor about your goals and needs.
Attend scheduled meetings and participate actively or let your Mentor know you won’t be attending.
Be respectful of other Mentees and Mentors. Provide a safe space for questions and mistakes.

Requirements¶

Be either a newly certified Carpentries instructor or be in the process of completing certification. Generally Mentees will have taught one or no workshops, but may have been helpers before.

To Participate¶

To join the mentoring program as a mentee, complete this form.

Mentors¶

Responsibilities¶

Decide on a meeting schedule with your Mentees.
Personalize meetings based on Mentee’s needs and desires.
Respond promptly to emails from your Mentees.
Follow up with Mentees who miss meetings.
Be respectful of Mentees. Provide a safe space for questions and mistakes.
Report Mentee attendance and progress to mentoring coordinator.

Time commitment¶

~4 hours/month for 3-5 months (or longer if accepting new Mentees). This breaks down to about 2 hours prep, 1 hour meeting and 1 hour answering emails per month. Variable depending on meeting frequency and prep time.

Requirements¶

Certified instructors who have taught at least 2 workshops.

To Volunteer¶

To join a mentoring group as a mentor, complete this form.

Mentoring Coordinator¶

Responsibilities¶

Recruit mentors and mentees for the Mentoring Program.
Pair Mentors and Mentees based on responses to Google form surveys.
Send email introductions for each mentoring team.
Follow up with each mentoring team on a monthly basis and ask if there”s anything you can do to help.
Keep track of program completion rates to assess success.
Get feedback from Mentors and Mentees about program.

Mentoring Groups Virtual Showcase¶

The Carpentries” community is invited to participate in a Virtual Showcase of our mentoring groups” projects. These will be scheduled at the end of each mentoring group term.

What to expect: Each group will present one slide outlining something they learned or completed with their mentoring group. We will also answer questions from the community and discuss the benefits of mentoring.
Why attend: Be inspired by the projects of your global community members! Be empowered to start a new project, contribute to a lesson, or prepare to teach a lesson. Explore the benefits of mentoring and being a part of a global community.

Contact¶

For information regarding the Carpentries Mentoring Groups, e-mail Kari L. Jordan. To join the next Instructor Development Committee meeting, sign up via this Etherpad.

Mentoring Groups Workflow¶

This workflow was set up to guide the Instructor Development Committee Mentoring Chair in running The Carpentries Mentoring Groups.

Preparing to Run Mentoring Groups¶

Meet with the Instructor Development Committee to set the dates of the Mentoring Groups
Add Mentoring Group dates to README on GitHub. Instructions
Update deadlines in the Mentor and Mentee Application forms
- The Carpentries Mentor Application form
- The Carpentries Mentee Application form

Recruiting Mentors and Mentees¶

Schedule a Mentoring Groups Info Session
- Add the dates for the info session to the community calendar.
Use this templated presentation as a guide
Add mentoring group applications to Carpentries Clippings, our community newsletter
Write blog post to recruit mentors and mentees for Carpentries Mentoring Groups
- Sample Post 1
- Sample Post 2
Inform Carpentries Member Organisations that Mentor/Mentee applications are open
- Contact The Carpentries Director of Membership and request that a version of this template e-mail be sent to Member Organisations
Inform Trainers that Mentoring Applications are open
- Contact The Carpentries Deputy Director of Instructor Training and request that a version of this template e-mail be sent to Trainers.
Schedule tweets for Carpentries Mentoring Groups recruitment
- Make a copy of this tweets template
- Draft tweets to be shared on The Carpentries Twitter account using the template. Include the dates you’d like the tweets to be scheduled.
- E-mail the tweets to the Community Engagement Lead on serah@carpentries.org.

Setting Up Mentoring Groups¶

E-mail mentors with mentee assignments
Use the results of the mentor and mentee applications to match one mentor with 4-5 mentees.
Add mentor/mentee assignments to the Mentoring Groups Etherpad.
Add mentor and mentee contact information to this spreadsheet to generate certificates at the end of the program.
Host Mentor Onboarding
- Schedule mentor onboarding in two different timezones.
- Add the mentor onboarding to the community calendar
- Add onboarding information to this Etherpad
- Prepare for the onboarding using this information from the Handbook
- Be sure to communicate to mentors who will get certificates.

Mid-Program Tasks¶

Send Mentoring Groups the Mid-Program Survey
- Use the following e-mail template to collect feedback from mentors and mentees half way into the program.
Review Mentoring Group Mid-Program Survey Results and address issues as needed.

Wrapping Up Mentoring Groups¶

Schedule Mentoring Groups Virtual Showcase
- Add the dates for the Virtual Showcase to the community calendar.
E-mail the mentoring groups with instructions for completing their slide for the Virtual Showcase
See past virtual showcase presentations in this folder
Create certificate for mentors and mentees
Send Mentoring Groups the Post-Program Survey
- Use the following e-mail template to collect feedback from mentors and mentees at the end of the program
Review Mentoring Groups Post-Program Survey Results and add highlights to the wrap-up blog post.
Write wrap-up blog post for mentoring groups
Add a summary statement on Mentoring Groups wrap-up to Carpentries Clippings, our community newsletter

INSTRUCTOR TRAINING¶

Para Trainers¶

Responsabilidades y Trainer Agreement¶

A partir de mayo de 2017, el grupo de Trainers adoptó un Acuerdo (Trainer Agreement) que describe las responsabilidades del Trainer. Solo los Trainers activos son miembros votantes de la comunidad de Trainers. Un Trainer inactivo puede reactivar su estado de Trainer en cualquier momento reanudando las actividades del Trainer.

Trainer Agreement¶

Estoy de acuerdo en seguir el Código de Conducta (CoC) en todas las comunicaciones e interacciones con la comunidad de The Carpentries y en informar de inmediato cualquier violación del CoC de la que tenga conocimiento.

Entiendo que los resultados del aprendizaje secundario de los talleres son tan importantes como sus objetivos establecidos. Voy a:

Comunicar los valores de la comunidad de The Carpentries a trainees y modelar ese comportamiento en la forma en que enseño
Proporcionar un ambiente acogedor y de apoyo para las trainees.
Modelar nuestra política de «mostrar, no decir» durante el instructor training
Conectar los principios utilizados en los talleres de The Carpentries con otros contextos de enseñanza.

Entiendo que es importante mantenerme al día y en contacto con la comunidad de Trainers para que mi enseñanza refleje las prácticas y el plan de estudios actuales. Por lo tanto, para ser un Trainer activo, acepto:

Brindar al menos dos instructor trainings por año
Organizar en promedio cuatro demostraciones de enseñanza por año (una por trimestre)
Asistir regularmente a las meetings de Trainers cuando sea posible y leer las minutas/notas de la reunión cuando no sea posible asistir
Leer emails enviados a la lista de distribución de Trainers
Mantenerme al día con la currícula del instructor training
Enseñe una currícula que cumpla con todos los requisitos actuales para la certificación de instructor
Proporcionar comentarios a otros trainers y al personal de las Carpentries sobre eventos de training para ayudar a continuar desarrollando nuestras ofertas

Entiendo que el personal de The Carpentries necesita una comprensión precisa de la disponibilidad del Trainer para planificar eventos de onstructor training. Si en algún momento ya no puedo servir como Trainer, informaré al personal de The Carpentries. Entiendo que solo los Trainers activos son miembros votantes de la comunidad de Trainers, pero que podré reactivar mi estado de Trainer en cualquier momento reanudando las actividades del Trainer.

Trainers Guide¶

Trainer Meetings¶

El grupo de Trainers se reúne regularmente. Nuestras reuniones incluyen tres secciones: 1) Discusión, donde compartimos experiencias y obtenemos consejos sobre cómo llevar a cabo eventos de capacitación de instructores, 2) Anuncios y 3) Tópico del mes, que pueden incluir actualizaciones de la currícula, conversaciones activas que ocurren en GitHub u otros canales de capacitación, presentaciones de invitados, etc. Las reuniones se encuentran listadas en nuestro Etherpad y en el Calendario de la comunidad. Si no es un entrenador, pero estás interesado en unirse a una reunión, por favor contáctese con Erin Becker (ebecker@carpentries.org). Las actas de estas reuniones se encuentran disponibles.

Registrarse para brindar un evento de Instructor Training¶

El Program Manager enviará un correo electrónico a la lista de Trainers pidiéndoles que completen su calendario para el próximo período de tiempo. Los Trainers deben inscribirse durante tantos días como estén disponibles y mantener esas fechas en su calendario hasta que se confirme el horario.
El Program Manager confirmará los eventos con cada Trainer, momento en el cual pueden liberar todas las demás fechas de su calendario.
El Pogram Manager invitará a los sitios miembros a registrarse para los próximos eventos. Los Trainees aceptados del proceso de solicitud abierta serán invitados a registrarse un mes antes de cada evento.

Tener en cuenta que para proporcionar la mejor experiencia a nuestros trainees, en casos excepcionales, los eventos pueden cancelarse debido a la baja inscripción. Si esto sucede, los trainees y Trainers serán notificados dos semanas antes del evento. Los trainees podrán inscribirse en un evento posterior.

El calendario para los próximos eventos de instructor training se encuentra aquí.

Trainer Checklists¶

Brindar un evento de Instructor Training¶

Cuatro semanas antes del evento¶

Contactar a tu co-Trainer(s) y decidir quien enseñará qué.
Crear un evento en Etherpad (usando el template de Etherpad) o Google Doc (usando el template de Google Doc) y una página web del taller (usando el template de training). Tener en cuenta que el documento de Google Doc no se mantiene actualmente y es posible que no esté sincronizado con los materiales de la lección.
Enviar los enlaces de Etherpad/Google Doc y la página web a training@carpentries.org.

Una semana antes del evento¶

Planificar la logística con los co-Trainer(s)
Revisar (o reservar un tiempo cercano al evento para revisar) los resultados de la encuesta de preevaluación para tú taller
Al enseñar de forma remota:
Familiarizarse con el uso de Zoom para las videoconferencias.
Probar la configuración de la videoconferencia con los co-Trainer(s) utilizando las credenciales de inicio de sesión previamente proporcionadas.
Decidir junto a los co-Trainer(s) si todos los Trainers deben estar presentes todo el evento o si iniciará sesión solo durante los horarios de enseñanza programados.
Hacer una copia del template Virtual Minute Cards y personalizarlo para el evento.
Si se enseña en persona:
Confirmar con el anfitrión que las salas para grupos están disponibles o hacer un plan alternativo
Crear un plan para imprimir folletos y determinar quién traerá notas adhesivas
Asegurarse de preparar la configuración audiovisual con los dongles / conectores correctos, etc.
Verificar la disponibilidad/horario de café, almuerzo o cualquier otro detalle que te interese

Durante el evento¶

Tomar asistencia
Recordar a los trainees miembros que llenen la solicitud (los solicitantes de Open Training ya lo han hecho).
Recordar a los trainees que se inscriban para la demostración, debate (enlaces en la lista de verificación de pago).
Monitorear en Etherpad/Google Doc las preguntas y respuestas a ejercicios.
Si se enseña de forma remota: apagar el video durante los ejercicios largos y los descansos para tomar café y desconectarlo durante el almuerzo.

inmediatamente después del evento¶

Enviar la lista de quienes completarion el training a checkout@carpentries.
Enviar un correo electrónico a los trainees agradeciéndoles por participar y el enlace a la lista de verificación de pago usando esta plantilla
Revisar los resultados de la encuesta y prepararse para la próxima reunión de discusión de Trainers.
Presentar cualquier problema o PR relevante al repositorio de instructor training.

A largo plazo después del evento.¶

Unirse a una reunión de Trainers para analizar cómo fue el evento.

Diferencias entre eventos de training en persona y online¶

Trainings en persona¶

Al mirar videos, proyectarlo a todo el grupo
Asignar (o dejar que los participantes seleccionen) grupos de trabajo.
Usar notas adhesivas para obtener comentarios en las pausas para el almuerzo y al final de cada día.

Online trainings (algunos grupos pequeños)¶

Al ver videos, hacer que un Trainer comparta la pantalla con el audio encendido o que una persona de cada grupo reproduzca el video para los participantes en su sitio.
Asignar (o dejar que los participantes seleccionen) grupos de trabajo.
Usar el formulario de tarjeta de minuta virtual para obtener comentarios en las pausas para el almuerzo y al final de cada día.
Hacer que los participantes hagan todos los ejercicios en grupos pequeños con los participantes del mismo sitio

Online trainings (completamente distribuido)¶

Al ver videos, hacer que todos los participantes los vean por separado.
Asignar grupos de trabajo aleatoriamente a salas de trabajo en Zoom. Asegurarse de eliminar los Trainers y ayudantes al asignar grupos.
Usar el formulario de tarjeta de minuta virtual para obtener comentarios en las pausas para el almuerzo y al final de cada día.
Hacer que los participantes compartan la pantalla con su sala de reuniones durante los ejercicios de programación en vivo.
Para hacer el ejercicio para configurar un sitio web del taller, colocar a los participantes en salas de reuniones y hacer que una persona comparta la pantalla mientras los demás ayudan a guiarlos verbalmente.

Realizar una Demostración de Enseñanza¶

Si deseas ver un ejemplo de demostración de enseñanza, hay una grabación de uno aquí.

Antes de la demostración¶

Registrarse para liderar demostraciones.
Familiarizarse con el uso de Zoom para las videoconferencias.
Para cada trainee, elegir un punto de partida adecuado en la lección que haya elegido. Las lecciones sugeridas están disponibles en la Currícula de capacitación de instructores (en Extras). No hacer que comiencen en medio de un episodio. Tener en cuenta que algunas lecciones (por ejemplo, la lección de Software Carpentry R con datos de inflamación) tienen episodios complementarios. No elegir de esos.

Durante la demostración¶

Ir a la sala del Zoom. El enlace está en el Etherpad.
Una vez que estén todos en la llamada (audio y video funcionando), recordarles el Código de Conducta, explicar el procedimiento para la sesión de demostración y recordarles que los trainees deben poder enseñar cualquier episodio de la lección que elijan. Preguntar si alguien se ha preparado solo para 5 minutos de un episodio en lugar de toda la lección, y si es así, sugerir su reprogramación. Puede ayudarles recordar que esta no es una prueba de alto riesgo sino una oportunidad amigable para recibir comentarios.
Pedir a quienes no se presenten que silencien su micrófono, y que den su opinión utilizando la misma rúbrica de positivo-vs-negativo y contenido-vs-presentación utilizada en el entrenamiento. Para una sesión completa (5 aprendices), deben agregar comentarios al etherpad. Si tiene menos personas, elegir que escriban comentarios y los entreguen verbalmente según lo permita el tiempo.
Dar la tarea al primer aprendiz, luego darles un poco de tiempo para configurar la demostración (es posible que tengan que importar algunos paquetes, cargar algunos datos, moverse a una carpeta determinada, etc.).
Pedirles que compartan su pantalla usando el menú inferior «Compartir Pantalla» en Zoom.
Una vez que estén listos, darles una cuenta regresiva de 3-2-1 para comenzar.
Usar un temporizador de cuenta regresiva que haga ruido una vez que hayan transcurrido los 5 minutos (por ejemplo, el teléfono), o simplemente decir «bong» muy fuerte al final de su tiempo.
Después del temporizador de cinco minutos, permítirles terminar su oración y decirles que se acabó el tiempo.
Usar una rúbrica para ayudarte a tomar notas.
Después de que el trainee haya terminado, primero preguntarles cómo pensaron ellos mismos que les fue. Si tiene tiempo, otros alumnos pueden dar retroalimentación verbal, o puede resumir lo que está en el panel de control. Luego, brindar comentarios centrados y constructivos basados en sus notas y los comentarios de los demás. Se puede elegir una o dos cosas para enfatizar particularmente para ayudar a enfocar los esfuerzos de los trainees a medida que proceden a enseñar un taller. A veces también es necesario tomarse un tiempo para estar (suavemente) en desacuerdo con los comentarios de otro alumno.
NO decirle al trainee si aprobó inmediatamente después de su demostración.
Repetir para los otros trainees.
Al final de la sesión, hacer preguntas generales.
Si todos sus trainees aprobaron, informar al grupo al final de la sesión de demostración. Si alguien no aprobó, decirles a todos que se les enviará un correo electrónico a cada uno para informarles si aprobaron.

Durante la demostración (Troubleshooting)¶

Consultar la guía de Zoom para ayudar a solucionar problemas de conexión.
Si un trainee está enseñando una lección de Python y su Jupyter Notebook no comienza, dirigirlo a http://jupyter.org/try.

Después de la Demostración¶

Enviar un correo electrónico a checkout@carpentries.org con nombres, aprobado/reprobado y SWC/DC/LC para cada uno de sus trainees.
Borrar los datos deEtherpad de tu sesión.
Enviar a cada trainee un correo electrónico para informarles si aprobaron o reprobaron la demostración de enseñanza. Si es necesario, hacerles saber la razón por la que no aprobaron y pedirles que vuelvan a intentarlo.

Puntos de partida para demostraciones¶

Esta tabla se ha movido. Las lecciones sugeridas están disponibles en la Currícula de Training de Trainers (en Extras).

Convertirse en un Trainer¶

El grupo de Trainers acepta periódicamente nuevos miembros a través de las aplicaciones. Los nuevos Trainers se someten a un programa de training de ocho semanas que se describe a continuación y aceptan el Acuerdo de Trainers.

Programa Trainers Training¶

Este bosquejo representa el compromiso de tiempo requerido para ser instructores de Trainer con las Carpentries. Leer y verificar la posibilidad de comprometerse con las responsabilidades que se detallan a continuación.

Los instructores de Trainers acuerdan cumplir con el Código de conducta en todas las comunicaciones e interacciones con la comunidad de The Carpentries.

Leer cómo funciona el aprendizaje de Susan Ambrose y discutir en formato de club de lectura con Trainers en formación. Calendario de lectura preliminar.
- Compromiso de tiempo: 1 hora por semana para meetings de 8 semanas; puede faltar a una meeting; ~10 horas de lectura
Unirse a las meetings de Trainers
- Compromiso de tiempo: 1 hora por mes; puede faltar a una meeting
Presenciar una sesión de demostración de enseñanza como shadow
- Compromiso de tiempo: 1 hora una vez.
Presenciar al menos medio día de un evento de capacitación de instructores en línea como shadow
- Compromiso de tiempo: 4 horas una vez
Enseñe una vez en línea o en persona con un Trainer experimentado (después de terminar el club de lectura)
- Compromiso de tiempo: 2 días una vez más preparación
Aceptar el trainer agreement

Compromiso de tiempo total para Trainers continuos: 4 días por año + 2.5 horas por mes

Total time commitment for new Trainers: 3 days + ~30 hours over 3 month period, including reading and prep time

calendario de lectura de Trainers Training¶

For the most recent Trainer Training schedule and discussion questions, see the Trainer Training Curriculum

Reviewing New Trainer Applications¶

Director of Instructor Training and Carpentries staff will decide on goals for Trainer recruitment.
Trainer Application will be modified to reflect these goals.
Open application period will be announced via Carpentries platforms including Twitter, Facebook, the Discuss email list, and blogs. Ask relevant community members to promote within their networks as well. Personal invitations can be sent with this email template.
Ensure communication emphasizes overall goals.
Ask 2-3 existing Trainers to help review applications in line with defined goals. There is no rubric for this. Reviewers should leave notes supporting their rankings.
Consolidate rankings, adding discretionary points for gaps in representation by characteristics like gender, race, geography, and experience.
Notify accepted applicants using this email template.
Schedule Book Club meetings across time zones.
Inform the Communications Lead so he/she can promote this.
Update the Trainer training Etherpad.
Update the Reading Guides as needed.
Take attendance at all Book Club meetings. At most one absence is allowed.
After Book Club is over, remind Trainers to complete follow up tasks.
Send out Trainer certificates.
Inform the Communications Lead so he/she can promote the new cohort.

Trainer Coordinator¶

The Trainer Coordinator plays an essential role in The Carpentries community by ensuring that teaching demonstrations run smoothly and by coordinating meetings for the Trainers group. The duties for this position are estimated to take about two hours per month.

Duties¶

Weekly:

Check the teaching demonstration Etherpad to ensure that all events for the next two weeks have Trainers listed.
If any events don’t have a Trainer listed, send out a reminder to the Trainer Slack channel and the Trainer mailing list asking Trainers to sign up. See the email templates for suggested language.
If one week before the demo is scheduled to take place, there is still no Trainer available, email team@carpentries.org. The Carpentries staff will try to find a staff member to cover the demo.
If three business days before the demo, there is still no one available to lead, send an email to the trainees who are signed up. Also, change the status to “Cancelled” on the Etherpad and notify the Trainers group that we had to cancel an event.

Bi-monthly:

Add teaching demonstration sessions for the next two months to the teaching demonstration Etherpad.
Use the Event Time Announcer to create a new event. Set the event location as “UTC”.
- Set the month, day, year, hour, minute, and second to reflect the recurring times on the Community Calendar.
- Click “show result” and verify that the event is displaying in UTC. It will also display in your computer’s system time.
- Add the link to the teaching demonstration Etherpad.
Make sure that the sessions are also listed on the community calendar.
- Events are listed on the community calendar as recurring with no end date. They will only need to be modified if there are changes made to the teaching demo schedule.
- If you do not have edit access to the community calendar, contact team@carpentries.org.
Email the Trainers mailing list and post a message to the Trainer Slack channel asking people to sign up for teaching demos for the next two months.
Add Trainer Discussion and Business meetings to the Trainers Etherpad using the template at the bottom of the Etherpad.

Bi-weekly:

Send out reminders to the Trainers mailing list and Slack channel about upcoming Trainer Discussion and Business meetings.

Monthly:

Take notes in Trainer Business meetings.
- If not available to take notes, coordinate a replacement notetaker.
- Submit notes as a pull request to the Trainers’ GitHub repository.
- Send email to Trainers mailing list and post to Slack channel after Business meetings with a link to the notes.
  - Note: There is no need to take notes in Trainer Discussion meetings.

Email templates (Trainer Coordinator)¶

Teaching demos without hosts¶

Subject: Need hosts for upcoming teaching demos

Dear Trainers,

Thanks to everyone for signing up for leading teaching demonstrations in the coming weeks. Please note that we are missing a Trainer to lead a session on [time and date UTC] [time and date link]. If you are available to lead, please add your name to the Etherpad. If we don’t have a host scheduled one week before the event we will need to cancel the demo and ask trainees to reschedule.

Here are some additional events in the next month that don’t have a Trainer listed yet. Please sign up on the Etherpad if you’re available.

[list available sessions by UTC and with time and date links]
[list available sessions by UTC and with time and date links]

As always, if you haven’t led a teaching demo before, now’s a great time to start! You can get a feel for how they are run by observing someone else’s demo session or watching a recorded teaching demo session. If you’ll be attending someone else’s training, please let the Trainer who is running the session know that you’ll be there.

If you have any questions about running a teaching demo, please contact Erin Becker.

Thank you![Name]

Teaching demo cancelled - trainees¶

Subject: Teaching demo cancelled - please reschedule

Dear checkout participant,

Thank you for signing up to do your teaching demonstration next week at [time in UTC from Etherpad] [time and date link]. Unfortunately, due to lack of volunteer availability, we need to cancel this session. There are still spots open in the upcoming sessions listed below(for which we do have leaders confirmed!).

[list available sessions by UTC and with time and date links]
[list available sessions by UTC and with time and date links]

Please add your name to one of these or another session. I apologize for any inconvenience this has caused for you and hope that you are able to reschedule your demonstration soon. I”m looking forward to having you in our instructor community.

Sincerely,[Name]

Teaching demo cancelled - Trainers¶

Subject: Teaching demo cancelled - no host

Dear Trainers,

This is just a quick notice that we’ve had to cancel a teaching demo for this coming week due to lack of Trainer availability. I’ve already followed up with the trainees who were scheduled to teach during that session and asked them to reschedule. If you haven’t lead a teaching demo in a while, please check out the upcoming sessions on our Etherpad: http://pad.software-carpentry.org/teaching-demos and sign up if you’re available.

As always, if you haven’t led a teaching demo before, now’s a great time to start! You can get a feel for how they are run by observing someone else’s demo session or watching a recorded teaching demo session. If you’ll be attending someone else’s training, please let the Trainer who is running the session know that you’ll be there.

Best,[Name]

New teaching demos available¶

Subject: New teaching demos available for [Months]

Hi folks, I”ve updated the teaching demo Etherpad to include dates through the end of [Month]. It would be great if everyone could check out the available time slots and sign up. Please remember that we need each Trainer to run one teaching demo every three months in order to cover all of the events.

A few events still need coverage in [Month]. Please sign up on the Etherpad if you can take any of the following:

[list available sessions by UTC and with time and date links]
[list available sessions by UTC and with time and date links]

As always, if you haven’t led a teaching demo before, now’s a great time to start! You can get a feel for how they are run by observing someone else’s demo session or watching a recorded teaching demo session. If you’ll be attending someone else’s training, please let the Trainer who is running the session know that you’ll be there.

Thanks!

All the best,[Name]

Discussion Meeting reminder¶

Subject: Trainer Discussion meeting this week

Hi all,Just a quick reminder that we”ll be having our Trainer Discussion meeting this week. Please join us to share your recent instructor training experience and get advice about upcoming events. Meeting details are here: http://pad.software-carpentry.org/trainers.

All the best,[Name]

Business Meeting reminder¶

Subject: Trainer Business meeting this week

Hi all,Just a quick reminder that we’ll be having our Trainer Business meeting this week. Please check out the agenda and join here: http://pad.software-carpentry.org/trainers.

All the best,[Name]

Business Meeting notes available¶

Subject: Trainer Business meetings notes

Hi all,

Thank you to all who attended our Business meetings this week. For those who weren’t able to attend, please read through the meeting notes to stay informed about important issues affecting the Trainer community. If you have any questions or comments, contact Erin Becker or send a mail to the Trainers list.

Best,[Name]

Email Templates (Trainers)¶

This section contains email templates for English and Spanish activities.

Templates in English¶

Email after training event¶

Subject: Thanks for attending Carpentries Instructor Training!

Hi everyone,

Thank you for participating in The Carpentries Instructor training workshop. We really enjoyed having you involved and getting to know you a bit. You are now well on your way towards becoming a certified Carpentries instructor. In order to finish your certification, please finish these tasks (https://carpentries.github.io/instructor-training/checkout/) by the 90-day deadline. If you have any questions about the checkout process, please contact checkout@carpentries.org.

Looking forward to having you as a Carpentries Instructor!

Best,

[ name ]

Reminder teaching demo¶

Subject: The Carpentries teaching demonstration

Hi,

According to https://pad.carpentries.org/teaching-demos-recovered you have signed up to give an online teaching demo on [ date ] at [ time ] (See this link for your local time: [ timeanddate.com link ]). I will be the Instructor Trainer running the session.

I wanted to make it very clear that I may give you any segment of the lesson you prepared to teach, so you must be ready to teach any part of your chosen lesson. Some people prepare to teach 5 minutes from a particular section and nothing else, and these often have to reschedule as they seldom are assigned the section they have prepared for. A lesson corresponds to a single line in the lesson tables (https://software-carpentry.org/lessons/ , http://www.datacarpentry.org/lessons/ , and https://librarycarpentry.org/lessons/) and a single repository on GitHub. Some lessons have supplementary modules, but you do not need to be prepared to teach the supplementary modules for your teaching demonstration.

For example, if you have chosen The Unix Shell, I may assign you any episode listed at http://swcarpentry.github.io/shell-novice/.

Please visit the Etherpad a little while before the demo starts, I will post a link there to another Etherpad we will be using for this demo.

See you at the demo session,

[ sender name ]

Trainee didn’t pass teaching demo¶

Subject: Carpentries instructor training: Teaching Demo

Hi [ trainee name ],

Thank you for doing a teaching demonstration. While you demonstrated good command of the subject material, I’ve determined not to pass you based on [ reason ]. [ Explanation of this reason. ] We are excited about having you as a Carpentries instructor and I would be happy to see you do another teaching demonstration [ making these changes ] to certify as an instructor.

Please let me know if you have any questions.

Best wishes,

[ sender name ]

Trainee did pass teaching demo¶

Subject: Carpentries instructor training: Teaching Demo

Hi [ trainee name ],

I’m happy to tell you that you have passed your teaching demonstration! You demonstrated a good command of the subject material and a solid understanding of The Carpentries teaching methods. We are excited about having you as a Carpentries instructor. I’ve forwarded this information to our staff. If this was the last stage in your instructor training checkout, you should get your official The Carpentries Instructor certificate in about a week, along with instructions for signing up to teach workshops. If you still have steps remaining in your checkout, please be sure to complete them before your deadline. If you have any questions, please email checkout@carpentries.org.

Welcome to The Carpentries Instructor community!

Best wishes,

[ sender name ]

Templates in Spanish¶

Bilingual Demo Session Reminder Email¶

Subject: Carpentries instructor training: Teaching Demo

Hello,

Thanks for signing up to complete your “Teaching Demo” as part of the instructor certification process. We will meet on [ Insert Date ] at [ Insert Time ] in this Zoom videoconferencing room (https://carpentries.zoom.us/my/carpentriesroom3). Please read this short bi-lingual description of how Teaching Demo session works (https://github.com/carpentries/latinoamerica/blob/master/traducciones/demo.md). Disclaimer: I understand Spanish better than I speak it. So, I will talk in Spanish as much as I can, but I will most likely give feedback about your teaching in English.

Please let me know if you have any questions or concerns.

Hola,

Gracias por inscribirte para completar tu demostración de enseñanza como parte del proceso de certificación para instructores. Nos reuniremos [ Insert Date ] [ insert time ] aquí: (https://carpentries.zoom.us/j/357144246). Por favor, lee ésta breve descripción bilingüe de cómo funciona la sesión de demostración de enseñanza aquí: (https://github.com/carpentries/latinoamerica/blob/master/traducciones/demo.md). Aviso: Entiendo el español mejor de lo que hablo. Por lo tanto, voy a hablar en español un poco, pero es muy probable que les dé comentarios sobre su enseñanza en Inglés.

Por favor, hazme saber si tienes alguna pregunta o inquietud.

Best/Saludos,

[ sender name ]

Spanish: trainee did not pass teaching demo¶

Subject: Entrenamiento para instructor de las Carpentries: Demostración de enseñanza

Hola [nombre del aprendiz],

Gracias por presentar tu demostración de enseñanza. A pesar de que has demostrado un buen conocimiento de los temas cubiertos, he determinado no aprobarte basada/o en [razón]. [Explicar la razón]. Estaremos muy contentos de recibirte como instructor de las Carpentries en el futuro y me gustaría verte hacer otra demostración [especificar los cambios necesarios] para certificarte como instructor.

Por favor, hazme saber si tienes alguna pregunta o inquietud.

Saludos,

[nombre del remitente]

Spanish: trainee did pass teaching demo¶

Subject: Entrenamiento para instructor de las Carpentries: Demostración de enseñanza

Hola [nombre del aprendiz],

Estoy muy contenta/o de informarte que has pasado tu demostración de enseñanza. Has demostrado un buen dominio del contenido de los materiales y de las metodologías de enseñanza de las Carpentries. EEs un gusto recibirte como instructor/a de las Carpentries. Ya he mandado esta información a nuestro staff. Si esta fue la última parte de tu proceso de certificación recibirás tu certificado oficial de las Carpentries en alrededor de una semana junto con las instrucciones para inscribirte para impartir talleres. Si aún tienes que completar algunos pasos en tu proceso de certificación asegúrate de completarlos antes de la fecha límite. Si tienes alguna pregunta, por favor manda un correo a heckout@carpentries.org.

Bienvenida/o a la comunidad de las Carpentries.

Saludos,

[nombre del remitente]

Para Administrators¶

Tracking Trainee Checkout Progress¶

Accepting Trainee Applications¶

All trainees will be reminded before and during the training event to complete the instructor application.
Carpentries Staff will assign all applications to the relevant training event in AMY.

Tracking Training Event Attendance¶

After a training event, trainers will email a list of trainees who completed and did not complete the event to checkout@carpentries.org.
Carpentries Staff will go to this person”s record in AMY and mark this step complete.

Tracking Discussion Attendance¶

After Community discussion sessions hosts will fill out the host questionarre.
Carpentries Staff will use this information to update trainee”s records in AMY and mark this step complete.

Tracking Teaching Demos¶

Discussion session hosts will email a list of trainees who participated in a teaching demo to checkout@carpentries.org, noting whether each participant passed or failed.
Carpentries Staff will go to this person”s record in AMY and mark this step complete.

Tracking Lesson Contributions¶

Trainees should email the link to their contribution to checkout@carpentries.org.
Carpentries Staff will go to this person”s record in AMY and mark this step as complete, including a link to their contribution.

Recording Extensions to Complete Checkout¶

A trainee may ask for an extension on their three months to complete their checkout.
Carpentries staff will go to this person”s record in AMY and make a comment in the notes field that an extension has been granted for three months from when requested.
The note should read: Extension granted through [DATE] - [STAFF INITIALS]

Awarding badges¶

Search in AMY for all persons not badged but eligible for a badge.
Open that person”s record and add SWC or DC instructor badge.

Trainee no-shows and cancellations¶

Cancellations¶

Cancellations with less than one week”s notice are treated as no-shows. See below. If a trainee gives at least one week”s notice that they will not be attending the event:

Cancellations (member seat):

In the Trainee”s record in AMY, go to Edit –> Tasks. Click the red X next to the task for the training they missed.
In Eventbrite, cancel this person”s registration. This ensures the member registration code can be used again.
Send Trainee and member contact this template email.

Cancellations (open seat):

In the Trainee”s record in AMY, go to Edit –> Tasks. Click the red X next to the task for the training they missed.
In Eventbrite, cancel this person”s registration.
Send trainnee this template email.

No-shows¶

If a trainee does not attend the training and does not give notice at least one week in advance:

Emergency situations, as determined by Carpentries staff (member seat):

In the Trainee”s record in AMY, go to Edit –> Tasks. Click the red X next to the task for the training they missed.
In Eventbrite, cancel this person”s registration. This ensures the member registration code can be used again.
Send Trainee and member contact this template email.

Emergency situations, as determined by Carpentries staff (open seat):

In the Trainee”s record in AMY, go to Edit –> Tasks. Click the red X next to the task for the training they missed.
Send Trainee and member contact this template email.

Non-Emergency situations (member seat):

In the trainee’s person record in AMY in the “Instructor Training Progress” section, add “Training” = FAILED.
Send Trainee and member contact this template email.

Non-Emergency situations (open seat):

In the trainee’s person record in AMY in the “Instructor Training Progress” section, add “Training” = FAILED.
No notification is sent. If the trainee contacts us, respond with template email.

Scheduling Training Events¶

The Program Manager collects availability from Instructor Trainers and generates a four month training calendar (January-April, May-August, September-December) three times a year.

Trainees will be asked for their availability in October, March, and July for each four month block, and a calendar will be published 6-8 weeks before each four month block.

Once the calendar is confirmed, the Program Manager updates it on the Member information page and on the internal Carpentries staff Zoom calendars. The Workshop Administration Team will create events in AMY for each of these scheduled trainings. The Workshop Administration Team will also create an Eventbrite registration page for each event and set up surveys in Survey Monkey for each event. Lastly, the Workshop Administration Team will reserve Zoom Room 1 for each event.

For Online Training Events¶

Trainees for each event may be a mix of member-affiliated and non-member affiliated (open training) applicants. Seats are first opened to member-affiliated applicants. One month before the event, remaining seats are offered to open training applicants.

The Director of Memberships or the Administrative Specialist notify the Program Manager when new member sites are ready for instructor training in Asana. This includes information about the agreement start and end dates, number of workshops and instructor training seats allowed, and any other special information. The Administrative Specialist enters this information in AMY. The Workshop Administration Team creates an Eventbrite registration code for this new membership. Note the registration codes document is available to Carpentries staff only.

The Program Manager emails member sites to introduce The Carpentries” Instructor Training Program and give their team members the opportunity to join posted training events according to these guidelines.

The Member contact invites their team members to sign up for an event as a team or as individuals. Individuals associated with member sites can sign up for an event at any time.

During the first week of each month, the Workshop Administration Team invites accepted applicants from the open application pool to register for upcoming events. The accepted applicant list is the union of these two queries in AMY:

State = «Accepted» and Matched = «Unmatched»
State = «Accepted» and Matched = «Matched trainee, Unmatched training»

One month before each event the Workshop Administration Team emails the event”s Trainers with information about setting up the website and etherpad for the event, and generally preparing to teach.

Two weeks before each event, the Workshop Administration Team will begin monitoring the event”s waitlist. If there are any cancellations, the seat will be offered to the next person on the waitlist. If this person does not claim their seat, it will go to the next person, and so on.

One week before each event, the Workshop Administration Team:

emails all registrants from Eventbrite with information to prepare for the training event.
emails the Trainers with information including Zoom room access and survey results.

During the training event, the Workshop Administration Team:

enters all registrants into AMY, associating them with the given event and membership.
contacts trainees missing their application form, asking them to submit it.

After the event, the Workshop Administration Team:

emails trainees missing applications
asks Trainers to send attendance list
records people who completed training and subsequent checkout steps in AMY. Emails about the training and checkout progress are typically sent to checkout@carpentries.org, a mailbox in Helpscout.

Email Templates (Administrators)¶

Initial Member Contact Email (online training)¶

SUBJECT: Carpentries Instructor Training for [ site_name ]

Hi [ site contact name ],

Congratulations on your institution’s [ new membership with The Carpentries / Carpentries membership renewal ]. As a [silver/gold/platinum] member, you have a total of [ number ] seats in Instructor Training available to you. We’d like to get you set up for Instructor Training early in your membership year so that your new Instructors can productively build a Carpentries community at your institution.

We run two-day, online Instructor Training workshops multiple times per month. These events are scheduled for a range of time zones, to better serve our global community. We recommend, if possible, that your trainees join the same training event and are co-localized. This enables them to know each other over the course of the event and build up your local community. We recognize that it can be difficult to coordinate everyone’s schedules, however, so we do provide the flexibility of trainees joining different events. If your trainees are not able to attend an event together as a team, we recommend that you host a social event for your trainees (and others in your community) to get together.

To register, please direct your team members to our Instructor Training workshop registration page (http://carpentries.github.io/instructor-training/training_calendar/index.html). Your trainees should register with the code: [ insert code here in bold ]. This code can be used [ number ] times. Please be sure to share this code with your trainees. They should also fill out our application form ( https://amy.carpentries.org/forms/request_training/ ) using the same code. For guidance about how to select your trainees, please visit our Information for Member Organisations page at http://carpentries.github.io/instructor-training/members/.

You can use this email template (https://docs.carpentries.org/topic_folders/instructor_training/email_templates_admin.html#initial-trainee-contact-email-from-member-site-to-their-prospective-trainees-online-training) to send this information to your group. If one of your affiliates is not able to attend after they”ve registered for an event, please get in touch with us at team@carpentries.org as soon as possible. In some cases, we will be able to transfer your training seat to another event. However, because the success of our program depends on accurately predicting our capacity needs, we may not be able to accommodate changes in registration unless we are notified at least one week in advance of the event.

Note that in order to provide the best experience for our trainees, in rare instances events may be canceled due to low enrollment. If this happens, your trainees will be notified two weeks before the event and will have the opportunity to sign up for a future event.

For more information about our Instructor Training program, including details about our curriculum, certification process, and logistical details of the training event itself, please visit our Information for Member Organisations page at http://carpentries.github.io/instructor-training/members/.

I’m excited to help you build your team of Carpentries instructors at [ site_name ]. Please let me know once you’ve shared this registration information with your trainees so we know that your team is ready to come on board. Feel free to get in touch if you have any questions about this process, including checking on the status of your remaining seats.

Best,

[ sender name ]

Introducing Host and Trainers (in-person training)¶

SUBJECT: Carpentries Instructor Training [date] @ [site name]: Making Introductions

Hi all,

This email is to introduce [ host_name ] of [ site_name ] with trainers [ instructor1_name ] and [ instructor2_name ]. They will be teaching an in-person Carpentries Instructor Training on[ workshop_date ] at [site_name] .

Instructors will work directly with [host_name] to make travel arrangements. We are not part of this process. This may include airfare, ground travel, hotel, and meals/incidentals. [host_name], it is up to you whether you want to book things directly or have instructors make their own arrangements and get reimbursed. Either way, please keep in mind our instructors are volunteering two days of their time to train your participants, so please support them in making travel and reimbursement as smooth as possible.

[ instructor1_name ] and [ instructor2_name ] , please feel free to introduce yourselves and share a bit about your backgrounds. We value the background and expertise you bring to this, and want to hear about you.

[ admin_name ] will be sending an email to all of the trainees [ month when email will be sent ] with information needed to prepare for the workshop. I will also be supporting all the administrative details to make this event a success.

[ host_name ] as you prepare for the training please keep in mind that there will be several breakout sessions during the training. If possible, please reserve at least 2 additional rooms for this to take place. Also, the instructors will be using sticky notes throughout the training, so please have 2 colors of sticky notes (enough for each person to have at least 4 of each color). These are essential to the way we operate.

Please let me know if you have any questions or concerns,

Best,

[ sender name ]

Initial Trainee Contact Email (from member site to their prospective trainees - online training)¶

SUBJECT: Invitation to become a certified Carpentries Instructor

Dear [ name ],

We are excited to announce that [ site name ] has become a member of The Carpentries!

The Carpentries (http://carpentries.org) is a global group of volunteers who develop and teach two-day, interactive, hands-on workshops on essential computing and data skills that are not part of basic research training in most disciplines.

As part of our Carpentries membership, we are able to have [ number ] people from [ site name ] complete The Carpentries’ instructor training program (https://carpentries.github.io/instructor-training/) and become certified Carpentries instructors. Certified instructors can teach Carpentries workshops (https://carpentries.org/workshops/), helping us reach more people and build these skills across our community. Instructors also have the opportunity to travel to teach Carpentries workshops at other institutions around the globe.

I would like to invite you to you to become one of our Carpentries instructors. Instructor training is held online via video-conference, over two consecutive days. If you are interested in becoming a Carpentries instructor, please register for one of the training events listed here: ( https://carpentries.github.io/instructor-training/training_calendar/ ) Please note you must use this code to register: [ code ]. You will also need to complete The Carpentries instructor training application form using the same registration code: https://amy.carpentries.org/forms/request_training/. This application is a formality - you are guaranteed to be accepted into the training program - but The Carpentries staff needs this application in order to get your information for training into their system.

If you are not interested in becoming a Carpentries instructor, or don’t have time - please let me know as soon as possible so that I can offer this seat to another person.

We are all excited to grow our Carpentries community and look forward to bringing you on board.

If you have any questions please contact me or The Carpentries team at team@carpentries.org.

Best,

[ sender name ]

Invitation to Open Training Applicants¶

SUBJECT: Invitation to join The Carpentries Instructor Training

Dear future Carpentries Instructor,

Thank you again for applying to our open Instructor Training program. We are excited to offer you the opportunity to register for an upcoming online instructor training event. You can check out our calendar of events here: (https://carpentries.github.io/instructor-training/training_calendar/) and sign up for any event that is less than one month away.

To register, click on the event you are interested in and use the following code on the Eventbrite page: [INSERT CODE]. Please do not share this code. Registration for open training applicants begins one month before each event, and closes one week before each event. Since you have been accepted for training, you may verify that you have completed the application when prompted to do so. It is not necessary to fill out the Instructor Training application again.

We will send periodic reminders when new events are open, but you may register for any event during the open period between 1 month and 1 week before the start date.

Please let me know if you have any questions about these instructions or if you would like to unsubscribe from these event invitations. We look forward to you joining The Carpentries community!

Best,

[INSERT SENDER’S NAME]

One Month Trainer Email (online training)¶

Hi [INSERT TRAINER NAMES],

Thank you for volunteering to teach the online Instructor Training on [INSERT DATES/TIME ZONE]! This email will help you to prepare for the training - please read it carefully and let me know if you have any questions.

Please set up the website for your training using this template: https://github.com/carpentries/training-template. Your workshop ID is [INSERT SLUG 20xx-xx-xx-ttt-online]. Please be sure to send me the link to your website.

You can create an Etherpad for your training using this template: https://pad.carpentries.org/ttt-template. This template includes all of the exercises and key-points of the lessons. Please feel free to customize your Etherpad as appropriate.

Get in touch with your co-Trainer(s) to decide who will teach which sections of the curriculum: http://carpentries.github.io/instructor-training/. This is also a good time to decide how you and your co-Trainer(s) will communicate during the training. We recommend using Slack direct message for this.

One week before the event, I will send you the final number registered for this Training. Please let me know if you have any questions about how to prepare for your event. I’ll also be checking in with you about a week before the event to share video-conferencing connection information and see if I can help with any last-minute questions.

Best,

[INSERT SENDER NAME]

One Week Trainer Email (online training)¶

Hi [INSERT TRAINERS NAMES],

We are just days away from the online Instructor Training to be held on [INSERT DATE/TIME ZONE]! Registration for your training has now closed and you have a total of [INSERT # OF PARTICIPANTS] signed up.

You should have just received the email I sent to your participants including Zoom room connection information and homework. Please let me know if there is any other information specific to your event that you would like shared with your trainees.

This event uses the Zoom video-conferencing platform. You can read more about how to use Zoom here: https://docs.carpentries.org/topic_folders/instructor_training/trainers_guide.html?highlight=zoom#zoom-manual-online-trainings. Logging in with the credentials below will give you host access, including creating breakout rooms and muting participants as needed. Please do not share these credentials with anyone. Participants will be given a direct link to enter the Zoom room and do not need these credentials.

Username: room1@carpentries.org Password: (hide for template email) Direct link: https://carpentries.zoom.us/my/carpentriesroom1

Your participants will be completing a survey before the event. This survey gives information about your participants’ backgrounds and expectations. Please look through the responses before your event. Your trainees will also be filling out a survey after the event. Below you will find the links to survey responses for your event. Please do not share these links.

Pre: [INSERT LINK] Post: [INSERT LINK]

Please be sure to take attendance both days of the training. Send the list of attendees who completed both days, as well as those who didn’t, to checkout@carpentries.org, along with any notes or feedback you would like to share. We need this list of names in order to give credit to trainees.

If you have any questions, please let me know.

Wishing you much success during your training! Best, [INSERT SENDER’S NAME]

One Week Trainee Email (online training)¶

SUBJECT: Information for your upcoming Instructor Training with The Carpentries

Hello everyone,

Thank you for registering for The Carpentries Instructor Training workshop on [ DATE-TIME-TIMEZONE ]. This email contains important information to help you prepare for the training - please read it carefully and let me know if you have any questions.

This training is for people who want to become certified Carpentries instructors. This workshop will introduce you to evidence-based best-practices of teaching. We will teach you how to create a positive environment for learners at your workshops, provide opportunities for you to practice and build your teaching skills, help you become integrated into the Carpentries community, and prepare you to use these teaching skills in teaching Carpentries workshops. For more information about what will be covered at this training, check out our Instructor Training curriculum: http://carpentries.github.io/instructor-training/.

This is training for teaching, not technical training. We recommend that you be familiar with at least one of the technologies that we teach (R, Python, the Unix bash shell, SQL, OpenRefine, spreadsheet software, and/or Git) before taking Instructor Training. We will not be covering the contents of our workshop curricula during Instructor Training, but we do provide optional post-training onboarding sessions and mentoring opportunities to help prepare Instructors to teach particular curricula.

Our instructor Trainers [ trainer1 ] and [ trainer2 ] will be leading your training. This online training will be conducted using the Zoom video conferencing platform. No log in is needed, but you may need to install a browser extension. To access the training please use this link: [INSERT LINK]. All participants are required to have their own laptop and earbuds/headphones. Some participants may be attending the training in the same room. If this is the case, please be sure that everyone is wearing their earbuds/headphones and are muted at all times when not speaking. Your Trainers have put together a workshop website with information about the schedule: [INSERT LINK]

Attendance is required for the full two-days of the workshop in order to certify as a Carpentries Instructor. Participants who miss more than one hour will not pass our training requirements. If you know ahead of time that you will miss an hour of the training, please notify your Trainers.

Before your training, please:

Complete our pre-workshop survey [INSERT LINK]. Your responses will help your Trainers understand your background and customize the workshop appropriately.
Read this short paper: https://carpentries.github.io/instructor-training/files/papers/science-of-learning-2015.pdf which provides a brief overview of some key evidence-based results in teaching.
Go to the Software Carpentry lessons page (http://software-carpentry.org/lessons/), the Data Carpentry lessons page (http://www.datacarpentry.org/lessons/), or the Library Carpentry lessons page (https://librarycarpentry.org/lessons/) to see what we currently teach. Carefully read through one episode of your choice. You will be using your selected episode for several in-class exercises, so be sure you are comfortable with the content. Note: an episode is not the entire lesson, but a single page of the lesson.

After your training, you will be asked to do three follow-up exercises online in order to become a certified Instructor. These requirements are detailed at http://carpentries.github.io/instructor-training/checkout/ and will be discussed at your training. If you have any questions about the workshop, the reading material, or anything else, please don’t hesitate to get in touch.

Happy Training - we are excited to have you on board!

Best, [ SENDER’S NAME ]

Missing Instructor Training applications¶

SUBJECT: Carpentries Instructor Training: Missing Application

Hi [ trainee name ],

On [ training_dates ], you [ participated (or) will be participating ] in an Instructor Training event for The Carpentries, but we have not yet received an application from you. To ensure that we can get you into our system and track your progress towards Instructor certification, please fill out the Instructor application form here: https://amy.carpentries.org/forms/request_training/.

Please use [ group_code ] as your group name.

Please contact checkout@carpentries.org if you have any any questions.

Best, [ sender name ]

Attendance checkout¶

SUBJECT: Carpentries Instructor Training [DATE]: Final Attendance

Hi [TRAINER NAMES],

Thanks again for teaching The Carpentries Instructor Training on [INSERT DATE]. I hope that you had a great experience. This is a friendly reminder to please send a list of participants who attended both days of your training, as well as who did not complete the training, to checkout@carpentries.org. Without this list, we are unable to give attendees credit for completing the training.

Please let me know if you have any questions.

Best, [ SENDER NAME]

Event Cancelation (online training)¶

Dear [ Trainer names ],

Thank you for volunteering to teach The Carpentries Instructor Training on [ dates/ time/timezone ]. Unfortunately, due to low enrollment, we will be cancelling this event. We are working on ways to better estimate our capacity needs so that we won’t need to cancel events in the future. Thank you again for all of the time you give to the community - I greatly appreciate your time and regret having to cancel this event. I hope we can get you in on another event later this year. Please let me know if you have any questions.

Best,

[ sender name ]

No-Show - Emergency Member (online training)¶

Note: This email will be sent as a response to contact from trainee or member site contact and doesn’t require a special subject line.

Dear [ trainee name ], (cc member site contact)

Thank you for letting us know why you were not able to attend The Carpentries Instructor Training on [ date of training ]. I’m sorry to hear about [ reason for emergency ] and would like to extend an invitation for you to attend a future online training event at a time that is convenient for you. When you’re able, please look at our calendar of upcoming events here: http://carpentries.github.io/instructor-training/training_calendar/index.html and register for an event that matches your availability. If you won’t be able to join an event and would prefer to transfer your seat in Instructor Training to someone else at your institution, please let us know and we will make the necessary arrangements with [ name of member site contact ].

Thank you for your involvement with The Carpentries community. We hope you’ll be able to join the Instructor team soon!

Best, [ name ]

No-Show - Emergency Open Applicant¶

Note: This email will be sent as a response to contact from trainee and doesn’t require a special subject line.

Dear [ trainee name ],

Thank you for letting us know why you were not able to attend The Carpentries Instructor Training on [ date of training ]. I’m sorry to hear about [ reason for emergency ] and would like to extend an invitation for you to attend a future online training event at a time that is convenient for you. When you’re able, please look at our calendar of upcoming events here: http://carpentries.github.io/instructor-training/training_calendar/index.html and register for an event that matches your availability. If you won’t be able to join an event and would prefer to transfer your seat to someone else on our waiting list, please let us know.

Thank you for your involvement with The Carpentries community. We hope you’ll be able to join the Instructor team soon!

Best, [ name ]

No-Show - Non-Emergency Member (online training)¶

SUBJECT: Missed you at The Carpentries Instructor Training!

Dear [ trainee name ], (cc member site contact)

We missed you at The Carpentries Instructor Training on [ date of training ] and wanted to reach out to you. Generally, we need to count no-shows in the number of Instructor Training seats that our institutional member sites use towards their membership benefits. This is to ensure that we are able to accurately plan our capacity for trainings. Since we didn’t hear from you before the event, we will be counting your seat as forfeited. We do make exceptions in limited circumstances (e.g. illness), so please do reach out to us if there was an extenuating circumstance and we will be able to make alternative arrangements for you to join another training event.

Looking forward to hearing back from you and to having you as part of The Carpentries Instructor team!

Best, [ name ]

No-Show Non-Emergency Open Applicant¶

Note: This email will be sent as a response to contact from trainee and doesn’t require a special subject line.

Dear [ trainee name ],

Thank you for reaching out to us about missing The Carpentries Instructor Training on [ date of training ]. Generally, we need to count no-shows as forfeited seats to ensure that we are able to accurately plan our capacity for trainings. Since we didn’t hear from you before the event, we will be counting your seat as forfeited. If you would like to be considered for a future Instructor Training event, you will need to submit a new application and be added to the waiting list. We do make exceptions to this policy in limited circumstances (e.g. illness), so please do reach out to us if there was an extenuating circumstance and we will be able to make alternative arrangements for you to join another training event without needing to go through the application process again.

Looking forward to hearing back from you and to having you as part of The Carpentries Instructor team!

Best, [ name ]

Cancellation - Member at least one week notice (online training)¶

Note: This email will be sent as a response to contact from trainee or member site contact and doesn’t require a special subject line.

Dear [ trainee name ], (cc member site contact)

Thank you for letting us know you will not be able to attend The Carpentries Instructor Training on [ date of training ]. We’re sorry you won’t be able to join us and would like to extend an invitation for you to attend a future online training event at a time that is convenient for you. Please look at our calendar of upcoming events here: http://carpentries.github.io/instructor-training/training_calendar/index.html and register for an event that matches your availability. If you won’t be able to join an event and would prefer to transfer your seat in Instructor Training to someone else at your institution, please let us know and we will make the necessary arrangements with [ name of member site contact ].

Thank you for your involvement with The Carpentries community. We hope you’ll be able to join the Instructor team soon!

Best, [ name ]

Cancellation - Open Applicant at least one week notice¶

Note: This email will be sent as a response to contact from trainee and doesn’t require a special subject line.

Dear [ trainee name ],

Thank you for letting us know you will not be able to attend The Carpentries Instructor Training on [ date of training ]. We’re sorry you won’t be able to join us and hope that you will be able to attend a future online training event. We have placed you back on the waiting list and you will continue to receive invitations to upcoming Instructor Training events when seats become available.

If you won’t be able to join an event and would prefer to take your name off the waiting list, please let us know.

Thank you for your involvement with The Carpentries community. We hope you’ll be able to join the Instructor team soon!

Best, [ name ]

Follow-up - Trainers Attendance List¶

Hi [INSERT TRAINERS NAMES],

Thank you for taking time to teach the Carpentries Instructor Training on [INSERT DATES]! I hope you had a great experience. I am following up with you to obtain the attendance from the training.

For your convenience, I have included the names of trainees in this [INSERT FILE]. Please indicate the attendance for both days so that I can record their progress and get them on track to becoming certified Carpentries instructors!

Please let me know if you have any questions.

Best,

[ sender name ]

Zoom test invitation to host site¶

Hi [Host Name],

Thank you for hosting a Carpentries Instructor Training on [ date/time including time zone]. We will be using the Zoom videoconferencing platform for this event. To ensure that the training runs smoothly, I’d like to set up a Zoom test run with you prior to the event. This should not take much time, however, it is important that this happens to detect any problems and have time to troubleshoot them prior to the training. We all want to stick to the schedule, and want to avoid spending time troubleshooting on the morning of the event.

A few things to consider when conducting the test:

Be in the room that the training will take place in.
Have access to the audio system that will be used
Have access to the projector that will be used

We will make sure that we can see and hear each other, and that I can see all the seats people will be in for the event itself.

To schedule a test run, you can [ email me/look at my calendar ]. Please let me know if you cannot find a time that works, so we can look for some other options.

I”m looking forward to having your team on board! Please let me know if you have any questions about how this works.

Best, [ sender name ]

Response to Instructor Training Inquiry¶

Hi [ name ],

Thank you for your interest in becoming a Carpentries Instructor! It sounds like you might be interested in applying to our Open Instructor Training program. Training slots are made available for free to Open applicants when they are not claimed by a member institution one month in advance.

We rank applications on a rolling basis; we are working to reduce wait times, but at present expect a delay of at least 1 month. If you have a specific need to be trained sooner (e.g. an upcoming workshop) please let us know. Multiple applicants from a single institution generally will not be invited at once, but may be accepted individually over time. To more rapidly build an Instructor community at your institution, consider becoming a Member. For more information see: https://carpentries.org/membership/.

The instructor training application is here: https://amy.carpentries.org/forms/request_training/. In order to have your application considered for Open training, be sure to leave the “Registration Code” entry space blank. Note that the expectations for Instructors are also listed on this page, and are a good idea to check before applying.

In the mean time, there are many ways to get involved with The Carpentries. For a complete list of roles, see our website here: https://carpentries.org/community/.

Thank you again for your interest in The Carpentries! I look forward to seeing you around the community.

Best regards,

[ sender name ]

Response to Instructor Training Application¶

This email is usually sent with a script. The canonical version of the text is the version below.

Hi [ name ],

Thank you for applying for The Carpentries Instructor Training program. We’re excited to have you as part of our community.

If you submitted your application for a specific instructor training workshop, please disregard the message below.

We receive hundreds of applications, and we cannot provide no-cost training for every applicant. Please, don”t let that discourage you! We”d like to help you bring workshops and instructor training to your organization. We’re working on ways to increase our capacity to offer trainings to individuals not affiliated with member institutions, and hope to be able to offer more of these trainings soon. Your application has been placed on our waiting list while we grow our capacity.

If you’d like to become a Member, get in touch with memberships@carpentries.org to learn more about how we can help you make the case at your organization. In the meantime, please get involved!

Join our discussion email list (https://carpentries.topicbox.com/groups/discuss)
Follow us on Twitter (@thecarpentries, @datacarpentry, @swcarpentry, and @libcarpentry)
Help at a local workshop (https://carpentries.org/)
Learn about our community (https://carpentries.org/community/)

Learn more about us!

Read our blogs (https://carpentries.org/blog/, http://www.datacarpentry.org/blog/, https://software-carpentry.org/blog/, and https://librarycarpentry.org/blog/)
Sign-up for our newsletter (https://carpentries.org/newsletter/)

Most of our instructor training events are offered as part of institutional memberships and Member organizations receive training priority. To fast-track your application, consider becoming a Member. For more information see: https://carpentries.org/membership/.

If you have questions about your application, please contact team@carpentries.org. Thanks again for applying!

Best, [ sender name ]

Checkout deadline approaching¶

Subject: Carpentries instructor training: Deadline approaching

Hi everyone,

You’re receiving this email because you recently attended a training event to become an Instructor with The Carpentries, but haven’t yet completed the follow-up tasks to become certified. We generally require new instructors to complete certification within three months of their training, to ensure that they are up to date on our teaching methods and practices. If you are still planning on certifying and would like an extension on your deadline, please send an email to checkout@carpentries.org. If you believe you’re receiving this email in error and have already completed the checkout process, please get in touch as we may have missed recording one of your checkout steps.

If you have any questions about the checkout process, please take a look at our checklist: http://www.datacarpentry.org/checkout/ and feel free to send any questions to checkout@carpentries.org.

Looking forward to having you as part of our Instructor community!

Best wishes,

[ sender name ]

Completed everything except lesson contribution¶

Subject: Carpentries instructor training: Lesson Contribution

Hi [ trainee name ],

Thank you for participating in an instructor discussion session and a teaching demonstration. I’d like to check you off in our system and issue you your instructor certification, but I don’t currently have a record of your lesson contribution. If you’ve already made a contribution, please send me a link to the PR or issue. If you’re working on your contribution, please check out these guidelines for some tips.

Please get in touch if you have any questions.

Best,

[ sender name ]

Completed lesson contribution¶

Subject: Carpentries instructor training: Discussion and teaching demo

Hi [ trainee_name ],

Thanks very much for your lesson contribution. When you have a moment, please go to the instructor discussion etherpad here: (https://pad.carpentries.org/instructor-discussion) to sign up for a discussion session, and then to the teaching demo etherpad (https://pad.carpentries.org/teaching-demos-recovered) to sign up for your final demo. For more information about completing your instructor certification, please see our simplified checklist: (http://www.datacarpentry.org/checkout/) and let us know if you have any questions.

Best,

[ name ]

Checkout extension granted¶

Subject: Carpentries instructor training: Extension granted

Hi [ trainee name ],

Thanks for getting in touch. I”ve recorded an extension for you through the end of [Month Year]. Please let me know if there”s anything else I can do to help with the checkout process. Looking forward to having you as a Carpentries instructor!

Best, [ sender name ]

Checkout completed¶

This email is usually sent with a script. The canonical version of the text is the version below.

Subject: Carpentries instructor training: Checkout completed

Hi [ trainee name ],

Thank you for completing your checkout. I”ve updated your status in our database and you are now officially certified as a Carpentries instructor. Your certificate is attached. Congratulations!

Please note that although your certificate reads either Software Carpentry, Data Carpentry, or Library Carpentry you are fully certified to teach all workshops for The Carpentries.

If you haven”t already, please be sure to join the instructors mailing list (https://carpentries.topicbox.com/groups/instructors). This is where you”ll hear about opportunities to teach at upcoming workshops. You can also join the general discussion list (https://carpentries.topicbox.com/groups/discuss) for broader interactions with The Carpentries community. In addition to being able to teach at Carpentries-organized workshops, you are also able to organize and host your own local workshops. You can find more information about running a workshop here (https://docs.carpentries.org/topic_folders/hosts_instructors/index.html). Your status as a newly certified Instructor also makes you eligible to vote for The Carpentries” Executive Council. Read more here (https://docs.carpentries.org/topic_folders/governance/index.html).

We also have a team of Regional Coordinators who help run workshops and build Carpentries communities around the world. You can read more about who they are and what they do here: https://carpentries.org/regionalcoordinators/

Please let us know if there”s anything we can do to help and welcome to the community!

Best,[ sender name ]

Recruiting new Trainers¶

Subject: Opportunity to join The Carpentries Trainers community

Hi [ name ],

I wanted to get in touch with you about an opportunity to get involved with The Carpentries community. Software Carpentry (SWC), Library Carpentry (LC), and Data Carpentry (DC) are lesson programs of The Carpentries (a fiscally sponsored project of Community Initaitives). We are focused on spreading computational literacy to researchers around the world. We run intensive, hands-on, two-day workshops to help researchers and other professionals develop the fundamental computational skills they need to do their research. Together, we run over 300 workshops a year, and have reached more than 25,000 learners in 30 countries.

Our workshops are taught by volunteers who go through a two-day training program focused on pedagogy and cognitive psychology. These training events are run by our Instructor Trainers who also help to develop and maintain our instructor training curriculum.

The Carpentries Trainers are an eclectic group. Some of us have formal training in pedagogy, some are experienced Carpentries instructors, others run Carpentries-like trainings as part of their jobs. We all share a commitment to helping new instructors become familiar and comfortable with The Carpentries teaching practices and principles.

If you’re interested in joining the Trainer community, please apply here (https://goo.gl/forms/yTx9yJzdWy6OAPtS2)! Applications for this round will be open until [application_deadline].

If you have any questions about the training process or the expectations for being a Trainer, please contact team@carpentries.org

To learn more about what we teach, check out our lessons here: (https://software-carpentry.org/lessons/), here: (http://www.datacarpentry.org/lessons/), and here: (https://librarycarpentry.org/lessons/). More detailed information about what Trainers do can be found here: (https://github.com/carpentries/policies/blob/master/trainer-agreement.md).

Looking forward to seeing an application from you!

Best,

[ sender name ]

Accepting new Trainers¶

Subject: Congratulations! Join the Carpentries Trainer Community

Hi all,

Thank you all for applying to become instructor Trainers with the Carpentries. A group of Trainers have reviewed the applications and we”re excited to invite each of you to the Trainer team.

We”ll be starting our new cohort of instructor Trainers in [ month ]. Our cohort will be [ number ] folks located in [ countries ]. We”ll be meeting once a week starting in [ month ] to discuss our text and how it relates to our instructor training curriculum. More details can be found in the preliminary reading schedule.

If you”re interested in being part of this cohort, please try to complete the following by [ deadline ] so that we can finalize the schedule and start our meetings!

Please fill out this poll [ link ] for scheduling book club meetings. Don”t forget to adjust the timezone shown (pull down menu above the time list). Please choose the days and times that work for you for the entire 8 week period of our book club. To complete certification as a Trainer, we”ll ask that you miss at most one of our 8 book club meetings. Since we are spread across several time zones, please be as accommodating as possible in filling out your availability. We will have two meeting times per week to accomodate all time zones, but you will only need to attend one of the weekly meetings.
Please take a look over the process for trainer training and make sure that all of the requirements of becoming a Trainer work with your schedule and other responsibilities. We”re excited to have you in the Trainer community, but do want to make sure that all Trainers are able to commit the time required, so that we are able to realistically determine the number of instructors we train per year.
Please get a copy of our text [ link ]. I”ll send out reading assignments and discussion guides in a later email.
Please also fill out your availability for instructor training events for [ month through month ] and add your name to the Trainers list in the second tab. This cohort of Trainers will be ready to co-teach instructor training events by the end of [ month ] and to teach on their own shortly after that.
Please add upcoming Trainer meetings (http://pad.software-carpentry.org/trainers-backup) to your calendar. These are also on the Community Calendar. Each of these is held in two different time zones - you don”t need to attend both meetings, but you”re welcome to!
Please sign up for the Trainers email list (http://carpentries.topicbox.com/groups/trainers) if you haven”t already done so.
Please respond to this email with a quick introduction so that we can all get to know each other. I”ll send out my introduction as a separate email following this.

I know that”s a lot! Let me know if you have any questions. I”m looking forward to seeing you all at our first book club discussion.

Best, [ name ]

Para Organizaciones Miembro¶

Joining a Training Event¶

When a site signs a new member contract or otherwise schedules a training event with the Carpentries, the Program Manager will contact the site to discuss instructor training. This includes reviewing the training curriculum and certification process.

The Program Manager will share the member training process and the current member training calendar with the member site, and the site can choose the dates that work best for them.

The Program Manager will share information about the training with all participants, including a link to our application form and some pre-reading material.

Host Checklist¶

Our training events are typically offered using the Zoom videoconferencing platform.

Before the event, the Workshop Administration Team will be in touch with the host site to set a test run of the Zoom videoconferencing set up. For the test run, the host should:

be in the same room as the event itself
use the same equipment (computer, projector, speakers, microphone) as the event itself
make sure people in the room can see and hear the person on the screen
make sure the person on the screen can see and hear all participants

Other things to be set up for the event include:

Reminding participants of the pre-reading material that was shared by the Program Manager
Reviewing the schedule to arrange for lunch and coffee breaks. Providing refreshments is suggested (people learn better with fuel!), but not mandatory. A sample schedule is here.
Allowing for break out space during the event. The training includes partner and small group activities. If the room is big enough this can be done in different corners of the room. Otherwise, a hallway alcove or nearby office may be a good fit.

LESSON DEVELOPMENT¶

For more information on lesson development with The Carpentries, please visit The Carpentries Curriculum Development Handbook.

Lesson Development Roles¶

Curriculum Advisory Committee¶

Curriculum Advisors are part of a team that provides the oversight, vision, and leadership for a particular set of lessons. Advisors represent The Carpentries community and should strive to embody The Carpentries philosophy by:

Recognizing the importance of communication and being welcoming to all contributors.
Giving feedback to contributors using The Carpentries model:
- Find what’s good. Be specific about improvements needed. Use motivational language.
- Evaluating lesson contributions in light of The Carpentries pedagogical model:
- Teach what’s most relevant and useful for learners.
- Avoid getting bogged down in technical details.
- Keep language motivating.
- Emphasize the importance of continued learning and improvement.

Curriculum Advisors are responsible for:

Routinely, as needed:
- Responding to requests for comments on curriculum in GitHub.
- Acting as Maintainers for the workshop homepage repository for their curriculum - making sure it’s up to date with the overall goals of the workshops, correcting links to curriculum, and updating as needed.
Meet bi-annually to:
- Discuss curricular updates that have been proposed by Instructors, Maintainers, or other community members.
- Provide recommendations for other potential updates based on current approaches in the field.
- Discuss proposals for new lesson ideas and provide recommendations about whether they should be developed or accepted and whether they should be incorporated into existing workshop curriculum or standalone.
- Provide a written report of the meeting regarding decisions around curriculum updates and recommendations.
- Review individual lessons to make sure curriculum-level learning objectives are being met by the set of lessons.
- Prepare the workshop homepage repository for lesson release. Curriculum Advisors will be listed as Editors for this repository at release.

Curriculum Advisors commit to serving a one year term, but are welcome to continue for additional years.

Lesson Infrastructure Subcommittee¶

Members of the Lesson Infrastructure Subcommittee serve as Maintainers for The Carpentries lesson template and its documentation, as well as for the Carpentry workshop template. As Maintainers, they also follow the Maintainer Guidelines.

Bug BBQs¶

A Bug BBQ is a day-long community-wide lesson development event. The goal of a Bug BBQ is to prepare lessons for publication.

Scheduling a Bug BBQ¶

Information about how to schedule a Bug BBQ - coming soon!

Communicating about a Bug BBQ¶

Creating a Bug BBQ Website¶

Information about how to create a Bug BBQ website - coming soon!

Announcing a Bug BBQ (Blog post template)¶

The Carpentries is preparing to publish {{ lesson list }} on Zenodo in {{ month(s) }}. This will be the first publication for our new {{ new lesson list }} lessons. We regularly publish our lessons to provide stable identifiers for polished versions of the lessons. This enables referenced discussions of the lesson materials and gives contributors a verifiable product to cite on their CVs or resumes.

This release will include the following lessons: {{ bulleted list of lessons, for Data Carpentry lessons, link to the workshop home page instead of individual repos }}.

If you’ve made a contribution to one of these lessons, you’re already an author. Help make sure the final product is polished and complete by getting involved in the lesson release.

Here’s a run-down of the lesson release process and our timetable for this release.

Resolve existing PRs. {{ dates }}
Freeze lessons to new significant changes. {{ dates }}
Bug BBQ to clean up lessons. {{ dates }}
Publish! {{ dates }}

{{ day, month, time UTC - day, month, time UTC }}

Click [this link]({{ FIXME https://www.timeanddate.com/worldclock/fixedform.html }}) to see the event in your local time.

Join with the community in a hacky-day to submit Issues and PRs to identify and fix problems and get us ready to publish. We’ll provide communication channels for you to work with other community members and guidelines for how to get started. Keep an eye open for more information about the Bug BBQ!

We’re excited to work with the community to release {{ lessons }}. Put these dates on your calendar, and we’ll send out reminders and updates too. These lessons belong to the community - help keep them great!

Release Process and Schedule¶

Lessons are released on a 6-month release cycle. Lesson releases are named by the year and month they happen, e.g., 2016.05.

Each lesson lives in the gh-pages branch of its own repository.
When a release is made, the lesson Maintainer(s) create a branch named after the release, e.g., 2016.05.
A Release Maintainer generates HTML pages for that release and adds them to the branch.
If there isn”t already a directory for that release in the swc-releases repository, the Release Maintainer creates one and adds an index.html page to it.
The Release Maintainer adds a submodule to the release directory of swc-releases that points to the newly-created release branch of the lesson.

More information about lesson releases coming soon!

Lesson Release checklist¶

For each lesson release, copy this checklist to an issue and check off during preparation for release

Scheduled Freeze Date: YYYY-MM-DDScheduled Release Date: YYYY-MM-DD

Checklist of tasks to complete before release:

[ ] check that the learning objectives reflect the content of the lessons
[ ] check that learning objectives are phrased as statements using action words
[ ] check for typos
[ ] check that the live coding examples work as expected
[ ] if example code generates warnings, explain in narrative and instructor notes
[ ] check that challenges and their solutions work as expected
[ ] check that the challenges test skills that have been seen
[ ] check that the setup instructions are up to date (e.g., update version numbers)
[ ] check that data is available and mentions of the data in the lessons are accurate
[ ] check that the instructor guide is up to date with the content of the lessons
[ ] check that all the links within the lessons work (this should be automated)
[ ] check that the cheat sheets included in lessons are up to date (e.g., RStudio updates them regularly)
[ ] check that languge is clear and free of idioms and colloquialisms
[ ] make sure formatting of the code in the lesson looks good (e.g. line breaks)
[ ] check for clarity and flow of narrative
[ ] update README as needed
[ ] fill out “overview” for each module - minutes needed for teaching and exercises, questions and learning objectives
[ ] check that contributor guidelines are clear and consistent
[ ] clean up files (e.g. delete deprecated files, insure filenames are consistent)
[ ] update the release notes (NEWS)
[ ] tag release on GitHub

Upcoming Lesson Releases¶

Information about upcoming lesson releases - coming soon!

Email Templates¶

Curriculum Advisory Committee Invitation¶

Subject: Invitation to Join the [ carpentry org ] [ lesson title ] Curriculum Advisory Committee

Dear [ name ],

Thank you for your interest in being a member of the [ carpentry org ] [ lesson title ] Curriculum Advisory Committee! Because of your experience working with [ relevant data types ] and your perspective on and commitment to teaching [ lesson title ] data skills, we would like to invite you to be a member of this committee. We think you bring important and unique insight to what skills should be taught to [ lesson title ] researchers as well as how they should be taught.

The [ carpentry org ] [ lesson title ] curriculum aims to teach the core skills and perspectives for working effectively and reproducibly with [ lesson title ] data. The role of the [ carpentry org ] [ lesson title ] Curriculum Advisory Committee is to provide the oversight, vision and leadership for the [ lesson title ] curriculum as a whole.

This Committee will meet bi-annually to:

Discuss curricular updates that have been proposed by Instructors, Maintainers or other community members.
Provide recommendations for other potential updates based on current approaches in the field.
Discuss proposals for new lesson ideas and provide recommendations about whether they should be developed or accepted and whether they should be incorporated into existing workshop curriculum or as standalone lessons.
Provide a written report of the meeting regarding decisions around curriculum updates and recommendations.

Additionally Committee members are expected to:

Be familiar with [ carpentry org ] [ lesson title ] lesson content and respond to content-related issues on individual lessons as needed.
Act as Maintainers for the “[ lesson title ] workshop” repository, making sure it’s up to date with the overall goals of the workshops and correct links to curriculum and update as needed.

Prior to lesson release (currently on a 6 month schedule):

Review individual lessons to make sure curriculum-level learning objectives are being met by the set of lessons.
Prepare the ‘[ lesson title ] workshop’ repository for release. Will be Editors for this repository at release.

Please let me know if you are still interested in serving on the [ lesson title ] Curriculum Advisory Committee and can commit to these responsibilities. If you have any questions before you can accept this role, please also let me know.

Thanks so much. We look forward to the opportunity to work with you!

Best,

[ sender name ]

Initiate Scheduling of First Meeting¶

Subject: Scheduling First Meeting of the [ carpentry org ] [ lesson title ] Curriculum Advisory Committee

Hi everyone,

Thank you to those who so far have confirmed your interest in being a part of the committee. I”d like to get us started on setting up our first bi-annual meeting. This meeting will be between [date] and [date], in advance of the [upcoming Bug BBQ or lesson release] which will be held [dates].

At our first meeting, we will be making decisions about some core proposed revisions to the existing [lesson title] lessons. The developers and Maintainers of the lessons will be providing that list, along with relevant background information, for people to look over in preparation for the meeting.

To help schedule the meeting, could everyone please add their availability to this [whenisgood](link to whenisgood poll) by this coming Friday [(date)]? Please make sure to put in your time zone at the top of the poll. I”ll look at the results and let everyone know the meeting time by [date] so that you can clear up any holds on your calendar.

Please let me know if you have any questions in advance of our first meeting in a few weeks. I”m looking forward to meeting everyone soon!

Best, [ sender name ]

Announce Meeting Times and Dates¶

Subject: First Meeting of the [ carpentry org ] [ lesson title ] Curriculum Advisory Committee

Hi all,

Thanks again for being a part of the [lesson title] CAC. We”ll be having our first bi-annual meeting to prepare for the [upcoming Bug BBQ or lesson release] which will be held [dates]. To accommodate the geographical diversity of our committee members, we”ll be having two meetings. I strongly recommend that those who can attend both do so, as it will help to build consistency across the meetings and a team-feeling for the group. Of course, if you”re only able to attend one meeting, that”s fine too!

The meetings will be at the times linked below (please click the links to see the time in your own time zone). I”ll be sending out information about meeting location and agenda early next week.

[meeting time 1](link to timeanddate event announcer) [meeting time 2](link to timeanddate event announcer)

Please let me know if you have any questions. Looking forward to meeting everyone soon!

Best, [ sender name ]

Follow up from Curriculum Advisory Committee Meeting¶

Subject: Follow-up Items from [lesson title] Curriculum Advisory Committee Meetings

Hi all,

Thank you again for a very productive set of meetings last week. I”ve put together minutes for our two meetings (combined in [this document](link to meeting minutes in https://github.com/datacarpentry/curriculum-advisors/)), including decision points and action items for follow-up. I wanted to run these by everyone to make sure that I”ve correctly identified the decisions that were made before I follow up with the Maintainers to move these decisions forward.

It would be greatly appreciated if you could take a look at the minutes and let me know by [date and time UTC](link to timeanddate event announcer) if you see any problems or have any objections to the decisions and action items. At that point, I will follow up with the Maintainers on the next steps.

Thank you everyone for bringing your backgrounds and expertise to the meetings last week and for your deep thought about this curriculum. I”m excited about [upcoming publication or major lesson change].

Please let me know if you have any questions or comments.

Best, [ sender name ]

LESSON MAINTENANCE¶

Maintainer Guidelines¶

The Carpentries Maintainers work with the community to make sure that lessons stay up-to-date, accurate, functional and cohesive. They monitor their lesson repository, make sure that PRs and Issues are addressed in a timely manner, and participate in the lesson development cycle including lesson releases. They endeavor to be welcoming and supportive of contributions from all members of the community.

Maintainers are responsible for:

Routinely:
- Ensuring reasonable response time to all submitted Issues and PRs. At a minimum, ensuring all Issues and PRs are acknowledged within two days.
- Quickly addressing issues and PRs tagged as “bug”s.
- Submitting Issues as they arise.
- Adhering to the Code of Conduct and alerting the Policy Subcommittee to any potential violations.
- Identifying potential new Maintainers based on their review activity.
Every six months:
- Participating in regular Issue Bonanza and Bug BBQ events, including organizing and tagging issues.
- Bringing in updates to the lesson template.

Maintainers represent The Carpentries community and should strive to embody The Carpentries philosophy, by:

Recognizing the importance of communication and being welcoming to all contributors.
Giving feedback to contributors using the Carpentries model:
- Find what’s good. Be specific about improvements needed. Use motivational language.
Evaluating lesson contributions in light of Carpentries pedagogical model:
- Teach what’s most relevant and useful for learners.
- Avoid getting bogged down in technical details.
- Keep language motivating.
- Emphasize the importance of continued learning and improvement.

Note: These guidelines are adapted from those currently in use by the Data Carpentry Genomics Maintainers and are provisional. The Maintainer team will be deciding on official guidelines for the full set of Carpentries lesson Maintainers.

How to stay in touch¶

The overall Maintainer community communicates using our mailing list and our Slack channel. If you don”t already have a Slack account with the Carpentries, you can create one.

The Maintainer community meets monthly to discuss issues relevant to all lesson Maintainers. Our meeting schedule can be found on our Etherpad and on the community calendar.

Each Lesson Team also has their own Slack channel. A link to join your lesson”s Slack channel can be found in the README file in your lesson repository.

How to handle issues¶

Information coming soon.

How to get help¶

There are many ways to request help on an issue or PR you are reviewing. To get help from other Maintainers or the general community, use the help wanted or good first issue labels.

If an issue affects the overall structure or scope of the lesson, you can refer the issue to your curriculum”s Curriculum Advisory Subcommittee by using the status:refer-to-cac label. Remember that the Curriculum Advisors only meet once every six months (in advance of lesson releases) and they will likely not be able to provide a quick response to your question.

You can also get help from other Maintainers and interested community members by posting a question to your lesson”s Slack channel.

How to suggest changes to the styling for all lessons¶

Information coming soon.

Maintainer Onboarding¶

New Maintainers go through an onboarding process. The curriculum for onboarding new Maintainers is available as a Maintainer Onboarding Lesson. This documentation describes how to recruit new Maintainers and take them through the onboarding process.

The application to become a Maintainer is a Google form.
Advertise for new Maintainers on the blog, mailing lists and Twitter.
Once the application period has closed, reviewing applications and send accepted applicants an invitation to become a Maintainer.
To set up a scheduling poll to schedule Maintainer Onboarding, use WhenIsGood. Click «Use Timezones» and then «SHOW OPTIONS». Unselect Sunday and Saturday. Add Duration = 60 minutes. Select «hide dates».
Add Maintainers who are going through training to the maintainer-onboarding Google Group. This is where announcements about upcoming meetings should be sent.
After the deadline has passed for responding to the Maintainer Onboarding scheduling poll, select the two times that maximize attendance. This needs to be done manually from the whenisgood results, as there isn”t a «choose two times» option.
Populate the Maintainer onboarding Etherpad with meeting dates and times. Use timeanddate meeting time announcer links to make it easy for people to convert meeting times to their own time zone.
Send out an email to the Google Group letting everyone know about the scheduling.
Set up a new event in AMY with the slug YEAR-MO-DA-maintainer-onboarding. Add all maintainer trainees as learners. Add onboarding leader as instructor.
One week before the first onboarding meeting, send a reminder email to the Google Group.
Run the three weeks of meetings according to the curriculum. Keep record of who participates in the AMY event.
If people are not able to make all of the meetings, email them to ask them to write out responses to the discussion questions and homeworks.
After the final onboarding meeting, do the following for each of the Maintainers who have completed the onboarding requirements:
- Give them «write» access to their lesson repository on GitHub.
- Add their name to the lesson table on the website.
- Award them a Maintainer badge in AMY.
Send email to the Maintainers email list announcing new Maintainers.
Run sendmail_maintainer_certificates.R to send new Maintainers their certificates.
Announce new Maintainers in the next newsletter.

How to label issues¶

"status" labels

help wanted
- Hex code: #DCECC7
- Short Description: Looking for Contributors
- Long Description: Issue reviewed by Maintainers, and ready to be addressed. Maintainers are looking for Contributors to address this issue, anyone is welcome to work on addressing the issue.
status:in progress
- Hex code: #9BCC65
- Short Description: Contributor working on issue
- Long Description: A Contributor is actively working on addressing the issue, this label should be used once someone has been assigned the issue. Because, we can only assign people using GitHub's interface when they are part of the organization, the assignment is done by tagging them in a comment of the issue. The Maintainer should set an initial deadline for a PR to be submitted. We suggest 7 days, but it can be adapted to the discretion of the Maintainer depending on the complexity of the task.
status:changes requested
- Hex code: #679F38
- Short Description: Waiting for Contributor to update PR
- Long Description: Maintainers have reviewed the pull request, and requested changes. Waiting on the Contributor to implement these changes.
status:wait
- Hex code: #FFF2DF
- Short Description: Progress dependent on another issue or conversation
- Long Description: Progress on addressing issue or merging PR is dependent on another issue or ongoing conversation and cannot be addressed at this time. Ideally this other conversation should be referenced in the comments.
status:refer to cac
- Hex code: #FFDFB2
- Short Description: Curriculum Advisory Committee input needed
- Long Description: Maintainers need advice from the Curriculum Advisory Committee to make a decision on how to proceed with the issue or pull request.
status:need more info
- Hex code: #EE6C00
- Short Description: More information needed
- Long Description: Not enough information is provided to proceed with the issue or pull request.
status:blocked
- Hex code: #E55100
- Short Description: Progress on addressing issue blocked
- Long Description: A technical problem is hindering progress. A Maintainer or someone else in the community should be notified to ensure that progress is being made.
status:out of scope
- Hex code: #EEEEEE
- Short Description: Proposed changes are out of scope
- Long Description: Changes proposed in the issue or in the pull request doesn't fall within the scope of the lesson
status:duplicate
- Hex code: #BDBDBD
- Short Description: Issue or PR already exists
- Long Description: The concern raised in the issue or pull request has already been mentioned. This previous issues/PR should be mentioned in the comment before this label is used.

"type" labels

type:typo text
- Hex code: #F8BAD0
- Short Description: Typo in text for the lesson,
- Long Description: Typo in the text/code of the lesson
type:bug
- Hex code: #EB3F79
- Short Description: Code included in the lesson needs to be fixed
- Long Description: Issue about the code, including challenges, answers.
type:formatting
- Hex code: #AC1357
- Short Description: Formatting needs to be fixed
- Long Description: Issue about something being wrong in the formatting of the lesson
type:template and tools
- Hex code: #7985CB
- Short Description: Issue about template and tools
- Long Description: Issue or feature request about a technical aspect of the lesson (e.g., in the scripts used to render the lesson), including the documentation of these tools. Pull requests should probably be directed to https://github.com/carpentries/styles
type:instructor guide
- Hex code: #00887A
- Short Description: Issue with the instructor guide
- Long Description: Issue related to the content of the instructor guide. Best suited to be addressed by someone familiar with the content of the lesson
type:discussion
- Hex code: #B2E5FC
- Short Description: Discussion or feedback about the lesson
- Long Description: Issue used to ask a question about how the lesson is taught, ask for clarification. Such issues might indicate that the instructor guide or the documentation may need to be updated.
type:enhancement
- Hex code: #7FDEEA
- Short Description: Propose enhancement to the lesson
- Long Description: Proposal to add new content to the lesson (e.g., introducing additional function, library, command, flag), or adding more technical detail on a topic already covered in the lesson. Such issues may need to be considered by the infrastructure sub-committee, the curriculum advisory committee, or other relevant group.
type:clarification
- Hex code: #00ACC0
- Short Description: Suggest change for make lesson clearer
- Long Description: Part of a lesson which, while not incorrect (i.e., not a bug) is presented in a way that is potentially confusing or misleading. Existing content could benefit from rephrasing or rearranging.
type:teaching example
- Hex code: #CED8DC
- Short Description: PR showing how lesson was modified in a workshop
- Long Description: PR that illustrates how someone modified the lesson in their workshop. Not intended to be merged, but as a way to document how other instructors have used the lesson. Can be closed once the label has been applied.

"difficulty" labels

good first issue
- Hex code: #FFEB3A
- Short Description: Good issue for first-time contributors
- Long Description: Good issue for a new Contributor to our lesson.

"priority" labels

high priority
- Hex code: #D22E2E
- Short Description: Need to be addressed ASAP
- Long Description: For issues and pull requests that needs to be addressed as soon as possible because the lesson uses code that doesn’t work anymore or includes information that is out of date.

How to populate a GitHub repository with these labels¶

The carpenter R pacakge provides helper functions to create these labels from a CSV file using the GitHub API. To use the GitHub API, you need to obtain a GitHub Personal Access Token (PAT). This PAT is a way for GitHub to identify you and should be treated as a password.

Once you have installed R and RStudio, at the RStudio console, install the remotes package:

install.packages("remotes")

Go to https://github.com/settings/tokens, and click on the «Generate new token» button.
Choose a name that will help you remember what you use this token for, and click on the repo box. Finish the creation of the token by clicking on «Generate token» at the bottom of the page. The token will be displayed on the screen.
Using RStudio or text editor, open (or create if it doesn”t exist), a ~/.Renviron file, and add (replacing the XXXX with your actual PAT):
```
GITHUB_PAT=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
```
Restart RStudio and check that your PAT is available by typing:
```
Sys.getenv("GITHUB_PAT")
```
If everything worked, you should see your PAT being displayed. If something didn”t work it will display empty quotes ("").
Use the remotes package to install carpenter. Type at the R console in RStudio:
```
remotes::install_github("fmichonneau/carpenter")
```
Make sure you have downloaded the CSV file that contains the information about the github labels. It is in the repository for the Carpentries handbook in the data folder.

Load the carpenter package and create the labels on one repository:

library(carpenter)
create_github_labels(label_csv = "~/path/to/csv/file/github_labels.csv",
  owner = "owner_of_github_repo",
  repo = "name_of_github_repo",
  delete_previous = FALSE)

If you set delete_previous to TRUE, all exisitng labels will be deleted from the repository (and removed from issues/PR that had it).

Email Templates¶

Inviting new Maintainers¶

Subject: Invitation to become a Carpentries Maintainer CC: Existing Maintainers for the repo and other new Maintainer applicants for the same repo.

Hi all,

Thank you for applying to become a Maintainer for {lesson name and link to repo}. We”re excited to have you on the Maintainer team! Your co-Maintainers are cc”d here.

As a Maintainer, you’re part of a team that is responsible for ensuring that your lesson materials stay up-to-date, accurate, functional and cohesive. You’ll monitor your lesson repository, make sure that PRs and Issues are addressed in a timely manner, and participate in the lesson development cycle including lesson releases. {Add a sentence about when the next lesson release is scheduled for.}

The new Maintainers for all of the Carpentries lessons will be meeting a few times before {month} for onboarding and training in the Carpentries maintenance workflow. Please fill out this schedule poll {add link to poll} by {deadline} with your general weekly availability. Our first meeting is tentatively set for the first week in {month} and we will be meeting three times. Don”t forget to select your timezone before filling out your availability. We have new Maintainers joining the team from all over the world, so please be as flexible as possible.

New Maintainers will be given write access to their lesson repos after completing the onboarding process. In the meantime, please start becoming familiar with your lesson materials, sign up for the Maintainer mailing list, and check out the dates of the next Maintainer general meeting. You”re more than welcome to start attending Maintainer meetings before our onboarding. Please let me know if you have any questions. Looking forward to seeing you in March!

Best, {name}

Maintainer onboarding meetings¶

Subject: Maintainer Onboarding Meetings

Hi everyone,

Thank you for adding your availability to the scheduling poll. Based on everyone”s responses, we will be meeting at two different times. You do not need to attend the same meeting each week, and I would actually encourage those who can do so to switch which meeting they attend so that we can all meet one another over the course of the onboarding.

We will be meeting for three weeks, starting the week of {date}. You can see the meeting times in your local time zone on our Etherpad. If you know that you will need to miss one of our meetings, please let me know as soon as possible so that we can make alternative arrangements for you to complete the training.

Before our first meeting, please:

Sign up for the Maintainer mailing list. This is a low-volume channel for communicating about issues relevant to the Maintainer community.
Add Maintainer meetings to your schedule. The meeting times are listed on the Maintainer Etherpad and on the Community Calendar. The Maintainer monthly meetings are not mandatory, but are encouraged as a way of getting to know the more experienced Maintainers.

If you have any questions, please let me know.

Looking forward to meeting all of you next month!

Best, {name}

Onboarding reminder¶

Subject: Reminder - Onboarding starts next week

Hi all,

Just a quick reminder that we”ll be starting our onboarding meetings next week. Please sign up for one of the two available sessions on our groups Etherpad.

During our meetings, we”ll be test-running a new curriculum for Maintainer Onboarding. Your suggestions and pull requests to this repository are more than welcome! This curriculum will form the basis for onboarding of new groups of Maintainers in the future, so please help to improve it.

Before our first meeting, please look at the first lesson in the Maintainer Onboarding curriculum (Social Aspects of Lesson Maintenance) and do your best to work through the exercises marked «Preparatory Homework».

Looking forward to seeing you all soon. Let me know if you have any questions.

Best, {name}

Missed onboarding meeting¶

Subject: Unable to attend Maintainer Onboarding

Thanks for letting me know. What I”m doing for people who have to miss a session is asking that they send me an email with their responses to the homeworks (including the preparatory homeworks) and discussions. Could you please take a look through the first lesson and send me your thoughts sometime next week?

Best, {name}

Welcoming new Maintainers¶

Subject: Welcome New Maintainers!

Today I”m happy to announce the addition of {number} new Maintainers to our team. Please join me in welcoming:

{Table of names and lessons for new Maintainers}

Each of these new Maintainers has gone through a three week onboarding program to help prepare them for the complex role that Maintainers serve in our community. We certainly couldn”t cover everything in these three meeting! Please help your new team mates as they run into snags and feel free to reach out to me with any questions or concerns.

Looking forward to seeing everyone in action!

Best, {name}

Subject: Opportunities to complete The Carpentries Maintainer onboarding

Hi all,

Thank you again for volunteering to act as a Carpentries Maintainer. You”re getting this email because you expressed interested in being a Maintainer but were not able to attend the onboarding sessions. If you are still interested in becoming a Maintainer, please choose one of the two following paths:

Reading through the three Maintainer Onboarding episodes, writing up your responses to the discussion questions and homeworks, and sending me your responses by {deadline}.

or

Joining the next Maintainer Onboarding session, which will be held in {month}.

Please let me know as soon as possible which of these two paths you”d like to follow, or if you are no longer interested in joining the Maintainer team.

Looking forward to hearing back from you.

Best, {name}

Contributing to Carpentries lessons¶

Lesson Maintainers actively maintain all Carpentries lessons. However, contributions are always welcome by all community members. Novice contributors can read this guide developed by Carpentries Instructors. It provides instructions for contributing to The Carpentries” lesson materials using graphical or command line interfaces with Git and GitHub.

Políticas¶

The Carpentries Privacy Policy¶

Effective date: 25 May 2018

This Privacy Policy covers personally identifiable information that may be provided to The Carpentries, including data provided at in-person events (e.g., workshops and conferences) and online. Changes to this Privacy Policy will be posted on this page. Any changes will only apply to information collected after the posted date of any such change. Additionally, information may be provided to governmental bodies and other entities as required by law. Information obtained and how it is used is described in sections below for

Workshop participants
Instructors
Other volunteers
Online spaces
Opt-in surveys
All participants

Definitions¶

Workshop participants - people participating, including but not limited to as learner, helper, or instructor in a Carpentries workshop
Hosts - people organizing a workshop at their local site
Instructors and Trainers - people who are teaching a Carpentries workshop
Instructor applicants and trainees - people who have applied to become instructors or are in the process of completing certification
Lesson contributors and maintainers - people who contribute to or maintain lessons
The Carpentries staff - people employed by The Carpentries
Authorized administrators - personnel, contractors or volunteers operating in an administrative capacity for The Carpentries as workshop or volunteer coordinators

How is personally identifiable information stored?¶

Personally identifiable information is stored in secure databases. Refer to Limitations section below.

Who has access to personally identifiable information?¶

Access will be limited to The Carpentries staff and Authorized administrators.

Section 1: Workshop Participants¶

Workshop participants include Learners, Helpers and Hosts

What information do we obtain?¶

We may obtain the name, email address and event attended of workshop participants. If you are a learner or helper, this information may be provided by you or by the workshop host. See Section V: Opt-in Surveys for information on our Opt-In surveys.

How is this information used?¶

We use this information to communicate with participants, including sending workshop information and program evaluation forms. Names and email addresses may be shared with the workshop host for the purpose of workshop logistics. Additionally, we may use your information to contact you about additional opt-in opportunities for training, teaching, surveys and/or community engagement. This information may also be used for statistical purposes. We do not provide personally identifiable information to any third party. However, we may share de-identified aggregate or summary information regarding participants publicly or with volunteers, partners or third parties, including but not limited to funding entities. See Section VI: All Participants for further information

Section 2: Instructors¶

Instructors includes Instructors, Trainers, Instructor Trainees and Instructor Applicants

What information do we obtain?¶

We may obtain the name and email address of participants at instructor training events and of current instructors. This information may be provided by the participant or event host. If you choose to complete a volunteer/instructor profile, we may store your name, email address, gender, nearest airport location, organizational affiliation, occupation, ORCID ID, GitHub and Twitter handle, and personal URL.

How is this information used?¶

We use this information to communicate with Instructors, including for instructor training events, training completion materials, communication about the organization, and opportunities to volunteer. Additionally, we may use volunteer information to contact you about additional opt-in opportunities for assessment, training, teaching, volunteering and/or community engagement. This information may also be used for statistical purposes. We do not provide personally identifiable information to any third party. However, we may share de-identified aggregate or summary information regarding instructors publicly or with volunteers, partners or third parties, including but not limited to funding entities. See Section VI: All Participants for further information

Section 3: Other Volunteers¶

Other Volunteers includes Lesson contributors and maintainers and Volunteers for subcommittees or programs

What information do we obtain?¶

We may obtain the name and email address of Other volunteers. If you choose to complete a volunteer/instructor profile, we may store your name, email address, gender, nearest airport location, organizational affiliation, occupation, ORCID ID, GitHub and Twitter handle, and personal URL.

How is this information used?¶

We use this information to communicate with Other volunteers, including communication about the organization and opportunities to volunteer. Additionally, we may use volunteer information to contact you about additional opt-in opportunities for assessment, training, teaching, volunteering and/or community engagement. This information may also be used for statistical purposes. We do not provide personally identifiable information to any third party. However, we may share de-identified aggregate or summary information regarding volunteers publicly or with other volunteers, partners or third parties, including but not limited to funding entities. See Section VI: All Participants for further information

Section 4: Online Spaces¶

This Privacy Policy is applicable to information that you provided/collected through physical (such as a paper form) and online means, including through our websites or other external online spaces (including but not limited to GitHub repositories, Etherpads, Google Documents, EventBrite and mailing lists). By using these spaces, you agree to the terms of this Privacy Policy. Some of these tools and services (including but not limited to GitHub, Google Documents, EventBrite and SurveyMonkey) have their own independent privacy policies. See Section V: Opt-In Surveys, for information specifically on survey information.

What information do we obtain?¶

We may collect information about visitors’ devices and browsers, such as browser version and type, IP address, website referred from and country of visitor. In addition, we may collect textual input (e.g. Etherpad entries) from you which may be associated with your name, affiliation and/or social media handles. If you provide financial information to pay for a workshop or partnership or make a donation, the transaction information will be processed on a third-party secured site. This information will only be accessible to our staff or authorized adminstrators and to the staff of our fiscal sponsor who is involved in processing financial transactions. We engage with third-parties (including but not limited to Square, WeDidIt, Eventbrite) to gather and collect this information securely and do not have access to or store any payment details in our systems

What do we do with this information?¶

We use this information to improve our sites and services. In addition, we may use contact information that you provide to contact you about additional opt-in opportunities for assessment, training, teaching, and/or community engagement. This information may also be used for statistical purposes. We do not provide personally identifiable information to any third party. However, we may share de-identified aggregate or summary information regarding vistors publicly or with volunteers, partners or third parties, including but not limited to funding entities. We may use publicly available data of the external online services in programmatic analysis and evaluation. See Section VI: All Participants for further information

Section 5: Opt-in Surveys¶

Community and workshop participants are invited to participate in a variety of opt-in surveys to better serve our community. These include but are not limited to pre-workshop and post-workshop surveys of learners and various survey instruments to evaluate programs or events.

What information do we obtain?¶

Opt-in surveys are entirely voluntary and information is not collected in a way that it is linked to personally identifiable responses without the respondent’s consent to self-identify. Surveys collect information particular to the event or program being evaluated and optional information about the participant. Gender and ethnicity data, when collected, is only collected from participants in the United States.

What do we do with this information?¶

We use this information to help evaluate and improve programs, report on impact and outcomes and understand the needs and interests of our community. This information may be used for statistical purposes. We do not provide personally identifiable information to any third party. However, we may share de-identified aggregate or summary information publicly or with volunteers, partners or third parties, including but not limited to funding entities. Where we share open-ended responses or testimonials, we always do so anonymously or ask for explicit consent to allow de-indentifed responses. See Section VI: All Participants for further information

Section 6: All Participants¶

Can I decide what communications to receive?¶

Yes. All communication with us is opt-in, except for participants receiving information about their program and for instructors, information required to maintain instructor status. You may occasionally be sent emails asking if you would like to opt-in to communication channels that we feel may be of interest to you (for example, a mailing list dedicated to your geographical area). In the absence of specific action from you, we will assume you choose not to join these channels.

Removing personal information¶

Participants may choose to disallow us from retaining their personal information at any time by notifying admin@carpentries.org. If you choose to exclude your information, we will delete your personal information from our databases. This may interfere with our ability to give you credit for training events you have completed or to contact you about upcoming events in your area.

Limitations¶

Your privacy is very important to us. However, due to the existing legal and technical environment (e.g., third party interception of information), we cannot ensure that your personally identifiable information will not be disclosed to third parties in ways not described in this policy. We may disclose information when we believe such disclosure is necessary to comply with the law; enforce our agreements, or protect the rights, property or safety of our users or others.

What about third party links on our websites?¶

Our websites provide links to third party sites as a service to visitors. We are not responsible for the privacy practices, security measures or data collection practices of third party sites or for their content. The choice to access these sites is at the visitor’s own risk.

Who should be contacted regarding this Privacy Policy?¶

For questions or comments about this Privacy Policy, please contact admin@carpentries.org.

Política de No Presentación del Instructor¶

The Carpentries no suelen participar en los arreglos de viaje para los talleres. En su lugar, una vez que los instructores han sido seleccionados, negocian el viaje y el alojamiento con el anfitrión del taller, y luego son reembolsados directamente por el anfitrión. Sin embargo, para brindar talleres de alta calidad de manera consistente, The Carpentries deben garantizar que los instructores cumplan con sus compromisos. En particular, debe hacer todo lo posible para garantizar que los instructores asistan a los talleres que acordaron impartir, para que los anfitriones tengan la cantidad adecuada de instructores y no incurran en gastos innecesarios.

Los instructores que no puedan cumplir con un compromiso de enseñanza acordado deberán notificar al coordinador del taller de The Carpentries lo antes posible. Si no se han hecho arreglos de viaje, y faltan por lo menos 6 semanas para el taller, los instructores podrán cancelar sin que se les haga preguntas. Si se reservó un viaje no reembolsable o faltan menos de 6 semanas para el taller, los instructores deben comunicar claramente el motivo por el cual faltaron a su compromiso de enseñanza. El coordinador del taller hará cargo de la comunicación con el anfitrión e intentará encontrar un instructor alternativo si es posible.

Dependiendo de la razón por la cual faltó a su compromiso de enseñanza acordado, se le podrá pedir a los instructores que reintegren los gastos de viaje o alojamiento no reembolsables en los que el anfitrión ya haya incurrido en su nombre. The Carpentries podrán ceder a este requisito en circunstancias especiales que se detallan a continuación, en base al juicio del Subcomité de Políticas de The Carpentries.

En algunos casos, The Carpentries anularán el requisito de que el instructor reembolse al anfitrión, y The Carpentries reintegrará al anfitrión los gastos incurridos. Las circunstancias en las que las Carpinterías reembolsarán al anfitrión los gastos incurridos por talleres perdidos incluyen, pero no está limitado a: enfermedades, lesiones, emergencias familiares o relacionadas con el trabajo, mal clima o mal funcionamiento de transporte. Se puede requerir que los instructores proporcionen la documentación apropiada al Subcomité de Políticas. Si un instructor está obligado a reembolsar los costos, pero se niega a hacerlo, o si un instructor no proporciona un aviso de cancelación adecuado más de una vez, The Carpentries se reserva el derecho de suspender su estatus de instructor de Carpentries.

The Carpentries Reimbursement Policy¶

Designed to be consistent with Community Initiatives reimbursement policies.

I. Policy Statement

Business expenses may be reimbursed if an individual paid the expense from personal funds.

This policy establishes the three components required for reimbursement of allowable non-compensation business expenses:

An allowable business expense
Substantiation of the expense with receipts and expense report
Approval of the expense

II. Who is Affected by this Policy

This policy affects all employees, volunteers, independent contractors, and guests seeking reimbursement or payment for necessary and reasonable non-compensation business expenses.

III. Definitions

Necessary Minimum purchase or service required to achieve a particular objective.

Reasonable An expense that is ordinary and reflects a prudent decision to incur the expense on behalf of The Carpentries business. Not extreme or excessive. Travel expenses should not exceed the current US federal per diem rates for the location of travel. If an expense exceeds these rates, a justification for additional spending should be included in the description of that expense.

Appropriate expense An expense that is suitable or fitting for a particular valid The Carpentries business purpose or activity.

Allowable expense A necessary, reasonable, and appropriate expense incurred for the primary benefit of The Carpentries activities and therefore permitted to be reimbursed or directly charged based on the permission of The Carpentries. Allowable expenses must meet 501(c)3 expense policies.

Original Receipt The original merchant receipt or invoice issued by the supplier or service provider to document and substantiate the business transaction. A digital image of the original receipt is allowable provided that it is legible. Electronic receipts are allowable.

Substantiation Documentation to support an incurred business expense that includes the original receipt, documentation of business purpose, names of persons in attendance, and an appropriate expense report for the incurred cost.

IV. Policy

The Carpentries provides reimbursement for appropriate and allowable expenses. These are business and travel related expenses, including transportation, hotels, and food. These expenses must be reasonable and necessary, as well as job-related.

SUBSTANTIATION AND ORIGINAL RECEIPTS

In order for a business expense to be approved and reimbursed, it must be properly substantiated. Original receipts (see above definition) for all expenditures are required. If sponsored by a particular agency or organization and requirements are more restrictive, the more restrictive receipt requirement will take precedence. If a required receipt has been lost, that information must be included when the reimbursement request is made.

EXPENSE REPORT

Reimbursement as a nontaxable payment can be made as long as:

the expense qualifies as an allowable business expense and
all substantiation and receipt requirements are met.

The sections below establish The Carpentries policy for reimbursement based on proper substantiation of the business expense, timely request for reimbursement, and payment approval.

APPROVAL AND REIMBURSEMENT

For each business expense reimbursement being requested, the request must include

the valid business purpose of the expense and
if travel related, the location and dates of the event.

DEADLINE TO SUBMIT EXPENSE REPORTS AND DOCUMENTATION

Expense Reimbursement DeadlinesTo be reimbursable, business expenses must be properly substantiated and submitted within certain time limitations.

Substantiation for the reimbursement should be submitted within 60 calendar days of when the expenses were incurred. For expenses incurred while traveling, the traveler will have 60 calendar days upon returning from travel to substantiate and submit the expenses.
If substantiation occurs more than 60 calendar days after the expenses were incurred, the expense reimbursement request must include an explanation for the delay.
Funds can be reimbursed before travel is completed, with receipts for the travel expenditure. If travel is not completed or is changed to have a lower cost, funds must be returned according to the “Return of Excess Amounts” section.

RETURN OF EXCESS AMOUNTS

Return of excess amounts must be done within 120 days after expenses are paid or incurred.

Community Initiatives will guide the process for repayment of funds.

If individuals are volunteers, they will be expected to repay “excess amounts” and it may affect their volunteer status with the organization.

V. Procedures

REIMBURSEMENT REQUEST

Those expecting reimbursement are responsible for discerning appropriate and allowable expenses. Requests must include

Person requesting
Vendor (for business expenses)
Meeting, location and dates of meeting (for travel expenses)
Reason for travel or expense
Designated expense category (travel, infrastructure, other)
If applicable, explanation of why requirements aren’t being met (e.g. missing receipt, submitted later than 90 days after purchase)
If a meal for business purposes besides travel, the people in attendance at the meal
Additional notes

Reimbursement requests and documentation should be submitted to the Administrative Support Specialist at finance@carpentries.org. The Administrative Support Specialist will organize the forms for the request, then submit to the Executive Director or the Executive Council Treasurer for approval, before sending the request to our fiscal sponsor for payment, in accordance with our reimbursement workflow. Reimbursement workflow guidelines are available for staff.

VI. Contact Roles and Responsibilities

Executive Director - Tracy Teal
Executive Council Treasurer - Raniere Silva
Administrative Support Specialist - Talisha Sutton-Kennedy

VII. Update Log

Updated on 2019-02-19 to replace Business Administrator with Administrative Support Specialist
Updated on 2018-07-06 to include Business Administrator in procedures and add federal per diem rates as guideline for expenses.
Updated on 2018-03-06 to reflect that reimbursements cannot be denied due their time of submission.
Updated on 2018-02-23 to reflect updated workflow with Community Initiatives and approval contacts.
Updated on 2018-01-31 to refer to Community Initiatives as our fiscal sponsor.
Updated 2017-12-22 to change from Data Carpentry to The Carpentries.

Carpentries Professional Development Policy¶

Staff Professional Development Fund

The Carpentries staff have access to a professional development fund (hereon after «Staff PDF») of $1000/year for each full time employee.

What Activities are Eligible?

The Staff PDF makes available funds for the purpose of supporting staff participation in professional development programs such as workshops and seminars and research activities.

Requests must demonstrate how the activity for which funding is sought supports the:

Current Strategic Plan for The Carpentries;
Employee”s Individual Professional Development:
- Through improving performance in the employee’s current position; or
- Through improving the employee’s qualifications for career opportunities that may arise within The Carpentries

When applying for reimbursement for professional development materials or activities, staff should provide a short description and justification of the expenditure. For large expenses (>$200), staff should seek prior approval from the Finance subcommittee.

REGIONAL COMMUNITIES¶

Regional Coordinators¶

Around the world, Carpentries workshops are organized by a team of Regional Coordinators. Our staff Workshop and Logistics Manager, SherAaron Hurt, manages workshops in most of the world. In some parts of the world, local Carpenters support managing local workshops and building local communities. They work with our member sites or as volunteers.

Regional Coordinators are the front face of The Carpentries, promoting our work and our culture in their geographical area. They manage workshop logistics, communicate with hosts and Instructors, and respond to general inquiries. The Regional Coordinators work together to support each other and ensure communities can thrive locally while maintaining quality and consistency globally.

Read more about the Regional Coordinators” role.

More information about the Regional Coordinators can be found on The Carpentries website.

Carpentries in Africa¶

What We Do¶

Support for the African community is provided by community members and the regional coordinator who will be appointed in 2019

Monthly African Instructor Meetup: Our monthly African instructor meetups have been running since 2017 and are attracting more and more interest. Here we discuss topics that are of interest to our instructors in the African context, including previous and upcoming workshops, available resources, opportunities, events, and more. The meetings are restricted to folks who have already participated in instructor training as we also focus on helping instructors to complete their checkouts, connecting instructors with others who can co-teach or co-organise workshops, and more.
Provide logistical support for workshops in Africa: The African Regional Coordinator will work closely with experienced African instructors to provide logistical support for workshops when needed.
Mentoring for Instructors and Helpers before a workshop: Some members of the African instructor community are willing to host online mentoring sessions for instructors and helpers before a workshop to ensure everyone knows what to expect and what is expected of them.

Join Us¶

To join the conversation about The Carpentries in Africa, sign up at Topicbox.

If you’ve trained as an instructor in Africa (even if you’re not qualified yet), please join the African instructors mailing list.

We would love to get more people involved in specific activities to support our growing African community.

Join the monthly African meetup: We would love to hear more voices at our monthly online meetup, on the 4th Thursday each month, 12:00 - 13:00 SAST (10:00 - 11:00 UTC). If you are keen to join or host a session, please sign up at our Etherpad.

Provide mentorship before workshops: If you are available to meet with an instructor/helper team before they run a workshop to answer any questions they may have or to help them prepare for the lessons they will be teaching, please get in touch via our email and we can pair you up with a team at a time and date that will suit you.

Historical support¶

The first Carpentries workshops in Africa were run in 2013 but it only really kicked off in 2015. An African Task Force was established in 2016, consisting of international mentors from the USA, UK, and Australia, and guided the first batch of trained African instructors through the checkout process as most of them were very isolated and new to the world of the Carpentries.

Since then more than 100 African instructors have participated in online or in-person instructor training events. The African Task Force was revived in December 2017, then completely consisting of African instructors. The task force played a role in mentoring instructors who had been trained but hadn’t qualified as well as qualified instructors who needed support before teaching a workshop. Small online sessions were hosted by task force members to demonstrate how various lessons are taught and to help solidify skills in the tools we teach. The second African Task Force finished its activities in December 2018. Some of the South African-based activities were funded through the Rural Campuses Connection Project II (RCCP II), which ended in March 2019. You can read more about the experiences of the African Task Force in this blog post and about RCCPII here.

Carpentries-es¶

La construcción de una comunidad sostenible y activa en América Latina incluye varias iniciativas: traducción de lecciones, capacitación de instructores, coordinación de talleres y recaudación de fondos. Este repositorio sirve como punto de entrada para este grupo de actividades.

Building a sustainable and active community in Latin America include several iniatives: lesson translation, instructor training, workshop coordination, and fundraising. This respository serves as a landing point for this diverse group of activies.

Cómo puedes ayudar¶

Hay muchas maneras de ayudar a construir la comunidad The Carpentries en América Latina.

Necesitamos hispanohablantes nativos y personas con manejo fluido del español para ayudar a traducir los materiales de las lecciones.
Necesitamos una forma de mantener sincronizadas las versiones en diferentes idiomas de las lecciones de The Carpentries para que las contribuciones hechas a una versión también aparezcan en otras versiones.
Necesitamos instructores experimentados para enseñar juntos y que guíen a nuevos instructores en América Latina, especialmente aquellos que están familiarizados con la región.
Necesitamos entrenadores ubicados en América Latina o con fuertes vínculos con la región.
Necesitamos ayuda con la coordinación de talleres por parte de personas familiarizadas con las estructuras de precios, la geografía y la infraestructura computacional en América Latina.
Necesitamos Campeones locales para difundir la palabra sobre las Carpentries, el trabajo que hacemos y abogar por los talleres y membresías de The Carpentries en la región.

Si puedes ayudar de alguna de estas maneras, o si sabes de alguna otra manera que puedas apoyar el desarrollo de la comunidad de The Carpentries en América Latina, ¡ponte en contacto con nosotros!

Cómo participar¶

Para ponerse en contacto con este grupo, envía un correo electrónico a local-latinoamerica@lists.carpentries.org. Para unirse a la lista de correo electrónico, visita Topic-Box. Para contactarnos directamente te invitamos a usar slack en el canal carpentries_es.

To contact this group, email local-latinoamerica@lists.carpentries.org. To join the email list, visit Topic-Box. To contact us directly you are invited to join slack in the carpentries_es channel.

¿Quién está involucrado?¶

Traducción de lección: Paula Andrea Martinez, Francisco Palm, Rayna Harris
Capacitación de instructores: Karen Word (con ayuda de Sue McClatchy, Rayna Harris, Belinda Weaver)

Reuniones bilingües¶

Hacemos reuniones bilingües para la sección «Enseñanza de las sesiones de demostración» de «Instructor Training Checkout». Inscríbete en el Etherpad o lee las instrucciones bilingües para saber cómo funcionan las sesiones de demostración.
We host bilingual meetings for the «Teaching Demo Sessions» part of Instructor Training Checkout. Sign up on the Etherpad or read the bilingual instructions for how the demo sessions work.

Traducciones¶

Los respositorios de GitHub para las traducciones en progreso son mantenidos por la organización carpentries-es. Varias lecciones de Data Carpentry y Software Carpentry tienen traducciones al lenguaje español completas. Estas se encuentran listadas en los sitios web de las lecciones de Data Carpentry y Software Carpentry.

The GitHub repos for translations in progress are maintained in the Carpentries-ES organization. Several Data Carpentry and Software Carpentry lessons have complete Spanish language translations. These are listed on the Data Carpentry and Software Carpentry lesson websites.

Regional Mailing Lists¶

All mailing lists for The Carpentries are hosted on Topicbox. This includes a number of mailing lists specific to local or regional communities.

Current local/regional mailing lists¶

Latin America¶

United States¶

TEACHING AND HOSTING¶

Opportunities for certified instructors to teach Carpentries workshops are listed here. Join the instructors mailing list to be notified when new opportunities are posted.

For centrally organized workshops, the Regional Coordinator will guide the host and instructor on following through on all these steps.

Certified instructors are also encouraged to run self organized workshops. For self organized workshops, the host and instructor are directly responsible for ensuring all the steps below are followed without support from the Regional Coordinator.

A global team of Regional Coordinators support workshop activity and community building in regions around the world. Read more about who they are and what they do.

Workshop checklists¶

Host checklist¶

A workshop host contacts the Carpentries staff about running a workshop. He or she will work with the Carpentries Program Manager and Workshop Administration Team to plan and implement the workshop.

Before the workshop, the host will

Decide on the Software Carpentry, Data Carpentry, or Library Carpentry curriculum that would best serve your learners
Fill out the workshop request form
Work with the Carpentries Program Manager and Workshop Administration Team to set dates and location for your workshop
- Be sure to account for other events and programs at your site that may affect room availability and participant availabilty
- Ensure your location is accessible
Recruit helpers to join your workshop. They don”t need to be directly connected with us. They do need basic knowledge of the tools we teach and enthusiasm to help others learn. We recommend 1 helper for every 8-10 students, not counting the two instructors.
Advertise your workshop. The Workshop Administration Team can help by creating an Eventbrite registration page.
Decide if you want to charge a workshop fee. Even a small fee can greatly reduce the no-show rate. If the Workshop Administration Team creates an Eventbrite registration page, the Carpentries can collect this fee via Eventbrite and use it to offset your workshop fee.
Work with the Carpentries Program Manager and Administrative Support Specialist to make arrangements to pay the workshop fee (only for centrally organized workshops). This includes being sure vendor forms or other documentation are in place. The actual invoice will be issued after the workshop is complete.
Make travel arrangements for visiting instructors (or communicate process to reimburse them for expenses)
Get emergency contact information for instructors in case of last minute changes
Arrange for required materials and equipment
Arrange for coffee, snacks, and/or lunch. We all learn better with fuel!
Email learners to remind them of workshop location, timing, and software installation requirements
Organize a meetup with the instructors the day before the workshop. While this is not always possible, it”s useful for the host and instructors to get to know each other. This can be over coffee, dinner, or anything else that works for your team.

During the workshop, the host will

Meet the instructors and learners
Ensure that the room is set up with all necessary materials and equipment
Periodically check in on the class to be sure things are running smoothly

After the workshop, the host will

Collect workshop attendance
Send attendance and any other feedback to the Carpentries Workshop Administration Team
Pay the workshop fee (only for centrally organized workshops)
Reimburse the instructors

Billing Guidelines¶

Payment for workshops is generally due 30 days after the invoice is issued.

Invoices overdue 4 or more months may lead to the cessation of work on current activities involving the organization to whom the overdue invoice was issued until the payment process is addressed.

Instructor Checklist¶

The Program Manager or Workshop Administration Team will introduce workshop hosts and instructors.

Before the workshop, instructors will

Decide on the order of the lessons and who will teach what modules
Set up the workshop website using the workshop template and send to the Carpentries Workshop Administration Team. Detailed instructions are in this repo”s README.
Create an Etherpad for the workshop
Assist the host in recruiting helpers if possible
Assist the host in ensuring the workshop location is accessible
Share emergency contact information with host in case of last minute changes
Practice teaching the material
Remind the host of the necessary equipment
Join a community discussion
Confirm criteria for reimbursement (per diem or save receipts)

During the workshop instructors will

Review Code of Conduct with learners
Remind learners to use sticky notes to give feedback
Get feedback at lunch and end of each day using minute cards
Support host in collecting attendee names and emails
Send out the post-workshop survey at the very end of the workshop

After the workshop instructors will

Remind the host to send workshop attendance data to the Carpentries Workshop Administration Team
Submit receipts for reimbursement
Send their own feedback to the Workshop Administration Team including any configuration problems
Take part in a community discussion
Report any lesson errors or suggest improvements on GitHub or by email to the Carpentries Workshop Administration Team

Helper Checklist¶

Helpers are often recruited from the local community at the host site to support Carpentries workshops. Helpers support learners one-on-one if they are stuck installing software, understanding a certain line of code, or any other parts of the learning process.

Before a workshop helpers will

Introduce themselves to the instructors, letting them know any particular areas of expertise
Review the curriculum the instructors will be teaching
Review the software installation instructions to be prepared to troubleshoot with learners
Make sure the instructors have listed you on the workshop website

During the workshop helpers will

Help learners with setup problems or anywhere else they get stuck
Monitor room for anyone who may need help. Learners may put up a red sticky note or indicate in other ways that they are stuck.
Monitor any questions that come up on the etherpad and answer them or remind the instructor about them during a break.

After the workshop helpers will

Send their own feedback to the instructors and the Workshop Administration Team including any configuration problems
Consider applying to become a certified Carpentries instructor

Teaching Rules:

Rule #1: Be kind

This means to be inclusive, respectful, mindful and welcoming.

Rule #2: Remember that we are all learners

Admitting that you don”t know everything helps create a growth mindset, where we are all constantly learning. When you make a mistake, calmly talk about the error, how it”s part of the process and necessary to make progress.

Rule #3: Be aware of demotivating attitudes

There are several things that can be demotivating or impair the learners” experience. Examples of what not to do:

Take over the learner”s keyboard. Instead, encourage and guide them through the solution, but let them type themselves.
Dive into deep discussions with more advanced learners (who might actually not need to be there). You can have those conversations

Rule #4: Be aware of demotivating words

Avoid saying things like:

Just: «oh, that”s easy, you just…»
«It”s too easy…»
«It”s too hard…»
«I can”t believe you don”t know X …»
Say negative things about any applications or OS (Word, Excel, Windows, Mac, GUI). No tool is perfect, and this kind of disdain is not productive or conducive to the learning process.

Code of Conduct (Summary View)

We are dedicated to providing a welcoming and supportive environment for all people, regardless of background or identity. By participating in this community, participants accept to abide by The Carpentries’ Code of Conduct and accept the procedures by which any Code of Conduct incidents are resolved. Any form or behaviour to exclude, intimidate, or cause discomfort is a violation of the Code of Conduct. In order to foster a positive and professional learning environment we encourage the following kinds of behaviours in all platforms and events:

Use welcoming and inclusive language
Be respectful of different viewpoints and experiences
Gracefully accept constructive criticism
Focus on what is best for the community
Show courtesy and respect towards other community members

If you believe someone is violating the Code of Conduct, we ask that you report it to the Carpentries Code of Conduct Committee completing [this form] (https://goo.gl/forms/KoUfO53Za3apOuOK2), who will take the appropriate action to address the situation.

More info can be found here: https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html

Email Templates¶

Use these templated emails for communicating with the learners

Tips For Instructors¶

This page has an assortment of practical tips for instructors.

Handling Software Installation¶

Installing software on laptops has gotten a lot better over the years, but it can still be a huge challenge at the start of a workshop. Here are some suggestions for making the process go as smoothly as possible.Software installation can be frustrating, but in the end, it almost always gets done. Be positive, and when it finally works, you can feel proud.

What you can do in advance:

Plan for installation help at the start of both workshop days. Put it on the schedule and make sure it”s clear that people can and should show up during that time.
Email the participants a week in advance and the day before to remind them to install the needed software before the workshops.
If possible, recruit helpers who use Linux, Mac, and Windows operating systems.
If you/helpers/instructors have time, test the install instructions on a fresh user account on your computer.
If you anticipate issues (or want to be extra prepared), have some of the emergency options listed below ready to go.
If you”re teaching for an organization where participants are bringing work laptops where they don”t have administrative access (common in government organizations) – ask about it. Try to plan ahead either with their central IT organization or with the «emergency exits» listed below.
Will you have decent Wi-Fi? A bunch of people installing software at once can kill a poor internet connection. If this is the case, prep a few flash drives with the relevant installers.

On the day of:

Refer to our Wiki page with common problems
If someone has come in early and the software still can”t be installed by the time the workshop starts, try one of the «emergency exits» below or keep working with them one-on-one until they”re able to start.
If someone comes in late or is having such trouble with installation that they can”t start, have them watch (and maybe work with a neighbor) until the first coffee break, when you can keep working on installation issues.

«Emergency Exits»

If there”s absolutely no way that you”ll be able to install the software locally on someone”s computer, consider using the following:

The «cloud» variants of RStudio or Jupyter.
Microsoft Azure gives you a cloud based Jupyter notebook with many languages and platforms installed. It also includes a shell terminal with git.
If your institution”s library does laptop rentals, rent 1-2 laptops and set them up with the software before the workshop and keep them on hand as loaners during the workshop.

Talking About the Code of Conduct¶

The Carpentries Code of Conduct is a key tool for fostering and upholding an inclusive, respectful learning environment. But for people who are new to the idea of a Code of Conduct, it can be a little awkward to talk about. Here”s a sample of how you might introduce the Code of Conduct – please don”t use this verbatim, but adapt it to your own audience and style of introduction:

The Carpentries is a community-led project. We value the involvement of everyone in the community. We are committed to creating a friendly and respectful place for learning, teaching and contributing. All participants in our events and communications are expected to show respect and courtesy to others.

What kinds of behaviors are expected?

All interactions should be professional regardless of platform: either online or in-person. In order to foster a positive and professional learning environment we encourage the following kinds of behaviours in all Carpentries events and platforms:

Use welcoming and inclusive language

Be respectful of different viewpoints and experiences

Gracefully accept constructive criticism

Focus on what is best for the community

Show courtesy and respect towards other community members

Examples of unacceptable behavior by participants at any Carpentries event/platform can be found in the Code of Conduct. We Instructors take the Code of Conduct very seriously, and we have a process for dealing with violations and complaints. Read the Reporting Guidelines section for the details on how to handle Code of Conduct violations.

Using Exercises¶

When teaching a lesson, it”s a very good idea to go through the lesson in advance and choose which exercises you want participants to try.

Once you”ve selected exercises, there are several ways to actually display them to the participants during the workshop. Any of these options may be the best choice depending on the tool you”re using or the kind of exercises you want to use.

From the lesson website (zoomed in)
- This is the least effort, but requires having the right lesson page open + finding the right exercise
Make slides
- More effort, but easy to flip forward to the next one
Have a document of some kind with all the exercises in it
- More effort, but exercises are all in one place.
Put exercises in the etherpad
- If you do this in advance, pretty low-effort.
- Can also use this with any of the other strategies so people can find the exercise in two places.
Online tool, like Socrative
- Requires time to set up, but is great for multiple choice and T/F questions and promotes participation

In all of these examples, you”ll have to switch from the tool you”re using for live coding to however you”re showing the exercises. For something like R or Python, one way to reduce the amount of switching is to put all the exercises in an R script / Python notebook and have that open alongside your main working script/notebook so that it”s relatively easy to switch back and forth.

General Tips¶

Introductions

The introduction is one of the most important pieces of the workshop! It sets the tone for the day. See the instructor training material for some suggestions of how to build a good workshop introduction.

Accessibility Check-In

Before you start, review our accessibility checkist..

Set up your computer and go to the back of the room. Is your font big enough?

If your room has a mic, use it, and have a helper stand in the back of the room as you start to confirm that you can be heard.

Varying Skill Level

Carpentries workshops frequently include many people with widely varying skills and experiences. See the end of the Carpentries Instructor Training on Carpentries teaching practices for some strategies to deal with a diverse classroom.

Preparing to Teach¶

It can be daunting to look at a Carpentries lesson and figure out just exactly how you”re going to teach it. Here are some suggestions for tackling a new lesson that you”ve never taught before:

Read through the Instructor Guide for the Lesson

Most Carpentries lessons include a guide for instructors. These are great for novices preparing to teach a lesson for the first time. As an example, see the instructor notes for the Software Carpentry Unix Shell lesson. Find instructor notes for other lessons through the Extras menu on each lesson”s home page.

Pick Exercises

Most of the lessons have more exercises than you will want to use. Go through the lesson and pick the ones that you think will be most helpful for your audience. If you anticipate mostly novices, look for easier or more scaffolded exercises. For a more advanced audience, a more general exercise might be better. If you”ll have both, have an option for each!

You won”t want to use all the exercises, but make sure that in this process, you commit to actually doing exercises. Exercises are time-consuming and it can be tempting (in the moment) to talk instead of taking the time to do an exercise. However, doing exercises is a huge part of the hands-on Carpentries model and also gives people a chance to chat with their neighbors, so it should be prioritized.

Speaking of priorities…

Prioritize

All of The Carpentries lessons have more material than you can easily cover in the time alloted, especially with a novice group. The Data Carpentry materials are closer to realistic workshop time estimates, but can still run slowly depending on the group.

So no matter what, go through the lesson in advance and decide what is most important to cover and what you would feel okay skipping (either skipping outright, or dropping it if you don”t have time).

As an example: the shell lesson has 7 sections – the first three are about basic file system navigation and file operations and the last four are about ways to use simple shell tools in more powerful ways. Often a workshop will cover the first three and then three out of the last four.

Practice

At the very least, do a dry run of all the commands you will be running / code you”ll be writing so that you know they work on your computer.
Hook your computer up to a projector and figure out how you”re going to manage your screen real estate, especially if everything is magnified.
- Rstudio: Rstudio can be particularly challenging because of all the panes. Reducing the size of the two right panes is usually needed to have enough space in the script/console panes.
- Jupyter notebooks: you can toggle the headers/toolbar off so that you have more scripting space
If you have the time, doing a full run-through where you actually practice what you”re going to say can be extremely valuable. Words are hard when you”re also trying to type and manage a classroom, so having said them once in practice gives you one less new thing to think about.

Join a community discussion

Joining a community discussion before your workshop is a great way to ask/resolve your questions about your coming workshop and also learn from the experience of other instructors!

Teaching unofficial Carpentries workshops¶

An official Carpentries workshop must cover the core lessons for that lesson program”s curriculum. Read more about the Software Carpentry, Data Carpentry, and Library Carpentry lessons. The workshop must also be taught by at least one certified Carpentries Instructor. While Instructors do receive lesson program specific badges, The Carpentries considers any badged Instructor qualified to teach any lesson.

All our lessons are available under a Creative Commons license, so anyone is welcome to use our lessons as they wish, provided they attribute them back to us. We often get questions about running un-official Carpentries workshops – meaning they are taught by non-certfied instructors, or they cover a portion of our curriculum but not the whole thing. We are excited to hear when this happens, but it is not something we are formally tracking.

We know this happens because our community members recognize the value of our curricula and have taken the initiative to adapt it to other contexts, where a two day workshop covering our full lesson set may not be the best fit. This demonstrates a lot of effort by the instructors and organizers. Also, while the impact on the learners is different than what we”d expect from a full workshop, there is still something significant that learners are taking away from this event. We may consider exploring ways to track these non-standard workshops (both to acknowledge the effort instructors put in and the impact it has on learners), but we don”t currently have the capacity to commit to this. So please continue doing all the wonderful work you do - and we hope we can reflect on this more soon!

Workshop needs¶

Participants are expected to come with their own laptops. Setting up a computer lab space is not necessary. Before the workshop, participants will receive instructions on what software they need to install and set up on their laptops.

Venue¶

A good venue is crucial to establishing a positive learning environment. Some things to consider include:

Tables arranged so participants can watch the instructor, use their laptops, and talk with their peers. Fold up desks are usually not a good choice.
Tables should also be arranged so helpers and instructors can easily mingle around the room.
The room should have a projector and screen that everyone can see, with HDMI, VGA, and Mac adapters to allow anyone to plug in their laptop.
High speed Wi-Fi internet access that can withstand everyone using it together. This may include securing guest access codes.
Power outlets for all participants. This may include setting up extension cords or power strips.
High table or podium that instructor can stand at while teaching. A flat podium is important; it”s difficult to use a laptop on a slanted podium.
Refreshments. People learn better when they are well fed. They also won”t lose as much instructional time if they don”t have to leave to get coffee.

Equipment and materials¶

Power strips, as noted above, to ensure everyone”s laptop stays charged
Sticky notes in two contrasting colors. These are an important part of how we get feedback during a lesson. We should have enough for each person to have about 8 of each color.
Name tags to help people get to know each other.
Extra pens and paper in case people want to take notes by hand
Sign in sheets
Flipchart or whiteboard with felt-tip pen (ideally several in different colors) for the instructor to visualise concepts or note important details.

Accessibility¶

It”s important to make sure the workshop space is accessbile to all individuals. The registration form should ask whether instructors, helpers, and learners need any advance arrangements to ensure they can participate in the event. This may include considering whether or not:

Building and room are accessible to those who can not use stairs (ramps, elevators, etc.)
Restrooms are accessible
There is a microphone for instructors
The screen is large enough and bright enough to be easily read
The building and room can accommodate service animals
Lactation space is provided

WORKSHOP ADMINISTRATION¶

Around the world, Carpentries workshops are organized by a team of Regional Coordinators. Our staff Workshop and Logistics Manager manages workshops in most of the world. In some parts of the world, local Carpenters support managing local workshops and building local communities. They work with our member sites or as volunteers. Read more about who they are and what they do.

This section outlines their work specifically as it relates to workshop adminstration.

Role and Expectations¶

The role of the Regional Coordinators is to be the front face of the Carpentries, promoting our work and our culture in their geographical area. The Regional Coordniators will manage workshop logistics, communicate with hosts and instructors, and respond to general inquiries. As a team, all administrators will work together to support each other and ensure communities can thrive locally while maintaining quality and consistency globally.

This includes the following responsibilities

Attend monthly admin team meetings. Time zones will be taken into consideration when scheduling these meetings. Attending other Carpentries community meetings is also highly recommended.
Read emails sent to the admin group. Stay up to date on all Carpentries operations as outlined in the Carpentries handbook. Respond to workshop requests from host sites in your region within two business days. This may include, but is not limited to:
- Sharing general Carpentries information
- Recruiting instructors
- Setting up surveys and registration
- Supporting other planning logistics
- Recording all information according to Carpentries’ systems.
Follow up on all completed workshops to collect attendance data and other feedback, and record this in Carpentries’ systems.
Serve as the “front face” of the Carpentries in their region by responding to general public inquiries and supporting our larger communication efforts and other initiatives.
Communicate Carpentries community values to instructors, host sites, and others constituents.
Communicate successes and challenges with Carpentries Workshop and Logistics Manager and other Regional Coordinators.
Promote the Carpentries culture of an inclusive and supportive learning environment informed by best practices in pedagogical research. Follow the Carpentries Code of Conduct and report any violations.
Elevate questions and issues to Carpentries staff as needed.

Workshop Administration workflow¶

For centrally organized workshops¶

One of the following occurs:
- Someone submits the Carpentries workshop request form
- Someone emails team@carpentries.org to request a workshop.
- Someone contacts a staff member to request a workshop.
Workshop & Logistics Manager or the Regional Coordinators for that region responds to request by email or phone/video call.
- Give them more information about the Carpentries as needed.
- Ask them for more information about their request.
  - Who is their target population?
  - What curriculum content do they want to cover?
  - What timeframe are they looking to host a workshop?
    - Remind them we need 2-3 months notice
    - Remind them to consider their own schedule and other events that may affect things like room availability
  - Remind them of the budget
    - US$2500 standard fee due to our fiscal sponsor (for non-member university, government, or non-profit sites only)
    - Costs for instructor travel (airfare, ground travel, hotel, and meals/incidentals) are managed entirely between host and instructors. We will look for local instructors but can not guarantee it. Member sites are still responsible for travel costs.
  - Ask them to complete the official request form
- Workshop & Logistics Manager or the Regional Coordinators records request form in AMY.
For non-member sites, Regional Coordinator asks host for invoicing contact, and introduces them to the Administrative Support Specialist to begin the invoicing process.
Regional Coordinator adds workshop to appropriate tab (by geography) on call for instructors sign up sheet and sends email to instructors list notifying them of upcoming opportunities.
Regional Coordinator reviews list of instructors signed up as interested in upcoming workshops and tentatively places them based on experience, geography, and skill set. See blog post for details. Selection guidelines include:
- Other workshops has that person signed up for in that time period If they have volunteered to teach three workshops over the next few months, we likely won’t place them at all of them. However, we will take advantage of their flexibility to get them in on at least one.
- Each person”s experience with The Carpentries We want to be sure to match up experienced instructors with new instructors, so new instructors are supported by experienced instructors.
- Each person”s skill set with Carpentries material We want to make sure each instructor is comfortable teaching the workshop content, and understands the other instructor”s skills.
- Each person”s acadmic or professional domain It can be helpful, but not required, to match the instructors” domain with the workshop audience. Instructors get opportunities to network in their fields, and learners get to hear from people working in those same fields.
- Geography While we do not guarantee local instructors at workshops, we do take this in consideration to keep the host site”s cost down and to help build local communities.
Regional Coordinator emails these instructors to confirm their availability, and returns back to the other instructors on the list if a conflict has since come up.
Regional Coordinator sends email to workshop instructors and hosts with introductory information. This includes links to guides for roles of host, instructor, and helper.
Regional Coordinator emails everyone else who signed up for that event thanking them for their time, letting them know other instructors were placed, and encouraging them to sign up for other opportunities.
Regional Coordinator reminds instructors to set up a workshop website using the workshop template.
Regional Coordinator sets up surveys in Survey Monkey and emails results links to hosts and instructors.
If needed Regional Coordinator sets up registration in Eventbrite.
- If there is a registration fee,Regional Coordinator informs Business Administrator that this will need to be refunded or applied to the workshop invoice.
In weeks leading up to workshop, Regional Coordinator sends check in emails to be sure planning is progressing smoothly.
After workshop is over Regional Coordinator sends email asking how things went and collecting attendance data.
Regional Coordinator records workshop attendance in AMY, and if additional information is provided, in the Workshop Documents GitHub repo.

For self organized workshops¶

Instructors notify Regional Coordinator about upcoming self organized workshop. This is no fee (suggested or mandated) for a self organized workshop.
Regional Coordinator reminds them that as a self organized workshop they will have access to our surveys but will not receive any other support in coordinating this workshop.
Regional Coordinator reminds instructors to set up a workshop website using the workshop template.
Regional Coordinator records this in AMY.
Regional Coordinator sets up surveys in Survey Monkey and emails results links to hosts and instructors. Explain to the hosts and instructors that this link should not be shared. Regional Coordinator informs hosts and instructors where to find the pre and post survey links to distribute to learners.
In weeks leading up to workshop, Regional Coordinator sends check in emails to be sure planning is progressing smoothly. This is optional as instructors and hosts should not be expecting direct support from us.
After workshop is over Regional Coordinator sends email asking how things went and collecting attendance data.
Regional Coordinator records workshop attendance in AMY.

AMY: the Carpentries” internal database¶

Logging in¶

Log in to AMY here. Contact Carpentries staff if you need login credentials.

_images/amy_login_screen.png AMY login screen goes here

AMY dashboard¶

All the menus and a search bar are displayed across the top. The main page has two columns, showing published workshops and unpublished workshops.

This view can be filtered to show workshops assigned to the logged in administrator, unassigned workshops, or all workshops.

_images/amy_dashboard.png AMY dashboard

Published workshops have a complete start and end date, a valid url, and a complete location.
Unpublished workshops are all workshops that do not meet the criteria to be published.

Published workshops will show up on the Software Carpentry, Data Carpentry, or Library Carpentry website, depending on how they are tagged.

From here you can also add new persons, events, organizations, or airports to the database.

_images/amy_add_new.png AMY add new elements

Adding a new organization¶

If the site name is not already in AMY, add a new one by selecting «New Organization.» Do not enter http:// or any slashes in the domain name.

_images/amy_new_organization.png AMY add new organization

Adding a new person¶

If a person”s record does not exist in the database, it can be added individually or as part of a bulk upload.

Adding an individual person record¶

Select «New person» and enter in as much information as possible. At minimum a personal name is required. If the airport is not listed, it will need to be added in.

The person”s privacy settings can also be set here. The person”s profile will display on The Carpentries website only if the consent box is checked.

_images/amy_new_person.png AMY add new person

Adding bulk person records¶

Person records can also be added in bulk from a .csv file using the Bulk add persons menu option in the New menu at the top right or the More menu. Note: To bulk add records, the persons must have a role specified (instructor,helper,learner,host) associated with a specific event.

_images/amy_bulk_add_person_menu.png AMY bulk add person menu

Use the blank template to generate a well formed csv noting each person”s personal name, family name (optional), email address (optional), role, and associated event. Any additional information about the person must be entered manually.

The role must exactly match the instructions here. The event slug must exactly match the slug for the event recorded in AMY.

This will take you to a screen where you can verify each record, correct any errors, and submit them for bulk upload. If a person with the same name and email already exists in the database, you will be able to match the new entry to the existing record. Otherwise a new person record will be created.

Adding a new airport¶

Airports are used as approximate geographic identifiers for our instructors. Each airport is identified by its three digit IATA code which can be looked up using the link in AMY.

Enter in the airport”s IATA code, full name, country, and latitude and longitude.

_images/amy_add_airport.png AMY add airport

Adding a new event¶

New events can be created one of several ways:

By manually entering all information on the new event page
By importing from URL on the new event page
By accepting a workshop request

Creating a new event manually¶

Create the workshop slug. This must be in the form YYYY-MM-DD-sitename (for example, 2018-01-01-hawkins. The same slug should be used for the workshop”s GitHub page and any other place the workshop is identified. If the exact date is not known, XX can replace the month and/or day (for example, 2018-01-xx-starfleet).

_images/amy_new_event_slug.png AMY new event slug

If known, enter in the workshop dates.

_images/amy_new_event_dates.png AMY new event dates

Select the host site name from the drop down menu. If the host site does not appear on the list, create a new organization.

_images/amy_new_event_host.png AMY new event host

Select the administrator from the drop down menu. This will almost always be Software Carpentry, Data Carpentry, Library Carpentry, or self organized.

_images/amy_new_event_administrator.png AMY new event administrator

Select the name of the Carpentries Regional Coordinator responsible for managing this workshop.

_images/amy_new_event_assigned_to.png AMY new event assigned to

Assign all appropriate tags to the event.
- SWC: Software Carpentry
- DC: Data Carpentry
- LC: Library Carpentry
- WiSE: Women in Science and Engineering
- TTT: Instructor Training
- LSO: Lesson Specific Onboarding
- ITT: Trainer Training
- LMO: Lesson Maintainer Onboarding
- online: Online events
- stalled: When host stalled event planning before workshop occurred
- unresponsive: When host/instructors were unresponsive to requests for attendance data
- hackathon: Non-workshop events. Hackathons related to lesson development or other topics.
- cancelled: When a fully scheduled event gets cancelled

_images/amy_new_event_tags.png AMY new event tags

TTT Open applications. For instructor training events, member sites become associated with the event as individuals from that member site are assigned to that event. Checking this box will allow people from the open application pool to be matched to this event as well.

_images/amy_ttt_open_applications.png AMY TTT Open Applications check box

Select the curricula taught at this workshop.

_images/amy_curricula_taught.png AMY curricula taught

Enter in the workshop”s url (to the GitHub page, not the repo). This is generally in the format username.github.io/YYYY-MM-DD-sitename.

_images/amy_new_event_url.png AMY new event url

Enter in the human language the workshop is taught in. This is especially important for the Carpentries to track workshops in languages other than English.

_images/amy_new_event_language.png AMY new event language

If the workshop is using Carpentries Eventbrite for registration, enter the Eventbrite key. This is not needed if the host site is using their own Eventbrite account or any other internal system.

_images/amy_new_event_eventbritekey.png AMY new event eventbrite

After the event is over, record the total number of learners who attended the workshop.

_images/amy_new_event_attendance.png AMY new event attendance

Enter only the email address for the main contact person for this event.

_images/amy_new_event_contact.png AMY new event contact

Add in the location including the country, venue name, address, and latitude/longitude coordinates.

_images/amy_new_event_location.png AMY new event location

Add in any other notes that may not be covered in any fields above. This will be transformed into a timestamped notes log once the event is saved.

_images/amy_event_comment.png AMY new event notes

Click «Submit» to save this event.

Creating a new event from URL¶

If you already have the event”s URL with properly formatted metadata using The Carpentries workshop template, the following information can automatically be imported:

Slug (created from GitHub repo name)
Start and end dates
Location details

Instructor and helper names will be in the notes field but not assigned in the database. All people will need to be assigned to the event.

All other information will need to be entered in as above.

Creating a new event from a workshop request¶

A workshop can be requested from a host site, and this information can be used to create an event in AMY. Select «Workshop requests» from the «Requests» menu.

_images/amy_workshop_request_menu.png AMY workshop requests

This page will show a list of all open workshop requests, with the name/email of the requestor, their affiliation, their preferred dates, the Carpentry type, and any other comments.

_images/amy_workshop_request_list.png AMY workshop request list

At the bottom of this page, the user has the option to accept or discard the request. Choosing «Change state to Accepted» will mark it as accepted in the workshop request list but will not create a new event. Select «Accept and create a new event» to create a new event from this request. All requests should be accepted (unless spam or otherwise inappropriate) so the Carpentries can maintain a history of workshop requests. Events can later be marked as stalled or cancelled.

This will open a page with a side by side view of the request details and view to create a new event. The new event can be created manually or if available, from the URL, as described above.

_images/amy_workshop_request_accept.png AMY workshop accept request

Assigning people to events¶

Regardless of how events are created, adding the people associated with each event can not easily be automated. Name matching is hard.

People can be associated with events one by one or as a bulk upload.

Assigning people to events one by one¶

Go to the event page and click the «Edit» button at the top of the page. Select the «Tasks» tab. (Note the sponsor tab is not currently being used.)

To add a new person to the event, start typing the person”s name in the «Person» field. Auto-completed suggested names will appear.

Add the person”s role in the event (Helper, Instructor, Workshop Host, Learner, Workshop Organizer). «Contributed to Lesson Materials» is not used in this context. «Title» and «URL» are also not used in this context.

If a person”s name does not appear in the dropdown, they may need to be added to the database.

Below this form, a list of all people assigned to this event is displayed. A person”s role can not be directly changed. Instead, delete the item and enter a new one.

When done, go back to the «Event» tab at the top of the page, and click «Submit» at the bottom of the event page to save changes. All people should now appear at the bottom of the event page.

Assigning people to events in bulk¶

See section above.

Instructor Training¶

Accepting Trainee Applications¶

In addition to tracking workshops, AMY also allows us to track applications to instructor training events. The public facing application is here. Applicants are given a group name if participating in a member training event. Open applicants will likely not have a group name.

Once an individual submits the form, the record can be viewed by going to Requests –> Training Requests.

Applications can then be searched by individual name, email address, group name, status (pending, accepted, or discarded), affliliation, or location.

Some trainees will already be in AMY because they were formerly learners or helpers at Carpentries events. If there is a record with a matching name and email address, they will show up with a «matched trainee» when you search for them. If «matched trainee» is blank, you will need to create a new person record for them.

To create a trainee record, click on the «i» icon at the far right of the individual”s line. If you know this person is in AMY under a different name or email address, look this person up here and click «Match to selected trainee account.» If this is a new person, click «Create new trainee account.»

_images/amy_training_match_record.png AMY Match Trainee Record

This will return you to the search screen, and this person”s record will be updated with the new trainee account.

Continue doing this until all relevant applications have a new trainee account. This must be done individually; it can not be done in bulk.

Once all trainees for a given event have trainee accounts, we can assign them to a specific training event and associate them with a specific member contract. This part can be done in bulk for each group of trainees with a unique training date and member site affiliation. The event and the member agreement must already have been created in AMY.

Check all the names to be assigned to the training event and membership, and then select the training event from the first drop down menu. Select the member agreement from the second drop down menu. If the trainees are coming through the open application process rather than a member agreement, check this box instead of choosing a member agreement.

Click «Accept & match selected trainees to chosen training.» The search screen will then update to show that the trainees have been matched to this event. The event page will also update to list these trainees as learners at that event.

_images/amy_instructor_training_match.png Match trainees to instructor training event

Tracking checkout progress¶

The above steps note that a trainee was accepted in to a training event. Completion of the training event and three steps towards trainee checkout can be tracked in AMY. Each person”s record will have a line for Instructor Training Progress.

_images/amy_training_progress.png AMY training progress

Click on the plus sign in the Training Progress line. This will go to a screen where you can track the all steps towards certification.

_images/amy_training_progress_steps.png AMY training progress steps

Recording completion of training event¶

On the screen above, select “Training” and note whether they passed or failed.

Recording completion of discussion session¶

On the screen above, select “Discussion” and note whether they passed or failed.

Recording completion of teaching demo¶

On the screen above, select “DC Demo” or “SWC Demo” depending on which lesson they used for their demo, and note whether they passed or failed.

Recording completion of lesson contribution¶

On the screen above, select “DC Homework” or “SWC Homework” depending on which lesson they used for their contribution, and note whether they passed or failed. In the notes section, link to their lesson contribution.

Issueing badges¶

The Carpentries has various badges that can be issued, including Data Carpentry Instructor, Software Carpentry Instructor, Trainer, Maintainer, and more.

An individual badge can be issued by going to a person”s record and clicking the Edit button.

_images/amy_edit_person.png AMY edit person

Choose the Awards tab on the next screen. Select the Badge type from the drop down menu, and fill in the date it was awarded. The associated event (such as a training event) and awarded by fields are optional. Click Submit to save the entry.

_images/amy_issue_badge.png AMY issue badge

Memberships¶

AMY is also used to track all Carpentries memberships. To create a new membership, the site must first be listed as an organization in AMY.

On the organization”s page, click the green «Add a membership» button. Enter the following information:

Variant (membership type)
Agreement start and end dates
Contribution type (Financial, Person-days, or other)
Workshops without admin fee per agreement
Self organized workshops per agreement (can be left blank as this is typically unlimited)
Instructor training seats (actual number alloted in contract)
Additional instructor training seats (any additional seats allowed beyond contracted amount)
Notes.

Reports¶

AMY comes with several built in reporting features that can be accessed by clicking Reports in the top menu. Most reports include an api link for further analysis.

List of instructors by time period will generate a list of all instructors who have taught or will teach a workshop in a given time period and can be downloaded as a csv file. This is especially useful when inviting instructors to discussion sessions.
Workshops over time, Learners over time, Instructors over time show cumulative numbers of workshops, learners, and instructors from the start of the Carpentries to present day.
How often instructors have taught returns a list of all instructors who have taught at least once with the number of workshops they have taught.
All activity over time returns data on the number of workshops, number of instructors, number of learners, and identifies gaps in data.
Workshop issues and Instructor issues identify specific workshops and instructors with gaps in data.
Find duplicates identifies persons that may be listed as duplicates due to having the same name or email address, and allows the user to merge them.

Roles in AMY¶

What you are able to edit or view depends on your assigned role in AMY.

Instructor login¶

Instructors can log in to AMY to view and update their own information. To do so, they must have a valid GitHub username in their profile. Instructors should visit the AMY login page and click on Log in with your GitHub account.

If an instructor is having trouble logging in, an administrator can verify the following information.

Be sure the GitHub user name is accurate.
Click on Change permissions and be sure Is active is checked. No other permissions should be checked unless the instructor is also an otherwise authorized user.
Logging in allowed should show next to the GitHub name in the profile. If it says Allow logging in with GitHub, click this to allow logging in. This must be done after setting permissions to active above.

Admin roles¶

Admin users will have rights to view and edit many other parts of the AMY database. The Django admin panel can be accessed from the top right menu, under the user”s name, generating a unique URL for the session.

An admin user can view their profile as if they were an ordinary user on this dashboard page.

Other tasks¶

Merging duplicate persons or events¶

If duplicate persons or event records exists, they can be merged. Select «Merge persons» or «Merge events» from the «More» menu.

Choose the two Persons or Events to be merged, and click «Submit» to see merge options. Here you can choose to keep the value from Person/Event A, from Person/Event B, or to combine the values.

Searching¶

General search¶

The quickiest and easiest way to search is using the search box in the top menu bar. This will perform a case insensitive search of any field in AMY, including searching for partial matches. For example:

12-12- will match any workshop slug containing that string (essentially any workshop on December 12 of any year.)
ola tes will match Nikola Tesla and Nolan Bates
stanford will match any one with a stanford email address, with stanford in their name, any workshops with stanford in the slug, the site Stanford University and any records with stanford in the notes.

Searching for Qualified Instructors¶

Under the «More» menu, select «Find Workshop Staff.» Here you can filter by the following criteria:

Airport: This returns a list of all Instructors beginning with those who list that airport as their closest airport, and then continues reaching farther out.
Country: This returns a list of all Instructors who are in that country. It does not continue to any proximate countries.
Latitude and Longitude: Like the Airport search, this begins with people whose listed airport is closest to that latitude and longitude, and then continues reaching farther out.
Badges: Selecting more than one Instructor badge will return a list of Instructors who have any of those badges. If no badge is selected, the search will return unbadged Persons.
Was helper at least once before, Was organizer at least once before, Is an in-progress instructor trainee are based on AMY”s current records
Languages, Gender, and Lessons come from the Person record for that individual.

Searching for Events¶

Clicking «Events» on the top menu bar will take you to a list of all recorded events - past, present, and future, including those that were stalled or cancelled.

Events can be searched from the left side options by Assignee, Tags, Host, Administrator, Invoice status (deprecated), Completed, Country, and Status.

Searching for Organizations¶

Clicking «Organizations» on the top menu bar will take you to a list of all recorded organizations, regardless of their involvement with The Carpentries.

Organizations can be searched by Country and Membership type.

Searching for Persons¶

Clicking «Persons» on the top menu bar will take you to a list of all recorded persons, regardless of their involvement with The Carpentries.

Persons can be searched for by badges and by teaching history. See the section above to search specifically for qualified instructors.

Setting up surveys using Survey Monkey¶

The Carpentries uses Survey Monkey to manage all workshop surveys.

Logging in¶

The Workshop Administration Team will have log in credentials from the Carpentries to set up surveys. They will share links to view survey results with workshop hosts and instructors. Hosts and instructors do not need log in credentials.

Contact team@carpentries with questions about logging in.

Setting up a workshop survey¶

If a learner accesses the survey from that workshop”s website (in the format username.github.io/YYYY-MM-DD-sitename), the survey links will be appended with the workshop slug (so https://www.surveymonkey.com/r/swc_pre_workshop_v1 becomes https://www.surveymonkey.com/r/swc_pre_workshop_v1?workshop_id=YYYY-MM-DD-sitename).

The «naked» link will take them to the exact same survey, but will make it slightly more difficult for us to share survey results.

The survey has already been designed, and we will not customize any of the questions for specific workshops or sites.

The existing questions about which workshop the learner is attending are being deprecated in favor of a new question:

_images/surveymonkey_workshopid.png Survey workshop id

Learners are prompted to fill in their workshop ID or the workshop date and location if the ID is not known. Having this information accurate and complete is crucial to being able to share survey results.

Modifying survey responses¶

Survey data can be modified once a user has submitted their response. To protect the integrity of our data, this should be done only if it is known that a respondent filled in an incorrect or incorrectly formatted workshop id.

From the survey page, select Analyze Results.

_images/surveymonkey_analyzeresults.png Survey analyze results

Following the instructions above, search for the possible responses to a workshop id. For example, search for all responses containing the word “starfleet” to find any one who may have attended the workshop “2018-01-01-starfleet”.

_images/surveymonkey_individualresponses.png Survey individual responses

Use the arrow icons to navigate to the response that needs editing, and click «edit».

_images/surveymonkey_selectresponse.png Survey select response

The survey will open in a new window. Navigate to the workshop id question without editing any other responses.

_images/surveymonkey_incorrectslug.png Survey find incorrect response

Type in the correct workshop id and click next.

_images/surveymonkey_correctslug.png Survey add correct response

Close this window so no other responses are affected. This should now show up modified and correct in the Survey Monkey responses.

Continue this for any incorrect response.

Running a report as described above should now give you correct responses.

Event registration using Eventbrite¶

Host sites can opt to use their own systems for registering learners at their workshops, or we can set up a registration page using Eventbrite.

Logging in¶

The Workshop Administration Team will have log in credentials from the Carpentries. They will give hosts of individual events access to log in to that event only.

Contact team@carpentries.org with questions about logging in.

Creating a new event¶

Click on «Manage Events» under «CARPENTRIES»

_images/eventbrite_start.png Eventbrite new event

You”ll see Live, Draft, and Past workshops. To create a new event, you can use one of the existing drafts as a template. Click on «Drafts.»

_images/eventbrite_livedraftpast.png Eventbrite events

Select «Manage» under the template for the appropriate Carpentries lesson program.

_images/eventbrite_selectdraft.png Eventbrite select draft

Copy this event, giving it a meaningful name.

_images/eventbrite_copyevent.png Eventbrite select draft _images/eventbrite_copyevent2.png Eventbrite copy event

You can now set up the new event page.

_images/eventbrite_locationanddate.png Eventbrite new event location and date

Fill in the address for the event location. If you don’t see boxes for address, city, state, country, etc., click on “Enter Address” to display them.

Fill the start/end date/time information. Note that Eventbrite does not let you have multiple day events, so for an event that goes 9 am to 5 pm both January 1 and 2 you have to make it look like it starts at 9 am on January 1 and goes until 5 pm on January 2. Otherwise Eventbrite treats it as two events. Be sure to select the correct time zone.

The overall template includes a templated description of the event. Update this with the start and end times, the GitHub link, and link to the pre-workshop survey. You can also add in any other information specific to that event.

_images/eventbrite_description.png Eventbrite new event description

Create tickets¶

Eventbrite allows for both free and paid tickets. These settings can not be changed once the event has been published, so be sure to verify this in advance. You can have a mix of free and paid tickets.

_images/eventbrite_tickettypes.png Eventbrite ticket types

If the workshop is entirely free, delete the paid ticket option by clicking on the trash can icon (or delete the free option if all tickets are paid).

Click on the gear icon to edit settings for that ticket type.

For free tickets, you can customize the ticket type name. Edit the number of tickets available and dates when ticket sales start and end.

_images/eventbrite_freeticketsettings.png Eventbrite free ticket settings

For paid tickets, you can customize the ticket type name. Edit the number of tickets available and dates when ticket sales start and end. Edit the cost per ticket. Select «Absorb fees.» You must also set a refund policy - be sure to confirm this with the host site.

_images/eventbrite_paidticketsettings.png Eventbrite paid ticket settings _images/eventbrite_refunds.png Eventbrite paid ticket settings

At this point the event is almost ready to be published. It”s a good idea to let the host contact look over the page before it goes live. You can do this by initially publishing it as password protected.

_images/eventbrite_savepassword.png Eventbrite password settings

Make it a private event, requiring a password.

You can now either save this event if you need to work on it more, or publish it (make it live).

_images/eventbrite_saveorpublish.png Eventbrite password settings

This will take you to your event dashboard where you can monitor ticket sales. Click «view» on the top right corner to see what this page will look like publicly.

Share this link with the host site along with the password you created so they can look over the page and confirm that it looks good, or suggest changes if needed. Once it looks good, select «edit» from the dashboard and remove the password so the page can be shared publicly.

Giving hosts access to view registration¶

Often a workshop host will want to check in to see who”s registered, manage the waitlist, email registrants, etc. You can set this up through Account Settings.

_images/eventbrite_acctsettings.png Eventbrite account settings

From here, select «Multi user access» from the options on the left.

You”ll see a list of all email addresses that have access to at least one of our events. If you”re giving an existing user access to a new event, select «edit» next to their email address. Otherwise click the «Add Email Address» button at the bottom of the page.

Enter the person”s email address and give them access to their event only.

_images/eventbrite_newuserevent.png Eventbrite new user event access

Give the user access to at most the following actions only:

Edit event details not including payment options
- Edit ticket types
- Customize the registration page
View order and attendee reports (read only)
- Manage orders and attendees
- Access to aggregate financial data
Send invites, manage contacts, and email attendees
Check in Attendees

_images/eventbrite_newuseractions.png Eventbrite new user event actions

The user should get notifications for:

Order confirmations
Contact the organizer
Refund requests

_images/eventbrite_newusernotifications.png Eventbrite new user event notifications

Email templates¶

From Regional Coordinator¶

General inquiry response¶

Subject: About hosting a Carpentries Workshop

Dear [ name ],

Thanks so much for inquiring about hosting a Carpentries workshop at [ site_name ]. Here”s some background about our programs and how we run.

Software Carpentry (SWC), Data Carpentry (DC), and Library Carpentry (LC) are programs of The Carpentries (a fiscally sponsored project of Community Initiatives). All programs offer two day long workshops taught live in-person by a team of two trained instructors. Software Carpentry focuses on best practices in computational programming that help scientists and researchers be more effective with their work. Lessons are domain agnostic and use generic data. All Software Carpentry workshops always cover three core areas: shell scripting (bash), version control (Git), and a programming language (R or Python). Read more here (https://software-carpentry.org/lessons/). Data Carpentry has a similar foundation but focuses on the data lifecycle, from cleaning & organization to analysis & visualization. Lessons and the data they use are domain specific, with offerings in ecology/biology, genomics, geospatial data, and more in the works. Read more here (http://www.datacarpentry.org/lessons/ ). Library Carpentry workshops teach people working in library- and information-related roles how to apply concepts from software development fields in library tasks and identify and use best practices in data structures.

All workshops have a standard fee of US$2500, plus any costs for instructor travel (which may include airfare, ground travel, hotel, and meals/incidentals). You can read more about the costs and how to request a workshop here for Software Carpentry (https://software-carpentry.org/workshops/request/) and here for Data Carpentry (http://www.datacarpentry.org/workshops-host/).

Workshops are offered on demand, not on a set schedule, and typically require 2-3 months lead time to plan.

I”d be happy to answer any questions you have about holding a Carpentries workshop at [ site_name ] by email, or set some time to talk by phone or videocall. Let me know what you”re thinking of doing, and we”ll talk about how we can work together. I look forward to hearing back from you.

Best,

[ your_name ]

New Teaching Opportunities on Signup Sheet¶

Subject: Upcoming Carpentries teaching opportunites in [REGION]

Hi Everyone,

We have uploaded new teaching opportunities in [REGION]! Please take a moment to review the upcoming workshops and be sure to add your name if you are interested. Travel within [REGION] will be covered.

Here is the signup sheet for your convenience: (INSERT THE LINK FOR THAT REGION FROM THE SIGN UP SHEET).

Feel free to email me with any questions! (SENDER NAME)

Logistics Information from Host¶

Use this template if the host did not fill out a workshop request form.*

Hi [Host Name],

Thanks so much for planning a Carpentries workshop at [site name]. I”m excited to work with you to ensure you have a successful workshop!

To help us learn more about what you want to do and support you accordingly, please fill out our workshop request form here (https://amy.carpentries.org/forms/workshop/). We”ll follow up with you promptly so we can get started planning.

Best,

[sender name]

Confirming instructor availability¶

Hi [ instructor name ],

You signed up as interested in teaching the [ Carpentry type ] workshop at [ site name ] on [ scheduled dates ]. I”m writing to see if you are still interested and available in doing this, and what questions you may have about it. If this works, I”ll send an email to you and the hosts at [ site name ] so we can get started planning.

If flexible dates Could you also let me know if you have any preferences or constraints in the date range we”re looking at?

Thanks so much for considering this - I”m hoping it works out for you. Can you let me know by [ date ]? I look forward to hearing from you.

Best,

[ sender name ]

Host and instructor introductions¶

Subject: Carpentries workshop at [ site_name ], [ Date of Workshop ] - Making introductions

Hi everyone,

This email is to introduce [ host_name ] of [ site_name ] with instructors [ instructor1_name ] and [ instructor2_name ]. They will be teaching a [ carpentry_type ] workshop on [ workshop_date ].

I also want to introduce our Regional Coordinator, [ admin_name ]. [ She or he ] will be supporting all of the logistical details with this workshop.

You can all read more about the roles of workshop hosts, instructors, and helpers here (http://docs.carpentries.org/topic_folders/hosts_instructors/index.html). I”ll highlight a few things here. There”s a lot of information here, so please take some time to read through things carefully and ask questions as needed.

Instructors will work directly with [ host_first_name ] to make travel arrangements. We are not part of this process. This may include airfare, ground travel, hotel, and meals/incidentals. [ host_first_name ], it is up to you whether you want to book things directly or have instructors make their own arrangements and get reimbursed. Either way, please keep in mind our instructors are volunteering two days of their time to teach with you, so please support them in making travel and reimbursement as smooth as possible. Instructors, please be sure to review the site”s policies around making travel arrangements and handling reimbursements - we want to be sure everything is handled quickly and efficiently.

[ host_first_name ] , can you share a little about who your learners are and what you and they are expecting? That will help our instructors be prepared. We also like to have a couple of helpers at each workshop from the local community. Would you be able to help secure a couple of helpers? They don”t need to be connected with us; they just need a good understanding of the technologies we teach and an enthusiasm to help others.

[ instructor1_first_name ] and [ instructor2_first_name ], please feel free to introduce yourselves and share a bit about your backgrounds. We value the background and expertise you bring to this, and want to hear about you.

[ instructor1_first_name ] and [ instructor2_first_name ] will divide up the curriculum:

https://software-carpentry.org/lessons/

OR

http://www.datacarpentry.org/lessons/

OR

https://librarycarpentry.org/lessons/

to know who”s teaching what. One of them will create the workshop”s web page on GitHub, which will include workshop details and instructions on what learners will need to install on their computers. The template can be found here:

https://github.com/carpentries/workshop-template

Please use the workshop id [ workshop_id in form of YYYY-MM-DD-sitename ]

[ host_first_name ], if you want to handle registration internally that”s fine. Otherwise [ admin_name ] can work with you to create an Eventbrite registration page. She will need to know a total count, the registration fee (if any, as well as a refund policy), and the exact location. Regardless, all learners should complete pre/post workshop surveys which will be available on the webpage the instructors create. [ admin_name ] will share links so you all can view survey results.

[ admin_name ] will check in over the next few weeks and after it”s all over to hear how it went – including getting attendance figures, ideally broken out by number registered and number attended each day. Any of you are also welcome to join our instructor discussion sessions before and/or after the workshop. It”s a great way to ask questions and share ideas with other instructors before you teach, and to give us feedback after you teach. Check out the schedule and sign up here: http://pad.software-carpentry.org/instructor-discussion

We are so glad to have everyone confirmed for this. Please email any questions you all may have for us or each other.

Thanks so much!

Best,

[ sender name ]

Other instructors placed¶

Subject: Carpentries workshop at [ site_name ]: Other instructors placed

Hi [ names ],

You signed up as interested in teaching at the [ Software_/ Data / Library ] Carpentry workshop at [ site_name ] scheduled for [ date ].

This is to let you know we have placed other instructors there. Thanks so much for signing up and please keep an eye out for other opportunities to teach. We”ll be sure to get you in on another workshop. Any questions please let me know.

Thanks!

[ sender name ]

Eventbrite information needed for Registration¶

Subject: Carpentries workshop at [site name]: Eventbrite Registration Information

Hi [names],

I look forward to working with you to ensure you have a fantastic workshop!

I can help you set up your registration page. If you would like my assistance, please provide me with the following information:

Exact location (address, building name, room number)
Number of registrants
Time of event
Fee (if any)
Refund policy (if there is a fee): none/1/7/30 days prior to event
Email address of those who will need access to the Eventbrite page to see registration and make changes

The registration form will be completed after the workshop website has been created and shared with me. Please remember to use the workshop id: [INSERT SLUG]

Best,

[SENDER]

Eventbrite Registration Setup¶

Hi [insert name]

I look forward to working with you to ensure you have a fantastic workshop!

I can help you with your registration. If you need my assistance, please provide me with the following information:

Exact location
Number of registrants
Time of event
Fee (if any)
Refund policy (if there is a fee): 1/7/30/none days prior to event
Who will need access to the Eventbrite page to see registration and make changes

Also, once you have created the workshop url, please remember to share. Using the workshop id:[ workshop_id in form of YYYY-MM-DD-sitename ]

Best,

[sender name]

Eventbrite Registration Complete¶

Hi [insert name],

Here is your link to the Eventbrite page: [insert eventbrite registration link]

Currently, there is a password [insert password] for you to go in and make any changes. Once you have approved, the password will be removed.

I have granted access for you to make edits to the emails you provided, please check your email. Feel free to update or edit when you see the need, this will eliminate you having to wait for me, if there is something urgent.

The Eventbrite Key is [insert eventbrite key, which is the 11 trailing numbers of the registration link] for you to add to your workshop url.

Please let me know if you have any other questions!

Best,

[sender name]

Pre workshop check in¶

I”m checking in to be sure you”re ready for your upcoming workshop on [ WORKSHOP DATE ]. If there are any last minute questions you have please let me know. As a reminder please be sure to review the items below to help you prepare for your workshop.

Review the host checklist: (hosts_instructors_checklist.html)
Review the accessibility checklist: (workshop_needs.html#accessibility) for learners
Review the equipment and materials: (workshop_needs.html#equipment-and-materials) needed for workshop
Lastly, please remember to take attendance daily. I will be asking for this information along with the total number registered each day along with any other feedback you would like to provide.

If you have any questions regarding any of this information, please do not hesitate to ask. Wishing you much success and I”ll check back in after it”s over to hear how it went.

Best,

[ sender name ]

Post workshop check in¶

Hi [ instructors/hosts ],

Thank you for volunteering your time to teach a [ Software | Data | Library Carpentry ]workshop on [ dates ] at [ site ]! We appreciate the dedication you’ve shown to help spread data management and computational programming skills, and the hard work you put into preparing for your workshop.

We want to be sure to give credit to all of our instructors and helpers in our database. Please take a moment to provide us with the following person”s email address:

[INSERT NAME 1]
[INSERT NAME 2]

Additionally, please remind your learners to complete the post-workshop survey. This survey asks them to self-evaluate how much they’ve learned and also to give their perspectives on the workshop’s major strengths and opportunities for improvement.

Here are your pre and post survey response links for you to review. As a reminder, please do not share these links publicly.

pre: [ LINK GOES HERE ]
post:[ LINK GOES HERE ]

For your convenience, below you will find several resources that are available to you as an instructor.

Weekly instructors discussion sessions where you can share your feedback and hear from other instructors. Feel free to join us whenever you are available. Check out the calendar here (http://pad.software-carpentry.org/instructor-discussion). Be sure to check your timezone when you sign up.

Data Carpentry (http://www.datacarpentry.org/blog/), Software Carpentry (https://software-carpentry.org/blog/), Library Carpentry (https://librarycarpentry.org/blog/) and The Carpentries (https://carpentries.org/blog/) also welcome blog posts from instructors and workshop hosts who share their experience conducting a workshop. You are more than welcome to contribute as well! If this is something that interests you, please let me know.

If you have any questions regarding anything I’ve shared do not hesitate to email me directly. Thanks for all of your hard work running this workshop!

Best,

[ sender name ]

Host and Business Administrator Introductions (non-members)¶

Subject: [SWC/DC/LC] Carpentries Workshop @ [LOCATION/DATE]: Introducing Administrative Support Specialist

(send to host and cc finance@carpentries.org)

Host,

This is [INSERT NAME OF Administrative Support Specialist], who will be assisting from The Carpentries with invoicing for your [WORKSHOP TYPE (SWC/DC/LC)] workshop on (DATE) at (LOCATION).

[PROVIDE Administrative Support Specialist SHORT DESCRIPTION OF WORKSHOP, I.E. BILLING AMOUNT, WHETHER OR NOT THEY WILL HAVE EVENTBRITE, ANY OTHER INFORMATION YOU HAVE RELEVANT TO BILLING]

He/She has put together this list of questions (https://carpentries.typeform.com/to/T1qPcJ) that usually gives him/her everything she needs to complete the invoicing process, including information about the billing contact, vendor registration paperwork, and POs.

If the person processing the invoice is someone other than you, it is probably best that they fill out this form, and Talisha will reach out with any questions and follow up on any paperwork that your organisation’s process requires. Alternatively, please feel free to connect [INSERT NAME OF Administrative Support Specialist] directly with your billing contact or respond to him/her directly with any information that is appropriate!

Please feel free to work with [INSERT NAME OF Administrative Support Specialist] directly. [INSERT NAME OF Administrative Support Specialist] will take care of all of the billing from here. As always, please feel free to let me know if you have any questions or concerns regarding workshop logistics.

Best,

[Sender]

Host and Business Administrator Introductions (members using Eventbrite)¶

Subject: [SWC/DC/LC] Carpentries Workshop @ [LOCATION/DATE]: Introducing Administrative Support Specialist

(send to host and cc finance@carpentries.org)

Host,

This is to introduce [INSERT NAME OF Administrative Support Specialist], who will be working with you to handle the Eventbrite revenue from your [WORKSHOP TYPE (SWC/DC/LC)] workshop on (DATE) at (LOCATION).

This revenue can either be donated to The Carpentries or returned to you by check (or wire, if needed) after the completion of the workshop.

Please let [INSERT NAME OF Administrative Support Specialist] know what you would like to do, and, if you would like the funds returned to you, the name the check should be made out to and the address where it should be sent. He/She is also happy to answer any questions or concerns you may have.

Eventbrite revenue is received by us 5-7 days after the event registration closes, and the processing time required to receive and then send out the funds to you can be up to two weeks, so you can expect to receive your funds within a month after your event.

Please feel free to work with [INSERT NAME OF Administrative Support Specialist] directly. [INSERT NAME OF Administrative Support Specialist] will take care of all of getting you the Eventbrite funds. As always, please feel free to let me know if you have any questions or concerns regarding workshop logistics.

Best,

[Sender]

Instructions for Instructors to Update AMY Profile¶

Hi [ person name ],

Thank you for inquiring about how to update your profile in AMY (https://amy.carpentries.org/). In order for you to be able to view and update your profile, we need to have a valid GitHub user ID for you. Once you share this with me, I will set up log in access for you.

From here you can update information such as your email address, twitter handle, location, and more. You can also select your privacy settings if you would like your profile to be displayed on our website (https://carpentries.org/instructors/).

Please let me know if you have any other questions.

Best,

[sender name]

From Instructors and Hosts¶

For Self Organized Workshops: Recruiting Co-instructor¶

Subject: Recruiting co-instructors for Carpentry Workshop

Hi [ person name ],

I”m organizing a local [ Data/Library/Software ] Carpentry workshop for [ estimated month/season of workshop ]. The Carpentries is a fiscally sponsored project of Community Initaitives. They teach skills that are immediately useful for researchers, using lessons and datasets that allow researchers to quickly apply what they”ve learned to their own work. I”m really excited about using the [ Data/Library/Software ] Carpentry curriculum here to help our [graduate students/staff/faculty - your target audience] become more efficient in their research.

I”ve completed instructor training for The Carpentries and am certified to teach their materials. To run a workshop, I”ll need at least one (preferably two) co-instructors to help out in teaching the material. The workshops are two days long and instructors usually switch every half day. I”m planning to cover [ your workshop topics ] and was hoping you could teach the [ topic ] section of the workshop. The Carpentries provides ready-to-go lesson materials, so we wouldn”t need to develop anything from scratch. If you”re interested, you can see the materials for [ topic ] here [ link to lesson ] and the rest of the curricular materials here [link to http://www.datacarpentry.org/lessons/ or https://software-carpentry.org/lessons/ ].

I”m looking forward to running a workshop here and think it will be very helpful to our [ target audience ]. If you”re interested in being a co- instructor, please let me know and we can get together and plan. Also let me know if you know anyone else who might be interested and able to help out with the [ topic ] part of the workshop.

Looking forward to working with you on this!

Best,

[ sender name ]

Recruiting Helpers¶

Subject: Recruiting helpers for Carpentry Workshop

Hi [ name ],

I”m running a [ Data/Library/Software ] Carpentry workshop on [ dates of workshop ]. The Carpentries is a fiscally sponsored project of Community Initaitives. They teach skills that are immediately useful for researchers, using lessons and datasets that allow researchers to quickly apply what they”ve learned to their own work. I”m really excited about using the [ Data/Library/Software ] Carpentry curriculum here to help our [graduate students/staff/faculty - your target audience] become more efficient in their research.

During the workshop, I”ll need a few people to help out in case learners run into problems or get stuck. Helpers move around the room to answer questions and help learners work through things like installation problems, error messages and unexpected output. You don”t need to be an expert in the tools we”re covering, just to have used one or more of them and be comfortable helping people troubleshoot. At this workshop, we”re planning on covering [ list of your topics ]. I think you would be a great person to help out with [ topic ]. If you”re interested, you can see the materials for [ topic] here [link to lesson] and the rest of the curricular materials here [link to http://www.datacarpentry.org/lessons/ or https://software-carpentry.org/lessons/ ]. Please let me know if you”re interested in being a helper and if you know anyone else who might be willing to help out.

Best,

[ sender name ]

Advertising your workshop¶

Subject: Carpentries workshop at [ site name ]

On [ dates ], [ organization name ] is hosting a [ Data/Library/Software ] Carpentry workshop for [ target audience/domain ].

The Carpentries is a fiscally sponsored project of Community Initiatives. They teach skills that are immediately useful for researchers, using lessons and datasets that allow researchers to quickly apply what they”ve learned to their own work. I”m really excited about using the [ Data/Library/Software ] Carpentry curriculum here to help our [graduate students/staff/faculty - your target audience] become more efficient in their research.

This workshop is focused on [ Carpentry/domain ]. The curriculum will include:

[names of lessons]
[names of lessons]
[names of lessons]
[names of lessons]

The target audience is learners who have little to no prior computational experience, and the instructors put a priority on creating a friendly environment to empower researchers and enable data-driven discovery. Even those with some experience will benefit, as the goal is to teach not only how to do analyses, but how to manage the process to make it as automated and reproducible as possible. For instance, after attending this workshop you will be able to:

[skill 1]
[skill 2]
[skill 3]

Space is limited and it will likely fill quickly. [ Add sentence about whether workshop is free or if there is a fee. ]. Here is a registration link [ link to your registration page ], and the workshop webpage [ link to your workshop webpage ] for more information. Questions? Send email to [ email contact ].

We hope to see you at the workshop!

Best,

[ sender name ]

Email learners before workshop¶

Hello,

We are excited for the [ Data/Library/Software ] Carpentry workshop this coming [ days of week ] and hope you are too. A few notes:

Be sure to complete the pre-workshop survey [ link to survey ]. We use this to calibrate the pace of the workshop and, together with a post-workshop survey, to assess how it went.

Make sure you have the necessary software installed on your laptop [ list required software for your workshop ]. Here are the instructions [ link to instructions ]. If you have any trouble, send us an email or come a little early [ day of week ] morning. Someone will be there by [ time ] to help with installation issues.

[ Say if you will be providing coffee, snacks, and/or lunch. Include time of lunch break if not providing lunch. ]

If you won”t be able to attend, please let us know so that we can offer your seat to someone on the waitlist.

Some links that will be used in the workshop: workshop page [ link to workshop page ], lesson materials [ link to lesson materials ], etherpad [ link to workshop etherpad ].

Getting to the workshop: [ add directions to your workshop location ]

Please read the Carpentries Code of Conduct (http://docs.carpentries.org/topic_folders/policies/code-of-conduct.html) so that we all are aware of how to treat each other respectfully.

We are committed to making sure that the workshop is accessible to everyone. Please tell us if there is anything we should know in advance in order to make the workshop accessible for you (e.g. sign-language interpreters, large-print handouts, lactation facilities).

Let us know if you have any questions, otherwise we will see you [day of week] morning!

Looking forward to seeing you soon!

Best,

[ sender name ]

Email learners after workshop¶

Hello, Thank you for attending our [ Data/Library/Software ] Carpentry workshop. We hope that you had fun and learned a lot of useful skills.

Please be sure to complete our post-workshop survey [l ink to survey ]. Your answers are essential to allow us to continuously improve our workshops for future learners.

If you have any other feedback about the workshop, or would like to get involved in the Carpentries community, please contact us (mailto:team@carpentries.org). You can also join the Carpentries Discussion mailing list (http://carpentries.topicbox.com/groups/discuss), follow us on Twitter (https://twitter.com/datacarpentry and https://twitter.com/swcarpentry), and get involved with lesson development on GitHub ( https://github.com/datacarpentry and https://github.com/swcarpentry/ ).

We hope to see more of you as you continue to develop your data analysis skills!

Best,

[ sender name ]

Encourage learners to complete pre-workshop survey¶

Hello,

We are excited to meet you at the upcoming [ Data/Software/Library Carpentry workshop ] (INSERT WORKSHOP WEBSITE LINK). To help your instructors provide an inclusive environment, and to learn more about your current experience with the tools you”ll learn, we ask that you complete our pre-workshop survey ( https://www.surveymonkey.com/r/swc_pre_workshop_v1 OR https://www.surveymonkey.com/r/dcpreworkshopassessment ).

Your responses will be recorded anonymously. Your IP address will be registered; however, your responses will remain anonymous. You are not required to take this survey to participate in our workshop, but your responses are very valuable to us. You may quit the survey at any time, or skip any item other than those required to correctly sort your responses.

If you have any questions about our assessment strategy, please contact Kari L. Jordan, Director of Assessment and Community Equity for The Carpentries at kariljordan@carpentries.org.

Our best,Your instructors

Encourage learners to complete post-workshop survey¶

Hello,

Thank you for attending the recent [ Data/Library/Software Carpentry workshop ]. We hope you left your workshop feeling empowered to continue learning more about the tools that were covered. We”d like to capture your thoughts about what was covered and your perception of the workshop overall. Please complete the post-workshop survey at (https://www.surveymonkey.com/r/dcpostworkshopassessment OR https://www.surveymonkey.com/r/swc_post_workshop_v1 ) as soon as possible.

If you have any questions about our assessment strategy, please contact Kari L. Jordan, Director of Assessment and Community Equity for The Carpentries at kariljordan@carpentries.org. We look forward to your continued involvement with our community!

Our best,Your instructors

¿Por qué se creó este manual?¶

En el pasado, información y recursos relacionados con las Carpentries estaban dispersos en varios sitios de la red. Este manual abarca la información en una manera centralizada sobre cómo gestionar un taller, crear o mantener una lección, participar en el curso de instructores y mucho más.

Muchos miembros de la comunidad han ayudado a la creación de este cuaderno, y así también aceptamos nuevas aportaciones. Ayúdanos a mejorar este recurso comunitario a través de la creación de incidencias (issues) o nuevas contribuciones (a traves de pull requests) en el presente repositorio de GitHub. (Nota: Si deseas ayudar con las traducciones accede a través de transifex).

Compilando el manual¶

Este sitio está construido utilizando el generador de documentación Sphinx (una herramienta de Python) y el tema Read the Docs para el estilo. (No debe confundirse con readthedocs.io: ¡el sitio no está alojado en readthedocs.io!)

Para obtener más información sobre el uso de Sphinx, consulte la Guía de inicio (sphinx-doc.org) o el Quick Start (readthedocs.io) para obtener una explicación sobre cómo usar Sphinx.

Dependencias requeridas¶

Para instalar las dependencias requeridas (Sphinx y el tema ReadTheDocs), ejecute el siguiente comando desde el directorio del repositorio para instalar todas las dependencias de Python:

pip install -r requirements.txt 

Después de instalar las dependencias, puede construir el sitio localmente ejecutando el siguiente comando desde el repositorio:

$ make html

Abra el archivo _build / html / index.html para obtener una vista previa del sitio localmente. Python ofrece una forma rápida de ejecutar un servidor web para albergar archivos locales. Ejecute lo siguiente:

$ cd _build/html

# Python 2:
$ python2 -m SimpleHTTPServer

# Python 3:
$ python3 -m http.server

En ambos casos, se ejecutará un servidor web local en el puerto 8000, así que navegue a http://localhost:8000 en su navegador para ver el sitio localmente.

Puede realizar cambios en el contenido del repositorio y volver a ejecutar make html para actualizar el contenido del sitio web. Si tiene problemas con que el sitio no se actualiza, puede eliminar el contenido del directorio _build (que se genera automáticamente) con rm -fr _build/*.

Si se agregan nuevos archivos o carpetas al Manual, será necesario actualizar index.rst para que Sphinx los incluya en el sitio final.

Estructura del Sitio¶

El nivel raíz index.rst genera las categorías principales y la barra lateral de navegación. Cada subsección es una carpeta en el directorio topic_folders. Cada carpeta dentro del directorio topic_folders tiene su propio archivo index.rst. Estos luego se expanden en las subcategorías en cada directorio.

Dentro del archivo index.rst de cada carpeta, el encabezado de una sección está definido por una cadena de «===» por debajo. Los subtítulos se pueden definir usando «###» en cada archivo de Markdown o por un encabezado con «—» por debajo en el archivo index.rst.

Formato de Hipervínculos¶

En los documentos de Markdown los enlaces se pueden formatear como Markdown estándar, con el texto entre corchetes y el hipervínculo entre paréntesis:

[text](hyperlink)

Para los archivos index.rst, los enlaces deben formatearse de la siguiente manera. Tenga en cuenta que el texto va seguido del hipervínculo entre paréntesis angulares, todo dentro de acentos graves (backticks) y luego seguido de un guión al piso (underscore).

`text<hyperlink>`_

Información Adicional¶

Este sitio está construido a partir del master branch de este repositorio (carpentries/handbook). Los cambios se pueden observar en vista previa aquí: http://docs-src.carpentries.org/. Los cambios en el sitio real https://docs.carpentries.org/ pueden tardar hasta un día en activarse una vez que los cambios se han enviado a Github, ya que el contenido del sitio está detrás de una CDN (Content Distribution Network o Red de distribución de contenido español) que almacena el contenido en caché.

Si está realizando cambios experimentales en el contenido, asegúrese de hacerlo en un branch que no sea master branch o live branch. Cuando sus cambios estén completos y listos para ser enviados al live site, abra un pull request en carpentries/handbook.

Los borradores se pueden agregar a la carpeta de drafts del repositorio carpentries/userguides (en el master branch) sin dañar nada. Los borradores no se crean para el live site y estos archivos pueden contener información inexacta o desactualizada.

Licencia¶

Documentación¶

La documentación de las Carpentries en este repositorio está disponible bajo la licencia Creative Commons Reconocimiento. El texto a continuación es un resumen inteligible para humanos (y no un sustituto) de la licencia real CC-BY 4.0.

Eres libre de:

Compartir—copiar y redistribuir el material en cualquier medio o formato
Adaptar—remezclar, transformar y crear a partir del material

para cualquier finalidad, incluso comercial.

El licenciador no puede revocar estas libertades mientras cumpla con los términos de la licencia.

Bajo las condiciones siguientes:

Reconocimiento—Debe reconocer adecuadamente la autoría (citando que tu material es una adaptación the material bajo Copyrigth © The Carpentries y, cuando sea posible, enlazando a http://carpentries.org/), proporcionar un enlace a la licencia e indicar si se han realizado cambios. Puede hacerlo de cualquier manera razonable, pero no de una manera que sugiera que tiene el apoyo del licenciador o lo recibe por el uso que hace.

No hay restricciones adicionales—No puede aplicar términos legales o medidas tecnológicas que legalmente restrinjan realizar aquello que la licencia permite. Con el entendimiento que:

Avisos:

No tiene que cumplir con la licencia para aquellos elementos del material en el dominio público o cuando su utilización esté permitida por la aplicación de una excepción o un límite.
No se dan garantías. La licencia puede no ofrecer todos los permisos necesarios para la utilización prevista. Por ejemplo, otros derechos como los de publicidad, privacidad, o los derechos morales pueden limitar el uso del material.

Software¶

Excepto donde se especifique, los ejemplos de programas y otro tipo de software provisto por las Carpentries están disponibles bajo la licencia MIT, aprovada bajo la Iniciativa para el Código Abierto (OSI por sus iniciales en inglés).

Traducción no oficial de la licencia MIT:

El aviso de copyright anterior y este aviso de permiso se incluirán en todas las copias o partes sustanciales del Software.

EL SOFTWARE SE PROPORCIONA «COMO ESTÁ», SIN GARANTÍA DE NINGÚN TIPO, EXPRESA O IMPLÍCITA, INCLUYENDO PERO NO LIMITADO A GARANTÍAS DE COMERCIALIZACIÓN, IDONEIDAD PARA UN PROPÓSITO PARTICULAR E INCUMPLIMIENTO. EN NINGÚN CASO LOS AUTORES O PROPIETARIOS DE LOS DERECHOS DE AUTOR SERÁN RESPONSABLES DE NINGUNA RECLAMACIÓN, DAÑOS U OTRAS RESPONSABILIDADES, YA SEA EN UNA ACCIÓN DE CONTRATO, AGRAVIO O CUALQUIER OTRO MOTIVO, DERIVADAS DE, FUERA DE O EN CONEXIÓN CON EL SOFTWARE O SU USO U OTRO TIPO DE ACCIONES EN EL SOFTWARE.

Marca registrada¶

«The Carpentries», «Software Carpentry», «Data Carpentry», y «Library Carpentry», junto con sus respectivos logos, son marca registrada de Community Initiatives.