├── .github └── workflows │ └── build-deploy.yml ├── .gitignore ├── CODEOWNERS ├── LICENSE.md ├── Makefile ├── _templates └── layout.html ├── conf.py ├── data └── github_labels.csv ├── drafts ├── blog_post_ideas.md ├── email-scripts.md ├── finance │ ├── expenses.md │ ├── index.rst │ └── invoicing.md ├── memberships │ ├── fieldbook.md │ ├── hubspot.md │ ├── index.rst │ └── membership_workflow.md └── survey_monkey.md ├── img ├── .DS_Store ├── comms-images │ ├── EOCY-fundraising-letter-pullquote.jpg │ ├── comms-plan-1.png │ ├── comms-plan-2.png │ ├── comms-tone-scale.png │ ├── fundraising-video-executive-director-long-form.png │ └── fundraising-video-title-card.jpg ├── logo.ico └── logo.png ├── index.rst ├── make.bat ├── readme.md ├── requirements.txt └── topic_folders ├── assessment ├── assessment-network.md ├── assessment.md └── index.rst ├── communications ├── guides │ ├── adhere-style-guide.md │ ├── community_events.md │ ├── images │ │ ├── blog_post-new_branch.png │ │ ├── blog_post-new_branch_new_folder.png │ │ └── calendly.gif │ ├── index.rst │ ├── select-blog-tags.md │ ├── share-opportunities.md │ ├── submit-news-item.md │ └── submit_blog_post.md ├── index.rst ├── resources │ ├── brand_identity.md │ ├── commons.md │ ├── comms-implementation-plan.md │ ├── comms-strategy.md │ ├── index.rst │ ├── logos.md │ ├── presentations.md │ └── style-guide.md └── tools │ ├── codimd.md │ ├── etherpads.md │ ├── github_organisations.md │ ├── images │ ├── .png │ ├── chat_waiting_room.png │ ├── claim_host.png │ ├── codimd_mode_buttons.png │ ├── event_setup.png │ ├── host_key.png │ ├── host_security_screenshare.png │ ├── host_security_waiting_room.png │ ├── make_cohost.png │ ├── participants_more.png │ ├── reserved_room.png │ ├── screenshare_advanced.png │ ├── someone_entered_waiting_room.png │ ├── view_rooms.png │ ├── view_waiting_room.png │ ├── zoom_claim_host.gif │ ├── zoom_closed_caption.png │ ├── zoom_make_host.gif │ └── zoom_screenshare_audio.png │ ├── index.rst │ ├── newsletter.md │ ├── slack-and-email.md │ ├── zenodo_communities.md │ └── zoom_rooms.md ├── for_instructors ├── current_instructors.md ├── images │ ├── amy_instructor_signup.png │ ├── amy_login_screen.png │ └── amy_user_profile.png ├── index.rst └── new_instructors.md ├── fundraising ├── carpentries-sponsorship-program.md ├── collaborating-on-grants.md ├── donation-request-resources.md └── index.rst ├── governance ├── board.md ├── bylaws.md ├── committee-guidelines.md ├── index.rst ├── lesson-program-governors.md ├── lesson-program-policy.md └── task-force-guidelines.md ├── hosts_instructors ├── certificates.md ├── handling_emergencies.md ├── hosts_instructors_checklist.md ├── index.rst ├── instructor_tips.md ├── online-workshop-recommendations.md ├── resources_for_online_workshops.md ├── unofficial_workshops.md └── workshop_needs.md ├── instructor_development ├── community_discussions.md ├── index.rst └── instructor_development_committee.md ├── instructor_training ├── cancellations_and_makeups.md ├── duties_agreement.md ├── email_templates_admin.md ├── email_templates_trainers.md ├── index.rst ├── members_join.md ├── scheduling_training_events.md ├── trainer_coordinator.md ├── trainers_guide.md └── trainers_training.md ├── lesson_development ├── CAC_meeting_checklist.md ├── cac-consult-rubric.md ├── curriculum_advisory_committees.md ├── curriculum_onboarding.md ├── index.rst ├── lesson_infrastructure_subcommittee.md ├── lesson_pilots.md ├── lesson_release.md ├── lesson_sprint_recommendations.md └── spotlight.md ├── maintainers ├── contributing.md ├── email_templates.md ├── github_labels.md ├── github_topics.md ├── index.rst └── maintainers.md ├── policies ├── coc-governance.md ├── coc-membership-agreement.md ├── coc-onboarding.md ├── code-of-conduct.md ├── cookie-policy.md ├── core-team │ └── professional-development-policy.md ├── dmca-policy.md ├── enforcement-guidelines.md ├── images │ └── coc_process_diagram.png ├── incident-reporting.md ├── incident-response.md ├── index.rst ├── index_coc.rst ├── instructor-no-show-policy.md ├── privacy.md ├── reimbursement-policy.md ├── termed-suspension.md └── terms-and-conditions.md ├── regional_communities ├── african_task_force.md ├── carpentries_en_latinoamerica.md ├── index.rst ├── regional_coordinators.md └── regional_email_lists.md └── workshop_administration ├── amy_manual.md ├── email_templates.md ├── expectations.md └── index.rst /.github/workflows/build-deploy.yml: -------------------------------------------------------------------------------- 1 | name: check, build, deploy docs.carpentries.org 2 | 3 | on: 4 | push: 5 | branches: main 6 | pull_request: 7 | 8 | jobs: 9 | build-deploy-docs: 10 | runs-on: ubuntu-20.04 11 | 12 | steps: 13 | - name: Checkout repository 14 | uses: actions/checkout@v2 15 | 16 | - name: Set up Python 3.8 17 | uses: actions/setup-python@v2 18 | with: 19 | python-version: 3.8 20 | 21 | - name: Install dependencies 22 | run: | 23 | python -m pip install --upgrade pip 24 | pip install -r requirements.txt 25 | 26 | - name: Build site 27 | run: | 28 | make html 29 | 30 | - name: Deploy 31 | uses: jakejarvis/s3-sync-action@master 32 | if: github.ref == 'refs/heads/main' 33 | with: 34 | args: --acl public-read --follow-symlinks --delete 35 | env: 36 | AWS_S3_BUCKET: 'docs.carpentries.org' 37 | AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} 38 | AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} 39 | SOURCE_DIR: '_build/html' 40 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | _build/* 2 | .DS_Store 3 | -------------------------------------------------------------------------------- /CODEOWNERS: -------------------------------------------------------------------------------- 1 | 2 | /topic_folders/governance/bylaws.md @carpentries/executive-council 3 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | ## License 2 | 3 | ### Documentation 4 | 5 | The Carpentries documentation material in this repository is 6 | made available under the [Creative Commons Attribution 7 | license][cc-by-human]. The following is a human-readable summary of 8 | (and not a substitute for) the [full legal text of the CC BY 4.0 9 | license][cc-by-legal]. 10 | 11 | You are free: 12 | 13 | * to **Share**---copy and redistribute the material in any medium or format 14 | * to **Adapt**---remix, transform, and build upon the material 15 | 16 | for any purpose, even commercially. 17 | 18 | The licensor cannot revoke these freedoms as long as you follow the 19 | license terms. 20 | 21 | Under the following terms: 22 | 23 | * **Attribution**---You must give appropriate credit (mentioning that 24 | your work is derived from work that is Copyright © The Carpentries 25 | and, where practical, linking to 26 | https://carpentries.org/), provide a [link to the 27 | license][cc-by-human], and indicate if changes were made. You may do 28 | so in any reasonable manner, but not in any way that suggests the 29 | licensor endorses you or your use. 30 | 31 | **No additional restrictions**---You may not apply legal terms or 32 | technological measures that legally restrict others from doing 33 | anything the license permits. With the understanding that: 34 | 35 | Notices: 36 | 37 | * You do not have to comply with the license for elements of the 38 | material in the public domain or where your use is permitted by an 39 | applicable exception or limitation. 40 | * No warranties are given. The license may not give you all of the 41 | permissions necessary for your intended use. For example, other 42 | rights such as publicity, privacy, or moral rights may limit how you 43 | use the material. 44 | 45 | ### Software 46 | 47 | Except where otherwise noted, the example programs and other software 48 | provided by The Carpentries are made available under the 49 | [OSI][osi]-approved 50 | [MIT license][mit-license]. 51 | 52 | Permission is hereby granted, free of charge, to any person obtaining 53 | a copy of this software and associated documentation files (the 54 | "Software"), to deal in the Software without restriction, including 55 | without limitation the rights to use, copy, modify, merge, publish, 56 | distribute, sublicense, and/or sell copies of the Software, and to 57 | permit persons to whom the Software is furnished to do so, subject to 58 | the following conditions: 59 | 60 | The above copyright notice and this permission notice shall be 61 | included in all copies or substantial portions of the Software. 62 | 63 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 64 | EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF 65 | MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND 66 | NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE 67 | LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION 68 | OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION 69 | WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 70 | 71 | ### Trademark 72 | 73 | "The Carpentries", "Software Carpentry", "Data Carpentry", and "Library Carpentry" and their respective logos 74 | are registered trademarks of [Community Initiatives][CI]. 75 | 76 | [cc-by-human]: https://creativecommons.org/licenses/by/4.0/ 77 | [cc-by-legal]: https://creativecommons.org/licenses/by/4.0/legalcode 78 | [mit-license]: https://opensource.org/licenses/mit-license.html 79 | [ci]: http://communityin.org/ 80 | [osi]: https://opensource.org 81 | -------------------------------------------------------------------------------- /Makefile: -------------------------------------------------------------------------------- 1 | # Minimal makefile for Sphinx documentation 2 | # 3 | 4 | # You can set these variables from the command line. 5 | SPHINXOPTS = -a 6 | SPHINXBUILD = sphinx-build 7 | SPHINXPROJ = CarpentriesUsersGuide 8 | SOURCEDIR = . 9 | BUILDDIR = _build 10 | 11 | # Put it first so that "make" without argument is like "make help". 12 | help: 13 | @$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O) 14 | 15 | .PHONY: help Makefile 16 | 17 | # Catch-all target: route all unknown targets to Sphinx using the new 18 | # "make mode" option. $(O) is meant as a shortcut for $(SPHINXOPTS). 19 | %: Makefile 20 | @$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O) 21 | -------------------------------------------------------------------------------- /_templates/layout.html: -------------------------------------------------------------------------------- 1 | {% extends "!layout.html" %} 2 | {% block footer %} {{ super() }} 3 | 4 | 40 | {% endblock %} 41 | -------------------------------------------------------------------------------- /data/github_labels.csv: -------------------------------------------------------------------------------- 1 | print_order,type,label,color,use_prefix,description,long_description 2 | 1,status,help wanted,#DCECC7,FALSE,Looking for Contributors,"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. Issues with this label will be listed on the Help Wanted page of The Carpentries website." 3 | 2,status,in progress,#9BCC65,TRUE,Contributor working on issue,"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." 4 | 3,status,waiting for response,#679F38,TRUE,Waiting for Contributor to respond to maintainers' comments or update PR,Maintainers responded to the Contributor's inquiry and are either waiting on the Contributor to reply back or implement proposed changes. 5 | 4,status,wait,#FFF2DF,TRUE,Progress dependent on another issue or conversation,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. 6 | 5,status,refer to cac,#FFDFB2,TRUE,Curriculum Advisory Committee input needed,Maintainers need advice from the Curriculum Advisory Committee to make a decision on how to proceed with the issue or pull request. 7 | 6,status,need more info,#EE6C00,TRUE,More information needed,Not enough information is provided to proceed with the issue or pull request. 8 | 7,status,blocked,#E55100,TRUE,Progress on addressing issue blocked,A technical problem is hindering progress. A Maintainer or someone else in the community should be notified to ensure that progress is being made. 9 | 8,status,out of scope,#EEEEEE,TRUE,Proposed changes are out of scope,Changes proposed in the issue or in the pull request doesn't fall within the scope of the lesson 10 | 9,status,duplicate,#BDBDBD,TRUE,Issue or PR already exists,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. 11 | 10,type,typo text,#F8BAD0,TRUE,Typo in text for the lesson,Typo in the text/code of the lesson 12 | 11,type,bug,#EB3F79,TRUE,Code included in the lesson needs to be fixed,"Issue about the code, including challenges, answers." 13 | 12,type,formatting,#AC1357,TRUE,Formatting needs to be fixed,Issue about something being wrong in the formatting of the lesson 14 | 13,type,template and tools,#7985CB,TRUE,Issue about template and tools,"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 " 15 | 14,type,instructor guide,#00887A,TRUE,Issue with the instructor guide,Issue related to the content of the instructor guide. Best suited to be addressed by someone familiar with the content of the lesson 16 | 15,type,discussion,#B2E5FC,TRUE,Discussion or feedback about the lesson,"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." 17 | 16,type,enhancement,#7FDEEA,TRUE,Propose enhancement to the lesson,"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." 18 | 17,type,clarification,#00ACC0,TRUE,Suggest change for make lesson clearer,"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." 19 | 18,type,teaching example,#CED8DC,TRUE,PR showing how lesson was modified in a workshop,"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." 20 | 19,type,accessibility,#2F1D46,TRUE,improve content compatibility with assistive technology as well as unassisted access,"PR with suggested accessibility improvements or issue used to ask a question or draw attention to an accessibility issue that needs to be addressed in the lesson content or across other Carpentries resources." 21 | 20,type,invalid,#CCCCCC,FALSE,PR considered as spam.,"Mostly around Hacktoberfest repositories receive spammy pull requests (insignificant, useless, or unnecessary changes). Tagging PRs with this label ensures that these PRs are not counted toward Hacktoberfest." 22 | 21,difficulty,good first issue,#FFEB3A,FALSE,Good issue for first-time contributors,Good issue for a new Contributor to our lesson. 23 | 22,priority,high priority,#D22E2E,FALSE,Need to be addressed ASAP,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. 24 | -------------------------------------------------------------------------------- /drafts/blog_post_ideas.md: -------------------------------------------------------------------------------- 1 | ### Blog post ideas 2 | 3 | We welcome blog posts from our community members about their experiences with The Carpentries or resources of interest to the community. Below are some guiding questions based on the blog post topic. These are just suggestions; please use them if helpful but feel free to structure your post in any way that makes sense to you. 4 | 5 | #### Blogging about instructor training events 6 | 7 | *What was interesting about your group of trainees?* Tell us about your trainees. Were they from a specific domain or field or spread across a wide range of fields? Do they come from a region or institutional type that is under-represented in the Carpentry community? What was their previous involvement with The Carpentries? What are they excited about becoming Carpentry instructors? 8 | 9 | *How did your trainees respond to the curriculum?* Did you do anything differently from the standard instructor training curriculum? How did it work out? What parts of the training resonated with your trainees? Were there any parts that didn’t go as well? Why do you think that was and what could be done differently next time? 10 | 11 | *Did anything unique happen?* What new ideas did your trainees have that you hadn’t thought of before? Did they make any suggestions about improvements to our instructor training or workshop curricula that you’re excited about? What was the most exciting discussion your group had during the training event? 12 | 13 | *What advice do you have for new instructors?* What do you wish someone had told you when you first became an instructor? Do you have any words of wisdom? How can we welcome your new group of trainees to the Carpentry community? -------------------------------------------------------------------------------- /drafts/email-scripts.md: -------------------------------------------------------------------------------- 1 | Scripts for sending automated emails are in this folder (along with testing files): 2 | 3 | https://drive.google.com/drive/u/0/folders/0B2Xc7BrFgkvUTmdQZUtDcDdTWEU 4 | 5 | -------------------------------------------------------------------------------- /drafts/finance/expenses.md: -------------------------------------------------------------------------------- 1 | ### Expense Reporting 2 | 3 | The Carpentries uses Zoho Expense for expense and reimbursement reporting and tracking 4 | 5 | #### Creating expenses in Zoho 6 | 7 | There are many ways to create expenses, including: 8 | 9 | * *Emailing a receipt to Zoho* If you click on 'Receipt Inbox' in the top right there's an email address. If you email receipts to that email address, it will automatically process them and turn them into an expense. It generally autodetects the amount and vendor. 10 | More: https://www.zoho.com/expense/help/receipts/ 11 | 12 | * *Using the Zoho app to take a picture of a receipt* The Zoho Expense app allows you take a picture of a receipt. Then it asks you if you want to add it automatically. It will take that receipt and get the amount and vendor. 13 | 14 | * *Adding an expense manually* Within Zoho Expense, in 'Expenses' you can click 'New'. Then you can add an expense by writing it in, or by dragging and dropping a receipt. You'll likely need to do this manual add for your Salary expense. 15 | 16 | There are categories for each of the expenses. We are tracking expenditures by category, so please add the category to each expense. Pick from whichever is most appropriate in the list. 17 | 18 | #### Submitting Expenses 19 | 20 | Expenses should be submitted in a report through Zoho once a month, at the end of the month. 21 | 22 | #### Expenses Report 23 | 24 | Create expenses individually, including each of the following: 25 | * *Date* 26 | * *Merchant* 27 | * *Category* We must use CI’s pre-determined categories, which have been entered into Zoho. Please do not create any new categories, but see the list below for explanations of the categories (according to CI) and examples for The Carpentries. Categories that we use often are highlighted for easy identification, since we tend to use the same categories most of the time. 28 | * *Amount* 29 | * *Description of item/Business purpose* 30 | * *Attach receipt or receipt image* 31 | 32 | Note: CI needs all of these pieces of information in order to process the reimbursement. 33 | 34 | Create a new report, title it appropriately and add all your expenses for the month to that report (or create the report first and add each expense to it as you create them). 35 | 36 | Once your report is together, click 'Submit'. The report will be sent to the Executive Director, who will respond with questions or approve the expense report, passing it on to CI and the Business Manager for reimbursement and recording. -------------------------------------------------------------------------------- /drafts/finance/index.rst: -------------------------------------------------------------------------------- 1 | FINANCE 2 | ------------------------ 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | * -------------------------------------------------------------------------------- /drafts/finance/invoicing.md: -------------------------------------------------------------------------------- 1 | ### Invoicing 2 | 3 | Invoicing is managed by The Carpentries' fiscal sponsor, Community Initiatives. More information about invoicing will go here. 4 | 5 | 1. do this 6 | 2. then do this 7 | 3. then do one more thing 8 | 9 | -------------------------------------------------------------------------------- /drafts/memberships/fieldbook.md: -------------------------------------------------------------------------------- 1 | ### Fieldbook Guide 2 | 3 | The Carpentries uses [Fieldbook](http://www.fieldbook.com) to manage membership information. 4 | Fieldbook tracks things such as 5 | 6 | * Membership dates 7 | * Contact information 8 | * Membership terms 9 | 10 | Within Fieldbook, the following definitions are used in the database: 11 | 12 | **Status Labels** 13 | * Pending - In discussion that we really confident will lead to membership 14 | * Out for Signatures - Agreement has been sent out for signatures (membership eminent) 15 | * Active - Agreement has been signed and term of agreement has started 16 | * Dormant - Agreement has been signed but term of agreement has not started 17 | * Expired - Term of agreement has ended 18 | * Lead - Interest in membership has been expressed, but an agreement may or may not be likely 19 | * Stale - At one point was pending or lead, but a membership does now not seem likely 20 | * New - this is the first membership agreement this organisation has had with us or a unique agreement with this organisation 21 | * Renew - this is the continuation of a previous agreement 22 | 23 | **Membership Type Labels** 24 | * Standard Silver: 4 coordinated workshops, 33% discount on further workshops, online training for 6 instructors, $7,500 25 | * Corporate Silver: 26 | * Standard Gold: 6 coordinated workshops, 50% discount on further workshops, online or in-person training for 15 instructors, $15,000 27 | * Standard Platinum: 28 | * Coordinated Platinum: 29 | * SWC Contract: 30 | * DC Contract: 31 | * Contract: 32 | * Annual fee: The amount a member has agreed to pay per year 33 | * Paid in Full: if checked, the member has paid the full amount for this agreement 34 | * Invoice: Link to invoice 35 | * Agreement: Link to signed agreement in GitHub (once it is completed) 36 | 37 | Notes: 38 | Multi-year agreement: split up agreements spanning more than 1 year into separate one-year agreements to make keeping track of invoicing and instructor training events easier 39 | 40 | **Invoice Request** 41 | * Not Ready to Request: Once agreement moves beyond ‘Lead’ status, indicates that there is something on the potential member’s end that is keeping us from being able to invoice. 42 | * Request from CI: the member is ready to receive an invoice, and we need to request one. 43 | * Requested: a request for invoice has been submitted to CI 44 | * Sent: CI has sent the invoice 45 | * Paid: the member has paid the full balance of the invoice. 46 | 47 | **Training Status** 48 | * Unknown (Please Check): training status is unknown. 49 | * Scheduling in Progress: Program Coordinator has been notified and is scheduling instructor training event. 50 | * Scheduled: To be marked when an instructor training event has been scheduled. 51 | * Complete: To be marked when an instructor training event has been completed. 52 | * Training Event: Link to instructor training event once Training Status is Scheduled. 53 | 54 | 55 | -------------------------------------------------------------------------------- /drafts/memberships/hubspot.md: -------------------------------------------------------------------------------- 1 | ### HubSpot Guide 2 | 3 | The Carpentries uses [HubSpot](https://www.hubspot.com/) to maintain a record of the contact that has been made with prospective members and successfully or unsuccessfully completed memberships. This is a place to make a note of conversations before they progress to any kind of paperwork and to help keep track of the progress of a conversation. 4 | 5 | 6 | **Definitions** 7 | * *Contacts*: People 8 | * Link people to companies and deals 9 | * *Companies*: Companies/organizations 10 | * HubSpot will automatically populate the company information (note: sometimes it gets it wrong) 11 | * *Deals*: an individual agreement 12 | * *Pipeline*: different tracks for different kinds of agreements 13 | * *Membership Pipeline*: a new agreement 14 | * *Stale*: this conversation has not gone anywhere 15 | * *Appointment scheduled*: the prospective member contact has made an appointment to speak about membership with Executive Director(s) 16 | * *Interested*: the prospective member contact has expressed the desire to become a member 17 | * *Agreement Drafted*: an agreement has been drafted and sent to prospective member contact for comments or approval. 18 | * *Contract Sent*: formal agreement has been agreed upon and is out for signatures 19 | * *Onboarding*: the agreement has been signed, and this organisation is now a member, going through the member onboarding process 20 | * *Closed Won*: all onboarding has been completed. 21 | * *Closed Lost*: this conversation is not going to progress to a membership. 22 | * *Renewal*: an agreement that is renewed 23 | * *Remind about renewal*: this member needs to be contacted about renewal because their current agreement will be expiring soon. 24 | * *Finalise new terms*: member would like to renew, and we are having a conversation with the member about the terms of the renewal agreement. 25 | * *Out for Signatures*: terms for the renewal have been agreed upon, and the renewal agreement is out for signatures. 26 | * *Invoiced*: the member has been sent an invoice for their renewal and the renewal agreement has been signed. 27 | * *Won’t renew*: member will not be renewing. 28 | * *Tasks*: things assigned to team members to do. 29 | 30 | **Features** 31 | * *Send emails* 32 | * Install google add-on to gmail in order to have the option to log emails sent to contacts in deals the contacts are linked to. 33 | * Choose in gmail to log and/or track emails. 34 | * Contacts response will also be logged in deal. 35 | * *Leave Notes* 36 | * Make a note of any change or additional information concerning the deal using notes. The person who left the note, date and time will all be logged. 37 | * Tag other team members in notes, to get their input, or be sure that they receive notice of the information you have entered. 38 | * *Assign Tasks* 39 | * Assign tasks within a deal to yourself or another team member. 40 | * Set up email notification that the task is due. 41 | * *Views* 42 | * View deals in a pipeline (or all together) in list format or board format. 43 | 44 | 45 | 46 | -------------------------------------------------------------------------------- /drafts/memberships/index.rst: -------------------------------------------------------------------------------- 1 | MEMBERSHIPS 2 | ------------------------ 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | * -------------------------------------------------------------------------------- /drafts/survey_monkey.md: -------------------------------------------------------------------------------- 1 | ### Setting up Surveys using Survey Monkey 2 | 3 | The Carpentries uses [Survey Monkey](https://www.surveymonkey.com/) to manage all workshop surveys. 4 | 5 | #### Logging In 6 | 7 | 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. 8 | 9 | Contact team@carpentries with questions about logging in. 10 | 11 | #### Setting up a Workshop Survey 12 | 13 | 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). 14 | 15 | The "naked" link will take them to the exact same survey, but will make it slightly more difficult for us to share survey results. 16 | 17 | The survey has already been designed, and we will not customise any of the questions for specific workshops or sites. 18 | 19 | The existing questions about which workshop the learner is attending are being deprecated in favour of a new question: 20 | 21 | ![Survey workshop id](images/surveymonkey_workshopid.png) 22 | 23 | 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. 24 | 25 | #### Sharing Survey Results: Web View 26 | 27 | Survey results can be shared as a website view with charts and graphs of aggregate data. 28 | 29 | From the workshop page, select `Analyse Results`. 30 | 31 | ![Survey analyse results](images/surveymonkey_analyzeresults.png) 32 | 33 | Select `Filter` and `Filter by Question and Answer`. 34 | 35 | ![Survey filter results](images/surveymonkey_filter.png) 36 | 37 | Select the question about the workshop ID: 38 | 39 | ![Survey results select question](images/surveymonkey_selectquestion.png) 40 | 41 | In the next box, enter the workshop ID that you want to get results for. Select `Exact phrase` to get that workshop ID exactly. 42 | 43 | ![Survey results matching words](images/surveymonkey_matchingwords.png) 44 | 45 | 46 | This will take you to an internal view of the survey results for that event. To create a public view, click the green `Save as` button at the top right, and select `Shared data link`. 47 | 48 | ![Survey results save as](images/surveymonkey_saveas.png) 49 | 50 | This will open a new page for you to set up your public view. 51 | 52 | Set the following options: 53 | 54 | * Access: Private. This means anyone with the link can view the results. You can make this password protected by selecting "Restricted." You can then share passwords with hosts, instructors, and anyone else who may need access. 55 | * Page Title: This will pre-populate with a default value. You can change this as you wish. 56 | * Page Description: Add any other information about the workshop. 57 | * Include: Be sure to check off Open-Ended Responses and Data Trends. Individual Responses should **not** be checked. 58 | * Branding: Leave this unchecked. 59 | 60 | Click `Get link`. 61 | 62 | ![Survey results share data](images/surveymonkey_sharedata.png) 63 | 64 | You will be given a link to the survey results. Click save. 65 | 66 | ![Survey results get link](images/surveymonkey_getlink.png) 67 | 68 | Your browser will now redirect to this link. The link can be shared with hosts and instructors. 69 | 70 | This link will also be included in the Shared Data List, at the bottom of the left side of the screen. 71 | 72 | ![Survey shared data list](images/surveymonkey_shareddatalist.png) 73 | 74 | It will be given a sequential number. Click on the `...` to rename it to the workshop ID. This list is monitored regularly, and anything with the sequential number will be deleted. 75 | 76 | 77 | #### Sharing Survey Results: Raw Data 78 | 79 | If requested, raw data as CSV can be exported and shared with hosts and instructors. 80 | 81 | From the internal view of the survey results click the green `Save as` button at the top right. This time, click `Export file`. 82 | 83 | ![Survey results save as](images/surveymonkey_saveas.png) 84 | 85 | From here you will have various options about what data to export and what format to export it in. Make your selections and name the filename with the workshop ID. 86 | 87 | This will then show up in the "Exports" list on the left side of the screen. Click the "..." to download data to share with hosts and instructors. 88 | 89 | ![Survey results export](images/surveymonkey_export.png) 90 | 91 | #### Modifying Survey Responses 92 | 93 | 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. 94 | 95 | From the survey page, select `Analyse Results`. 96 | 97 | ![Survey analyse results](images/surveymonkey_analyzeresults.png) 98 | 99 | 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'. 100 | 101 | ![Survey individual responses](images/surveymonkey_individualresponses.png) 102 | 103 | Use the arrow icons to navigate to the response that needs editing, and click "edit". 104 | 105 | ![Survey select response](images/surveymonkey_selectresponse.png) 106 | 107 | The survey will open in a new window. Navigate to the workshop id question without editing any other responses. 108 | 109 | ![Survey find incorrect response](images/surveymonkey_incorrectslug.png) 110 | 111 | Type in the correct workshop id and click next. 112 | 113 | ![Survey add correct response](images/surveymonkey_correctslug.png) 114 | 115 | Close this window so no other responses are affected. This should now show up modified and correct in the Survey Monkey responses. 116 | 117 | Continue this for any incorrect response. 118 | 119 | Running a report as described above should now give you correct responses. 120 | 121 | 122 | -------------------------------------------------------------------------------- /img/.DS_Store: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/img/.DS_Store -------------------------------------------------------------------------------- /img/comms-images/EOCY-fundraising-letter-pullquote.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/img/comms-images/EOCY-fundraising-letter-pullquote.jpg -------------------------------------------------------------------------------- /img/comms-images/comms-plan-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/img/comms-images/comms-plan-1.png -------------------------------------------------------------------------------- /img/comms-images/comms-plan-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/img/comms-images/comms-plan-2.png -------------------------------------------------------------------------------- /img/comms-images/comms-tone-scale.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/img/comms-images/comms-tone-scale.png -------------------------------------------------------------------------------- /img/comms-images/fundraising-video-executive-director-long-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/img/comms-images/fundraising-video-executive-director-long-form.png -------------------------------------------------------------------------------- /img/comms-images/fundraising-video-title-card.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/img/comms-images/fundraising-video-title-card.jpg -------------------------------------------------------------------------------- /img/logo.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/img/logo.ico -------------------------------------------------------------------------------- /img/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/img/logo.png -------------------------------------------------------------------------------- /index.rst: -------------------------------------------------------------------------------- 1 | The Carpentries Handbook 2 | ------------------------ 3 | 4 | 5 | `The Carpentries `_ teaches foundational coding, and data science skills to researchers worldwide. `Software Carpentry `_, `Data Carpentry `_, and `Library Carpentry `_ workshops are based on our lessons. Workshop hosts, Instructors, and learners must be prepared to follow our `Code of Conduct `_. 6 | 7 | 8 | .. toctree:: 9 | :maxdepth: 2 10 | :glob: 11 | 12 | topic_folders/policies/index_coc.rst 13 | 14 | Below are general resources of use to various segments of The Carpentries community. 15 | 16 | 17 | .. toctree:: 18 | :maxdepth: 2 19 | :glob: 20 | :caption: General Resources 21 | 22 | topic_folders/assessment/index.rst 23 | topic_folders/communications/index.rst 24 | topic_folders/for_instructors/index.rst 25 | topic_folders/fundraising/index.rst 26 | topic_folders/governance/index.rst 27 | topic_folders/instructor_development/index.rst 28 | topic_folders/instructor_training/index.rst 29 | topic_folders/lesson_development/index.rst 30 | topic_folders/maintainers/index.rst 31 | topic_folders/policies/index.rst 32 | topic_folders/regional_communities/index.rst 33 | topic_folders/hosts_instructors/index.rst 34 | topic_folders/workshop_administration/index.rst 35 | 36 | .. toctree:: 37 | :maxdepth: 2 38 | :caption: About 39 | :glob: 40 | 41 | readme 42 | LICENSE 43 | 44 | -------------------------------------------------------------------------------- /make.bat: -------------------------------------------------------------------------------- 1 | @ECHO OFF 2 | 3 | pushd %~dp0 4 | 5 | REM Command file for Sphinx documentation 6 | 7 | if "%SPHINXBUILD%" == "" ( 8 | set SPHINXBUILD=sphinx-build 9 | ) 10 | set SOURCEDIR=. 11 | set BUILDDIR=_build 12 | set SPHINXPROJ=CarpentriesUsersGuide 13 | 14 | if "%1" == "" goto help 15 | 16 | %SPHINXBUILD% >NUL 2>NUL 17 | if errorlevel 9009 ( 18 | echo. 19 | echo.The 'sphinx-build' command was not found. Make sure you have Sphinx 20 | echo.installed, then set the SPHINXBUILD environment variable to point 21 | echo.to the full path of the 'sphinx-build' executable. Alternatively you 22 | echo.may add the Sphinx directory to PATH. 23 | echo. 24 | echo.If you don't have Sphinx installed, grab it from 25 | echo.http://sphinx-doc.org/ 26 | exit /b 1 27 | ) 28 | 29 | %SPHINXBUILD% -M %1 %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% 30 | goto end 31 | 32 | :help 33 | %SPHINXBUILD% -M help %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% 34 | 35 | :end 36 | popd 37 | -------------------------------------------------------------------------------- /readme.md: -------------------------------------------------------------------------------- 1 | ### Why was this handbook created? 2 | 3 | Historically, information and resources related to [The Carpentries](https://carpentries.org/) have been spread across various websites, Google docs, GitHub repos, and more. The handbook is a one-stop shop that consolidates information on running a workshop, developing or maintaining lessons, participating in an instructor training event, and more! 4 | 5 | Many community members have contributed to this handbook, and we welcome feedback on this Handbook. Feel free to submit issues or pull requests to [this GitHub repo](https://github.com/carpentries/docs.carpentries.org/) to improve this community resource. 6 | 7 | 8 | ### Building this site 9 | 10 | This site is built using the [Sphinx](http://www.sphinx-doc.org/en/stable/) documentation generator (a Python tool) and the [Read the Docs theme](https://github.com/rtfd/sphinx_rtd_theme) for the style. (Not to be confused with readthedocs.io - the site is _not_ hosted at readthedocs.io!) 11 | 12 | For more information about using Sphinx, see the [Getting Started guide (sphinx-doc.org)](http://www.sphinx-doc.org/en/stable/usage/quickstart.html) or the [Quick Start (readthedocs.io)](https://docs.readthedocs.io/en/latest/intro/getting-started-with-sphinx.html#quick-start) for an explanation of how to use Sphinx. 13 | 14 | #### Required dependencies 15 | 16 | To install the required dependencies (Sphinx and the ReadTheDocs Sphinx theme), execute the following command from the repository directory to install all Python dependencies: 17 | 18 | ``` 19 | pip install -r requirements.txt 20 | ``` 21 | 22 | After installing the dependencies, you can build the site locally by executing the following command from the repository: 23 | 24 | ``` 25 | $ make html 26 | ``` 27 | 28 | Open the file `_build/html/index.html` to preview the site locally. Python offers a quick way to run a web server to serve local files. Run the following: 29 | 30 | ``` 31 | $ cd _build/html 32 | 33 | # Python 2: (Deprecated; not recommended) 34 | $ python2 -m SimpleHTTPServer 35 | 36 | # Python 3: 37 | $ python3 -m http.server 38 | ``` 39 | 40 | In both cases, a local web server will be run on port `8000`, so navigate to in your browser to view the site locally. 41 | 42 | You can make changes to the contents of the repository, and re-run `make html`, to update the website contents. If you are having problems with the site not refreshing, you can delete the contents of the `_build` directory (which are automatically generated) with `rm -fr _build/*`. 43 | 44 | If new files or folders are added to the Handbook, `index.rst` will need to be updated for those to be included in the final site by Sphinx. 45 | 46 | #### Site structure 47 | 48 | The root level `index.rst` generates the main categories and the sidebar navigation. Each sub-section is a folder in the `topic_folders` directory. Each folder within the `topic_folders` directory has its own `index.rst` file. These then expand into the subcategories in each directory. 49 | 50 | Within each folder's `index.rst` file, the section heading is defined by a string of `=` beneath it. Subheadings can be defined using `###` in each markdown file or by a heading with `-` under it in the `index.rst` file. 51 | 52 | ##### Formatting Hyperlinks 53 | 54 | In markdown documents, links can be formatted in standard markdown, with the text in square brackets and the hyperlink in parentheses: 55 | 56 | ``` 57 | [text](hyperlink) 58 | ``` 59 | 60 | For the `index.rst` files, links must be formatted as follows. Note the text is followed by the hyperlink in pointy brackets, everything is wrapped in backticks, and then followed by an underscore. 61 | 62 | ``` 63 | `text`_ 64 | 65 | ``` 66 | 67 | **Links to external markdown documents** 68 | 69 | Something in this template causes `.md` extensions to get stripped, breaking links to things like markdown documents in a GitHub repo. This can be fixed by adding an anchor tag (`#`) to the end of the url. For example, `https://github.com/carpentries/docs.carpentries.org/blob/topic_folders/file.md` would become `https://github.com/carpentries/docs.carpentries.org/blob/topic_folders/file.md#`. 70 | 71 | 72 | #### Additional information 73 | 74 | This site is built from the main branch of [this repo (carpentries/docs.carpentries.org)](https://github.com/carpentries/docs.carpentries.org/). Changes can be previewed live here: . Changes to the actual site can take up to a day to go live once changes have been pushed to GitHub, since the contents of the site are behind a CDN (Content Distribution Network) that caches content. 75 | 76 | If you are making experimental changes to content please be sure to do so in a non-main, non-live branch. When your changes are complete and ready to be pushed to the live site, open a pull request in [carpentries/docs.carpentries.org](https://github.com/carpentries/docs.carpentries.org). 77 | 78 | Draft content can be added to the [drafts folder of the carpentries/userguides repo](https://github.com/carpentries/usersguides/tree/main/drafts) (in the main branch) without breaking anything. Draft content is not built to the live site and these files may contain inaccurate or out of date information. 79 | -------------------------------------------------------------------------------- /requirements.txt: -------------------------------------------------------------------------------- 1 | Sphinx>=4.3.0 2 | sphinx_rtd_theme>=1.0 3 | sphinx-notfound-page==0.3 4 | myst-parser>=0.17.2 5 | -------------------------------------------------------------------------------- /topic_folders/assessment/assessment-network.md: -------------------------------------------------------------------------------- 1 | ### Assessment Network 2 | 3 | #### About 4 | The Assessment Network was established in October 2016 as a space for those working on assessment within the open source/research computing space to collaborate and share resources. 5 | 6 | #### What We Do 7 | The Assessment Network meets quarterly to discuss best-practices and projects around assessing outcomes in scientific computing. For past meeting information, check out the [minutes](https://github.com/carpentries/assessment/tree/main/assessment-network/minutes) in the Assessment Network [repo](https://github.com/carpentries/assessment/tree/main/assessment-network). 8 | 9 | #### Get Involved 10 | To join the Assessment Network, email Kari Jordan at [kariljordan@carpentries.org](mailto:kariljordan@carpentries.org). 11 | -------------------------------------------------------------------------------- /topic_folders/assessment/assessment.md: -------------------------------------------------------------------------------- 1 | ## Learner Assessment 2 | 3 | Assessment plays a key role in ensuring the success, longevity, and evolution of The Carpentries workshops. The primary goal of our assessment efforts is to evaluate the impact we are having teaching data skills throughout our global community. Our assessment efforts are meant to guide the development, implementation, and instruction of our workshops. We are committed to providing directed feedback to our community regarding our assessment targets and using information collected from assessment to improve how we teach data skills and build learning communities. 4 | 5 | Our assessment tools will cover content knowledge, self-efficacy, and metacognitive strategies. Additionally, evaluation will occur at the end of each workshop and 6 months after a workshop with data releases published bi-annually, and an annual review of our impact will be published on our [website](https://carpentries.org/assessment/). Source code, data, and additional information are also available in this [GitHub repository](https://github.com/carpentries/assessment). 6 | 7 | We are committed to supporting our learners, accommodating their differences, and encouraging them to grow individually and become part of our community of practice. We also encourage them to understand, reflect upon, and monitor their own learning. 8 | 9 | We assess our learners by measuring changes in their attitudes, motivation, and self-efficacy. Our pre-workshop survey includes questions about learners' attitudes about the content covered in their workshop, and their objectives (i.e. what they hope to learn). 10 | 11 | We also ask questions to measure learners' mindset (growth vs. fixed). Our objective is to measure their confidence in their ability to learn, not necessarily execute specific tasks. 12 | 13 | Additionally, we measure learners' perception of skill growth and whether or not they plan to recommend our workshops to colleagues. 14 | 15 | Our pre- and post-workshop surveys can be previewed below. 16 | 17 | 18 |
19 |

Important

20 |

21 | Please note that the forms below are for demonstration only. The answers typed 22 | here will not be taken into account by our assessment efforts. If you are 23 | looking for the pre- or post-workshop surveys for a workshop you are attending, 24 | please use the links provided on your workshop website. If you are unsure where 25 | to find them, please send an email at 26 | team@carpentries.org. 27 |

28 |
29 | 30 | 31 | ### Pre-workshop survey 32 | 33 |
34 | 35 | 36 | 37 | 38 | 39 | ### Post-workshop survey 40 | 41 |
42 | 43 | 44 | 45 | 46 | ## Programmatic Assessment 47 | 48 | In May 2018, we began regularly publishing programmatic assessment reports. These reports provide overviews of our workshop and instructor activities. More information including published reports can be found on [our website](https://carpentries.org/assessment/). 49 | -------------------------------------------------------------------------------- /topic_folders/assessment/index.rst: -------------------------------------------------------------------------------- 1 | Assessment 2 | ======================= 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | * 9 | -------------------------------------------------------------------------------- /topic_folders/communications/guides/adhere-style-guide.md: -------------------------------------------------------------------------------- 1 | ## Adhering to The Carpentries Style Guide 2 | 3 | In contributing to The Carpentries website, handbook and other resources, remember to refer to [The Carpentries Style Guide](https://docs.carpentries.org/topic_folders/communications/resources/style-guide.html) and format your contributions accordingly. 4 | 5 | For example, headings should use title casing, and tools like the [Title Case Converter](https://titlecaseconverter.com/) serve as a definitive guide to formatting for Title Casing, complete with reasons for or against capitalising certain words. 6 | 7 | Another meaningful example is spellings. Because The Carpentries is a global community-led organisation, content standardisation is important. Our Style Guide currently recommends the use of British English in all our resources across the board. More about this in the language section of our Style Guide. 8 | 9 | ## Formatting Hyperlinks 10 | 11 | Hyperlinks on the websites for The Carpentries and its lesson programs should be formatted using [Jekyll's link formatting syntax](https://jekyllrb.com/docs/liquid/tags/#links). This includes: 12 | 13 | - using `{% link %}` for pages. For example, `[Become a member organisation]({% link pages/membership.md %})` 14 | - using `{% post %}` for blog posts. For example `[blog post]({% post _posts/2021/05/2021-05-01-blogging-from-the-future.md %})` 15 | - not using relative paths 16 | - not including `https://carpentries.org/` (or the respective website) in the URLs. The `baseurl` should be defined in the website's `_config` file. 17 | - using `{{ urlimg }}` for images. For example, ``. The `urlimg` should be defined in the website's `_config` file. 18 | - using `{{ filesurl }}` for files. For example, `[Read the report]({{ site.filesurl }}/docs/2021/05/future.pdf)` 19 | 20 | 21 | **How can you help?** 22 | 23 | As you read through the resources we make available on the [Data Carpentry](https://datacarpentry.org), [Library Carpentry](https://librarycarpentry.org/), [Software Carpentry](https://software-carpentry.org/) and [The Carpentries](https://carpentries.org/) websites as well as this Handbook and other resources, you can go to the appropriate repository and either: 24 | - open an issue and report instances of these anomalies (low time requirement), or 25 | 26 | - submit a Pull Request with edits that help standardise spellings, headings, etc (Moderate time requirement ). 27 | 28 | We are also keen on continued resource provenance, so please report any broken links as and when you come by them. [Internet Archive's Way Back Machine](https://archive.org/web/) is a powerful tool to help you view resources in broken links, and potentially find alternative/updated links to the same resources. 29 | -------------------------------------------------------------------------------- /topic_folders/communications/guides/community_events.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ### Signing up to Host or co-Host a Community Discussion or Teaching Demo 4 | 5 | The Carpentries uses [Calendly](https://calendly.com/thecarpentries) to manage scheduling of Community Discussion sessions and Teaching Demos. Four times a year, Discussion Hosts and Instructor Trainers will be asked to slot in their availability. Additionally, custom forms are used for Trainers to schedule Instructor Training events. 6 | 7 | ![Calendly Demo](./images/calendly.gif) 8 | 9 | 10 | For the period |1 Jan - 31 Mar
(Q1) |1 Apr - 30 Jun
(Q2) |1 Jul - 30 Sep
(Q3) |1 Oct - 31 Dec
(Q4)| 11 | -------------------------|--------------------|---------------------|---------------------|--------------------| 12 | Signups open on |15 Nov |15 Feb |15 May |15 Aug | 13 | Responses
due by |30 Nov |28 Feb |31 May |31 Aug | 14 | Calendar
published by |7 Dec |7 Mar |7 Jun |7 Sept | 15 | 16 | Once Discussion Hosts and Trainers have scheduled themselves in for a Community Discussion session or Teaching Demo via Calendly, The Carpentries Core Team will ensure that these events appear on the relevant Etherpads ([Community Discussions](https://pad.carpentries.org/community-discussions) or [Teaching Demos](https://pad.carpentries.org/teaching-demos)) and on the [Community Calendar](https://carpentries.org/community/#community-events). 17 | 18 | This system aims to build these sessions around the Host or Trainer availability. The community of Hosts and Trainers should represent a good cross-section of the general Carpentries community, and should offer the broader community a better option of sessions to attend. 19 | 20 | #### Event Cancellations 21 | 22 | We recognise that even after scheduling their own events, Hosts or Trainers may have conflicts and may need to cancel a scheduled event. If this happens, please contact community@carpentries.org for Discussion Sessions or instructor.training@carpentries.org for Teaching Demos and Instructor Training as soon as possible so a Core Team member can ensure another Host is able to cover this event. -------------------------------------------------------------------------------- /topic_folders/communications/guides/images/blog_post-new_branch.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/guides/images/blog_post-new_branch.png -------------------------------------------------------------------------------- /topic_folders/communications/guides/images/blog_post-new_branch_new_folder.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/guides/images/blog_post-new_branch_new_folder.png -------------------------------------------------------------------------------- /topic_folders/communications/guides/images/calendly.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/guides/images/calendly.gif -------------------------------------------------------------------------------- /topic_folders/communications/guides/index.rst: -------------------------------------------------------------------------------- 1 | How-to guides 2 | ============= 3 | 4 | 5 | .. toctree:: 6 | :maxdepth: 1 7 | :titlesonly: 8 | :glob: 9 | 10 | 11 | adhere-style-guide.md 12 | submit_blog_post.md 13 | select-blog-tags.md 14 | submit-news-item.md 15 | share-opportunities.md 16 | community_events.md 17 | -------------------------------------------------------------------------------- /topic_folders/communications/guides/share-opportunities.md: -------------------------------------------------------------------------------- 1 | ## Sharing Job Postings and other Community Opportunities 2 | 3 | The Carpentries has three main mechanisms by which to share job postings and other community opportunities: One is within our newsletter, [Carpentries Clippings](https://carpentries.org/newsletter/) the second is our [#jobs channel on Slack](https://carpentries.slack.com/) and the third is the [opportunities mailing list on Topicbox](https://carpentries.topicbox.com/groups/opportunities). 4 | 5 | ### Criteria for Posting 6 | In order to ensure that postings for opportunities featured on Carpentries channels are applicable and of relevance to our community, The Carpentries Core Team has a list of criteria that a posting must meet in order to be shared. If the posting does not meet the criteria, then the post will be removed or modified after discussion with the poster. However, we reserve the right to remove a posting without notice, in particular, if we believe that the opportunity has been submitted automatically (i.e., by a bot). 7 | 8 | This criteria was developed over 2020 by The Carpentries Core Team in order to ensure we are adequately screening opportunities. 9 | 10 | #### Here are the criteria we consider when deciding whether to feature a job posting: 11 | - **Organisational Alignment with The Carpentries** 12 | - Does the organisation which is hiring have similar goals to The Carpentries? 13 | - Do our goals directly support each other? 14 | - **Carpentries Code of Conduct** 15 | - Does the organisation abide by our Code of Conduct and/or have their own published Code of Conduct that has the same priorities as The Carpentries' 16 | - Note: If The Carpentries publishes a posting from an organisation and is then made aware by our community of incompatibility with our Code of Conduct, we will remove the posting 17 | - **Quality of The Posting** 18 | - Does the posting bear relevance to our community? 19 | - Are the skills and experiences sought by the posting organisation compatible with the skills our community has or seeks to gain? 20 | - Does the posting mention The Carpentries by name? 21 | - **Prior Knowledge/work with the Posting Organisation** 22 | - Often, The Carpentries posts job opportunities from affiliate or member organisations. 23 | - If we have prior interactions and knowledge of the organisation, this is a strong indicator of a valuable opportunity post that our community will appreciate. 24 | 25 | Note: These criteria are not strictly quantitative and rely on the judgment of the core team. 26 | 27 | ### Sharing Postings on Carpentries Clippings 28 | Carpentries Clippings is a biweekly newsletter to members of our community featuring community news, program updates of note, and opportunities relevant to the wider Carpentries community. 29 | 30 | In order to share a job posting that we will feature in Carpentries Clippings, please follow the [Sharing Relevant Announcements](https://docs.carpentries.org/topic_folders/communications/guides/submit-news-item.html) guide. 31 | 32 | ### Sharing Job Postings and other Community Opportunities on Slack 33 | Once you have read the criteria above and joined the #jobs channel on The Carpentries Slack, you can share relevant announcements to the group. Please include the following information when posting: 34 | 35 | - Job Title 36 | - Organisation 37 | - Location (if applicable) 38 | - Posting/Application Deadline 39 | - Link for more information and to apply 40 | 41 | Note: Please do not request that applicants or those interested in the opportunity contact you by DM. 42 | 43 | If a post does not contain the above or does not meet the criteria outlined earlier, then a member of The Carpentries Core Team will reach out to you via Slack DM to address the concerns and suggest modifications. 44 | 45 | In cases where this process is not able to be carried out effectively (such as if the posting is by a spam bot), the Core Team will remove the posting, and with repeated instances of this, will potentially remove the account from the #jobs channel. 46 | 47 | ### Sharing Job Postings and other Community Opportunities on the "opportunities" Mailing List on Topicbox 48 | Posting opportunities to the ["opportunities" mailing list](https://carpentries.topicbox.com/groups/opportunities) requires one to be a member of the group. 49 | 50 | To join the group, navigate to the mailing list and click "Join The Conversation" and enter the required information. Once you are a member of the group, please include the following information when sharing a posting. 51 | 52 | - In the title field please include the opportunity title and organisation 53 | - In the body of the message, include other relevant information about the opportunity including deadlines, links to apply and learn more, location (if applicable) 54 | 55 | Once you have submitted the posting, moderators of the mailing list will approve the posting or reach out to you if the posting does not meet the criteria to address the concerns and suggest modifications. 56 | -------------------------------------------------------------------------------- /topic_folders/communications/guides/submit-news-item.md: -------------------------------------------------------------------------------- 1 | ### Sharing Relevant Announcements 2 | 3 | The Carpentries have a number of mechanisms for pushing out news. These include: 4 | 5 | - Our newsletter, [*Carpentry Clippings*](https://carpentries.org/newsletter/), which appears every two weeks. 6 | - Our [Facebook page](https://www.facebook.com/carpentries), which community members are welcome to follow and comment on. 7 | - Twitter feeds for [The Carpentries](https://twitter.com/thecarpentries), [Software Carpentry](https://twitter.com/swcarpentry), [Data Carpentry](https://twitter.com/datacarpentry), and [Library Carpentry](https://twitter.com/libcarpentry). 8 | 9 | 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](mailto:team@carpentries.org) with *For Newsletter*, *For Twitter*, or *For Facebook* as the subject line. 10 | -------------------------------------------------------------------------------- /topic_folders/communications/guides/submit_blog_post.md: -------------------------------------------------------------------------------- 1 | ## Collaborative Blog Post Writing 2 | 3 | The Carpentries welcomes blog posts from our community members including workshop host sites, instructors, learners, and more. Are you interested in publishing a post on The Carpentries blog? 4 | 5 | ### Sharing blog post ideas 6 | 7 | - Join The Carpentries Slack and share your blog post idea in the #blog-post-ideas channel to start discussion and invite other community members to collaborate with you (preferred) 8 | 9 | - Email community[at]carpentries[dot]org with your idea and one of the team will facilitate amplification of the idea in the community so others can reach out and collaborate with you (option) 10 | 11 | 12 | -------------------------------------------------------------------------------- /topic_folders/communications/index.rst: -------------------------------------------------------------------------------- 1 | Communications 2 | ================ 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | 9 | tools/index.rst 10 | resources/index.rst 11 | guides/index.rst 12 | 13 | 14 | 15 | 16 | 17 | -------------------------------------------------------------------------------- /topic_folders/communications/resources/brand_identity.md: -------------------------------------------------------------------------------- 1 | # Brand Identity 2 | 3 | ## Carpentries Brand Colours 4 | 5 | ### Main Brand Colours 6 | 7 |

★Black: #383838 or rgb(56, 56, 56).

8 | 9 |

★Midnight: #001483 or rgb(0, 20, 131,).

10 | 11 |

★Fire: #FF4955 or rgb(255, 73, 85).

12 | 13 |
14 |

★Golden: #FFC700 or rgb(255, 199, 0).

15 |

★Buttercup: #FFF7F1 or rgb(255, 247, 241).

16 |
17 | 18 | ### Lesson Program Colours and Shades 19 | 20 |

★General Carpentries: #081457 or rgb(8, 20, 87).

21 | 22 |
23 |

★General Carpentries (Light): #E3E6FC or rgb(227, 230, 252).

24 |
25 | 26 |

★Data Carpentries: #205959 or rgb(32, 89, 89).

27 | 28 |
29 |

★Data Carpentries (Light): #40AEAD or rgb(64, 174, 173).

30 |
31 | 32 |

★Software Carpentries: #201434 or rgb(32, 20, 52).

33 | 34 |
35 |

★Software Carpentries (Light): #D2BDF2 or rgb(210, 189, 242).

36 |
37 | 38 |

★Library Carpentries: #A4050E or rgb(164, 5, 14).

39 | 40 |
41 |

★Library Carpentries (Light): #F99697 or rgb(249, 150, 151).

42 |
43 | 44 | ### Secondary/Supplementary Colours and Shades 45 | 46 |

★Lake: #0044d7 or rgb(0, 68, 215).

47 | 48 |
49 |

★Pond: #719eff or rgb(113, 158, 255).

50 | 51 |

★Sky: #E6F1FF or rgb(230, 241, 255).

52 | 53 |

★Dew: #F5F8FF or rgb(245, 248, 255).

54 | 55 |

★Fog: #E6EAF0 or rgb(230, 234, 240).

56 | 57 |

★Mist: #E6EEF8 or rgb(230, 238, 248).

58 | 59 |

★Sunrise: #FC757E or rgb(252, 117, 126).

60 | 61 |

★Dawn: #FFD6D8 or rgb(255, 214, 216).

62 | 63 |

★Sunshine: #FFE7A8 or rgb(255, 231, 168).

64 |
65 | 66 | 67 | ## Carpentries Fonts 68 | 69 | The font used in the headers on the website is [Lato](https://fonts.google.com/specimen/Lato). 70 | The font used in the body of the website is [Roboto](https://fonts.google.com/specimen/Roboto). 71 | -------------------------------------------------------------------------------- /topic_folders/communications/resources/commons.md: -------------------------------------------------------------------------------- 1 | ### Carpentries Commons 2 | 3 | [The Carpentries Commons](https://github.com/carpentries/commons) GitHub repository is a place for open sharing of reusable material, such as text for grants, wording for job or tenure applications, slide decks for conferences, workshop descriptions, promotional copy, and so on. 4 | 5 | Carpentries Core Team will have write access to add, edit and upload material here. Other members of our community will need to fork the repository and submit pull requests. -------------------------------------------------------------------------------- /topic_folders/communications/resources/index.rst: -------------------------------------------------------------------------------- 1 | Resources 2 | ======================= 3 | 4 | 5 | .. toctree:: 6 | :maxdepth: 1 7 | :titlesonly: 8 | :glob: 9 | 10 | 11 | style-guide.md 12 | brand_identity.md 13 | commons.md 14 | logos.md 15 | presentations.md 16 | comms-strategy.md 17 | comms-implementation-plan.md 18 | -------------------------------------------------------------------------------- /topic_folders/communications/resources/logos.md: -------------------------------------------------------------------------------- 1 | ### Logos 2 | 3 | #### Carpentries Logo Usage Policy 4 | 5 | ##### Introduction 6 | The goal of this document is to outline policy around the usage and modification of The Carpentries trademarks. 7 | 8 | The names “The Carpentries”, “Software Carpentry”, and “Data Carpentry,” and their associated logos are all trademarked. 9 | This policy is for any cases in which you use the Carpentries name/logo. 10 | 11 | ##### Uses that don’t require prior approval 12 | Stating that a workshop is a Carpentries workshop, or that a workshop is based on Carpentries material, is always allowed. 13 | 14 | It is acceptable to use the trademark in acknowledging or crediting The Carpentries in journal articles, conference presentations, keynotes, grant applications, and the like. In cases of acknowledgement or attribution, you may use the term “The Carpentries” or the unaltered logos to indicate this, without our prior approval. 15 | 16 | ##### Uses that require approval from The Carpentries 17 | Any usage of a derived/modified version of The Carpentries logo or wordmark must have prior approval. This includes commercial and non-commercial uses. 18 | 19 | The Carpentries has a number of local and domain-specific communities, and we encourage the development of derived/modified logos that indicate the group’s location or focus. To support the development of domain and region-specific logos, we have outlined the approved modifications to The Carpentries logo and wordmark below. 20 | 21 | The colours of the “wrench mark” can be modified to what is appropriate for your domain/region, but no added shapes or distortions (including orientation) are allowed. The domain/region name for your group should be added beneath The Carpentries in Carpentries red (Hex: FF4955) 22 | 23 | If you are a local Carpentries member and wish to modify the logo according to these guidelines, please email [community@carpentries.org](mailto:carpentries.org) and we will either approve your modification or assist you in creating the modified version. 24 | 25 | Other modifications of the logo that leave the name and logo intact are allowed under this policy with approval from The Carpentries Community Development Team. 26 | 27 | Uses of The Carpentries name or logo in conjunction or combination with another group’s name or logo (EX: using the wrenchmark with the colours of another organisation, or adding components of another organisation’s logo to The Carpentries) are prohibited. 28 | 29 | If you or your group is currently using The Carpentries name or logo in this manner, please email [community@carpentries.org](mailto:community@carpentries.org), and we will work with you to find an alternative. 30 | 31 | License for this Policy 32 | This policy has been adapted in part from the Python Software Foundation’s [Trademark Use Policy](https://www.python.org/psf/trademarks/). Interested parties may adapt this policy document freely under the [Creative Commons CC0 license](https://creativecommons.org/publicdomain/zero/1.0/). 33 | 34 | #### Links to Logo Files 35 | 36 | * [The Carpentries](https://github.com/carpentries/logo) 37 | * [Data Carpentry](https://github.com/datacarpentry/logos) 38 | * [Library Carpentry](https://github.com/LibraryCarpentry/lc-styleguide/tree/main/logo) 39 | * [Software Carpentry](https://github.com/swcarpentry/communications/tree/main/misc/logo) 40 | 41 | #### Virtual Backgrounds 42 | Virtual backgrounds featuring the logos of The Carpentries lesson programs are available for download and use in the [Carpentries Commons GitHub repository](https://github.com/carpentries/commons/tree/main/virtual-backgrounds). 43 | -------------------------------------------------------------------------------- /topic_folders/communications/resources/presentations.md: -------------------------------------------------------------------------------- 1 | ### Presentations 2 | 3 | It is great for community members to give presentations on The Carpentries! 4 | Include your work with The Carpentries in a presentation, or you are more than welcome 5 | to give talks or discuss the organisation in general. 6 | 7 | There are some general Google slide decks as well as ones more tailored to 8 | particular topics or events. The General slide deck is CC0, so you are welcome to use it how you wish. Please just keep attributions on individual figures or photos if they are there. 9 | 10 | Other slide decks are CC-BY. 11 | 12 | Please use the following template when you are presenting on a topic related to The Carpentries. The template can be modified and adapted as necessary. However, please ensure that you are adhering to the general visual identity including colors, blocks, and fonts. 13 | [Carpentries Presentation Template](https://docs.google.com/presentation/d/1y0lvjLwDe34qe7gGiZiBrVLWwVuA6haw9eNDjNqxMKM/edit?usp=sharing) 14 | 15 | [General Carpentries slide deck CC0](https://docs.google.com/presentation/d/1fYTlCSQAkVPSalyFAcFxwqRIQ2Ez7YvQDIwOExyg5ts/edit?usp=sharing) 16 | 17 | [Google drive with slide decks](https://drive.google.com/drive/folders/12D0D9F2GJX4TIwzWkSHYdaI0VFdYYCul) 18 | 19 | [List of past Data Carpentry presentations on Zotero](https://www.zotero.org/groups/597593/datacarpentry/items/collectionKey/WT38F37Q) including abstracts and links to slide decks. 20 | 21 | Updates to slide decks or contributing your slide decks is encouraged and welcomed too! 22 | -------------------------------------------------------------------------------- /topic_folders/communications/tools/codimd.md: -------------------------------------------------------------------------------- 1 | ### CodiMD 2 | 3 | #### General Usage 4 | 5 | The Carpentries also offers [CodiMD](https://codimd.carpentries.org/) as another collaborative note taking platform. CodiMD recognises [Markdown](https://www.markdownguide.org/cheat-sheet/) syntax, 6 | allowing users to utilise simple markup to format the content they add to the shared document. 7 | 8 | The CodiMD interface provides three modes: 9 | 10 | * _Edit_: an editor-only interface, which fills the browser window with a space for writing text. 11 | * _Both_: a half-and-half interface, filling the left half of the window with the editor interface, 12 | and the right half with the (uneditable) viewing interface. 13 | * _View_: a read-only, formatted interface, 14 | which fills the browser window with the rendered version of the notes entered in the Edit view. 15 | Any Markdown markup used in the Edit view will be applied in the View interface, 16 | appearing as formatted text (headings, bold, italics, links, etc) and images. 17 | 18 | These modes can be selected with buttons to the top-left of the interface. 19 | 20 | ![The viewing mode buttons for a CodiMD document](images/codimd_mode_buttons.png) 21 | 22 | A new CodiMD document can be created by appending a descriptive name to the url `https://codimd.carpentries.org/`, 23 | such as `https://codimd.carpentries.org/committeename`, 24 | or by visiting and clicking the "+ New guest note" button. 25 | 26 | Documents are synchronised as you type, so that everyone viewing this page sees the same text. 27 | This allows everyone to collaborate on documents. 28 | Contributions from different users are underlined in different colours. 29 | Hovering the cursor over content will display the name (or guest identifier) of the person who wrote it, 30 | and the current location of different users' cursors is also displayed in Edit mode. 31 | 32 | See for a full list of features available on CodiMD. 33 | 34 | Use of this service is restricted to members of The Carpentries community; 35 | this is not for general purpose use (for that, try [HackMD](https://hackmd.io/)). 36 | 37 | Users are expected to follow our [code of conduct]( https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html). 38 | All content is publicly available under the [Creative Commons Attribution License](https://creativecommons.org/licenses/by/4.0/). 39 | 40 | 41 | #### Document Access Levels & Accounts 42 | 43 | Account creation and login is not required to create and edit CodiMD documents. 44 | 45 | To register an account on the platform: 46 | 47 | 1. [Visit the platform homepage](https://codimd.carpentries.org/) and 48 | click the "Sign In" button near the top-right of the browser window. 49 | 2. When the pop-up appears, prompting the user to enter an email address and password, 50 | type in the email address and password you want to use for your account. 51 | 3. Click the "Register" button. 52 | 53 | Account holders gain access to two features: 54 | 55 | 1. Ability to restrict access to documents the user owns: 56 | in View mode the person who created a document can select from several options 57 | to control who else is able to view and edit its content. 58 | Look for a dropdown menu with blue icon and text 59 | near top-left of a document's content to find these options. 60 | Some of these access levels also allow editing and viewing rights 61 | only to registered account holders. 62 | 2. A history of documents created and visited by the user, 63 | accessible via the History tab of the landing page. 64 | The documents listed in this history can be searched, sorted, filtered, 65 | and organised into folders. 66 | 67 | 68 | #### Troubleshooting 69 | 70 | If you encounter issues with the CodiMD platform, 71 | please contact us at team@carpentries.org and a team member will help you troubleshoot. 72 | 73 | 74 | #### See Also 75 | 76 | [Etherpad](https://docs.carpentries.org/topic_folders/communications/tools/etherpads.html) is another collaborative note taking platform used by the community members. 77 | -------------------------------------------------------------------------------- /topic_folders/communications/tools/etherpads.md: -------------------------------------------------------------------------------- 1 | ### Etherpads 2 | 3 | #### General Usage 4 | 5 | The Carpentries offers the use of our [Etherpads](https://pad.carpentries.org/) as collaborative note taking tool during workshops, training events, and other Carpentries related events. A list of our most commonly used pads and other resources can be found on our [pad-of-pads](https://pad.carpentries.org/pad-of-pads). This list is manually created and typically only includes pads of interest to the general community. It will not include pads specific to single events or groups. 6 | 7 | A new Etherpad can be created by appending a descriptive name to the url `https://pad.carpentries.org/`, such as `https://pad.carpentries.org/committeename`. 8 | 9 | Pads are synchronised as you type, so that everyone viewing this page sees the same text. This allows everyone to collaborate seamlessly on documents. 10 | 11 | Use of this service is restricted to members of The Carpentries community; this is not for general purpose use (for that, try [Etherpad.wikimedia.org](https://Etherpad.wikimedia.org/)). 12 | 13 | Users are expected to follow our [code of conduct]( https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html). All content is publicly available under the [Creative Commons Attribution License](https://creativecommons.org/licenses/by/4.0/). 14 | 15 | 16 | #### Troubleshooting 17 | 18 | While Etherpads are generally reliable, you may find an Etherpad not loading as expected. In this case, you can try appending `/export/html` to an Etherpad's url. For example, if `https://pad.carpentries.org/committeename` is not loading, it may be possible to recover its text by going to `https://pad.carpentries.org/committeename/export/html`. This text content can then be copied and pasted to a new Etherpad. Note this will not preserve the Etherpad's history. The chat will often still be active in the broken Etherpad, so it is recommended that you link to the new Etherpad in the broken Etherpad's chat. 19 | 20 | If other Etherpad issues arise, please contact us at team@carpentries.org and a team member will help you troubleshoot. 21 | 22 | 23 | #### See Also 24 | 25 | [CodiMD](https://docs.carpentries.org/topic_folders/communications/tools/codimd.html) is another collaborative note taking platform used by the community members. 26 | -------------------------------------------------------------------------------- /topic_folders/communications/tools/github_organisations.md: -------------------------------------------------------------------------------- 1 | # GitHub Organisations Owned by The Carpentries 2 | 3 | The Carpentries owns many GitHub organisations, used for individual lesson programs and Carpentries-wide work. 4 | 5 | * [The Carpentries](https://github.com/carpentries): The Carpentries website, instructor training curriculum, and other materials related to The Carpentries project as a whole. 6 | * [Data Carpentry](https://github.com/datacarpentry): Curricula and other materials related specifically to the Data Carpentry lesson program. 7 | * [Library Carpentry](https://github.com/librarycarpentry): Curricula and other materials related specifically to the Library Carpentry lesson program. 8 | * [Software Carpentry](https://github.com/swcarpentry): Curricula and other materials related specifically to the Software Carpentry lesson program. 9 | * [The Carpentries - Spanish Translations](https://github.com/carpentries-es): Spanish language lesson transitions that are in development or have been archived. Active lesson translations can be found in the respective lesson program's repo. 10 | * [Reproducible Science Curriculum](https://github.com/Reproducible-Science-Curriculum): Hosts lessons that started as an independent project from Data Carpentry. These lessons are not actively developed or taught. 11 | * [CarpentryCon](https://github.com/carpentrycon) Planning for the bi-annual CarpentryCon event. 12 | * [CarpentryConnect](https://github.com/carpentryconnect) Planning local and regional Carpentries events. 13 | * [carpentries-workshops](https://github.com/carpentries-workshops): Future home for workshop website repos (which will include an automated build process). 14 | * [data-lessons](https://github.com/data-lessons): Community developed lessons in various stages of development. 15 | * [The Carpentries Lab](https://github.com/carpentries-lab): Future home of peer-reviewed community developed lessons that follow the format of The Carpentries. 16 | * [carpentries-incubator](https://github.com/carpentries-incubator): A designated space for community members to develop lessons collaboratively. A central location for lesson development that isn't tied to individual user accounts. 17 | 18 | ## Past Organisations 19 | 20 | Occasionally, our GitHub organisations are moved, merged, or split. 21 | 22 | * [carpentrieslab](https://github.com/carpentrieslab): Former home of peer-reviewed community developed lessons. Replaced by [carpentries-lab](https://github.com/carpentries-lab). 23 | -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/chat_waiting_room.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/chat_waiting_room.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/claim_host.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/claim_host.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/codimd_mode_buttons.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/codimd_mode_buttons.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/event_setup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/event_setup.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/host_key.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/host_key.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/host_security_screenshare.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/host_security_screenshare.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/host_security_waiting_room.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/host_security_waiting_room.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/make_cohost.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/make_cohost.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/participants_more.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/participants_more.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/reserved_room.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/reserved_room.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/screenshare_advanced.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/screenshare_advanced.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/someone_entered_waiting_room.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/someone_entered_waiting_room.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/view_rooms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/view_rooms.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/view_waiting_room.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/view_waiting_room.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/zoom_claim_host.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/zoom_claim_host.gif -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/zoom_closed_caption.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/zoom_closed_caption.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/zoom_make_host.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/zoom_make_host.gif -------------------------------------------------------------------------------- /topic_folders/communications/tools/images/zoom_screenshare_audio.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/communications/tools/images/zoom_screenshare_audio.png -------------------------------------------------------------------------------- /topic_folders/communications/tools/index.rst: -------------------------------------------------------------------------------- 1 | Tools 2 | ====== 3 | 4 | 5 | .. toctree:: 6 | :maxdepth: 1 7 | :glob: 8 | 9 | 10 | etherpads.md 11 | codimd.md 12 | github_organisations.md 13 | newsletter.md 14 | slack-and-email.md 15 | zenodo_communities.md 16 | zoom_rooms.md 17 | -------------------------------------------------------------------------------- /topic_folders/communications/tools/newsletter.md: -------------------------------------------------------------------------------- 1 | ### Newsletter 2 | 3 | Our newsletter, [*Carpentry Clippings*](https://carpentries.org/newsletter/), appears every two weeks. 4 | 5 | #### Newsletter Content 6 | 7 | * *Highlights from The Carpentries Community Calendar*: Includes items from The Carpentries calendar, such as upcoming events. 8 | * *Community News*: A place to report on all kinds of things - events, workshop or conference reports, awards, lesson releases, new reports ... 9 | * *Committee and Task Force Activity*: Includes announcements directly from task force and committee chairs and summaries from meeting notes. 10 | * *What you may have missed on the blog and mailing lists*: Includes highlights of key conversations on the *Discuss* email list, other lists or things on the blog that need further highlighting. 11 | * *Tweet of the Week*: One noteworthy tweet is chosen and a screen captured image is included. 12 | * *Optional: Papers & manuscripts for and from the community*: Includes announcements that were made on the *Discuss* email list, Twitter, or other media. 13 | * *Optional: Offcuts*: Includes other unusual news that may be of interest. 14 | * *Optional: Joinery*: Includes other ways to get involved in The Carpentries community and ways The Carpentries community is involved in other conferences, etc. 15 | * *Optional: Toolshed (Posts from our Past)*: A place to highlight handy posts from the blog or discussion list archives that might still be relevant to postings to lists and other issues. 16 | * *Community Job postings*: Includes information that has come through on the *Discuss* email list, Twitter, and other media. 17 | * *Other places to connect*: This section is standardised for all newsletter issues. 18 | 19 | #### Submitting Newsletter Content 20 | 21 | Carpentries Core Team manage newsletter content through this [private Asana project](https://app.asana.com/0/1111365359623439/1111365359623465). Submissions from community members are welcome by emailing [newsletter@carpentries.org](mailto:newsletter@carpentries.org). 22 | 23 | 24 | #### Publishing the Newsletter 25 | 26 | This information is intended for Core Team or community members who have taken on the responsibility of publishing the newsletter. 27 | 28 | Each newsletter is a campaign on MailChimp. 29 | 30 | To create a new newsletter, log in to MailChimp and click on *Campaigns*. Make a copy of the latest newsletter and rename the copy to reflect the current date (e.g. `Carpentry Clippings, 27 March, 2018.`). 31 | 32 | Check the *To* field is correctly set as going to *x* number of newsletter subscribers. 33 | 34 | Check the *From* field is correctly set as coming from *The Carpentries*. 35 | 36 | Make sure the date in the *Subject* line is changed to the new newsletter date. 37 | 38 | Select *Edit design* to add newsletter content. When the newsletter opens, click the pencil icon in the newsletter on the left to open the newsletter for editing. (Editing is all done within the right pane; the left pane renders the public view as you edit.) 39 | 40 | Remove the old content and paste in the new, leaving the headings so that the formatting for them is not disturbed. 41 | 42 | Be sure to update the date at the top of the email as well. 43 | 44 | Highlight each paragraph and click *Clear styles* if anything you are copying in appears in bold when you do not want it to. 45 | 46 | Add images by clicking on the *Image* icon in the edit window. All images must be no more than 550px wide to render properly. These can be resized within MailChimp by working with the image styling and location. 47 | 48 | Go to *Preview and Test* to preview the newsletter before sending it out. This includes a desktop and mobile version preview. Send a test email to yourself to preview it in your email client. 49 | 50 | *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 Core Team channel so Core Team have a chance to review the newsletter before it goes out. 51 | 52 | The newsletter will now be locked. If any changes need to be made after the newsletter has been scheduled, you will need to _pause_ the campaign, make changes, and restart the campaign. 53 | 54 | After a campaign has been paused and then restarted, it is important to double check 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. 55 | 56 | As soon as the newsletter has been sent out, move it to the **Carpentry Clippings** folder. This adds it to the [searchable online archive](https://carpentries.org/newsletter/) 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. 57 | 58 | #### Tips and Tricks 59 | 60 | 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: 61 | 1. Copy and paste text in the Mailchimp editor. 62 | 1. Select all text in the Mailchimp editor and click *Clear Styles*. 63 | 1. Select all text and set font to Arial 12 point. 64 | 1. Select the title ("Carpentries Clippings, ") and set font to 18 pt bold. 65 | 1. Select each subheading one by one (*Highlights from The Carpentries Community Calendar*, *Community News*, etc.) and set font to 16 pt bold. 66 | 1. Select each item heading one by one and set font to 14 point regular. 67 | 68 | [Mailchimp customer service chat](https://us14.admin.mailchimp.com/support/) is hard to find on their website but quite responsive to requests for help. 69 | -------------------------------------------------------------------------------- /topic_folders/communications/tools/zenodo_communities.md: -------------------------------------------------------------------------------- 1 | # The Carpentries Zenodo Communities 2 | 3 | We use [Zenodo](https://zenodo.org/) to publish lesson releases and various other documents, 4 | such as The Carpentries Annual Reports, conference reports, and other 5 | material relating to The Carpentries and the individual lesson programs. 6 | Follow the links below to browse the resources published in each Zenodo community: 7 | 8 | * 9 | * 10 | * 11 | * 12 | -------------------------------------------------------------------------------- /topic_folders/for_instructors/images/amy_instructor_signup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/for_instructors/images/amy_instructor_signup.png -------------------------------------------------------------------------------- /topic_folders/for_instructors/images/amy_login_screen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/for_instructors/images/amy_login_screen.png -------------------------------------------------------------------------------- /topic_folders/for_instructors/images/amy_user_profile.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/for_instructors/images/amy_user_profile.png -------------------------------------------------------------------------------- /topic_folders/for_instructors/index.rst: -------------------------------------------------------------------------------- 1 | For Instructors 2 | ======================= 3 | 4 | 5 | This material is for current and aspiring Carpentries Instructors. 6 | Find material here on becoming an Instructor, how you can develop as an Instructor, and what networking opportunities 7 | our community offers. 8 | 9 | **Thank You to Instructors!** 10 | 11 | We are very grateful to our community of Instructors! From those who teach once or twice a 12 | year to those who organise entire programs, from those who have just gotten involved to those who have 13 | deeply embedded themselves as mentors, discussion hosts, committee and Task Force members, and 14 | instructor Trainers: EVERY Instructor helps make The Carpentries what we are. Thank you!! 15 | 16 | 17 | 18 | .. toctree:: 19 | :maxdepth: 2 20 | :glob: 21 | 22 | * 23 | -------------------------------------------------------------------------------- /topic_folders/for_instructors/new_instructors.md: -------------------------------------------------------------------------------- 1 | ## Become a Carpentries Instructor 2 | 3 | We are always glad to welcome new Instructors to our community! 4 | 5 | A Carpentries Instructor is a person who has completed our two-day 6 | [Instructor training course workshop](https://carpentries.github.io/instructor-training/), and 7 | has performed the required follow-up tasks to complete 8 | the [checkout process](https://carpentries.github.io/instructor-training/checkout) to become a certified (or ‘badged’) 9 | Instructor. Our Instructor training has the following overall goals: 10 | 11 | - Introduce participants to *evidence-based teaching practices*. 12 | - Teach participants how to *create a positive environment* for learners at workshops. 13 | - Provide opportunities for participants to *practise and build teaching skills*. 14 | - Help participants become integrated into *The Carpentries community*. 15 | - Prepare participants to use these skills in teaching *Carpentries workshops*. 16 | 17 | ### Who Are the Instructors? 18 | 19 | Our [Instructor community](https://carpentries.org/instructors/) includes researchers, librarians, data scientists, and many others 20 | from a wide range of backgrounds, disciplines, career stages, and countries. Many of our Instructors are 21 | people who have attended a Carpentries workshop, and who have been inspired to go on and train as Instructors to 22 | share the skills they learned and now use in their work. 23 | 24 | ### What Knowledge is Needed? 25 | 26 | Some would-be Instructors worry about how knowledgeable one has to be about the material we teach in order to become an Instructor. 27 | While our Instructors have experience in one or more of our content areas, such as shell, git, SQL, Python, R, OpenRefine or 28 | spreadsheet software, some are relatively new to the skills. 29 | 30 | Some people might be surprised to hear that feeling like a content ‘expert’ is not a necessary qualification to becoming an 31 | Instructor! We encourage newer learners to become Instructors. This is because: 32 | 33 | a) often the best people to teach a novice level curriculum are *not* experts, but rather 34 | people who have recently been novices themselves (we will discuss why this is so in the training!) 35 | b) teaching is actually an excellent way to become more familiar with the material. 36 | 37 | And because Carpentries Instructors never teach alone, you will always have help around if you get stuck! 38 | 39 | Many Instructors add to the number of lessons they feel comfortable teaching only gradually. Not knowing the material well should not hold you back from applying to become an Instructor. However, if you do want to apply, it would be useful to have attended a Carpentries workshop either as a learner or helper and have some familiarity with at least one of the topics. That way, you will know more about what being an Instructor involves, and you can assess whether the workshop style and teaching method are for you. 40 | Having already participated in a workshop will be a plus on our [scoring rubric](https://github.com/carpentries/Instructor-training/blob/gh-pages/files/rubric.md#) if you decide to apply. 41 | 42 | ### Motivation for People to Train as Instructors 43 | 44 | People train as Instructors for many reasons: 45 | 46 | 1. *To make their own lives better.* By teaching their peers how to build and share better software, our Instructors are indirectly helping to create things that they themselves can use. 47 | 2. *To build a reputation.* Teaching a workshop is a great way for people to introduce themselves to places they would eventually like to work, and a great way to make contact with potential collaborators. 48 | 3. *To get practice teaching.* We are training more Instructors every year, and giving them opportunities to teach, which is useful for people with academic careers in mind. 49 | 4. *To help get people of diverse backgrounds into the pipeline.* Some of our Instructors are involved in part because they want computational science to include people from a broader range of backgrounds. 50 | 5. *Teaching forces you to learn new things, or learn old things in more detail than you already know.* See this paper: [Graduate Students' Teaching Experiences Improve Their Methodological Research Skills](http://science.sciencemag.org/content/333/6045/1037)". 51 | 6. *To make the world a better place.* 52 | 7. *To acquire useful skills for careers.* Instructors can expect to develop [this skill set](https://github.com/carpentries/commons/blob/main/text-for-instructors.md#). You can re-use and re-purpose this wording for use in grant and job applications and for your CV. 53 | 8. *To join a community* of people who care about inclusive teaching of computational skills. 54 | 9. *Because it is fun.* It really is ! 55 | 56 | Read more about Instructor motivations in Dr. Beth Duckles's report, [*Value of Software Carpentry to Instructors*](https://software-carpentry.org/files/bib/duckles-instructor-engagement-2016.pdf). 57 | 58 | ### Steps to Becoming an Instructor 59 | 60 | Anyone who supports the aims of The Carpentries is welcome to apply for Instructor training. However, we are not able to 61 | guarantee training to all applicants. Member organizations get first priority for Instructor Training seats. For individuals 62 | interested in becoming certified Instructors outside the scope of membership, applications may be submitted for review 63 | through our Open Instructor Training program. 64 | 65 | Open Instructor Training applications are reviewed and scored periodically, with expected wait times of 1-3 months from 66 | submission. When space is available in upcoming events, we invite Open applicants in order of scoring to register. Multiple 67 | applicants from a single institution will generally not be admitted at the same time. Acceptance to Open Instructor Training 68 | does not expire, and registration codes may be used for any online training event between 1 month and 1 week prior to its start date. 69 | 70 | How do we score applicants? See our [scoring rubric](https://github.com/carpentries/Instructor-training/blob/gh-pages/files/rubric.md#). 71 | Applications below a threshold score may be declined. However, we welcome enthusiastic instructors to correspond and re-apply. 72 | 73 | To request training as an Instructor, please fill out this [form](https://amy.carpentries.org/forms/request_training/). 74 | 75 | Occasionally, open training events offered to the general public may be announced 76 | in our [mailing list](https://carpentries.topicbox.com/groups/discuss), 77 | newsletter, [*Carpentry Clippings*](http://eepurl.com/cfODMH), or through 78 | our [Mastodon](hachyderm.io/@thecarpentries) feed. 79 | For all other events, seats are reserved for trainees affiliated with member institutions or admitted individually through our Open Instructor Training program. 80 | -------------------------------------------------------------------------------- /topic_folders/fundraising/carpentries-sponsorship-program.md: -------------------------------------------------------------------------------- 1 | 2 | # The Carpentries Sponsorship Program 3 | 4 | The Carpentries Sponsorship program aims to help The Carpentries partner with like-minded organisations who want to contribute financially to help The Carpentries achieve our mission and vision. 5 | 6 | For more information about the Sponsorship Program and for details on sponsorship levels and benefits, please visit our [website](https://carpentries.org/sponsorship/). 7 | -------------------------------------------------------------------------------- /topic_folders/fundraising/collaborating-on-grants.md: -------------------------------------------------------------------------------- 1 | # A Guide for Collaborating with The Carpentries on Grants 2 | 3 | ## Statement to Interested Collaborators 4 | This guide was developed for potential collaborators interested in involving The Carpentries in a grant proposal. We value all contributions to our mission and are excited to collaborate with individuals and organisations interested in mission-aligned activities (i.e., Carpentries workshops, Instructor training, curriculum, and community development). We offer two options for collaborating with The Carpentries on grant proposals: 5 | 6 | 1. **Request a letter of support**. If you are planning to budget Carpentries programming (i.e., workshops, membership, instructor training seats) into your grant proposal and would like to request a letter of support, please [complete this form](https://carpentries.typeform.com/to/oK25vSPE). Pricing for Carpentries programming is on our [membership page](https://carpentries.org/membership/). All requests for letters of support require **five business days** to be fulfilled. 7 | 8 | 2. **Request to meet one of our program leads**. If you have an idea supporting one of the Carpentries' [strategic priorities](https://carpentries.org/strategic-plan/) and would like to co-write a grant proposal, please schedule a meeting with the corresponding program lead using the links below. Minimum requirements for co-writing a grant proposal with The Carpentries are provided below. 9 | - [Carpentries in Africa](https://calendly.com/angelique_v) - Angelique Trusler 10 | - [Community Development](https://calendly.com/kariljordan) - Kari L. Jordan 11 | - [Curriculum](https://calendly.com/tobyhodges) - Toby Hodges 12 | - [Membership](https://calendly.com/ebecker-1) - Erin Becker 13 | - [Workshops and Instruction](https://calendly.com/sheraaron/) - SherAaron Hurt 14 | 15 | We invite you to include The Carpentries in your grant to support workshops, membership, and Instructor training whether you apply as an individual institution or a consortium. We are also happy to collaborate on grant proposals supporting our mission, [core values](https://carpentries.org/values/), and priorities. This guide should be used as a resource in advance of proposal development. 16 | 17 | ## How is The Carpentries Funded? 18 | Funders who help The Carpentries fulfill our mission and vision _**financially**_ include [Member Organisations](https://carpentries.org/members/), [Sponsors](https://carpentries.org/sponsorship/), charitable foundations, and individual supporters ([The Carpentries Philanthropy](https://carpentries.us14.list-manage.com/subscribe?u=46d7513c798c6bd41e5f58f4a&id=33f76196ac)). The Carpentries is currently funded by grants and sponsorships (~56%), memberships (~30%), workshop/instructor training fees (~5%), and other sources including donations and curriculum development. We aim to be transparent in our sources of revenue and how they align with our vision and values and seek funding to support existing priorities and future goals in alignment with our [strategic plan](https://carpentries.org/strategic-plan/). Below is a list of sources of grants and sponsors who have funded The Carpentries. 19 | 20 | ### Current and Past Grants and Subawards 21 | - [Alfred P. Sloan Foundation](https://sloan.org/) 22 | - [California Digital Library (CDL)](https://cdlib.org/) 23 | - [Chan Zuckerberg Initiative (CZI)](https://chanzuckerberg.com/) 24 | - [Gordon and Betty Moore Foundation](https://www.moore.org/) 25 | - [Lawrence Berkeley Laboratory](https://carpentries.org/supporters/) 26 | - [Mozilla Open Source Support (MOSS) Program](https://www.mozilla.org/en-US/moss/) 27 | - [Network of the National Library of Medicine (NNLM) National Training Office (NTO)](https://nnlm.gov/about/offices/nto) 28 | - [R Consortium](https://www.r-consortium.org/) 29 | - [United States Department of Agriculture (USDA)](https://carpentries.org/supporters/) 30 | - [Mellon Foundation](https://www.mellon.org/grant-programs/public-knowledge) 31 | 32 | For more information about grants we have received from these sources, please read our [blog posts tagged grants](https://carpentries.org/posts-by-tags/#blog-tag-grants). 33 | 34 | ### Current and Past Sponsors 35 | - [Biotech Partners](http://www.biotechpartners.org/) 36 | - [Jump Recruits, LLC](https://jumprecruits.com/) 37 | - [Posit](https://rstudio.com/) 38 | 39 | For more information about sponsorship opportunities, visit our [Sponsorship Program page](https://carpentries.org/sponsorship/). 40 | 41 | ## Minimum Requirements for Co-Writing a Grant with The Carpentries 42 | The Carpentries has identified deliverables ideal for in-kind support and/or grant funding in curriculum development, community development, workshops, instructor training, and infrastructure. These projects typically require that a percentage of The Carpentries Core Team time be written into the grant budget to support program development, administration, and infrastructure. Below are examples of minimum requirements for co-writing a grant with The Carpentries. 43 | 44 | - **Timeframe:** Please allow 3-6 months to work on a grant proposal with a Core Team Lead. Expect several meetings/co-working sessions to develop the proposal narrative and budget during that time. A clearer timeline will be co-developed once a decision to move forward with writing a grant has been made. 45 | - **Budget:** The Carpentries is a fiscally sponsored project of Community Initiatives. As such, all budget proposals will include an 11.11% fee on the income The Carpentries receives. Additionally, for any key personnel working on the grant, a **minimum of 15%** of their time throughout the grant must be included in the budget. Key personnel may include, but is not limited to, Core Team Leads, administrators, or contractors working with The Carpentries. Lastly, support to be written into a grant budget may include infrastructure, equipment, and/or travel as appropriate. 46 | -------------------------------------------------------------------------------- /topic_folders/fundraising/donation-request-resources.md: -------------------------------------------------------------------------------- 1 | # Donation Request Resources 2 | 3 | ## Introduction 4 | The following resources were created to aid The Carpentries community in fundraising for the organisation. 5 | 6 | ## Donation Request Letter - Individual 7 | 8 | Email Subject Line: A Call to Action: Help The Carpentries Meet Our Fundraising Goal 9 | 10 | Dear \[potential donor’s name\] 11 | 12 | My name is \[your name\], and I am the \[position or role at your institution\]. I am also \[position or role\] with The Carpentries, an organisation whose mission is to build global capacity in essential data and computational skills. The Carpentries helps train and foster an active, inclusive, diverse community of learners and instructors that promotes and models the importance of software and data in research. 13 | 14 | The Carpentries is in the process of [transitioning out of fiscal sponsorship](https://carpentries.org/blog/2023/08/Carpentries-transition-to-independent-status/) to operate as an independent 501(c)(3) non-profit organisation, and is seeking donations from individuals who wish to support its desire for independence to carry out its global mission. This move towards independence will empower The Carpentries to have greater autonomy, allowing it the flexibility to innovate, experiment, and respond swiftly to emerging trends and challenges in data science and education. 15 | 16 | **You can support our transition to independence by donating any amount.** 17 | 18 | The Carpentries supports more than 3,000 highly skilled Instructors in communities in over 100 countries across the world. We have experience training educators, researchers, librarians, and technologists. We are working to scale our instructor training and curriculum development programs to respond to the shift in the nature of education around the world. **Now more than ever we need you to champion our mission**. You can help us teach data skills to the communities that need them most by donating any amount you feel comfortable with. 19 | 20 | Donating even a small amount can make a big difference \- we value all contributions. Your donation will allow The Carpentries to scale as an independent tax-exempt non-profit organisation,and will help bring Carpentries programming to individuals who might otherwise have barriers to participation. 21 | 22 | If you are interested in supporting The Carpentries’ mission of teaching data skills globally, {{"[please visit our Donate page]({})".format(donate)}} to give any amount you are comfortable with. 23 | 24 | Thank you so much\! 25 | 26 | Sincerely, 27 | \[Your name\] 28 | \[Your role within The Carpentries\] 29 | 30 | ## Short Calls to Action/Mastodon Length Messages 31 | - A Call To Action: Support The Carpentries
32 | Consider donating to The Carpentries to help us reach our annual fundraising goal!
{{ donate }} 33 | 34 | - “The Carpentries supports more than 4,200 highly skilled instructors in communities in 65 countries. Now more than ever, we need you to champion our mission.” - Dr. Kari L. Jordan
35 | Help us teach data skills to the communities that need them most.
36 | {{ donate }} 37 | 38 | - Thank you to everyone who has donated to help The Carpentries achieve our mission! With your help, we are on track to reach our goal. Please consider donating to help us achieve our annual fundraising goal.
39 | {{ donate }} 40 | 41 | -------------------------------------------------------------------------------- /topic_folders/fundraising/index.rst: -------------------------------------------------------------------------------- 1 | Fundraising 2 | ======================= 3 | 4 | 5 | .. toctree:: 6 | :maxdepth: 2 7 | :glob: 8 | 9 | carpentries-sponsorship-program.md 10 | collaborating-on-grants.md 11 | donation-request-resources.md -------------------------------------------------------------------------------- /topic_folders/governance/bylaws.md: -------------------------------------------------------------------------------- 1 | # The Carpentries Bylaws 2 | 3 | The Carpentries bylaws are available on [The Carpentries website](https://carpentries.org/governance/#bylaws). -------------------------------------------------------------------------------- /topic_folders/governance/committee-guidelines.md: -------------------------------------------------------------------------------- 1 | ## The Carpentries Committee Guidelines 2 | 3 | These guidelines provide the recommended process for creating committees to ensure transparency, accountability, and sustainability of committee activities. 4 | 5 | ### Committee Proposal 6 | A committee proposal should: 7 | - explain the need for or the context for the committee 8 | - explain why it should be an ongoing/longer-term committee 9 | - list the aims and objectives of the committee 10 | 11 | Committee proposals can be submitted by creating an 12 | issue in the [*committees* repository](https://github.com/carpentries/committees/issues) in [The Carpentries GitHub](https://github.com/carpentries/) or by emailing the proposal to the [Core Team](mailto:team@carpentries.org). 13 | 14 | ### Committee Formation 15 | Committee proposals do not require formal approval, though the [Community Team should be informed](mailto:community@carpentries.org) of committee formation. Active committees are listed on [The Carpentries website](https://carpentries.org/committees/) with a link to public documentation. 16 | 17 | ### Committee Operations 18 | The following are recommended guidelines for committees. Each committee should: 19 | 20 | - Create an official [committee charter](https://github.com/carpentries/committees/blob/main/committee-charter-template.md), including the [committee's roles and responsibilities](https://github.com/carpentries/committees/blob/main/committee-charter-template.md#roles-and-responsibilities) 21 | - Appoint a committee chair and, optionally, a co-chair and identify term limits for chair/co-chair/members 22 | - Request a [Core Team](https://carpentries.org/team/) member liaison to serve as a point of contact and (optionally) attend the committee meetings 23 | - Create a public space for the committee, including: 24 | - The committee's charter 25 | - Contact information for the committee 26 | - Other public materials (if available) 27 | - Information on when committee meetings are held 28 | - Meeting notes (if appropriate) 29 | - Names of the current and past members, including their roles 30 | - Name of the Core Team liaison (if applicable) 31 | - Information on how to join the committee 32 | - Create internal [documentation for operational procedures](https://github.com/carpentries/committees/blob/main/committee-charter-template.md#operational-procedures) (which may also be made public), including: 33 | - Process for recruiting and/or selecting new members 34 | - Process for on-boarding new members 35 | - Process for off-boarding members 36 | - Succession plan for chair/co-chair 37 | - Decision-making process 38 | - Maintain internal and public-facing communication: 39 | - Organise committee meetings (at least twice a year) and post meeting notes in a consistent location (meeting notes should be public unless the work of the committee requires them to remain private) 40 | - Post meetings in the [community calendar](https://carpentries.org/community/#community-events). Note that meetings do not necessarily need to be open to public to attend even though they are added to the calendar - for example, the Code of Conduct Committee's business meetings are public, but incident response meetings are not. 41 | - Aim to host at least one community discussion per year to share about the committee's activities 42 | - Utilise other [The Carpentries community communication pathways](https://docs.carpentries.org/topic_folders/communications/index.html) to engage with the community as needed 43 | 44 | Templates for creating committee documentation are available from the [*committees* repository](https://github.com/carpentries/committees). 45 | 46 | ### Committee Termination 47 | A committee may naturally cease to function upon fulfilling its goals, in which case the Core Team should be notified. 48 | 49 | ### Past & Current Committees 50 | 51 | - [Code of Conduct Committee](https://carpentries.org/coc-ctte/) 52 | - [Curriculum Advisory Committees](https://carpentries.org/curriculum-advisors/) (CACs) 53 | - [Lesson Infrastructure Committee](https://carpentries.org/lesson-infra/) 54 | - [Instructor Development Committee](https://carpentries.org/inst-dev/) 55 | - [Trainer Leadership Committee](https://github.com/carpentries/trainers/blob/main/governance.md) 56 | - [Lesson Program Governance Committees](https://carpentries.org/blog/2022/11/lesson-program-governance/) 57 | 58 | ### Update Log 59 | - 2024-01-25: Renamed Committee Policy to Committee Guidelines, including recommendations and removing requirements for committees. 60 | - [Approved on 2022-12-02](https://github.com/carpentries/executive-council-info/blob/main/minutes/2022/EC-minutes-2022-12-02-Q4.md) by the Executive Council. 61 | - [Approved on 2020-09-23](https://github.com/carpentries/executive-council-info/issues/44) by the Executive Council. 62 | -------------------------------------------------------------------------------- /topic_folders/governance/index.rst: -------------------------------------------------------------------------------- 1 | Governance 2 | ======================= 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | bylaws.md 9 | board.md 10 | committee-guidelines.md 11 | task-force-guidelines.md 12 | lesson-program-policy.md 13 | lesson-program-governors.md 14 | 15 | -------------------------------------------------------------------------------- /topic_folders/governance/task-force-guidelines.md: -------------------------------------------------------------------------------- 1 | ## The Carpentries Task Force Guidelines 2 | 3 | These guidelines provide the recommended process for establishing a task force to ensure transparency, accountability, and sustainability of task forces' activities. 4 | 5 | ### Task Force Proposal 6 | A task force proposal should: 7 | - explain the need for or the context of the task force 8 | - list the aims and objectives of the task force 9 | - set a timeline for starting and completing the task force's activities/deliverables. 10 | 11 | Task force proposals can be submitted by [creating an 12 | issue](https://github.com/carpentries/task-forces/issues) in the 13 | [*task forces* repository](https://github.com/carpentries/task-forces) in [The Carpentries GitHub](https://github.com/carpentries/) or 14 | by emailing the proposal to the [Core Team](mailto:team@carpentries.org). 15 | 16 | ### Task Force Formation 17 | Task force proposals do not require formal approval, though the [Core Team should be informed](mailto:team@carpentries.org) of task force formation. Active task forces are listed in [The Carpentries task forces repository](https://github.com/carpentries/task-forces) with a link to its public documentation. 18 | 19 | ### Task Force Operations 20 | The following are recommended guidelines for committees. Each committee should: 21 | 22 | - Create the official [task force charter](https://github.com/carpentries/task-forces/blob/main/task-force-charter-template.md), 23 | including the task force's roles and responsibilities 24 | - Appoint the task force chair and, optionally, a co-chair 25 | - Request a [Core Team](https://carpentries.org/team/) member liaison to serve as a point of contact and (optionally) attend the task force meetings 26 | - Create a public space for the task force, including: 27 | - The task force's charter and its current status (e.g., active, completed) 28 | - Contact information for the task force 29 | - Other public materials (if available) 30 | - Information on when the task force meetings are held 31 | - Meeting notes (if appropriate) 32 | - Name of the Core Team liaison 33 | - Information on how to apply to join the task force 34 | - Create internal [documentation for operational procedures](https://github.com/carpentries/task-forces/blob/main/task-force-charter-template.md#task-force-charter-name-of-task-force) (which may also be made public), including: 35 | - Process for recruiting and/or selecting new members 36 | - Decision-making process 37 | - Maintain internal and public-facing communication: 38 | - Organise regular meetings to progress with the task force's activities and post meeting notes in a consistent location (meeting notes should be public unless the work of the task force requires them to remain private) 39 | - Post meetings in the community calendar (note that meetings do not necessarily need to be open to the public to attend even though they are added to the calendar) 40 | - Utilise other [Carpentries community communication pathways](https://docs.carpentries.org/topic_folders/communications/index.html) to engage with the community as needed 41 | 42 | The task force's public documentation should be stored in a folder within the [`task-forces` repository](https://github.com/carpentries/task-forces) 43 | in [The Carpentries GitHub](https://github.com/carpentries/). 44 | 45 | ### Task Force Termination 46 | A task force will naturally cease to function upon fulfilling its goals, in which case the Core Team should be notified. 47 | 48 | ### Past & Current Task Forces 49 | 50 | - [CarpentryCon Task Force](https://carpentries.org/carp-con-tf/) - a recurring task force that gets periodically 51 | reformed to organise the international [CarpentryCon](https://carpentries.org) conference on behalf of The Carpentries. 52 | - Other past and current task forces can be found in [The Carpentries Task Force Repository](https://github.com/carpentries/task-forces). 53 | 54 | ### Update Log 55 | - 2024-01-25: Renamed Task Force Policy to Task Force Guidelines, including recommendations and removing requirements for task forces. 56 | - [Approved on 2022-12-02](https://github.com/carpentries/executive-council-info/blob/main/minutes/2022/EC-minutes-2022-12-02-Q4.md) by the Executive Council. 57 | - [Approved on 2020-09-23](https://github.com/carpentries/executive-council-info/issues/44) by the Executive Council. 58 | -------------------------------------------------------------------------------- /topic_folders/hosts_instructors/certificates.md: -------------------------------------------------------------------------------- 1 | ### Learner Certificates 2 | 3 | We do not badge learners, but we do give them certificates of attendance if requested. 4 | 5 | If you would like to give your learners certificates of participation following a workshop, please refer to [our certificates repo](https://github.com/carpentries/learner-certificates). This includes `svg` templates for the certificates and Python scripts to generate them. 6 | -------------------------------------------------------------------------------- /topic_folders/hosts_instructors/handling_emergencies.md: -------------------------------------------------------------------------------- 1 | ### Handling Emergencies 2 | 3 | We know that unexpected things can happen, even with the best laid plans. Below are some tips to help deal with unexpected situations. 4 | 5 | **Situation: Co-instructor cannot come due to illness, flight delay, etc.** 6 | * Contact team@carpentries.org. Depending on how much notice we get, we may be able to help find another Instructor. 7 | * Contact your helpers and host to see if any of them can provide extra support, and even teach a portion of the lessons 8 | * If your co-Instructor is delayed (rather than having to cancel entirely), adjust the schedule of your event so that person's lesson come later in the event. 9 | 10 | **Situation: Group cannot get on wi-fi** 11 | * If you anticipate this in advance, come with a handful of thumb drives to install software and data files 12 | * If only some learners can get on wifi, consider pairing them up so they can follow on the connected person's machine 13 | 14 | **Situation: Building or classroom is locked** 15 | * Ensure that you have emergency contact information for hosts(s) before the workshop and any other people involved in logistics. 16 | * Contact all participants if possible, and put signs on doors letting them know the workshop is postponed until further notice. 17 | * If your room is locked, check with building staff to see if a nearby room is available. 18 | -------------------------------------------------------------------------------- /topic_folders/hosts_instructors/index.rst: -------------------------------------------------------------------------------- 1 | Teaching and Hosting 2 | ########################## 3 | 4 | 5 | Certified instructors can view opportunities to teach Carpentries workshops `in AMY `_. Join the `instructors mailing list `_ to be notified when new opportunities are posted. 6 | 7 | Certified instructors are also encouraged to run workshops themselves. When organising a workshop, you 8 | have two options: a Centrally-Organised or Self-Organised workshop. 9 | 10 | One way to understand the distinction between Centrally-Organised and Self-Organised workshops is who 11 | is responsible for certain key workshop components: 12 | 13 | Centrally-Organised Workshop 14 | ****************************** 15 | 16 | * registration managed by The Carpentries Workshop Administration Team 17 | * instructor recruitment managed by The Carpentries Workshop Administration Team 18 | 19 | Self-Organised Workshop 20 | ****************************** 21 | 22 | * registration managed by local organizer 23 | * instructor recruitment managed by local organizer 24 | 25 | 26 | .. note:: 27 | **Recruitment of Instructors for Self-Organised workshops** 28 | 29 | While Self-Organised workshops are not managed by The Carpentries Workshop Administration Team, we want to be able to provide you with resources to make the load lighter. When hosting a Carpentries workshop there are many steps in the coordination process. One of the most important components is ensuring you have Instructors to teach your workshop. This can be even more difficult when you have to recruit the instructors for a Self-Organised workshop. 30 | 31 | The Workshop Administration Team has seen an increase in both Self-Organised workshops and Centrally-Organised workshops. With this increase, we have also seen a decrease 32 | in the amount of available instructors to teach Centrally-Organised workshops. As an organisation, we need to ensure that we are able to provide Instructors for our paid workshops while also providing resources for Self-Organised workshops. 33 | 34 | 35 | To ensure the Instructor community is not oversaturated with request to teach, the Workshop Administration Team has identified specific places for recruiting Instructors, Supporting Instructors and/or helpers for a Self-Organised workshop. Below are the channels you can use: 36 | 37 | - Any local or group specific mailing list on `TopicBox `_ 38 | 39 | - Any local or group specific Slack channel 40 | 41 | *These channels were designed specifically for community members to communicate about specific needs and to build local capacity. Recruiting done in any other channel will be removed*. 42 | 43 | 44 | In both cases, the host site is expected to pay for instructor travel (if needed) and 45 | cover local costs. For a Centrally-Organised workshop, there is a fee if the organiser 46 | is not already a Carpentries member. 47 | 48 | Note that you are free to charge what you choose for a workshop; 49 | this is a perennial topic of discussion among the Carpentries community and there's 50 | a good summary of points here: `Carpentries Blog on Charging for Workshops `_. 51 | 52 | In both cases (self- or Centrally-Organised), you can start the workshop 53 | process by completing the `Carpentries workshop request form `_ and 54 | then proceeding through the relevant checklists and list of tips below. 55 | 56 | For Centrally-Organised workshops, the Regional Coordinator will guide the host and instructor(s) on following 57 | through on all these steps. 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. 58 | 59 | For Self-Organised workshops, the host and instructor are directly responsible for ensuring all the steps below are followed without support from the Regional Coordinator. If you are planning to self-organise a workshop, check out these `Tips for Organising Your First Carpentries Workshop `_. 60 | 61 | .. toctree:: 62 | :maxdepth: 2 63 | :glob: 64 | 65 | hosts_instructors_checklist.md 66 | instructor_tips.md 67 | unofficial_workshops.md 68 | workshop_needs.md 69 | handling_emergencies.md 70 | certificates.md 71 | 72 | Resources for Online Workshops 73 | ****************************** 74 | 75 | In the wake of COVID-19 in early 2020, The Carpentries community came together to share experiences, tips, and best practices for teaching online. This page lists all the resources developed and links to ongoing conversations by The Carpentries Core Team and community on different platforms. 76 | 77 | .. toctree:: 78 | :maxdepth: 2 79 | :glob: 80 | 81 | resources_for_online_workshops.md 82 | 83 | 84 | Publishing Workshops 85 | ****************************** 86 | 87 | Workshops are published to `The Carpentries website `_ and the appropriate lesson program sites (`Data Carpentry `_, `Library Carpentry `_, or `Software Carpentry `_) when all of the following criteria are met: 88 | 89 | * A workshop request or notification form has been submitted 90 | * The workshop request form gives permission to list the workshop on our websites 91 | * The workshop venue has been identified on the workshop website 92 | * At least one instructor is identified 93 | 94 | -------------------------------------------------------------------------------- /topic_folders/hosts_instructors/unofficial_workshops.md: -------------------------------------------------------------------------------- 1 | ### Teaching Non-standard Carpentries Workshops 2 | 3 | A [standard Carpentries workshop](https://carpentries.org/workshops/#workshop-core) must cover the core lessons for that lesson program's curriculum. Read more about the [Software Carpentry](https://software-carpentry.org/lessons/), [Data Carpentry](https://datacarpentry.org/lessons/), and [Library Carpentry](https://librarycarpentry.org/lessons/) 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. 4 | 5 | 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 certified Instructors running non-standard workshops -- meaning they cover a portion of our curriculum but not the whole thing. 6 | 7 | We are excited to hear when this happens! We know this happens because our community members recognise 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 organisers. Also, while the impact on the learners is different than what we would expect from a full workshop, there is still something significant that learners are taking away from this event. If you are running a non-standard workshop using Carpentries materials, please let us know by [completing this form](https://amy.carpentries.org/forms/self-organised/) so we can ensure your workshop is recorded in our system. 8 | -------------------------------------------------------------------------------- /topic_folders/hosts_instructors/workshop_needs.md: -------------------------------------------------------------------------------- 1 | ### Workshop Needs 2 | 3 | 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. 4 | 5 | #### Venue 6 | 7 | A good venue is crucial to establishing a positive learning environment. Some things to consider include: 8 | 9 | * 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. 10 | * Tables should also be arranged so helpers and instructors can easily mingle around the room. 11 | * 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. 12 | * High speed Wi-Fi internet access that can withstand everyone using it together. This may include securing guest access codes. 13 | * Power outlets for all participants. This may include setting up extension cords or power strips. 14 | * High table or podium that instructor can stand at while teaching. A flat podium is important; it is difficult to use a laptop on a slanted podium. 15 | * Refreshments. People learn better when they are well fed. They also will not lose as much instructional time if they do not have to leave to get coffee. 16 | 17 | #### Equipment and Materials 18 | 19 | * Power strips, as noted above, to ensure everyone's laptop stays charged 20 | * 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. Note that colorblindness can be an issue with differently-colored stickies (say red/green or blue/yellow), so alternate methods for feedback include offering sticky notes in two distinct shapes, or using a heavy marker to draw symbols on the sticky notes to convey meaning. 21 | * Name tags to help people get to know each other. 22 | * Extra pens and paper in case people want to take notes by hand 23 | * Sign in sheets 24 | * Flipchart or whiteboard with felt-tip pen (ideally several in different colors) for the instructor to visualise concepts or note important details. 25 | 26 | #### Accessibility 27 | 28 | It is important to make sure the workshop space is accessible 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: 29 | 30 | * Building and room are accessible to those who can not use stairs (ramps, elevators, etc.) 31 | * Restrooms are accessible 32 | * There is a working microphone for instructors ([Our feedback](https://zenodo.org/record/1325464#.YVJIWS-B0ea) notes inability to hear at the back of the room as a common concern) 33 | * The screen is large enough and bright enough to be easily read 34 | * The building and room can accommodate service animals 35 | * Lactation space is provided 36 | -------------------------------------------------------------------------------- /topic_folders/instructor_development/index.rst: -------------------------------------------------------------------------------- 1 | Instructor Development 2 | ======================= 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | instructor_development_committee.md 9 | community_discussions.md 10 | -------------------------------------------------------------------------------- /topic_folders/instructor_development/instructor_development_committee.md: -------------------------------------------------------------------------------- 1 | ## Instructor Development Committee 2 | 3 | ### Instructor Development Committee Roles 4 | 5 | #### Co-Chairs 6 | 7 | ##### Responsibilities 8 | 9 | The Co-Chairs of the Instructor Development Committee are responsible for: 10 | 11 | 1. Scheduling monthly committee meetings. 12 | - Meetings held monthly, twice in one day with each co-chair hosting one meeting to accommodate time zones. 13 | 2. Working with fellow co-chair to plan and share the monthly meeting agenda in advance (i.e. 1 or 2 weeks ahead of time). 14 | 3. Leading one of the monthly committee meetings (or delegate when absent). 15 | 4. Delegating tasks that come up each month. 16 | - This can be done through a co-chairs meeting after monthly committee meeting. 17 | 5. Following up with other committee members regarding their duties/concerns. 18 | 6. Gathering feedback from community and other committee members about desired instructor development efforts and/or outcomes. 19 | 7. Adding/modifying new committee roles as necessary. 20 | 8. Evaluating committee roles on a yearly basis. 21 | 22 | ##### Time Commitment 23 | 24 | - 1-2 hours/week 25 | - 2 year term, first year serving as co-chair and second year serving as Member at Large 26 | - Limit to two consecutive terms 27 | 28 | ##### Requirements 29 | 30 | - Certified Carpentries Instructor 31 | 32 | #### Secretary 33 | 34 | ##### Responsibilities 35 | 36 | The Secretary of the Instructor Development Committee is responsible for: 37 | 38 | 1. Recording notes and attendance at IDC Leadership Meetings and IDC Meetings. 39 | 2. Adding notes to the [Instructor Development GitHub Repository](https://github.com/carpentries/instructor-development) after each meeting 40 | 3. Emailing a summary of notes to the [instructor-development list on TopicBox](https://carpentries.topicbox.com/groups/instructor-development). 41 | 4. Updating IDC Etherpad with meeting connection information and details 42 | 5. Monitoring the [Instructor Development Topicbox](https://carpentries.topicbox.com/groups/instructor-development) for ideas/issues to bring back to the committee. 43 | 44 | ##### Time Commitment 45 | 46 | - 1-2 hours/week 47 | - 1 year term 48 | - Limit to two consecutive terms 49 | 50 | ##### Requirements 51 | 52 | - Certified Carpentries Instructor 53 | 54 | #### Communications Chair 55 | 56 | ##### Responsibilities 57 | 58 | The Communications Chair of the Instructor Development Committee is responsible for: 59 | 60 | 1. Adding IDC Meetings to The Carpentries Community Calendar 61 | 2. Actively recruiting participants to join IDC meetings and projects by sending out communications via Slack, Topicbox, Twitter (with the help of The Carpentries Communications Lead, Omar Khan) and The Carpentries Blog. 62 | 3. Creating communications around IDC projects or other initiatives. 63 | 64 | ##### Time Commitment 65 | 66 | - 1-2 hours/week 67 | - 1 year term 68 | - Limit to two consecutive terms 69 | 70 | ##### Requirements 71 | 72 | - Certified Carpentries Instructor 73 | 74 | #### Mentoring Chair 75 | 76 | ##### Responsibilities 77 | 78 | The Mentoring Chair of the Instructor Development Committee is responsible for: 79 | 80 | 1. Using the [Mentoring Groups Workflow](https://docs.carpentries.org/topic_folders/instructor_development/mentoring_groups_workflow.html) to recruit mentors/mentees and managing The Carpentries Mentoring Groups. 81 | 2. Reporting back to IDC Leadership and Carpentries Core Team Liaison about Mentoring Group metrics and any concerns or revisions to the mentoring groups. 82 | 3. Maintaining The Carpentries Mentors' Etherpad and Mentoring Groups' Etherpad 83 | 4. Updating the [Mentoring Groups](https://docs.carpentries.org/topic_folders/instructor_development/mentoring_groups.html) section of the handbook as necessary. 84 | 5. Managing the #mentoring channel in The Carpentries Slack. 85 | 6. Coordinating with the [Communications Chair](#communications-chair) on communications campaigns around mentoring. 86 | 87 | ##### Time Commitment 88 | 89 | - 1-2 hours/week 90 | - 2 year term, first year serving as Mentoring Chair and second year serving as Member at Large 91 | - Limit to two consecutive terms 92 | 93 | ##### Requirements 94 | 95 | - Certified Carpentries Instructor 96 | 97 | #### Special Projects Chair 98 | 99 | ##### Responsibilities 100 | 101 | The Special Projects Chair of the Instructor Development Committee is responsible for: 102 | 103 | 1. Facilitating the formation of task forces/committees as appropriate to accomplish desired project outcomes. 104 | 2. Supporting any of the other Chairs/Leaders in their roles as needed. 105 | 106 | ##### Time Commitment 107 | 108 | - 1-2 hours/week 109 | - 2 year term, first year serving as Special Projects Chair and second year serving as Member at Large 110 | - Limit to two consecutive terms 111 | 112 | ##### Requirements 113 | 114 | - Certified Carpentries Instructor 115 | 116 | #### Members at Large 117 | 118 | ##### Responsibilities 119 | 120 | The Members at Large of the Instructor Development Committee are responsible for: 121 | 122 | 1. For those Members at Large previously serving as Co-Chairs, Mentoring Chair, or Special Projects Chair, will serve as mentor to incoming members serving in these roles. 123 | 2. Attends IDC monthly meetings to increase community representation during IDC discussions. 124 | 3. Support activities of the IDC as needed. 125 | 126 | ##### Time Commitment 127 | 128 | - 1-2 hours/week 129 | - 1 year term 130 | - Limit to two consecutive terms 131 | 132 | ##### Requirements 133 | 134 | - Certified Carpentries Instructor 135 | 136 | -------------------------------------------------------------------------------- /topic_folders/instructor_training/cancellations_and_makeups.md: -------------------------------------------------------------------------------- 1 | ## Attendance Policy 2 | 3 | 4 | ### No Shows 5 | 6 | A ‘No Show’ is when a trainee does not cancel or contact the [Instructor Training Team](mailto:instructor.training@carpentries.org) before an event, and does not attend training. In a 'No Show' event, the training seat will be considered used. 7 | 8 | If extenuating circumstances have prevented a trainee from cancelling, contacting, or attending an event, they may request permission to register for an additional event using the same registration code by emailing instructor.training@carpentries.org. IMPORTANT: **Requests to re-register must be received within 7 days after the end date of the training. ** 9 | 10 | Trainees with multiple unexplained no-shows may be barred from future registration. 11 | 12 | 13 | #### Partial Absence 14 | 15 | Trainees who miss up to 4 hours (1 half day) of an event can schedule a 45-minute 1:1 makeup meeting to complete their training with The Carpentries Director of Workshops and Training. [Makeup meetings can be scheduled via Calendly.](https://calendly.com/sheraaron/instructor-training-makeup). To prepare for a makeup meeting, trainees should review all sections of the Instructor Training Curriculum they missed and come prepared to share thoughts and questions about those sections. Trainees who missed more than 4 hours of an event **should not** schedule a makeup meeting. (See Re-taking a Training Event, below.) 16 | 17 | Trainees are not eligible for Instructor certification until their record indicates they have completed an entire Instructor Training event. 18 | 19 | 20 | #### Re-taking a Training Event 21 | 22 | Trainees who miss more than 4 hours (1 half day) of an event are not eligible for a makeup meeting but can ask to attend another event in full. To request permission to register for an additional training event, trainees should email [instructor.training@carpentries.org](mailto:instructor.training@carpentries.org) within 30 days of a missed event. 23 | 24 | When re-taking a training, trainees who miss more than 2 hours may be marked absent, even when they have attended part of a prior event. Multiple partial trainings may not be used to complete the training requirement. 25 | 26 | 27 | #### Ineligibility for Makeup Opportunities 28 | 29 | Trainees who miss an event in full without cancelling within 7 days (no-show) or who miss part of an event but do not request a makeup opportunity within 7 days are ineligible to register for a new training event using the same registration code. Trainees interested in completing training may contact [instructor.training@carpentries.org](mailto:instructor.training@carpentries.org) to be advised on their options for re-admission. 30 | 31 | 32 | ## Checkout Extensions Policy 33 | 34 | Trainees are asked to complete checkout within 90 days of attending an Instructor Training event. Having a deadline is necessary to support busy people in prioritising a goal we all care about. However, it is sometimes necessary for trainees to postpone completing checkout. 35 | 36 | Trainees who are unable to complete checkout within the 90-day deadline should contact us at [instructor.training@carpentries.org](mailto:instructor.training@carpentries.org) to request an extension. Extensions may be granted up to one year after the checkout deadline. After one year, you may contact instructor.training@carpentries.org to explore opportunities to re-take the training. 37 | -------------------------------------------------------------------------------- /topic_folders/instructor_training/duties_agreement.md: -------------------------------------------------------------------------------- 1 | ### Instructor Trainers 2 | 3 | 4 | Instructor Trainers (‘Trainers’) are certified to teach at all authorized Carpentries Instructor Training workshops, onboarding new Instructors who may in turn 5 | become certified to teach Data Carpentry, Library Carpentry, and Software Carpentry workshops. Trainers also play a role in the Instructor ‘checkout’ process, 6 | evaluating trainees’ teaching demonstrations. The Trainer community plays a leading role in The Carpentries, maintaining our flagship Instructor Training 7 | Curriculum, contributing to relevant policies, and bringing instructional practices to bear in leadership roles across our local and global communities. 8 | 9 | Trainers benefit from being part of a global community of pedagogically trained professionals with a shared interest in promoting robust teaching practices and 10 | propagating data skills worldwide. Trainers continually build on their own pedagogical and communication skills through co-instruction and monthly community 11 | discussions about Instructor training. Trainers have opportunities to influence what we teach, through curriculum maintenance, and to steer the progress of this 12 | community, through leadership roles. Trainers often play leadership roles in their home communities, mentoring local Instructors, and modeling best practices. 13 | 14 | 15 | ##### Active Status Renewal Process 16 | 17 | Version 1.0.1 -- Approved 8 February, 2023 18 | 19 | Active status for Instructor Trainers is renewed annually in March. 20 | 21 | New Trainers who have not yet been certified for a full year and Trainers who have returned to Active status within the past year 22 | will automatically be renewed. 23 | 24 | Active status may be renewed by either: 25 | A) participating in curriculum and community activities during the prior year, as described below OR 26 | B) meeting with the Director of Workshops and Training to catch up on curriculum and community changes and discuss plans for the coming year 27 | 28 | Trainers who do not renew their Active status before the deadline will have their status changed to Alumni. Instructions for Alumni returning to 29 | Active status are detailed below. 30 | 31 | In the case of option A, above, certification will be renewed automatically when records indicate that Trainers have completed all activities expected 32 | for Active Trainers, detailed below. If records are incomplete, Trainers may self-report their activities via a form. The Trainers Leadership Committee 33 | will review form responses and recommend either renewal or a meeting (option B) based on reported activities. 34 | 35 | ###### Participation Expectations for Active Instructor Trainers 36 | In order to be renewed based on prior participation, a Trainer is expected to participate as follows during the 1 year period prior to renewal: 37 | 38 | - teach at least 1 Instructor Training event, and 39 | - host at least 2 teaching demos, and 40 | - attend at least 4 Trainer community meetings 41 | 42 | OR 43 | 44 | - equivalent engagement with curriculum, trainees, or the Trainer community, as approved by the Trainers Leadership Committee 45 | 46 | As a general rule, equivalent activities must be self-reported via form submission. Trainers Leadership will provide guidance to help Trainers choose 47 | what to share in the form, and when to select a meeting instead. 48 | 49 | ##### Trainer Alumni Status 50 | 51 | Active Trainers may elect to become inactive by requesting Trainer Alumni status at any time by contacting instructor-training@carpentries.org. Alumni may also submit re-activation requests to the same address. 52 | 53 | Trainer Alumni will not be allowed to: 54 | - serve in an Instructor role at Carpentries Instructor Training events 55 | - host teaching demonstrations 56 | - vote in Trainer community elections 57 | Exceptions may be made at the discretion of The Carpentries Core Team. To request permission to teach or host a demo, contact team@carpentries.org. 58 | 59 | Trainer Alumni may elect to: 60 | - continue to receive Topicbox Instructor Training emails & participate in conversations 61 | - continue to participate in the Slack private Trainers channel 62 | - receive an annual newsletter during agreement renewal with community updates and details on how to return to Active status 63 | - serve in a Helper role at Carpentries Instructor Training events 64 | 65 | A Trainer who wishes to return to Active status will have a different path depending on the amount of time they’ve been inactive: 66 | - 0-12 months: meet with Director of Workshops and Training to catch up on latest news & discuss plans for re-activating 67 | - more than 12 months: review Trainer Training curriculum, observe part of an Instructor Training workshop, and meet with Director of Workshops and Training to catch up and discuss plans, including re-introduction to the Trainer community via meetings or other arrangements 68 | 69 | 70 | 71 | 72 | -------------------------------------------------------------------------------- /topic_folders/instructor_training/index.rst: -------------------------------------------------------------------------------- 1 | Instructor Training 2 | ======================= 3 | .. toctree:: 4 | :maxdepth: 1 5 | 6 | For Trainers 7 | ------------------------- 8 | .. toctree:: 9 | :maxdepth: 1 10 | 11 | duties_agreement.md 12 | trainers_guide.md 13 | trainers_training.md 14 | trainer_coordinator.md 15 | email_templates_trainers.md 16 | 17 | Administrative Policies and Procedures 18 | --------------------------------------- 19 | .. toctree:: 20 | :maxdepth: 1 21 | 22 | cancellations_and_makeups.md 23 | tracking_checkout.md 24 | scheduling_training_events.md 25 | email_templates_admin.md 26 | 27 | For Member Organizations 28 | ------------------------- 29 | .. toctree:: 30 | :maxdepth: 1 31 | 32 | members_join.md 33 | -------------------------------------------------------------------------------- /topic_folders/instructor_training/members_join.md: -------------------------------------------------------------------------------- 1 | ## Email templates (Members) 2 | 3 | ### Trainee Recruitment Email (From Member Contact) 4 | 5 | Dear [ name ], 6 | 7 | We are excited to announce that [ site name ] has become a member of The Carpentries! 8 | 9 | [The Carpentries](https://carpentries.org) is a global community of volunteers who develop and teach interactive, hands-on workshops on computing and data skills, addressing basic training needs that are unmet in most disciplines. 10 | 11 | As part of our Carpentries membership, we can have [ number ] people from [ site name ] complete [The Carpentries’ Instructor Training program](https://carpentries.github.io/instructor-training/) and become certified Carpentries Instructors. 12 | 13 | Certified Instructors can co-teach [Carpentries workshops](https://carpentries.org/workshops/) here at [ site name ], helping us reach more people and build these skills across our community. In addition, Carpentries Instructors also have the opportunity to teach as part of a team at other institutions in The Carpentries network, meeting others with similar skills who enjoy sharing them. Hosting institutions cover travel and expenses for volunteer Instructors teaching workshops in-person. 14 | 15 | [Service as a Carpentries Instructor is a voluntary activity. This service can support existing work responsibilities in a variety of roles. It also represents an opportunity for career development. Carpentries Instructors are sought after in a variety of academic and professional teaching roles. Participation as an Instructor builds skills as well as a track record in teaching while expanding your professional network.] 16 | 17 | The Carpentries Instructor Training is primarily focused on evidence-based teaching practices and does not include technical skills training. It is expected that trainees will have or will develop the technical skills necessary to guide learners through the entry level curricula for one or more [Data Carpentry](https://datacarpentry.org/lessons/), [Library Carpentry](https://librarycarpentry.org/lessons/), or [Software Carpentry](https://software-carpentry.org/lessons/) workshops. 18 | 19 | If you are interested in being trained and certified as a Carpentries Instructor, please [ instructions to express interest or apply ] by [ deadline ]. 20 | 21 | Please get in touch with questions! 22 | 23 | 24 | ### Selected Trainee Information Email (From Member Contact for pooled training events) 25 | SUBJECT: Invitation to become a certified Carpentries Instructor 26 | 27 | Dear [ name ], 28 | 29 | Thank you for your interest in Carpentries Instructor Training! I am pleased to be able to offer you an opportunity to be trained through our Carpentries membership. 30 | 31 | Instructor Training events are held online via video conference, with schedule options including two full days or four half days. There are two steps to register: 32 | 33 | 1. Visit the [Instructor Training Calendar](https://carpentries.github.io/instructor-training/training_calendar) and select an event. Click on the link to Eventbrite and use the following code: [ CODE ]. Please do not share this code. 34 | 2. Complete The Carpentries’ [profile-creation form](https://amy.carpentries.org/forms/request_training/) using the same registration code: [ CODE ]. This allows The Carpentries to track your progress to certification. 35 | 36 | You will receive more details about your training from The Carpentries (instructor.training@carpentries.org) one week prior to your event. Be sure to look out for this email, and check your spam filters. There is a small amount of preparation expected before the training as well as three short tasks involved in certification. To learn more, see [Preparing for your Training](https://carpentries.github.io/instructor-training/#preparing-for-your-training). 37 | 38 | If anything comes up and you are no longer interested or able to participate, please let me know as soon as possible so that I can offer this seat to another person. 39 | 40 | We are all excited to grow our local Carpentries community and look forward to bringing you on board. 41 | 42 | If you have any questions, please contact me or The Carpentries Instructor Training team at instructor.training@carpentries.org. 43 | 44 | Best, 45 | 46 | [ sender name ] 47 | 48 | -------------------------------------------------------------------------------- /topic_folders/instructor_training/scheduling_training_events.md: -------------------------------------------------------------------------------- 1 | ### Scheduling Training Events 2 | 3 | Instructor Training events, bonus modules, and teaching demos are scheduled on a quarterly basis [as described here](../communications/guides/community_events.md). Four times a year, the Core Team will poll Trainers for their availability to teach Instructor Training. At the same time, Trainers will be asked to sign up to host teaching demos using Calendly. 4 | 5 | The Core Team creates a training calendar by matching up availability of Trainers. Once the training calendar is confirmed, it is posted [Member information page](https://carpentries.github.io/instructor-training/training_calendar/). Member sites each receive a unique registration code allowing their team members to sign up for these events. 6 | 7 | Teaching demos are listed on the [teaching demo etherpad](https://pad.carpentries.org/teaching-demos). Trainees can sign up for teaching demos at any time. 8 | -------------------------------------------------------------------------------- /topic_folders/instructor_training/trainer_coordinator.md: -------------------------------------------------------------------------------- 1 | ### Email templates 2 | 3 | #### Reminder to Trainers signed up for teaching demos 4 | 5 | Hi! 6 | 7 | You’re signed up to host a Carpentries teaching demo within the next two weeks! 8 | 9 | Please double check your time/date link on the [etherpad](https://pad.carpentries.org/teaching-demos) and confirm this one-hour time slot in your calendar. 10 | 11 | If you know in advance that you will have a conflict and are unable to host your demo, please email the Trainers list request a replacement. In most cases Core Team will fill in as needed if a replacement isn’t found. 12 | 13 | If you have a last-minute conflict, please use Slack as well as email to request a replacement. You may use "@here" to get 14 | the attention of all online group members as well as tagging Karen Word and Erin Becker in your request on Slack. If you are 15 | unable to get help in time, please contact your trainees to [cancel](https://docs.carpentries.org/topic_folders/instructor_training/trainer_coordinator.html#teaching-demo-cancelled-trainees) or reschedule. 16 | 17 | Instructions for hosting demos are [here](https://docs.carpentries.org/topic_folders/instructor_training/trainers_guide.html#running-a-teaching-demonstration). 18 | Please get in touch with questions, and enjoy your demo session! 19 | 20 | Best, 21 | 22 | [Name] 23 | 24 | 25 | 26 | #### Teaching demos without hosts 27 | 28 | Subject: Need hosts for upcoming teaching demos 29 | 30 | Dear Trainers, 31 | 32 | We are missing a Trainer to lead a session on [time and date UTC] [time and date link]. If you are available 33 | to cover this session, please add your name to the [etherpad](https://pad.carpentries.org/teaching-demos). Also, please 34 | reply to this thread so that others know this event is covered. 35 | 36 | 37 | Thank you! 38 | [Name] 39 | 40 | 41 | #### Teaching demo cancelled - trainees 42 | Subject: Teaching demo cancelled - please reschedule 43 | 44 | Dear checkout participant, 45 | 46 | Thank you for signing up to do your teaching demonstration at [time in UTC from Etherpad] [time and date link]. Unfortunately, we need to cancel this session due to [reason (optional)]. There are still spots open in upcoming sessions on the Etherpad, and I hope you will be able to find one that suits your schedule. 47 | 48 | I know it is hard to make time for these sessions, and I apologise for any inconvenience this has caused. I look forward to having you as a part of our Instructor community. 49 | 50 | Sincerely, 51 | [Name] 52 | 53 | 54 | #### Meeting notes available 55 | Subject: Trainer meetings notes 56 | 57 | Hi all, 58 | 59 | Thank you to all who attended our 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 would like to contine a conversation started at this meeting, please send a message to the Trainers list. 60 | 61 | Best, 62 | [Name] 63 | -------------------------------------------------------------------------------- /topic_folders/instructor_training/trainers_training.md: -------------------------------------------------------------------------------- 1 | ### Becoming a Trainer 2 | The Trainers group periodically accepts new members via application. New Trainers undergo an ten-week training program outlined below and agree to the [Trainer Agreement](duties_agreement.md). 3 | 4 | #### Trainers Training Program 5 | 6 | This outline represents the time commitment required for being an Instructor Trainer with The Carpentries. Please read through and check to see that you are able to commit to the responsibilities outlined below. 7 | 8 | Instructor Trainers agree to abide by the [Code of Conduct](http://www.datacarpentry.org/code-of-conduct/) in all communications and interactions with The Carpentries community. 9 | 10 | * Trainees who are not previously certified Instructors will be asked to concurrently pursue [Instructor certification](https://carpentries.org/become-instructor/) 11 | * Read [How Learning Works: Eight Research-Based Principles for Smart Teaching, 2nd Edition](https://www.wiley.com/en-us/How+Learning+Works%3A+Eight+Research-Based+Principles+for+Smart+Teaching%2C+2nd+Edition-p-9781119861690) by Marie K. Norman and discuss in book club format with Trainers-in-training. Preliminary reading schedule. 12 | * Time commitment: 1 hour per week for 10 weeks meetings; can miss one meeting; ~10 hours reading 13 | * Join Trainer meetings 14 | * Time commitment: 1 hour per month; review minutes for missed meetings 15 | * Shadow a teaching demonstration session (previously certified Instructors) 16 | * Time commitment: 1 hour one time 17 | * Shadow at least half a day of an online instructor training event (previously certified Instructors) 18 | * Time commitment: 4 hours one time 19 | * Agree to fulfill the duties outlined in the [Trainer Agreement](duties_agreement.md) for a period of 1 year. 20 | 21 | Total time commitment for previously certified Instructors to become certified Instructor Trainers: 22 | ~30 hours over 3 month period, including reading and prep time 23 | 24 | #### Trainers Training Reading Schedule 25 | 26 | For the most recent Trainer Training schedule and discussion questions, see the [Trainer Training Curriculum](https://carpentries.github.io/trainer-training/) 27 | 28 | 29 | -------------------------------------------------------------------------------- /topic_folders/lesson_development/cac-consult-rubric.md: -------------------------------------------------------------------------------- 1 | ## Curriculum Advisory Committee Consultation Rubric 2 | 3 | This rubric defines the division of responsibilities between The Carpentries Maintainers and The Carpentries Curriculum Advisory Committees (CACs). 4 | [Roles and responsibilities](https://docs.carpentries.org/topic_folders/lesson_development/curriculum_advisory_committees.html#roles-and-responsibilities) 5 | of Curriculum Advisory Committee members are documented elsewhere in this Handbook. 6 | [Current committee membership can be found on The Carpentries website](https://carpentries.org/curriculum-advisors/). 7 | 8 | ### Issues over which Maintainers have full authority and which do not need CAC involvement 9 | 10 | - Addition or removal of exercises 11 | - Reorganization of material within episodes 12 | - Addition or removal of callout boxes 13 | - Addition or removal of or changes to figures 14 | - Changes to episode timings 15 | - Changes to lesson text 16 | 17 | ### Issues about which Maintainers should notify the CAC 18 | 19 | - Any new versions of a dataset (either a new release or a modification of existing data) 20 | - Any major adjustments to the lesson (e.g., episode order, passwordless access) 21 | - Any updates to a lesson that Maintainers wish to share for informational purposes 22 | 23 | _What to do if your curriculum does not have an active CAC?_ Maintainers do not need to notify anyone when handling issues described in the list above. ([View the list of active CACs on The Carpentries website](https://carpentries.org/curriculum-advisors/).) 24 | 25 | ### Issues that may benefit from Maintainers consulting with the CAC, but over which Maintainers retain authority 26 | 27 | - Addition of a new library or package 28 | - Introduction of a new topic / learning objective (e.g., [adding file permissions to LC shell lesson](https://github.com/LibraryCarpentry/lc-shell/issues/63)) 29 | - Updates to software/packages that are minor versions (e.g., Python 3.7 -> 3.8) when the new version is backwards compatible with current version 30 | - Additions of experimental features (e.g., `git checkout` → `git restore` / `git switch`) 31 | - Any change to a lesson that impacts the content/scope of another lesson in the curriculum 32 | - For Incubator lessons - Review of a lesson outline where lesson developers would like the lesson to be considered for eventual adoption into 33 | a Lesson Program’s official curriculum 34 | - Issues which are not covered anywhere else in this rubric 35 | 36 | _What to do if your curriculum does not have an active CAC?_ Maintainers may consult the Curriculum Team ([by email](mailto:curriculum@carpentries.org) or tagging the `core-team-curriculum` team on the relevant GitHub issue/pull request/discussion) and/or the wider community when handling issues described in the list above. For example, where more perspectives are needed, it may be helpful to use [relevant communication channels](https://carpentries.org/connect/) to call for input and feedback from the Instructor community. ([View the list of active CACs on The Carpentries website](https://carpentries.org/curriculum-advisors/).) 37 | 38 | ### Issues for which Maintainers must seek CAC approval 39 | 40 | - Replacing the dataset used in the lesson with a different dataset. This does not include cases in which the data being used in the lesson is being updated to a 41 | new version (e.g., a new data release) or is modified to make it more suitable for the teaching environment 42 | (e.g., introduction of messiness to the dataset). 43 | - Changing the software being used in the lesson. This does not include updating to a new stable, backwards-compatible version of the 44 | existing software (e.g., Python 3.6 → 3.7.x), but does include: 45 | - Updating to a non-backwards compatible version of existing software (e.g., Python 2.x → 3.x, R 3.x → 4.x) 46 | - Change in plotting library (e.g., Matplotlib, Plotly, Seaborn, ggplot, Altair) 47 | - Change in libraries / packages taught (i.e., removal or replacement) 48 | - Change in SQL dialect (e.g., SQLite, MySQL, PostgreSQL, MSSQL Server) 49 | - Change in IDE being used to teach the lessons (RStudio, Jupyter Notebook) 50 | - Change from GitHub as remote hosting platform to a different remote hosting platform, e.g., GitLab 51 | - Removal of an entire episode’s worth of content 52 | - Change in lesson infrastructure (e.g., moving Genomics lessons from AWS to CyVerse) 53 | - Retirement of a lesson (e.g., MATLAB, Mercurial) 54 | - Addition of a new lesson to the core curriculum (e.g., adding Julia as an alternative to R / Python) 55 | - Adding or removing prerequisites from a lesson (for curricula with multiple lessons) 56 | - Promotion or graduation of a lesson from alpha to beta to stable. Decisions on approval can be based on recommendations from the Curriculum Team, 57 | CAC member involvement in lesson pilot workshops, and/or open peer review of lessons in The Carpentries Lab. 58 | 59 | _What to do if your curriculum does not have an active CAC?_ Maintainers should consult the Curriculum Team ([by email](mailto:curriculum@carpentries.org) or tagging the `core-team-curriculum` team on the relevant GitHub issue/pull request/discussion) when handling issues described in the list above. The Curriculum Team will coordinate and facilitate a discussion among community members likely to be affected by the changes (other Maintainers, Instructors, etc). ([View the list of active CACs on The Carpentries website](https://carpentries.org/curriculum-advisors/).) 60 | -------------------------------------------------------------------------------- /topic_folders/lesson_development/curriculum_onboarding.md: -------------------------------------------------------------------------------- 1 | ## Creating Curriculum Onboarding Materials for Instructors 2 | 3 | ### For Curriculum Developers 4 | 1. Make a copy of [the Curriculum Onboarding presentation template](https://docs.google.com/presentation/d/11owgvSWIIPEDIrLqEqtSrN-5gtgxxEHxkEeOJxbzh2E/edit) 5 | - If preparing an onboarding session for a Data Carpentry, Library Carpentry, or Software Carpentry curriculum, you can use one of the following lesson program-specific templates: 6 | - [Data Carpentry curriculum onboarding template](https://docs.google.com/presentation/u/0/d/1VTBWHL5BHPfZ0Ejiuwk5lUGFUGaLTujTs_OfybrEZrA/edit) 7 | - [Library Carpentry curriculum onboarding template](https://docs.google.com/presentation/u/0/d/1FCFfeH7wnv5sg2OI-ykzDafRdyDPkVhiyPdCSESEMo8/edit) 8 | - [Software Carpentry curriculum onboarding template](https://docs.google.com/presentation/u/0/d/1U6F6hzxH2uGouS9wfqny9f6rPrOXM7KLWsyKUDawEPw/edit) 9 | 2. Edit the presentation by following the guidance in the template. 10 | - Use any template slides that you want to. You are not required to stick rigidly to the structure and layout provided in the template. 11 | - Do not be afraid to add images and other visuals to make the presentation more engaging - just make sure they are [compatible with the CC-BY license](https://creativecommons.org/faq/#can-i-combine-material-under-different-creative-commons-licenses-in-my-work) of the presentation and include the appropriate attribution information. 12 | - Refer to [the Accessible Presentation Guidelines](https://docs.google.com/document/d/1xc6idZHp86RNfcm6f-D2LltKHCPjXrGuHftCuYWedKg/edit) as you prepare the presentation. 13 | 3. (Optional but recommended) Prepare a script for the presentation. 14 | - This could be placed in the presenter notes of the onboarding slides, or a separate text document (e.g. a Google Doc, a CodiMD document). 15 | - A script can help you make a smooth presentation, but also doubles up as a transcript that can be added to the video on YouTube and facilitate closed captioning. 16 | - To create a new CodiMD document, visit https://codimd.carpentries.org and click the "New note" (if logged in) or "New guest note" button. Use the pencil or split window buttons near the top-left to switch to editing and split-screen mode. 17 | 4. When the presentation is ready, record a video presenting the onboarding. 18 | - Use whatever software you are most comfortable with to record the video. 19 | - You can use Zoom to record the presentation: 20 | - use the screen sharing feature to share the slides as you present. 21 | - use the record feature to record the presentation. 22 | - consider recording multiple "takes" (runs through the presentation). 23 | - to make it easier to identify the breaks between takes when editing the video, hold an object (e.g. a piece of paper) in front of the camera briefly between each repeat. 24 | - Although not required, you could present the onboarding in a community discussion-type event and record that meeting (with participants' permission). 25 | - A curriculum onboarding presentation should be no more than 45 minutes long. 26 | 5. Share the recording, a link to the slides, and a copy of the script (if you have one) with The Carpentries Curriculum Team (curriculum@carpentries.org), who will edit it and publish in the [Curriculum Onboarding Videos playlist](https://www.youtube.com/watch?v=gfaNFaKIOrY&list=PLXLapl_LKb4e73Vf2e3rS2q2TDJ7oh_DX) on our YouTube channel. 27 | 28 | ### For Core Team 29 | 30 | 1. Review the video and check the following: 31 | - The presentation and recording conforms to [The Carpentries Code of Conduct](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html) 32 | - The quality of the sound and video is sufficient 33 | - The presentation includes each of the sections laid out in [the onboarding presentation template](https://docs.google.com/presentation/d/11owgvSWIIPEDIrLqEqtSrN-5gtgxxEHxkEeOJxbzh2E/edit) 34 | - What You Can Expect From This Onboarding 35 | - Curriculum Overview 36 | - Overview of Lessons (if curriculum contains multiple lessons) 37 | - Common Challenges 38 | - Acknowledgements 39 | - The length of the onboarding video is in the range of 15-45 minutes 40 | 2. Upload video to YouTube as a private video, let YouTube auto-generate the captions 41 | 3. After captions are ready (usually done in 24 hours), download the transcript file 42 | 4. Edit the transcript, using the script for reference if it was shared by the video's creator(s), and upload it back to the video 43 | 5. When you are ready to make the video public, add it to the Curriculum Onboarding playlist. This should automatically change the visibility setting. 44 | 6. Announce the availability of the video to the community on general Slack channel, instructors TopicBox list, in newsletter, link to it from the Instructor Notes page of the relevant lesson site(s) 45 | -------------------------------------------------------------------------------- /topic_folders/lesson_development/index.rst: -------------------------------------------------------------------------------- 1 | Lesson Development 2 | ======================= 3 | 4 | For more information on lesson development with The Carpentries, please visit `The Carpentries Curriculum Development Handbook `_. 5 | 6 | .. toctree:: 7 | :maxdepth: 2 8 | :glob: 9 | 10 | curriculum_advisory_committees.md 11 | curriculum_onboarding.md 12 | lesson_infrastructure_subcommittee.md 13 | lesson_sprint_recommendations.md 14 | lesson_pilots.md 15 | lesson_release.md 16 | spotlight.md 17 | -------------------------------------------------------------------------------- /topic_folders/lesson_development/lesson_infrastructure_subcommittee.md: -------------------------------------------------------------------------------- 1 | ## Lesson Infrastructure Subcommittee 2 | 3 | Members of the Lesson Infrastructure Subcommittee serve as 4 | Maintainers for [The Carpentries lesson template](https://github.com/carpentries/styles) and 5 | [its documentation](https://github.com/carpentries/lesson-example), as 6 | well as for The Carpentries [workshop template](https://github.com/carpentries/workshop-template). 7 | As Maintainers, they also 8 | follow the [Maintainer Guidelines](../maintainers/maintainers.md). 9 | -------------------------------------------------------------------------------- /topic_folders/lesson_development/lesson_release.md: -------------------------------------------------------------------------------- 1 | ### Release Process and Schedule 2 | 3 | Lesson releases are 4 | named by the year and month they happen, e.g., `2016.05`. 5 | 6 | 1. Each lesson lives in the `gh-pages` branch of its own repository. 7 | 2. When a release is made, 8 | the lesson Maintainer(s) create a branch named after the release, 9 | e.g., `2016.05`. 10 | 3. A Release Maintainer generates HTML pages for that release and adds them to the branch. 11 | 4. If there isn't already a directory for that release in the [`swc-releases` repository][swc-releases], 12 | the Release Maintainer creates one 13 | and adds an `index.html` page to it. 14 | 5. The Release Maintainer adds a submodule to the release directory of [`swc-releases`][swc-releases] 15 | that points to the newly-created release branch of the lesson. 16 | 17 | ### Lesson Release Checklist 18 | 19 | **For each lesson release, copy this checklist to an issue and check off 20 | during preparation for release** 21 | 22 | Scheduled Freeze Date: YYYY-MM-DD 23 | Scheduled Release Date: YYYY-MM-DD 24 | 25 | Checklist of tasks to complete before release: 26 | 27 | - [ ] check that the learning objectives reflect the content of the lessons 28 | - [ ] check that learning objectives are phrased as statements using action words 29 | - [ ] check for typos 30 | - [ ] check that the live coding examples work as expected 31 | - [ ] if example code generates warnings, explain in narrative and instructor notes 32 | - [ ] check that challenges and their solutions work as expected 33 | - [ ] check that the challenges test skills that have been seen 34 | - [ ] check that the setup instructions are up to date (e.g., update version numbers) 35 | - [ ] check that data is available and mentions of the data in the lessons are accurate 36 | - [ ] check that the instructor guide is up to date with the content of the lessons 37 | - [ ] check that all the links within the lessons work (this should be automated) 38 | - [ ] check that the cheat sheets included in lessons are up to date (e.g., RStudio updates them regularly) 39 | - [ ] check that language is clear and free of idioms and colloquialisms 40 | - [ ] make sure formatting of the code in the lesson looks good (e.g. line breaks) 41 | - [ ] check for clarity and flow of narrative 42 | - [ ] update README as needed 43 | - [ ] fill out “overview” for each module - minutes needed for teaching and exercises, questions and learning objectives 44 | - [ ] check that contributor guidelines are clear and consistent 45 | - [ ] clean up files (e.g. delete deprecated files, insure filenames are consistent) 46 | - [ ] ensure that repository is tagged with (at minimum) the following topics: "lesson", "stable", the name of its lesson program (hyphenated, e.g. "data-carpentry"), and the human language it is written in (e.g. "english") 47 | - [ ] update the release notes (NEWS) 48 | - [ ] tag release on GitHub 49 | 50 | [swc-releases]: https://github.com/swcarpentry/swc-releases/ 51 | -------------------------------------------------------------------------------- /topic_folders/lesson_development/lesson_sprint_recommendations.md: -------------------------------------------------------------------------------- 1 | ## Lesson Sprint Recommendations 2 | 3 | One way of making progress and encouraging collaboration on the development 4 | of a lesson is to organise a dedicated event such as a co-working session 5 | or a lesson development sprint. 6 | 7 | Members of The Carpentries community collaborated to create 8 | a set of recommendations for anyone planning to run such an event. 9 | [These recommendations are presented as an appendix to The Carpentries Curriculum Development Handbook](https://cdh.carpentries.org/lesson-sprint-recommendations.html). 10 | -------------------------------------------------------------------------------- /topic_folders/lesson_development/spotlight.md: -------------------------------------------------------------------------------- 1 | ## The Carpentries Incubator Lesson Spotlight 2 | 3 | The Incubator Lesson Spotlight is a regular feature in 4 | The Carpentries blog and newsletter, 5 | highlighting a lesson currently under community development. 6 | The purpose of the Spotlight series is to raise the visibility of that lesson 7 | among the broader community, 8 | and to encourage community members to contribute to 9 | the further development of that lesson. 10 | 11 | Any lesson in [The Carpentries Incubator][incubator] is eligible to be included 12 | in the series, regardless of the stage of development that lesson is currently in. 13 | It is a good way for lessons in the early stages of development 14 | to attract new collaborators, 15 | and for those in later stages 16 | to invite others to informally review the lesson 17 | and to try teaching the material. 18 | 19 | **If you are a developer of a lesson in The Carpentries Incubator, 20 | you can submit your lesson to be featured in 21 | the series by filling in 22 | [the Incubator Lesson Spotlight content submission form][ils-form]**. 23 | 24 | In the form, you will be asked to provide 25 | some basic details of the lesson and your collaborators, 26 | some information about the objectives and the history of the lesson, 27 | and a description of how The Carpentries community can best contribute 28 | to its ongoing development. 29 | This information will be used by the Core Team 30 | to create a post for [The Carpentries blog](https://carpentries.org/blog/), 31 | an item for the [Carpentries Clippings newsletter](https://carpentries.org/newsletter/), 32 | and related posts to social media. 33 | When the blog post has been drafted, 34 | a pull request will be opened to add that post to the website. 35 | You will be tagged for a (optional) review of this pull request 36 | before it is published. 37 | 38 | Incubator Lesson Spotlight features are intended to raise the visibility of 39 | the lesson and to encourage other community members to get involved in its 40 | further development, 41 | so it is best to think about how you can prepare your lesson for new contributors 42 | before the feature is published. 43 | This might mean labelling existing issues 44 | (e.g. to appear on [the Help Wanted page][help-wanted]) 45 | or creating new ones, 46 | making sure that your CONTRIBUTING.md is up-to-date, 47 | and/or planning publication of the Spotlight feature to fit with a relatively quiet 48 | period in your schedule so that you can respond promptly 49 | to any new issues and pull requests. 50 | 51 | [help-wanted]: https://carpentries.org/help-wanted-issues/ 52 | [ils-form]: https://docs.google.com/forms/d/e/1FAIpQLScJimGMtzqAFE-Tii-LvbfGZqtKj0OC4ken7_Qdlta8uZXAUA/viewform 53 | [incubator]: https://github.com/carpentries-incubator/ 54 | -------------------------------------------------------------------------------- /topic_folders/maintainers/contributing.md: -------------------------------------------------------------------------------- 1 | ## Contributing to Carpentries Lessons 2 | 3 | Lesson Maintainers actively maintain all Carpentries lessons. 4 | However, contributions are always welcome by all community members. 5 | Novice contributors can read the [Instructions for contributing to The Carpentries' lesson materials 6 | using graphical or command line interfaces with git and GitHub][novice-guide] developed by Carpentries Instructors. 7 | 8 | The [Help Wanted page][hwp] lists issues in need of attention 9 | and is a good place to find out where your contributions are most needed. 10 | 11 | [novice-guide]: https://github.com/carpentries-incubator/swc_github_flow/blob/HEAD/for_novice_contributors.md 12 | [hwp]: https://carpentries.org/help-wanted-issues 13 | -------------------------------------------------------------------------------- /topic_folders/maintainers/github_topics.md: -------------------------------------------------------------------------------- 1 | ## GitHub Topics for Lesson Repos 2 | 3 | Across The Carpentries lesson programs, lesson repos are assigned [topics](https://github.blog/2017-01-31-introducing-topics/). From GitHub: 4 | 5 | > *Topics are labels that create subject-based connections between GitHub repositories and let you explore projects by type, technology, and more.* 6 | 7 | Following a [maintainer discussion](https://github.com/carpentries/maintainer-RFCs/issues/5), The Carpentries has begun assigning topics to all lesson repositories. An overview of how these topics are assigned is in [this Google document](https://docs.google.com/spreadsheets/d/1ftV5L2C01aeHrMTWG0WWVm3MSeHMFZOEKw2a7ing138/edit#gid=0). 8 | 9 | -------------------------------------------------------------------------------- /topic_folders/maintainers/index.rst: -------------------------------------------------------------------------------- 1 | Lesson Maintenance 2 | ======================= 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | maintainers.md 9 | github_labels.md 10 | github_topics.md 11 | email_templates.md 12 | contributing.md 13 | 14 | -------------------------------------------------------------------------------- /topic_folders/policies/coc-membership-agreement.md: -------------------------------------------------------------------------------- 1 | # Membership Agreement for the Code of Conduct (CoC) Committee 2 | 3 | This document describes the responsibilities that the members of the Code of Conduct committee (CoCc) must agree to meet in order to fulfill the requirements of their roles on the committee. 4 | 5 | > *The committee is what turns a code of conduct from a written document into meaningful action.* 6 | > Valerie Aurora, FrameShift Consulting 7 | 8 | ## Core Membership Agreement: 9 | 10 | The main purpose of the CoCc is to: establish, maintain and uphold the Code of Conduct; educate members of the community of policies and behaviors that can help create a more inclusive and welcoming environment; and protect all members from harm in community spaces. 11 | 12 | In order to uphold the CoC, the CoCc members will: 13 | 14 | * support the objectives and mission of The Carpentries by abiding by its CoC and other policies and procedures. 15 | * learn about the [Code of Conduct](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html#) and [reporting guidelines](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html#incident-reporting-guidelines), and as CoC advocates, bring awareness of it into any Community spaces that they are part of. 16 | * understand and be comfortable to act on CoC related reports as per the [enforcement guidelines](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html#enforcement-manual) put in place for the relevant community spaces. 17 | * actively help develop and maintain existing and new documents to facilitate the work of the [CoCc](https://github.com/carpentries/docs.carpentries.org/tree/main/topic_folders/policies). 18 | * avoid *conflicts of interest* [1] when processing CoC related reports. Failure to declare a conflict of interest may be considered a breach of the CoC. 19 | * maintain the confidentiality of any reported incidents, the identity of persons involved and discussions that take place within the committee. 20 | * not make any comments about any matters that they have been informed of as part of their duties as a CoCc member unless authorized to do so. 21 | * hold themselves accountable for their responsibilities as trustees and understand that they are expected to follow through on their commitments. 22 | * respect and promote diversity, equity, and inclusion in the community and act in the best interests of the Carpentries community impartially, putting aside any individual affiliations such as organizations or other Carpentries committees, and personal biases. 23 | 24 | 25 | ## Further Roles and Responsibilities: 26 | 27 | In addition to the core membership agreement, CoCc members will be required to: 28 | 29 | * support the committee chair and the designated Core Team liaison in collective decision making. In order to do so, they will prepare fully for meetings, which will include reading reports and related documents carefully, querying anything they do not understand, thinking through issues before meetings and completing any tasks assigned to them. 30 | * attend in the order of 75% of all *CoCc Business meetings* [2]. In these meetings, CoCc members will actively engage in discussion, voting and contributing in a constructive way, listening carefully, challenging sensitively and avoiding conflict. 31 | * promptly respond to emails, or, if they realize they will be out of touch for a while, inform the committee chair. 32 | * participate in any training that is organized to support the work of the committee, and to responsibly use any technical solutions that the CoCc is asked to use in order to maintain the security and privacy of personal information conveyed to the committee. 33 | 34 | 35 | ### [1] Note on *Conflicts of Interest*: 36 | 37 | A conflict of interest is a situation where a member of the CoCc could be perceived to not act in the interest of the Carpentries and the members of the community. Such situations can, for instance, occur when the members have close ties with one of the parties in a CoC incident (e.g. family relationships, close friendships, business ties, or even personal considerations). Such conflicts of interest may make it difficult to fulfill their duties impartially. 38 | 39 | 40 | If any member of the committee happens to face a conflict of interest while handling a case, they are expected to: 41 | * inform the chair of the CoCc and/or the full committee of the conflict of interest, 42 | * not be involved in the case, and if required, temporarily leave their position as a CoCc member to avoid any bias. 43 | 44 | 45 | ### [2] Note on the *CoCc Meetings*: 46 | 47 | The committee conducts two types of meetings: 48 | 49 | * **Business meetings**: these are meetings where we discuss the status of current documents, issues brought to us by the community and other CoC related matters. 50 | * **Incident report related meetings**: in these meetings those that have volunteered to decide the course of action for a reported incident meet and discuss the situation. To decide on an issue, a minimum of 3 members must participate, thus not all members need to participate in every case. 51 | 52 | 53 | ### Onboarding of new committee members: 54 | 55 | New committee members will be included in committee discussions only after they have fulfilled the onboarding requirements specified by the CoCc and The Carpentries Executive Council. 56 | 57 | 58 | ### Leaving the Committee: 59 | 60 | * If a CoCc member wishes to leave the committee at any time, they will inform the Committee chair in advance (giving enough notice to hand-over their responsibility) in writing, stating their reasons for leaving. 61 | * Breach of any part of the CoC by any CoCc member may result in a fair procedure being put in motion that may result in them being asked to resign from the CoCc. Should this happen they will be given the opportunity to be heard. In the event they are asked to resign from the committee, they will accept the majority decision of the committee in this matter and resign at the earliest opportunity. 62 | 63 | 64 | ## Relevant information: 65 | 66 | * CoC committee: [https://carpentries.org/coc-ctte](https://carpentries.org/coc-ctte/) 67 | * [CoC Handbook Documentation](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html) 68 | 69 | 70 | ## References: 71 | 72 | * This document is largely based on “[The Code of Good Governance, DIY Committee Guide](http://www.diycommitteeguide.org/sites/default/files/2016-03/code-of-good-governance-2016.pdf), 2016” http://www.diycommitteeguide.org/download/example-code-of-conduct-volunteer-now 73 | * [How to Respond to Code of Conduct Reports](https://files.frameshiftconsulting.com/books/cocguide.pdf), Valerie Aurora and Mary Gardiner, 2018 74 | 75 | -------------------------------------------------------------------------------- /topic_folders/policies/coc-onboarding.md: -------------------------------------------------------------------------------- 1 | # CoCc Onboarding procedures for new members 2 | 3 | Any voting member of the Carpentries community, as defined in The Carpentries bylaws, is eligible to express their interest to volunteer to sit on the [Code of Conduct Committee (CoCc)](https://carpentries.org/coc-ctte/) (CoCc). 4 | The Committee will invite new members every year through open calls and from available volunteers. When a current member needs to step down quickly/urgently, the Onboarding team will open an extraordinary call for volunteers. 5 | 6 | The [template document](https://docs.google.com/document/d/12GtF4xbnfm0aopKZAUOaFhKJ1OB1SOj09PHBbxY55kk/edit?usp=sharing)) provides a set of questions used in the previous calls for application. These questions can be updated or changed by the Code of Conduct committee for subsequent calls as needed. 7 | 8 | Application review is carried out by the onboarding team members, and applicants are selected based on their previous experience and motivation to support the work of CoCc in the future. 9 | The onboarding team brings their decision to be discussed by the rest of the CoCc. The rest of the CoCc flags issues or concerns and confirms the selection when they agree with the initial decision. 10 | New members are invited to sit in the CoCc as full members upon their onboarding as described below. 11 | 12 | ## General onboarding procedure: 13 | 14 | Members invited or elected as Staff/Core Team and EC liaison, as well as selected through open calls for volunteers, will become full members through the following onboarding process: 15 | 16 | * Read [The Carpentries CoC document](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html) 17 | * Review CoC [process flow diagram](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html#process-flow-diagram) 18 | * Read first chapter of [How to respond to Code of Conduct Reports](https://drive.google.com/file/d/1B3rC9fwSDDVzrJ-e-vCO5O4Q3ndfzy47/view), a book by Valerie Aurora, based on a short guide written by Mary Gardiner. 19 | * Read the four CoC policy documents 20 | * [Incident Response Guidelines](https://docs.carpentries.org/topic_folders/policies/incident-response.html) 21 | * [Incident Reporting Guidelines](https://docs.carpentries.org/topic_folders/policies/incident-reporting.html) 22 | * [Incident Response Procedure](https://docs.carpentries.org/topic_folders/policies/enforcement-guidelines.html) 23 | * [Termed Suspension Guidelines](https://docs.carpentries.org/topic_folders/policies/termed-suspension.html) 24 | * Review the [membership agreement](https://docs.carpentries.org/topic_folders/policies/coc-membership-agreement.html) (includes confidentiality agreement) 25 | * Review the [CoCc Governance Document](https://docs.carpentries.org/topic_folders/policies/coc-governance.html) 26 | * Participate in an onboarding meeting: Bring questions, challenge our processes and finish onboarding. 27 | * Send an acknowledgment of the [membership agreement](https://docs.carpentries.org/topic_folders/policies/coc-membership-agreement.html) by email to the committee . 28 | 29 | ### Access to CoCc resources 30 | 31 | The Onboarding committee will file a GitHub Issue to update the composition of the CoCc (onboarded/offboarded members). The Staff/Core Team Liaison will add the new members to and remove previous members from the: 32 | * Mailing list (coc@carpentries.org) 33 | * Google drive folder (non-restricted for all members) 34 | * Google drive folder (restricted for chairs and staff liaison) 35 | * Update CoCc web page with bio: https://carpentries.org/coc-ctte/ 36 | * Slack Channels: Private for CoCc for discussion and updates 37 | 38 | #### Information management 39 | 40 | * New members need to not have access to previous incidents 41 | * Staff liaison should be responsible for maintaining previous records 42 | * Only the Staff Liaison and the CoCc chair have access to the restricted Google Drive where reports are received and stored - and names and information of the reporters and reportees are maintained. They are responsible for communicating that with the rest of the committee. 43 | * All notes are maintained in another Google drive that are accessible for all CoCc members. Report handling meeting notes are taken with pseudonymised the reporter and reportee names. 44 | * All transparency reports are released periodically on GitHub repository for Executive Council, maintained under The Carpentries GitHub organisation: https://github.com/carpentries/executive-council-info/tree/main/code-of-conduct-transparency-reports. 45 | * All CoCc policies are released on The Carpentries Handbook: https://docs.carpentries.org/topic_folders/policies/index_coc.html. 46 | 47 | 48 | ### Next steps 49 | 50 | * The Carpentries Staff Team and Executive Council (EC) will be notified by the onboarding team members about any new members 51 | * All CoCc members will be eligible to join general discussion and business meetings upon their onboarding 52 | * New Staff/Core Team Liaison will be included in committee discussions only after they have fulfilled the onboarding requirements specified by the CoCc and had a handover meeting with the previous Team Liaison stepping down from this role 53 | * New EC Liaison will be included in committee discussions only after they have fulfilled the onboarding requirements specified by the CoCc and had a handover meeting with the previous EC Liaison stepping down from this role 54 | * All members will follow the [membership agreement](https://docs.carpentries.org/topic_folders/policies/coc-membership-agreement.html) (includes confidentiality agreement) and the [governance procedure](https://docs.carpentries.org/topic_folders/policies/coc-governance.html#) closely 55 | 56 | 57 | ## Follow-up Procedures 58 | 59 | ### Mock incident-based training as ongoing process 60 | 61 | Upon onboarding of new members, the designated CoCc members (specific area leads) will hold discussion on the following content as part of the CoCc business meeting: 62 | * Discussion based on selected theories from ([How to respond to Code of Conduct Reports](https://drive.google.com/file/d/1B3rC9fwSDDVzrJ-e-vCO5O4Q3ndfzy47/view)) - Aurora and Gardner. 63 | * Specific CoC policy and enforcement documents 64 | * Mock-scenario or external incident-based discussions for exercise 65 | 66 | Currently, the CoCc training team is responsible for holding training and discussion sessions as part of the continuing CoC committee development. 67 | -------------------------------------------------------------------------------- /topic_folders/policies/cookie-policy.md: -------------------------------------------------------------------------------- 1 | # The Carpentries Cookie Policy 2 | 3 | 4 | **Last updated:** 2022-01-15 5 | 6 | To make our sites work properly, we sometimes place small data files called cookies on your device. A cookie is a small text file that a website saves on your computer or mobile device when you visit the site. It enables the website to remember your actions and preferences (such as login or other preferences) over a period of time, so you do not have to keep re-entering them whenever you come back to the site or browse from one page to another. 7 | 8 | We have put our cookies into the following categories to make it easier for you to understand why we need them: 9 | 10 | 1. **Strictly necessary:** These are used to help make our websites work 11 | efficiently, provide security features on our websites, and provide services 12 | that are required to provide the services you expect from our websites. 13 | 2. **Performance/analytics:** These are used to analyze the way our websites 14 | work and how we can improve it. 15 | 3. **Functionality:** These help to enhance your experience by remembering 16 | choices you have made concerning the features of the websites (e.g., 17 | username, language, region you are in). 18 | 19 | While we intend to limit third-party cookies, there might be pages on our 20 | websites that may set third party cookies. For instance, when we embed content 21 | from another site (e.g., a video), or when we use an external logging system 22 | (e.g., you log into AMY using your GitHub credentials) they may set a cookie. We 23 | try to limit these situations, but cannot always control how these sites use 24 | cookies. 25 | 26 | ## Cookies and You 27 | 28 | If you choose not to enable cookies, you will still be able to browse our 29 | websites, but it will restrict some of the functionality of our websites or what 30 | you can do. 31 | 32 | ### Matomo 33 | 34 | We use [Matomo](https://matomo.org/) for our site analytics. We set it up to 35 | reduce the amount of personal information it collects about your visit and no 36 | cookies are used. It is enabled on , 37 | , , 38 | , , 39 | , , 40 | , and some of our sub-domains including 41 | . 42 | 43 | ### Other cookies 44 | 45 | **Cookies on , , , ** 46 | 47 | Cookies on these sites are only first-party cookies that are strictly necessary or improve the functionality of the sites. 48 | 49 | 50 | ## Updating this cookie notice 51 | 52 | We will update the list of cookies we use from time to time. If we make any changes, we will update the “Last Updated” date at the top of this document. 53 | 54 | 55 | ## Controlling your cookies 56 | 57 | You can control cookies in your browser to enable or disable them. If you wish 58 | to restrict or block the cookies which are set by any website, you should do 59 | this through the web browser settings for each web browser you use, on each 60 | device you use to access the internet. 61 | -------------------------------------------------------------------------------- /topic_folders/policies/core-team/professional-development-policy.md: -------------------------------------------------------------------------------- 1 | ### Carpentries Professional Development Policy 2 | 3 | **Core Team Professional Development Fund** 4 | 5 | The Carpentries Core Team have access to a professional development fund (hereon after "Core Team PDF") of $1000/year for each full time employee. 6 | 7 | **What Activities are Eligible?** 8 | 9 | The Core Team PDF makes available funds for the purpose of supporting Core Team participation in professional development programs such as workshops and seminars and research activities. 10 | 11 | Requests must demonstrate how the activity for which funding is sought supports the: 12 | 13 | 1. Current Strategic Plan for The Carpentries; 14 | 1. Employee's Individual Professional Development: 15 | - Through improving performance in the employee’s current position; or 16 | - Through improving the employee’s qualifications for career opportunities that may arise within The Carpentries 17 | 18 | When applying for reimbursement for professional development materials or activities, Core Team should provide a short description and justification of the expenditure. For large expenses (>$200), Core Team should seek prior approval from the Finance subcommittee. 19 | -------------------------------------------------------------------------------- /topic_folders/policies/dmca-policy.md: -------------------------------------------------------------------------------- 1 | # The Carpentries DMCA Policy 2 | 3 | **Last updated:** 2022-01-15 4 | 5 | We respect the copyright and other intellectual property rights of others and 6 | expect users of our website and application (collectively, the "Services") to do 7 | the same. In accordance with the United States Digital Millennium Copyright Act 8 | (the "DMCA") and other applicable law, we have a policy of terminating, in 9 | appropriate circumstances and at our sole discretion, users of the Service who 10 | are deemed to be repeat infringers. We also may, in our sole discretion, limit 11 | access to the Service and terminate the accounts of any users of the Service who 12 | infringe any intellectual property rights of others, whether or not there is any 13 | repeat infringement. See our Terms for more information. 14 | 15 | ## Notification of Alleged Copyright Infringement 16 | 17 | If you believe that content available on or through our Services infringes one 18 | or more of your copyrights, please immediately notify our Copyright Agent by 19 | mail, email or faxed notice (“Notification”) providing the information described 20 | below, which Notification is pursuant to DMCA 17 U.S.C. § 512(c)(3). A copy of 21 | your Notification will be sent to the person who posted or stored the material 22 | addressed in the Notification. Please be advised that pursuant to federal law 23 | you may be held liable for damages if you make material misrepresentations in a 24 | Notification. Thus, if you are not sure that content located on or linked to by 25 | our Website infringes your copyright, you should consider first contacting an 26 | attorney. 27 | 28 | **All Notifications should include the following:** 29 | 30 | * A physical or electronic signature of a person authorized to act on behalf of 31 | the owner of an exclusive right that is allegedly infringed. 32 | * Identification of the copyrighted work claimed to have been infringed, or, if 33 | multiple copyrighted works at a single online website are covered by a single 34 | notification, a representative list of such works at that website. 35 | * Identification of the material that is claimed to be infringing or to be the 36 | subject of infringing activity and that is to be removed or access to which is 37 | to be disabled, and information reasonably sufficient to permit us to locate 38 | the material (e.g. the URL link of the material). 39 | * Information reasonably sufficient to permit us to contact the complaining 40 | party, such as the name, account name, address, telephone number, and e-mail 41 | address at which the complaining party may be contacted. 42 | * A statement that the complaining party has a good faith belief that use of the 43 | material in the manner complained of is not authorized by the copyright owner, 44 | its agent, or the law. 45 | * A statement that the information in the notification is accurate, and under 46 | penalty of perjury, that the complaining party is authorized to act on behalf 47 | of the owner of an exclusive right that is allegedly infringed. 48 | 49 | Submit your notice to our designated DMCA agent by mail or email as set forth 50 | below: 51 | 52 | * Email: [privacy@carpentries.org](mailto:privacy@carpentries.org) 53 | * Mailing address: 54 | The Carpentries c/o Community Initiatives 55 | 1000 Broadway, Suite #480 56 | Oakland, CA 94607 57 | USA 58 | 59 | Please note that you may be liable for damages, including court costs and 60 | attorney's fees, if you materially misrepresent that content on the Services is 61 | copyright infringing. 62 | 63 | Upon receiving a proper notification of alleged copyright infringement, we will 64 | remove or disable access to the allegedly infringing material and promptly 65 | notify the alleged infringer of your claim. We also will advise the alleged 66 | infringer of the DMCA statutory counter-notification procedure described below 67 | by which the alleged infringer may respond to your claim and request that we 68 | restore this material. 69 | 70 | Please note that our furnishing your claim to the alleged infringer will include 71 | the personal information you provide in your notification, which the alleged 72 | infringer may use to contact you directly. As such, by submitting a notification 73 | of alleged copyright infringement, you consent to disclosure of your information 74 | in the aforementioned manner. 75 | 76 | ## Counter Notification 77 | 78 | If you believe your copyrighted material has been removed from the Services as a 79 | result of a mistake or misidentification, you may submit a written 80 | counter-notification letter to us. To be an effective counter-notification under 81 | the DMCA, your letter must include substantially the following: 82 | 83 | * Identification of the material that has been removed or disabled and the 84 | location at which the material appeared before it was removed or disabled. 85 | * A statement that you consent to the jurisdiction of the Federal District Court 86 | in which your address is located, or if your address is outside the United 87 | States, for any judicial district in which our Company is located. 88 | * A statement that you will accept service of process from the party that filed 89 | the Notification or the party's agent. 90 | * Your name, address and telephone number. 91 | * A statement under penalty of perjury that you have a good faith belief that 92 | the material in question was removed or disabled as a result of mistake or 93 | misidentification of the material to be removed or disabled. 94 | * Your physical or electronic signature. 95 | * You may submit your Counter Notification to our Copyright Agent by mail, or 96 | email as set forth above. 97 | 98 | If you send us a valid, written Counter Notification meeting the requirements 99 | described above, we will restore your removed or disabled material after 10 100 | business days but no later than 14 business days from the date we receive your 101 | Counter Notification, unless our Copyright Agent first receives notice from the 102 | party filing the original Notification informing us that such party has filed a 103 | court action to restrain you from engaging in infringing activity related to the 104 | material in question. Please note that if you materially misrepresent that the 105 | disabled or removed content was removed by mistake or misidentification, you may 106 | be liable for damages, including costs and attorney's fees. Filing a false 107 | Counter Notification constitutes perjury. 108 | 109 | 110 | ## License 111 | 112 | Please note our DMCA Policy is released under a Creative Commons 113 | Attribution-NonCommercial-ShareAlike (CC BY-NC-SA) licence. 114 | -------------------------------------------------------------------------------- /topic_folders/policies/images/coc_process_diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/carpentries/docs.carpentries.org-archive/75ec49e87397235ed5ecb4fbea16afe1c01dfdf1/topic_folders/policies/images/coc_process_diagram.png -------------------------------------------------------------------------------- /topic_folders/policies/incident-reporting.md: -------------------------------------------------------------------------------- 1 | ### Code of Conduct Incident Reporting Guidelines 2 | 3 | ##### Reporting a Potential Code of Conduct Incident 4 | 5 | If you are attending a Carpentries workshop, in-person event, or participating in one of our online events or communication channels and believe someone is in physical danger, please ask your workshop host, instructor(s), or another community member to contact the appropriate emergency responders (police, crisis hotline, etc.). Prior to a Carpentries workshop or in-person event, event organisers should determine emergency contact numbers and local procedures. 6 | 7 | If you believe someone violated the [Code of Conduct](../policies/code-of-conduct.md) during a Carpentries event or in a Carpentries online space, we ask that you report it. If you are not sure if the incident happened in a Carpentries governed space, we ask that you still report the incident. You are encouraged to submit your report by completing the [Code of Conduct Incident Report Form][reporting-form]. The form may be completed anonymously, or you may include your contact information. 8 | 9 | __[Submit a Code of Conduct Incident Report][reporting-form]__ 10 | 11 | The Code of Conduct Committee takes all incident reports seriously and will review all reports according to our [Enforcement Guidelines](enforcement-guidelines.md). A report guarantees review, but not necessarily that an action will be taken. 12 | 13 | ##### Alternative Contact Points 14 | 15 | If you would prefer other ways to contact us, an email to [coc@carpentries.org](mailto:coc@carpentries.org) will be seen by all of the [Code of Conduct committee](https://carpentries.org/coc-ctte). If you are uncomfortable reporting to the Code of Conduct committee, incidents can also be reported to Cam Macdonell, the designated ombudsman for The Carpentries, at [confidential@carpentries.org](mailto:confidential@carpentries.org). 16 | 17 | The Carpentries Executive Director (Kari L. Jordan) can also be contacted by telephone at +1-407-476-6131 or email at [kariljordan@carpentries.org](mailto:kariljordan@carpentries.org). 18 | 19 | 20 | ##### Confidentiality 21 | 22 | You are welcome to report an incident anonymously. If you would like someone to follow-up with you about the progress of your incident report however, you would need to provide contact information. 23 | 24 | **All reports will be kept confidential** with details shared only with the Code of Conduct committee members. In the case that a CoC committee member is involved in a report, the member will be asked to recuse themselves from ongoing conversations, and they will not have access to reports after the enforcement decision has been made. Resolution action may also include removal of that member from the CoC committee. 25 | 26 | In rare cases, the CoC committee may suspend a community member. In such cases, the Executive Council and Carpentries Core Team will be informed in order to prevent future harm to the community, and The Carpentries Core Team [Immediate Response Checklist](incident-response.html#checklists-for-responding-to-an-incident) will be employed. 27 | 28 | Some incidents happen in one-on-one interactions, and though details are anonymised, the reported person may be able to guess who made the report. If you have concerns about retaliation or your personal safety, please note those concerns in your report. You are still encouraged to report the incident so that we can support you while keeping our community members safe. In some cases, we can compile several anonymised reports into a pattern of behaviour, and take action on that pattern. 29 | 30 | The Code of Conduct committee may determine that a public statement should be made about the incident and/or the action taken. If that is the case, the identities of all reporters and reportees will remain confidential unless those individuals instruct the CoC committee otherwise. 31 | 32 | 33 | ##### Report Data 34 | Reports can be filed anonymously with minimal details. If you do not feel you can provide details, we would still like to be aware that an incident occurred. Our ability to act is impacted by the amount of information you can provide, however. 35 | 36 | Information about an incident may be communicated to relevant Carpentries personnel in cases where a community member is suspended from engaging in The Carpentries community. In those cases, the [Termed Suspension Checklist](termed-suspension.md) will be employed. 37 | 38 | ##### Following Up with Reporter(s) 39 | 40 | Once a report is filed through the [Code of Conduct Incident Report Form][reporting-form] or other communication channels, the Code of Conduct committee will handle the review and follow up according to the procedures in the [Enforcement Guidelines](enforcement-guidelines.md). 41 | 42 | 43 | [reporting-form]: https://goo.gl/forms/KoUfO53Za3apOuOK2 44 | -------------------------------------------------------------------------------- /topic_folders/policies/index.rst: -------------------------------------------------------------------------------- 1 | Policies 2 | ======================= 3 | 4 | .. toctree:: 5 | :maxdepth: 1 6 | :glob: 7 | 8 | privacy.md 9 | terms-and-conditions.md 10 | cookie-policy.md 11 | dmca-policy.md 12 | instructor-no-show-policy.md 13 | reimbursement-policy.md 14 | core-team/professional-development-policy.md 15 | -------------------------------------------------------------------------------- /topic_folders/policies/index_coc.rst: -------------------------------------------------------------------------------- 1 | Code of Conduct 2 | ======================= 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | code-of-conduct.md 9 | incident-response.md 10 | incident-reporting.md 11 | enforcement-guidelines.md 12 | termed-suspension.md 13 | coc-membership-agreement.md 14 | coc-governance.md 15 | -------------------------------------------------------------------------------- /topic_folders/policies/instructor-no-show-policy.md: -------------------------------------------------------------------------------- 1 | ### Instructor No-Show Policy 2 | 3 | The Carpentries is usually not involved in travel arrangements for workshops. Instead, once instructors have been selected, they negotiate travel and accommodation with the workshop's host, and are then reimbursed directly by the host. In order to consistently provide high-quality workshops, however, The Carpentries must ensure that instructors fulfill their commitments. In particular, it must do what it can to ensure that instructors show up for workshops they have agreed to teach, so that hosts have the appropriate number of instructors and do not incur unnecessary expenses. 4 | 5 | Instructors who find that they will not be able to meet an agreed upon teaching engagement are required to notify The Carpentries workshop coordinator as soon as possible. If travel arrangement have not been made, and the workshop is at least 6 weeks away, instructors may cancel with no questions asked. If non-refundable travel has been booked or it is less than 6 weeks from the workshop, instructors should clearly communicate the reason for missing their teaching engagement. The workshop coordinator will then handle communication with the host and attempt to find an alternate instructor if possible. 6 | 7 | Depending on their reason for missing their agreed upon teaching engagement, instructors may be required to reimburse any non-refundable travel or accommodation costs that the host may already have incurred on their behalf. The Carpentries may waive this requirement in special circumstances outlined below, based on the judgement of The Carpentries Policy Subcommittee. 8 | 9 | In some cases, The Carpentries will waive the requirement for the instructor to reimburse the host, and The Carpentries will reimburse the host for any expenses incurred. Circumstances in which The Carpentries will reimburse the host for any expenses incurred for missed workshops include, but are not limited to: illness, injury, family or work related emergencies, weather or transportation malfunction. Instructors may be required to provide appropriate documentation to the Policy Subcommittee. If an instructor is required to reimburse costs, but refuses to do so, or an instructor fails to provide adequate notice of withdrawal more than once, The Carpentries reserves the right to suspend their Carpentries instructor status. -------------------------------------------------------------------------------- /topic_folders/regional_communities/carpentries_en_latinoamerica.md: -------------------------------------------------------------------------------- 1 | ## Carpentries-es 2 | 3 | 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. 4 | 5 | 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. 6 | 7 | ### Como puedes ayudar / Ways to Help 8 | 9 | Hay muchas formas de ayudar a construir la comunidad de Carpentries en América Latina. 10 | 11 | - Necesitamos hablantes nativos y con fluidez de español para ayudar a traducir los materiales de las lecciones. 12 | 13 | - Necesitamos una forma de mantener sincronizadas las diferentes versiones de idiomas de las lecciones de The Carpentries para que las contribuciones hechas a una versión aparezcan en las otras. 14 | 15 | - Necesitamos instructores experimentados para enseñar y guiar a los nuevos instructores en América Latina, especialmente aquellos familiarizados con la región. 16 | 17 | - Necesitamos Capacitadores ubicados en América Latina o con fuertes vínculos con la región. 18 | 19 | - Necesitamos ayuda con la coordinación de talleres de personas familiarizadas con las estructuras de precios, la geografía y la infraestructura computacional en América Latina. 20 | 21 | - Necesitamos campeones locales para correr la voz sobre The Carpentries y el trabajo que hacemos y abogar por los talleres y membresías de The Carpentries en la región. 22 | 23 | Si puede ayudar de alguna de estas formas, o conoce otra forma en la que pueda apoyar el desarrollo de la comunidad de The Carpentries en América Latina, [¡póngase en contacto a través de la lista de correo!](mailto:local-latinoamerica@lists.carpentries.org) 24 | 25 | There are many ways to help build The Carpentries community in Latin America. 26 | 27 | - We need native and fluent Spanish speakers to help translate lesson materials. 28 | - We need a way to keep different language versions of The Carpentries lessons in synch so that contributions made to one version also appear in other versions. 29 | - We need experienced instructors to teach with and to mentor new instructors in Latin America, especially those familiar with the region. 30 | - We need Trainers located in Latin America or with strong ties to the region. 31 | - We need help with workshop coordination from people familiar with pricing structures, geography and computational infrastructure in Latin America. 32 | - We need local Champions to spread the word about The Carpentries and the work that we do and advocate for The Carpentries workshops and memberships in the region. 33 | 34 | If you can help in any of these ways, or know of another way you can support development of The Carpentries community in Latin America, please [get in touch via the mailing list!](mailto:local-latinoamerica@lists.carpentries.org) 35 | 36 | ### Cómo participar / How to Get Involved 37 | 38 | Para ponerse en contacto con este grupo, envía un correo electrónico a [local-latinoamerica@lists.carpentries.org](mailto:local-latinoamerica@lists.carpentries.org). Para unirse a la lista de correo electrónico, visita [Topic-Box](https://carpentries.topicbox.com/groups/local-latinoamerica). Para contactarnos directamente también te invitamos a usar [slack](https://slack-invite.carpentries.org/) en el canal **carpentries_es**. 39 | 40 | To contact this group, email [local-latinoamerica@lists.carpentries.org](mailto:local-latinoamerica@lists.carpentries.org). To join the email list, visit [Topic-Box](https://carpentries.topicbox.com/groups/local-latinoamerica). To contact us directly you are invited to join [slack](https://slack-invite.carpentries.org/) in the **carpentries_es** channel. 41 | 42 | ### ¿Quién está involucrado? / Who is Already Involved? 43 | 44 | - Traducción de lección / Lesson translation: Paula Andrea Martinez, David Perez-Suarez, Rayna Harris 45 | - Capacitación de instructores / Instructor training: Karen Word 46 | 47 | ### Reuniones bilingües / Bilingual Meetings 48 | 49 | - Hacemos reuniones bilingües para la sección "Demostración de enseñanza" de ["Instructor Training Checkout"](https://carpentries.github.io/instructor-training/checkout/). Inscríbase en el [Etherpad](https://pad.carpentries.org/teaching-demos) o lea las [instrucciones bilingües](https://github.com/carpentries/latinoamerica/blob/main/traducciones/demo.md) para saber cómo funcionan las sesiones de demostración. 50 | 51 | - We host bilingual meetings for the "Teaching Demo Sessions" part of [Instructor Training Checkout](https://carpentries.github.io/instructor-training/checkout/). 52 | Sign up on the [Etherpad](https://pad.carpentries.org/teaching-demos) or read the [bilingual instructions](https://github.com/carpentries/latinoamerica/blob/main/traducciones/demo.md) for how the demo sessions work. 53 | 54 | ### Traducciones / Translations 55 | 56 | Los respositorios de GitHub para las traducciones en progreso son mantenidos por la organización [carpentries-es](https://github.com/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](https://datacarpentry.org/lessons/) y [Software Carpentry](https://software-carpentry.org/lessons). Las lecciones en proceso de traducción antes de ser oficiales se pueden encontrar en la organización [carpentries-i18](https://github.com/carpentries-i18n). 57 | 58 | The GitHub repos for translations in progress are maintained in the [Carpentries-ES organization](https://github.com/Carpentries-ES). Several Data Carpentry and Software Carpentry lessons have complete Spanish language translations. These are listed on the [Data Carpentry](https://datacarpentry.org/lessons/) and [Software Carpentry](https://software-carpentry.org/lessons) lesson websites. Lessons that are being translated before becoming oficial can be found in the organisation [carpentries-i18](https://github.com/carpentries-i18n). 59 | 60 | -------------------------------------------------------------------------------- /topic_folders/regional_communities/index.rst: -------------------------------------------------------------------------------- 1 | Regional Communities 2 | ======================= 3 | 4 | .. toctree:: 5 | :maxdepth: 2 6 | :glob: 7 | 8 | regional_coordinators.md 9 | african_task_force.md 10 | carpentries_en_latinoamerica.md 11 | regional_email_lists.md 12 | 13 | -------------------------------------------------------------------------------- /topic_folders/regional_communities/regional_coordinators.md: -------------------------------------------------------------------------------- 1 | ## Regional Coordinators 2 | 3 | Around the world, Carpentries workshops are organised by a team of Regional Coordinators. 4 | Our Deputy Director of Workshops and Meetings, 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](https://carpentries.org/members/) or as volunteers. 5 | 6 | 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. 7 | 8 | Read more about the Regional Coordinators' [role](https://docs.carpentries.org/topic_folders/workshop_administration/expectations.html). 9 | 10 | More information about the Regional Coordinators can be found on [The Carpentries website](https://carpentries.org/regionalcoordinators/). 11 | -------------------------------------------------------------------------------- /topic_folders/regional_communities/regional_email_lists.md: -------------------------------------------------------------------------------- 1 | ## Regional Mailing Lists 2 | 3 | All mailing lists for [The Carpentries](https://carpentries.topicbox.com/groups) are hosted on Topicbox. This includes a number of mailing lists specific to local or regional communities. 4 | 5 | ### Current local/regional mailing lists 6 | 7 | #### Africa 8 | - [Africa](https://carpentries.topicbox.com/groups/local-africa) 9 | - [Middle-East and North Africa](https://carpentries.topicbox.com/groups/local-middle-east) 10 | 11 | #### Asia 12 | - [Bangladesh](https://carpentries.topicbox.com/groups/local-bangladesh) 13 | - [India](https://carpentries.topicbox.com/groups/local-india) 14 | 15 | #### Australia/New Zealand 16 | - [Australia and New Zealand](https://carpentries.topicbox.com/groups/local-aunz) 17 | 18 | #### Canada 19 | - [Vancouver](https://carpentries.topicbox.com/groups/local-vancouver) 20 | 21 | #### Europe 22 | - [Germany](https://carpentries.topicbox.com/groups/local-germany) 23 | - [Heidelberg](https://carpentries.topicbox.com/groups/local-heidelberg) 24 | - [United Kingdom](https://carpentries.topicbox.com/groups/local-uk) 25 | - [Nordic countries](https://carpentries.topicbox.com/groups/local-nordic) 26 | 27 | #### Latin America 28 | - [Latin America](https://carpentries.topicbox.com/groups/local-latinoamerica) 29 | - [Puerto Rico](https://carpentries.topicbox.com/groups/local-puertorico) 30 | 31 | #### United States 32 | - [Bay Area](https://carpentries.topicbox.com/groups/local-bayarea) 33 | - [Boston](https://carpentries.topicbox.com/groups/local-boston) 34 | - [Colorado](https://carpentries.topicbox.com/groups/local-colorado) 35 | - [Davis, CA](https://carpentries.topicbox.com/groups/local-davis) 36 | - [Lansing, MI](https://carpentries.topicbox.com/groups/local-lansing) 37 | - [Merced, CA](https://carpentries.topicbox.com/groups/local-merced) 38 | - [Seattle, WA](https://carpentries.topicbox.com/groups/local-seattle) 39 | - [Southeast US Library Carpentry](https://carpentries.topicbox.com/groups/local-libcarpentry-southeast-u) 40 | - [Southern California](https://carpentries.topicbox.com/groups/local-socal) 41 | - [Southwest United States](https://carpentries.topicbox.com/groups/local-swusa) 42 | - [University of California](https://carpentries.topicbox.com/groups/local-uc) 43 | - [Washington DC Area](https://carpentries.topicbox.com/groups/local-dc) 44 | -------------------------------------------------------------------------------- /topic_folders/workshop_administration/amy_manual.md: -------------------------------------------------------------------------------- 1 | ## AMY: The Carpentries' internal database 2 | 3 | AMY is a database application for The Carpentries. It allows The Carpentries to track programmatic activity including: 4 | 5 | * workshops 6 | * instructor training 7 | * individual roles and badges 8 | * institutional membership 9 | 10 | Most functionality is limited to authorized administrative users. Individuals whose data is tracked in AMY can view only their own profile page. [Read how to access and update your profile](https://docs.carpentries.org/topic_folders/for_instructors/current_instructors.html#accessing-and-updating-your-instructor-profile). 11 | 12 | The code base can be found in the [AMY GitHub repo](https://github.com/carpentries/amy). 13 | 14 | The [web based application can be found here](https://amy.carpentries.org/). 15 | 16 | [Documentation for AMY administrators can be found here](https://carpentries.github.io/amy/). 17 | -------------------------------------------------------------------------------- /topic_folders/workshop_administration/expectations.md: -------------------------------------------------------------------------------- 1 | ### Role and Expectations 2 | 3 | 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 Coordinators 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. 4 | 5 | 6 | This includes the following responsibilities 7 | 8 | * 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. 9 | * Read emails sent to the admin group. 10 | Stay up to date on all Carpentries operations as outlined in the [Carpentries handbook](https://docs.carpentries.org/index.html). 11 | Respond to workshop requests from host sites in your region within two business days. This may include, but is not limited to: 12 | * Sharing general Carpentries information 13 | * Recruiting instructors 14 | * Setting up surveys and registration 15 | * Supporting other planning logistics 16 | * Recording all information according to Carpentries’ systems. 17 | * Follow up on all completed workshops to collect attendance data and other feedback, and record this in Carpentries’ systems. 18 | * 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. 19 | * Communicate Carpentries community values to instructors, host sites, and others constituents. 20 | * Communicate successes and challenges with Carpentries Workshop and Logistics Manager and other Regional Coordinators. 21 | * 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. 22 | * Elevate questions and issues to Carpentries Core Team as needed. 23 | 24 | 25 | 26 | 27 | -------------------------------------------------------------------------------- /topic_folders/workshop_administration/index.rst: -------------------------------------------------------------------------------- 1 | Workshop Administration 2 | ======================== 3 | 4 | Around the world, Carpentries workshops are organised by a team of Regional Coordinators. 5 | Our Core Team 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. 6 | 7 | This section outlines their work specifically as it relates to workshop administration. 8 | 9 | .. toctree:: 10 | :maxdepth: 2 11 | :glob: 12 | 13 | expectations.md 14 | amy_manual.md 15 | email_templates.md 16 | --------------------------------------------------------------------------------