Library Carpentry Curriculum Advisory & Governance Committee Etherpad



Resources


Github: https://github.com/LibraryCarpentry/curriculum-advisors
Email list: https://carpentries.topicbox.com/groups/curriculum-advisors-lc
Carpentries Handbook section: https://docs.carpentries.org/topic_folders/lesson_development/curriculum_advisory_committees.html
CAC-onboarding slides: https://docs.google.com/presentation/d/1xuMCP43EUvmFqvHDX9w4BwOdvWMDcjW0BGxyOQVFSBs/edit?usp=sharing

2026 and 2027 meetings are moving to the LC Governors Etherpad

  1. Upcoming meetings (2025): 

Tuesday, December 2, 2025 at 16:00:00


https://www.timeanddate.com/worldclock/fixedtime.html?iso=20251202T1600
Zoom: https://berkeley.zoom.us/j/95407896404?pwd=aRCsFJcFRQphCZPtVXNykNwc1XvzQl.1

Sign in:

Administrative & Governance


Lesson Maintenance & Migration Strategy



Future meeting:



LC Marc-Edit Review for Carpentries Lab (Monday, Nov 10, 2025)


Attending: 



Notes on transition to LCGC (Oct 27, 2025):



Meeting with Toby Hodges, Nathaniel Porter, Jennifer Stubbs, and Cody Hennesy
Absent: Nicky Garland, Lebogang Seleka, Tim Dennis
Also on LCGC: Eka Grguric, Annajiat Alem Rasel

Introductions:
Relevant experience in Carps/career

TH liaison to core team, no background in libraries, 5 years with LC, Limon in S. Germany
CH: Head social sciences div in UC Berkeley libraries, CAC couple years, taught workshops, co-author update LC Python intro
Jennifer: Based in Illinois. Maintainer, working in libraries, started teaching LC through NYU Shaghai's training offer. Worked on some lesson updates and engaging with AI discussions at the moment.
NP
In Virginia Tech, Christianberg, 
Data consultant then to LC, no official librarian job title. Trainer community, Instructor training, Maintainer lead, developed qualitative software lessons ( in process of becoming official)

What committee does:
LC Governors with responsibility /authority to guide strategy of lesson program.  Community governance, specific to LC (unlike board of directors as a whole, overall governance all Carpentries).
Director of Curriculum leads core team support of individual lessons--rely on LCG guidance, to help Toby make decisions based in library expertise.  Ideally separation of powers core team to community.
Do: 1. strategic guidance =curriculum, absorbed CAC, development, adoption of new lessons, retire existing lessons, new directions (lesson topics needed soon/future for libraries), identify projects to ask Core Team support community assessment or collaboration opportunities
2. powers/responsibility: advocacy, empowered to speak on behalf of LC, at conferences, as respresentative of LC program, occasionally be point of contact for general community, board of directors, core team, maintainers, etc.
3. Communications: core team maintains LC lesson website; far less material on websites needing LC specific revision/update.  https://github.com/LibraryCarpentry/librarycarpentry.org/pull/72
----current PR: to resolve ^^^^^
If LCG identities priorities, Toby as point of contact to facilitate data/survey.
Erin Becker might attend as delegate occasionally.
Q1 Chair secretary? as under CAC.  Co-chairs?  Yes might work well. Alternate chair month to month or divide following:
Chair= agenda in advance, coordinate activities outside meetings (delegate, followup), construct next meeting agenda; watch Github, mailing list, slack for issues to bring to LCG to build agenda
SEcretary schedules meetings (in main calendar): do a year at a time, not last minute.  Upload meetings minutes to github repo lcg/governance
Possible to split if timezone/global shift required.
 Q2: If publishing: LCG to review and Core Team communications manager: Oscar Masinyana (reach out directly) 
 Cody: CAC: 2-3 years
 many lessons retired, combed through, updated and trying to move lessons from concepts/pre-alpha or from alpha to beta, the UCLA open sci for Librarians lesson set
 Groups of authors attend to facilitate each level-up
 Carpentries Lab review of LC MarcEdit to move into "stable"
 Codesprint: AI for GLAM
 Next year: create pathways, thematic lessons by audience types to package the long menu of lessons to identify the best 4 for __________ 
 Research Data Management interrupted due to US grants
 Pathways: highly useful; given growing varieties of genres (unlike clear boxes of DC and SC)--inspired by DC/SC
 Cody offered to schedule for next year.  #1 time zone, globally: Pacific Coast US/Canada, UK, Botswana, and Bangladesh.  Is there an hour that is reasonable?  Or plan how to work as two meetings.
 Toby will add everyone to the Topicbox for LCGC
 Discuss by email in the coming week.
 Next: expect email with link (recording, notes, and PR).  Ideally PR may be mergable already as is.
 Volunteers for Chair, for Secretary
 Availability for Dec 2?
 
 Thank you very much for volunteering to serve LCG.  Fundamental roles to health of project.  Toby feels more confident with community minded, experience committee as part of team.  (notes by JAWS)


Tuesday, August 5, 2025 at 15:00:00



Sign-in



Agenda


Wednesday, June 4, 2025 at 01:00:00



Sign-in


- Cody Hennesy
- Tim Dennis

Apologies:
Annajiat

Agenda



Thursday, April 3, 2025 at 15:00:00



Sign-in



Agenda


Questions for authors:


Tuesday, February 4, 2025 at 02:00:00 



Sign-in


Agenda


    1. Wikidata lesson Guests: Rabea Müller (muellerr@zbmed.de) rescheduled for Aug 5
      1. https://librarycarpentry.github.io/lc-wikidata/
      2. Previous conversation: https://github.com/LibraryCarpentry/lc-wikidata/issues/61
      3. Currently listed under conceptual
      4. Toby (in absentia): If you do discuss the wikidata lesson in this meeting (Rabea is based in Germany, where it will be 3am when the call begins?) please could you ask what should be done about this issue from the LC website? I have not been sure what to do with it https://github.com/LibraryCarpentry/librarycarpentry.org/issues/50
    2.  LC research data management workshop/pathway
      1. Funding from NIH to Carpentries for travel to two-day curriculum development drive for RDM lessons
      2. More info: https://docs.google.com/document/d/14JRzqMcGFto6NnLREdhzJN4Qqsa3fi1XPFI8w4Gi-Dw/edit?tab=t.0
      3. We need participants
      4. Tim will email Jen at U Chicago
    3. Annajiat - economic grant for digital scholarship lab proposal
      1. looking for templates for DS labs - how they structure their work; 
      2. piloting workshops; two year project, building infrastructure from scratch
      3. they have spaces, they plan to build technology (cameras, scanners), workshops
      4. Some potential good sites/articles:
        1. https://www.colorado.edu/crdds/
        2. https://crl.acrl.org/index.php/crl/article/view/24713/33406
        3. https://publishing.escholarship.umassmed.edu/jeslib/article/id/780/
        4. Tim will find book chapter on developing UCLA DSC 
    4. Tim will fix the blog entry for marc-edit 
      1. https://github.com/LibraryCarpentry/carpentries.org 
      2. capture the markdown for the blog, delete the repository 
      3. fork the new website 
      4. make the PR  https://github.com/carpentries/carpentries.org/pull/378
    5. Updates:
      1. LC R maintainer is making some small updates to lesson
      2.  UCLA students are converting AI for GLAM lesson to workbench and move to LC
        1. Tim will have student convert to workbench in preparation for RDM work: https://librarycarpentry.github.io/lc-fair-research/
      3. Four Curating for Reproducibility lessons are now on the workbench - 
        1. e.g., https://github.com/ucla-data-science-center/lc-cure-01
        2. https://github.com/ucla-data-science-center/lc-cure-03
        3. https://github.com/ucla-data-science-center/lc-cure-04
        4. https://github.com/ucla-data-science-center/lc-cure-02 
        5. Should they move to the incubator or go into LC?
    6. For upcoming meeting:
      1. Open Qualitative Lesson  with Taguette (Nathaniel Porter) - 
        1. https://github.com/LibraryCarpentry/lc-open-qualitative-research
      2.  Irene and Jessica to discuss A Path to Open, Inclusive, and Collaborative Science for Librarians lesson
      3. get lawrence to convert: https://librarycarpentry.github.io/lc-fair-research/
    7. To do:
      1. Cody will reach out Rabea
      2. Tim will reach out to Nathaniel


2024-11-21  UTC 15:00 - cancelled


https://www.timeanddate.com/worldclock/fixedtime.html?iso=20241121T1500

Sign-in



Agenda




2024-09-19 UTC 23:00


Sign-in: 

Agenda



2024-07-18 UTC 15:00 



Zoom: https://umn.zoom.us/j/94874193141?pwd=Y0cwWDR6M2lTRVJiUGo2c3I1MFZEQT09


Sign-in: 
-Jennifer Stubbs (she/her), LC-OpenRefine Maintainer; Instructor since 202202, jastubbs@bradley.edu
- Cody Hennesy
- Tim Dennis
- Toby Hodges

Agenda



2024-05-16 UTC 2300


Sign-in: 
- Cody Hennesy (he/him) chennesy@umn.edu
- Tim Dennis (he/him) tdennis@library.ucla.edu
- Eka Grguric (she/her) eka.grguric@ubc.ca
- Annajiat Alim Rasel, annajiat@gmail.com

Agenda: 

2024-03-14 UTC 15:00


Sign-in: 



Agenda: 



2024-01-18 UTC 23:00


Join Zoom Meeting:
https://umn.zoom.us/j/98152059087?pwd=VkZoRnZpWGxqYXBJUGtSL21PYXFiZz09

Sign-in: 




Agenda: 



  1. Introductions
  2.  AI for GLAM code sprint - planning (Jan 31) - (Cody)
    1. UTC Wednesday, January 31, 2024 at 1:00 to 8:00 pm
      1. Start time: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240131T1300
      2. Zoom: https://umn.zoom.us/j/94839281281?pwd=eFF0eDd6MWVzc1YvSmtTeERaeGtMQT09
      3. Planning doc: https://pad.carpentries.org/ai-glam-sprint
        1. Project manager shifts (CAC)
        2. Organizing issues for people to help with (Maintainers)
          1. Nora and Daniel couldn't make it due to time diff
          2. Goals - marking items off the checklist so that the lesson is publishable as Stable and can move into new LC Core curriculm
            1. Suggested changes to the Intro to AI for GLAM lesson: https://github.com/carpentries-incubator/machine-learning-librarians-archivists/issues/82
          3. Once the lesson is stable we can announce it more formally
        3.  Outreach plans - Tim submitted post for Carpentries blog - 
          1. Cody will share on Library Carpentries Slack + discuss@lists.carpentries.org
          2.  Leigh will share on AI for GLAM Slack
          3.  Mary will share with Australia groups - if there's interest we can extend the time of the sprint and hand off
        4. Tim will look into whether a couple of UCLA students can convert it to the new workbench beforehand
        5. Workshop on Tuesday, the 23rd hosted at Smithsonian Institute
        6. Carpentries Slack channel (carpentries.slack.com) sub-channel is #lc-ai-glam
  3. Restructure our core curriculum based on recent changes (this item could take some time)
    1. Let's break this down 
    2. Approved changes: https://github.com/LibraryCarpentry/lc-overview/issues/49
    3. Decommission lesson or archived 
    4. Changing LC website to reflect 
    5. Decommission LC-Overview Lesson - Determine new home for Episode 3 - Jargon Busting
      1. https://github.com/LibraryCarpentry/lc-overview/issues/59 
    6. https://github.com/LibraryCarpentry/lc-overview/issues/57
    7.  Tim, Mary, and Cody will schedule a meeting to finish up LC Overview decommission
      1. 5pm - Cody will set it up
  4. LC-CAC Github repo:
    1. https://github.com/LibraryCarpentry/curriculum-advisors 
  5. Changes to Core team open call (Jan 15) -- Phil Reed in absentia today, apologies for time zones
    1.  Phil attended the call, notes: https://pad.carpentries.org/2024-01-15-0900-discussing-cac-support
    2. Reiterates what Toby has previously said about the Core Team who now say:
      1. They will no longer coordinate CAC recruitment and onboarding
      2. They will no longer provide a liaison to each CAC
      3. They will communicate to Maintainers when a CAC becomes inactive
    3.  We are responsible for organising our own onboarding but can use Core Team to promote call.
    4. Note, Software Carpentry may combine CAC and Advisory Groups due to size.
    5. Tim & Cody are meeting with Toby on 1/22 7-7:30 pm UTC (https://carpentries.zoom.us/j/86739786103) - feel free to join 
  6. Intro to Computational Thinking https://github.com/carpentries-incubator/proposals/issues/182 
    1. Submitted to incubator
    2. Next steps:
      1. First, we need to talk to Toby to see how to move the lesson to Library Carpentry repo as alpha lesson in Extended Curriculum
      2. Then, once it's in LC repo, CAC should review it according to the checklist [https://docs.carpentries.org/topic_folders/lesson_development/lesson_release.html] and add issues as needed
      3. As we have more and more new lessons we should put together a communication kit to get the word out on new lessons - Outlets + info 
  7. Intro to Curation for Reproducibility (Tim) - https://curating4reproducibility.org/training/
    1. Sent email to maintainers to inquire about progress
    2. Offered help with transition to Workbench
  8. New Python lesson draft: https://github.com/chennesy/lc-python-intro/
  9. UCLA DSC - currently has 2 students who are pretty versed in the Workbench
    1. LMK if they can help move any lesson work along? Tim - tdennis@library.ucla.edu
  10. March agenda:
    1. CAC Recruitment
    2. Address + update LC website

2023-11-16 UTC 1600


Sign-in



Agenda


  1. Proposal to revise title of Introduction to Working with Data (Regular Expressions) lesson
    1. See issue: https://github.com/LibraryCarpentry/curriculum-advisors/issues/22
    2. Name isn't quite right and isn't a great first lesson in the curriculum
    3. We want to keep the lesson, but need to find a place for it - table for future meeting focused on how to restructure our core curriculum based on recent changes. Action item for new year to schedule: lesson paths;
    4. Possible better titles: Pattern matching (Regular expressions)
    5. Improvement ideas:
      1. Could add something with OpenRefine and/or Excel if it comes after those in the order
      2. Regex crossword solvers  as another way to show a real-world or more comprehensible example before moving on to Library Management System (LMS) or database searches
      3. Could add an earlier, optional episode of pattern matching pre-regex with just ? * common symbols from common places like searching a library database or files on your computer. Get that understood before moving onto more powerful regex. Feedback from some learners that it is too big a leap to go into regex and not understand the purpose and context.
  2. Curriculum on-boarding update - plan to hold community session in early 2024
    1. https://docs.google.com/presentation/d/1GCqeFDGeiMn3oDTsTOgdspRXqtnKt-WtXyeH_u0pIV8/edit#slide=id.p
    2. Toby arranged for these onboarding sessions, and Cody helped fill out first draft of slides. Liz Stokes and Lisa McAulay updated slides with suggestions. Toby implemented many updates. 
    3. There are some changes to make given changes with LC Overview lesson. 
    4. Plan to have a community session in Jan or Feb to present this. It will be recorded (to Carpentries YouTube) so we can share the presentation with others as needed. 
    5. Open to presenting: Phil, Tim, and Cody can all help present. 
    6. Probably two sessions for different time zones
  3. Intro to AI for GLAM 
    1. Being offered as part of Fantastic Futures: https://ff2023.archive.org/pages/program/
    2. Question about platform for slides for lessons like this one
      1. Slides work really well for this lesson, so it would be good to have a shared slidedeck. There is a place for it in the instructor notes.
      2. CodiMD - included in Carpentries, and does slides (example: https://codimd.carpentries.org/p/B_E_Gw_8-)
      3. Is there a way to integrate into episodes?
    3. Cody went to FF workshop and went well - train the trainer style, good LC promotion 
      1. substantial number of issues outlining the order of episodes, etc. https://github.com/carpentries-incubator/machine-learning-librarians-archivists/issues/82
      2. Cody will follow up with maintainers and see if we can organize a sprint to help move this fwd
  4. LC Overview lesson disposition - 
    1. Follow up on the decision to retire the LC Overview Lesson and distribute some of its content to other lessons or locations.
    2. Lisa McAulay and Tim Dennis to coordinate the migration of episodes to other lessons  - still need to meet on this. We had to cancel a couple of meetings, but have meeting set for before the year end.
  5. Guiding Learners on Configuring Multi-Factor Authentication for GitHub Accounts:
    1. Toby Hodges to open a PR regarding the new GitHub multi-factor authentication requirements. Lisa McAulay to assist in completing it.
    2. Is this completed?
      1. Toby: yes, it was merged here https://github.com/LibraryCarpentry/lc-git/pull/152/files
  6. LC Intro to Python:
    1. Cody Hennesy to continue developing the lesson with a focus on Pandas/JupyterLab using the dataset from the Chicago Public Library.
    2. Seek Python experts interested in co-maintaining the lesson.
    3. Scott Peterson at UCB is going to help with maintaining the new lesson 
    4. Meetings: https://pad.carpentries.org/lc-python-maintainers
    5. Hoping to have up by Feb. 2024 & Tim and Cody proposed piloting at IASSIST 2024 (May)
    6. Cody's forked lesson should work as a development space; 
      1. once it's done, can make one big pull request.
      2. How should CAC weigh in? Help review
      3. Officially: should alpha test it on own fork and then move it to beta once it's been tested
      4. Cody will share with CAC first once the updated version is ready for an initial review
      5. R for ecologists lesson was re-written recently in the Incubator and the DC CAC for ecologists is reviewing it.
      6. (🤘) Tim might be able to participate in an online alpha version; 
  7. MarcEdit Move to extended:
    1. Phil Reed to contact maintainers regarding this move.
    2. Phil has heard nothing back from lesson maintainers
    3. It's under Extended now, instead of Conceptual
    4. Phil action items: 
      1. There is still some work to do on the LC website to match maintainer names (leads) with results from the survey
      2. Will also follow up with maintainers to offer support in a general way
  8. FAIR Data message on topicbox from Gerrit C
    1. Phil did reach out to see if they wanted to follow up but hasn't heard back
  9. CACs plan for engaging with maintainers
    1. We should invite maintainers to meetings occassionally
    2. New year project - maybe put energy into a Sprint
    3. Carpentries Connect event in Germany in Nov 2024 - could be a good fit for LC-CAC event
  10. Intro to Computational Thinking:
    1. Still need to add to Carpentries Incubator
    2. Tim will move  to the incubator
    3. How to add acknowledgement for originating author of lessons like this? Not a great place for it. 
    4. put note in index.md - acknowledging Belinda as the person who wrote it in the first place and link to her original lesson 
  11. Consider arranging a sprint to clear out issues and encourage community involvement.
    1. For new year
  12. UCLA-IMLS Open Science Lessons Update:
    1. Tim Dennis to provide an update
    2. Lessons are  https://ucla-imls-open-sci.info/, but in different states of completion
    3. 2024 will be moved into incubator and piloted 
    4. Second call will go out soon. will write a Carpentries post to share broadly.
  13. Future Meeting Times:
    1. Confirm the start of the new schedule for alternating meeting times (UTC 15:00 and UTC 23:00) beginning in 2024.
    2. Cody created events, thanks! 
    3. CAC recruitment will be coming up next year
    4. Policy for CAC members is two-year terms, but you can stay on if you want  to commit to another two years. 
    5. CAC Onboarding will be two years after initial round (April 2024).
    6. Tim can reach out to Mary about interest 
    7. Tim open to rolling off chair and remaining as member

2023-09-21 UTC 1500 



Sign-in: 



Agenda
  1. Meeting times for future meeting (Tim) 
    1.  Would be great to alternate times in a way that Aus/NZ folks can attend these. 
    2. Two meetings in the same day is a recipe for decisions not getting made - hard to do action-oriented work in that way. Neither group wants to make a decision. Two meetings in the same day is also a lot more work for chair.
    3.  Rotating meetings is the best option. 
    4. Current proposal is: alternating UTC 15:00 and UTC 23:00 meetings. Approved.
    5. When? Start new schedule in 2024. Stick with current end of 
  2. LC Overview lesson disposition
    1. Lisa McAulay (lc-overview maintainer), Toby, and Cody met and propose that the LC Overview lesson be retired. See details about possibilities for where to move episode content here: https://github.com/LibraryCarpentry/lc-overview/issues/49#issuecomment-1683957172
    2. Recommendations:
    3. Recommend that some constituent parts of the LC Overview Lesson be distributed to other lessons or locations (see recommendations below)
    4. Recommend the LC retire the LC Overview Lesson from the LC Curriculum and the LC Core Curriculum
    5. Move the parts:
      1. Filenames & formats and Keyboard shortcuts content would be a better fit in the Foundational Computer Skills lesson in the Incubator https://github.com/carpentries-incubator/foundational-computer-skills/ but that lesson has never really got going.
    6.  When lessons are retired, what options do we have in terms of findability/searchability?
      1. Toby: in the past LC has moved them into the Incubator and flagged them as inactive/orphaned. 
        1. We probably wouldn't want to move this lesson into the Incubator - probably better to make it a read-only archive in LC. Or strip LC content and move it into incubator. 
        2.  We could take markdown from specific episodes and save it in a new repo with Github Pages.
      2. There are also links from LC lessons under Retired. 
      3. Note: Top 10 FAIR and LC Webscraping were retired but wasn't moved to Incubator; LC-XML was retired to the Incubator. Toby will follow up on those
      4. LC-CAC approves the general idea and Lisa is on board to migrate episodes to other lessons, etc. Tim can help Lisa to make sure stuff is moved properly.
      5. Toby: LC-CAC is the final decision maker on this. 
      6. A core lesson has never been retired - we should put something on the landing page of the lesson (index.md), on the Libraries channel, slack (#libraries) and topicbox (https://carpentries.topicbox.com/groups/discuss-library-carpentry), instructors channels (#instructors, https://carpentries.topicbox.com/groups/instructors), (no need to write blog post since it's LC specific); 
      7.  Set a deadline and give people a heads-up before it happens. 
      8.  Lisa and Tim will keep Cody in the loop on timing/deadline. Lisa can add callout box to lesson.
        1. Add a callout box in the Index.md file - the best we can do right now. 
      9. Jargon Busting - is it a teaching tool and not a curricular content? Does fit into the timetable of a lesson. Could move it into instructor notes page in Tidy Data (Toby: or as a separate .md file in the instructors/ folder) - could also add inline instructor notes at the point in the lesson where it could be a good fit. 
  3. Guiding Learners on configuring multi-factor authentication for their GitHub accounts (Toby) - 10 min
    1. GitHub starting to require multifactor authentication for users. This should be acknowledged in the LC git lesson. Erin and Toby reached out to relevant maintainers and they had helpful perspectives.
    2. recommendation from SWC+LC Git Maintainers:
      1. "1. If you already use an authenticator app, add GitHub to that [link to GitHub Docs]. 
      2. 2. If you have access to a smartphone but do not already use an authenticator app, install one and add GitHub for 2FA [link to GitHub docs]. 
      3. 3. If you do not have access to a smartphone or do not want to install an authenticator app, set up 2FA via text message [link to GitHub docs] or a secondary email address [link to GitHub docs]. 
      4. View other options for configuring 2FA in the GitHub documentation [link to GitHub docs]"
      5.  It's not ideal in terms of folks without smartphones would make it quite difficult (you can buy a USB key instead of using text/phone app).
      6. Toby will open PR and Lisa will try to finish it soon.
  4. LC Intro to Python (Cody)
    1. Met with Nathaniel Porter and Owen Stephens and got helpful feedback. Likely to move forward with dataset consisting of (cleaned up) yearly circulation data from Chicago Public Library (open in data.gov). A narrative based around getting yearly CSVs and shaping it into annual report.
    2.  Pandas/JupyterLab focus
    3. And then future plans/hopes to develop web scraping and APIs python lessons
    4.  If you know Python people who would be interested in co-maintaining send them in Cody's direction
  5. MarcEdit move to conceptual lesson and contact maintainers (Phil)
    1. Intro to Computational Thinking (Tim)
      1. Repo: https://github.com/ucla-data-science-center/intro-computational-thinking
      2. https://ucla-data-science-center.github.io/intro-computational-thinking/ 
        1. This looks great, and exciting to see
      3. next steps to move to LC or incubator - 
        1. Toby: we should use the same process as we have for AI for GLAM lesson.
        2. Agreed: use checklist, and path for inclusion in LC.
        3. Incubator - lesson dev takes place
        4. Lab - lesson review takes place
        5. Toby: It should move into Incubator and submitted for review in Labs. Once it passes Lab review it will move into LC.
        6. To move to Incubator: open an issues in proposals repo (https://github.com/carpentries-incubator/proposals/issues/new?assignees=tobyhodges&labels=proposal&projects=&template=lesson_proposal.yml&title=%5BProposal%5D%3A+), answer questions about whether or not you want to keep PRs, etc. in tact.
        7.  Once Incubator repo is ready, open a new issue here to submit for review: https://github.com/carpentries-lab/reviews/issues/new?assignees=tobyhodges&labels=review&projects=&template=review_submission.yml&title=%5BReview%5D%3A+
        8. Someone from CAC to act as a co-editor.
        9. Phil added Intro to Computational Thinking to spreadsheet of lessons: https://docs.google.com/spreadsheets/d/192j2nRgusL1S75OZxDcivFtQZ1EedRj6ZARA7u3N80A/edit?pli=1#gid=0
    2. Intro to AI for GLAM -Discuss any unresolved checklist issues from this lesson at a future meeting. https://github.com/carpentries-incubator/machine-learning-librarians-archivists
      1.  There are still a lot of issues with checklist. 
      2. What is CAC's role when lesson needs some work, and work isn't happening?
        1. Mark: catch more flies with honey; this AI content is of high interest right now in higher ed; we should encourage them to move it forward.
        2.  Phil is meaning to contact AI for GLAM. He might have funds to teach the lesson in Manchester, so that could be a good way to incentivize work on it. Could help get issues resolved. 
        3. We could also arrange a sprint to help them clear out issues. 
        4. Toby: encourages you to bring in others to get involved. Think about how the lesson will be maintained in the long run. Might be a good area for bringing in more community around the lesson. Esp contributors to lesson, future maintainers. 
        5. If we do a sprint we can try to encourage other LC folks (not just CAC) to take part. 
        6. Phil will follow up once strike is over. We can discuss setting up a sprint during Nov meeting. 
        7. Mark: has a possibility of teaching AI for GLAM with a local research group.
    3. UCLA-IMLS Open Science Lessons update (Tim) - can move to Nov


    --------------------------------------

    2023-08-17 UTC 1500 (LC-CAC Subgroup - LC Overview)



    Sign-in: 



    Agenda


    1. Looking at LC Overview lesson https://librarycarpentry.org/lc-overview/
      1. Do we *need* an overview for LC? Does the motivation still apply now?
      2. LC was the last lesson program to join, followed the model from existing DC curricula at the time e.g. Ecology, which had an overview.
      3. A lot of LC "workshops" were half-day sessions at conferences, which do not (need to) happen now
      4. A lot of the content does not belong in a lesson now. Can and should live in other places.
      5.  Promotional content (what LC is and why you should dig it?) should be moved out of the lesson 
      6.  Possible pathways through LC curriculum should also be moved into other Carpentries spaces (LC Onboarding slides, Carpentries Instructor Training).
      7. We could "archive" the old LC Overview site. Maybe start a new lesson that much pared down.
      8. Think about leaving lesson online but redirecting people who find it to the relevant place where they can find the content now (if we decided to keep it).
      9. Episodes worth retaining:
        1.  Jargon busting https://librarycarpentry.org/lc-overview/03-jargon-busting/index.html
          1. 45-60 mins, good as a foundational session for a workshop: bring people to the same level
          2. Not substantial enough to be a standalone lesson
          3. Try to help people feel less alienated by jargon
          4. Cody has always taught Tidy Data as first lesson in workshop, Jargon Busting could be a good fit in there?
          5.  When Jargon Busting is transitioned to new workbench it could be added as an Instructor View note as how to run that session as an intro for either Tidy Data or Intro to Data (RegEx)
          6. Jargon Busting page could appear as page for multiple lessons (with redirects), but technically a part of the Tidy Data lesson. An optional intro to multiple lessons
      10.  Episodes to move elsewhere:
          1. Keyboard shortcuts and file naming could go into Incubator lesson called foundational computer skills https://github.com/carpentries-incubator/foundational-computer-skills
            1. Make a PR to add these lessons to Incubator Lessons / add link to Incubator as part of the Pathways.
          2.  Or those episodes could go into Intro to Computational Thinking lesson (Belinda Weaver) https://weaverbel.github.io/intro-computational-thinking/ (or be combined with that content in some way)
      11. Content not worth retaining (in a lesson):
        1. Index page
        2. Intro to LC https://librarycarpentry.org/lc-overview/02-intro-to-library-carpentry/index.html
        3. Computational Approach
        4. One up, One down
        5. Further Reading
    2. Lisa's recommendation: retire the lesson and find better fit for each part 
      1. Library speak: de-accession, i.e. there is a protocol for this, with reasonable stewardship
      2. Cody: CAC retired some lessons recently but these were not core curriculum
      3. Cody: can take this to next CAC, sum up main points and plan for next steps
      4. We should keep the Maintainers in the loop (via an issue) once decision/recommendation is ready
        1. We can change status on librarycarpentry.org/lessons page from "stable" to "to be retired" or similar
        2. And add a banner or similar to the top of the lesson landing page and episodes, linking to the issue
        3. And maybe send out a message to libraries channels e.g. on Slack, mailing list
    3. Off-topic: LC-Git lesson
      1. Cody is going to teach in Nov; will pilot an initial episode that starts the lesson in GitHub; start with GitHub search (use repos that are interesting for library workers); will share outline with Lisa after teaching;
      2. See also: https://github.com/carpentries-incubator/github-without-command-line (based on https://miketrizna.github.io/github-without-command-line/)
      3. Cody can ask Zhian and the workbench channel about how to update banners manually (re LC Python)


    2023-07-20 UTC 1600 


    https://umn.zoom.us/j/97918222420?pwd=dnNTcisrTmMyeEhrSWRPNEJsTjFmQT09

    Sign in



    Agenda


    1. Introductions
    2. Introduction to Data Curation for Reproducibility  (Florio Arguillas, Cornell; Limor Peer, Yale U; Thu-Mai Lewis Christian, UNC-CH) 
      1.  All lessons: https://curating4reproducibility.org/training/
      2. Lesson 1: https://curating4reproducibility.org/cure-carpentry-01-intro/ 
    1. LC Instructor Onboarding Slidedeck - initial draft (Toby and Cody): https://docs.google.com/presentation/d/1GCqeFDGeiMn3oDTsTOgdspRXqtnKt-WtXyeH_u0pIV8/edit
      1. Draft of onboarding for people who want to teach LC curriculum
      2. idea is some of us would present this at a community call, record that and put the edited video on The Carpentries YouTube channel
      3. Liz S, Lisa McA, and Tim had volunteered to review slidedeck; 
        1.  Plan would be to present this onboarding as a community call + a recording for anyone interested in learning more about LC lessons
        2. Toby will email the folks to review the slidedeck
      4. Phil & Cody to help record/present 
      5. On the Carpentries side they want to have a full collection of onboarding videos for the YouTube channel; that's the minimum; we could record a separate video for the YouTube channel - which might make it easier for updates; could be integrated in Instructor Trainings where a lot of the folks are specifically interested in LC;
      6. There will be a maintenance role as LC curr evolves - when do we re-record this?
    2.  Lisa M - LC Git and/or LC Overview updates
      1.  Still on her radar - will focus on the LC Git lesson right now and Cody/Phil would be available to help
        1. Cody teaching Git Nov 13
      2. LC Overview has not been transitioned to the workbench because the format doesn't suit the workbench
        1. Zhian working on a new solution that should help organize these kinds of overviews in a better way
        2. The problem is that the episodes are free-standing - 
        3. Toby would really like LC-CAC to decide what you want to happen to that content (the episodes in the Overview lesson);
        4. Lisa proposes to work on Overview lesson first - can a subgroup
          1. Toby, Mark & Cody will meet with Lisa in ~1 month - Cody will set up meeting - all will review the content before that meeting.
          2.  Idea to integrate professional development overview for computing in libraries
    3. Intro to AI for GLAM (just an update) 
      1. Lesson needs to be converted to workbench (Tim can have student work on this)
        1. (copying from above) the tooling to (semi-)automatically convert a lesson to the new infrastructure is here https://github.com/carpentries/lesson-transition, documented in the README - that documentation will be improved over the next couple weeks
      2. Checklist issues: https://github.com/carpentries-incubator/machine-learning-librarians-archivists
        1. Talk about these next time if they're still not resolved 
    4. UCLA-IMLS Open Science Lessons & upcoming lesson development workshop (can address next meeting)
      1. Running weekly from Aug. 1-Oct 12 (twice a week for timezones) 
      2. Winning topics: 
        1. Understanding CARE Principles for research data
        2. Research Community Outreach with Open Science Team Agreements
        3. Open science hardware: an introduction for librarians
        4. A Path to Open, Inclusive, and Collaborative Science for Librarians
        5. Data Management (and Sharing) Plans for Librarians 101
        6. Open Qualitative Research
        7. Reproducible research workflows
    5.  Process to take over maintenance for Introduction to Python (alpha) - https://librarycarpentry.org/lc-python-intro/ (Cody) [quick question if there's time] - Toby can stick around to discuss this, if you are able to stay? Perfect, thanks.
      1.  No current maintainers; No commits since Apr 19, 2022 (other than workbench); Uses Spyder 
        1. Tim: I want Jupyter Lab, rather than Spyder
        2. Cody: copy of SWC gapminder Python lesson, not many changes from that.
        3. What would process be for becoming Maintainer
      2. Should we contact Konrad Förstner (previous maintainer) first?
        1. Cody will reach out
      3.  How to make major changes without disrupting live lesson?
        1. To live lesson: add note that this will be changed on date -----, contact such and such
        2. Fork repo, than transition fork to workbench, then do development, then CAC should review the fork, and when decision is made we can figure out how to merge it (or replace it)
        3. Phil will email the Edinburgh LC folks to give them a heads up
        4. Cody will start work on the fork - doesn't need to be perfect before integrating
    6. Action items from last meeting: 

    NEXT MEETing: 

    2023-05-18 UTC 15:00 


    https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230518T1500


    Sign in


    Notetaker: Cody


    Agenda



    1. Introductions (5 min)
    2. LC-Git lesson - possibility to add GitHub Desktop episode(s) and/or create a shell-free Git lesson. (Phil, Lisa McAulay) (10 min)
      1.  Lisa is the maintainer, and likes the idea of this change; Phil and Lisa have discussed
      2.  Idea is to possibly integrate Nathaniel Porter's changes from this fork: 
        1. https://github.com/ndporter/lc-git-gui / 
        2. https://ndporter.github.io/lc-git-gui/
        3. We could encourage Nathaniel to move this to the incubator and we can link to it within the LC Git lesson for folks who want more info;
      3. Unaddressed use case: librarians who want to look at other people's code and work with it, but they don't have code of their own; Rather than use Nathaniel's lesson, it might be nice to address the use case of reusing GitHub code;
        1. Discovering code, and promote reproducibility; start from someone else's code;
        2. How to communicate with people on Git
      4. Three diff ideas:
        1. Current lesson
        2. GitHub GUI
        3. GitHub literacy (how to find and adapt code from GitHub)
      5. We like the idea of reordering episodes to start with GitHub literacy content (searching on GitHub, starting an issue), then go to editing on GitHub, then possibly GitHub Pages, then Git command line last
      6. Current structure is a barrier - you have to teach 45 min of bash before Git
      7. How to approach a lesson that needs a major rewrite?
        1.  Also how to invite reviewers and co-maintainers?
        2. Lisa has some ideas for how to get started
        3. Tim will reach out to Chris E for a possible earlier lesson that flipped the order of starting with GitHub
        4. Phil will contact Nathaniel about 
      8. LC-CAC needs to re-engage with maintainers, and especially think about ideas for maintainers who have volunteered to continue, but who are non-responsive
    3.  LC overview lesson - possibility to clarify paths through curriculum; organization of episodes within the lesson - Lisa McAulay (10 min)
      1.  Lisa needs help with this; this lesson does not work - it's currently a barrier
      2. Needs to be restructured;
      3. Episodes: Jargon busting, Keyboard shortcuts, 
      4. It's not currently a lesson in terms of having content; 
      5. LC-CAC: 
        1. We should follow Data Carpentry to create lesson overviews for curriculum
        2. We should move the episodes out of LC-overview
        3. We can make lesson paths on this page
        4. Lisa will come up with a proposal for our meeting in two months
          1. We want to keep Jargon busting and some other episodes (Foundations for LC and Computation)
    4.  Updated LC lesson audit following transition to new Workbench (Phil) (10 min)
      1.  https://docs.google.com/spreadsheets/d/192j2nRgusL1S75OZxDcivFtQZ1EedRj6ZARA7u3N80A/edit#gid=0
      2. Phil has been noting which lessons have migrated to workbench, and updating maintainers, and adding a note on maintainers who did not reply to survey, and when maintainers are correct on website, and lesson metadta with maintainers list is correct
      3. Idea to still reach out to maintainers
    5.  MarcEdit lesson moving to alpha (Phil) https://github.com/LibraryCarpentry/librarycarpentry.github.io/pull/172#issuecomment-1531661517 (5 min) 
      1.  Moved from conceptual to alpha, and updated to workbench:
      2. http://librarycarpentry.org/lc-marcedit/ 
      3.  So we need to move it to the appropriate place (Conceptual) on the LC website
      4.  MarcEdit isn't mentioned in the maintainer survey so not sure about current maintainers - we should check with the maintainers to make sure they're correct. 
      5. We can approve the move to alpha, and also share suggestions for continuing to advance towards beta
        1. Add instructor notes
        2. Remove original material or justify its existence
        3. Feedback on when it's been taught 
        4. Lesson Release checklist: https://docs.carpentries.org/topic_folders/lesson_development/lesson_release.html 
      6. Phil will add it to the Extended Curriculum on the LC website and change the status
    6. Please fill in this (very short!) check-in survey to tell us whether you are happy to continue as a Curriculum Advisor for Library Carpentry (Toby) https://forms.gle/WcLgcKrsbo2WfWJ38 (5 min) 
      1. Tim -completed it, said yes
      2. Cody - done, I said Yes
      3. Phil - done, I said yes
    7.  Request brief update on LC Lesson Program Governance Committee and relationship with CAC (Phil) (10 min)
      1. (Toby) Sorry I am not here to discuss this "in-person": the LCGC was established with five members: Eka Grguric (Chair), Lisa McAulay (Secretary), Belinda Weaver, Yared Abera, Mary Filsell. 
        1. Briefly: the idea is that the Governance Committee (LCGC) has a  similar role to that of the Advisory Group that came before it, with responsibility for overall strategy and advocacy for the lesson program. Curriculum matters are still the responsibility of the CAC and (unless you hear otherwise from the LCGC) this group has authority over matters relating to curriculum development, adoption of new lessons, etc. 
        2. During the Governance Committee onboarding, I encouraged the GC Chairs to invite their respective CAC chairs to meetings whenever relevant, and I hope to see a healthy dialogue taking place between the two groups. As far as I am aware, the group has not yet scheduled its first meeting. 
        3. Please list the questions you have for me below, and I will come back to answer them on Friday. You are also welcome to schedule a meeting with me any time via https://calendly.com/tobyhodges
        4. Questions we have: 
      2. UCLA Taught Intro to AI for GLAM https://ucla-data-science-center.github.io/2023-05-08-UCLA/. The lesson generated great discussion and interaction from primarily librarian audience (one iSchool faculty also showed). We are currently formulating feedback for authors. (5 min) 
        1.  UCLA taught it and we have some feedback for the lesson authors. 
        2. Will add instructor notes
        3. Lesson currently has checklist integrated as issues
        4. Tim will contribute back to that
        5. Question for Toby:
          1. When will incubator lessons be migrated to new workbench?
          2. There is no fixed timeframe - some lessons may never transition. 
          3. Current plan is for Zhian to run an onboarding session to show Incubator developers how to transition their own lessons. After that, Core Team will support transition of community-owned lessons when there is a reason for us to need it e.g. when lesson passes peer review in The Carpentries Lab; when lesson is to be adopted by a lesson program (e.g. when it would become an official LC lesson); when a member organisation is developing the lesson(s) and they request this; etc.
      3.  Python lesson - table the idea for retirement of the current lesson for when Toby is here
        1. Cody will brainstorm ideas - DOAJ lesson - across the whole new lesson

      Action items: 



      2023-03-16 UTC 16:00


      https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230316T1600
      https://umn.zoom.us/j/99716368718?pwd=dkJWUDZEVkxma05iK04rYTUxaU45dz09

      Sign-in: 


      Annajiat Alim Rasel, Bangladesh
      Toby Hodges (arriving a few minutes late, sorry), Germany
      Cody Hennesy, Minnesota/US
      Tim Dennis
      Phil Reed, Manchester UK

      Notetaker: Cody

      Agenda



      1.  Quick updates:
        1. Maintainer emails (on hold after Erin's email to all maintainers) - Phil
          1. https://github.com/LibraryCarpentry/curriculum-advisors/issues/12
        2. LC Onboarding slides - Cody met with Toby and will draft slides; Liz S, Phil R, and Lisa McAuley volunteered to review slides/script and/or help present. Initial plan is to present live on zoom (maybe June) to folks who are interested and record the session so others can review later.
          1. Draft slides: https://docs.google.com/presentation/d/1GCqeFDGeiMn3oDTsTOgdspRXqtnKt-WtXyeH_u0pIV8/edit#slide=id.p
          2. Why are there no Schedule or next page links on the Workshop Overview page? https://librarycarpentry.org/lc-overview/ - this is confusing - geared towards organizers, not learners. 
            1. hard to link to sub-parts due to lack of navigation, no schedule table on the landing page
            2. Phil: I have taught from the workshop overview occasionally, remember that this lesson was more intended for benefit of organisers.
            3. Tim: 
            4.  Figure out a better way to present this - it's helpful for instructors and organizers but confusing for potential learners - this could fit in with Lesson Paths (look at SWC and Data Carpentry)
            5. Toby: In DC each curriculum has its own path - links out to lessons - workshop overview helps people to understand intended order, and add set up instructions in one page for the full workshop/path; the LC overview differs because it has episodes which makes it seem like it's a lesson to be taught; the main thing to figure out is what to do with the Episodes on the Overview Lesson.
            6. Tim: ideas for what we could do?
              1. reach out to Maintainers? Invite them to have a conversation with LC-CAC about improving Lesson paths - we will wait to see if current Maintainers respond to Erin's recent email before proceeding; Jesse Johnston opted in to remain a maintainer
              2.  Toby: if you opened a PR I would add a section before Wrapping up a Workshop, describing all of the lessons with one or two sentences. I would move all of the pages to Extras and remove Episodes pages altogether. 
                1. Phil: but some overlap with what is already written under "Part 1: Introduction to working with data"
              3. Tim: how much of these episodes should still be on our page
              4.  Toby: The LC lesson website is the responsibility of the incoming Governance committee, but CAC retains direct responsibility for the Lessons pages; CAC can approach Toby directly to make changes to the Lesson page
              5. Tim: DC makes sense because they have multiple curricula, but we have different paths; we have episode introductions - 
              6. Phil: wonder if maintainers for LC Overview responded to Erin's call
              7. Toby: “One curriculum, multiple workshops” is I think how our style guide would dictate that we describe it
              8. Cody will email Jesse and Lisa about joining us at next meeting to go over what belongs on the workshop overview and any changes they're already thinking about. 
                1. Toby: I stand corrected re: lc-overview: Rayvn Manuel also responded to the survey and opted into continuing. They also commented that they want to connect more with the other maintainers on their lessons - so might be good to reach out to all three Maintainers together.
      2. Discuss: alt version of LC git lesson by Nathaniel Porter to focus on GitHub Desktop (Phil) 
        1. https://github.com/ndporter/lc-git-gui / 
        2. https://ndporter.github.io/lc-git-gui/
        3.  This came out of an LC Slack conversation about the LC Git lesson that Liz McAuley started; Nathaniel shared his GitHub Desktop variation which focuses on GUI interface
        4. GUI/GitHub first
        5.  Ideal: one lesson with different paths - does the new template allow for that? No. 
        6. Lesson authors might not want to be maintainers - is there protocol for moving from Incubator to finding Maintainers? It's up to CAC
          1. Toby: We should take into account the likely sustainability of a lesson - are there active maintainers/authors? Do the authors intend to stay on as maintainers? Or is there interest from the wider community in maintaining?
          2.  Phil: is there evidence that LC would benefit from having a GUI oriented lesson? If so, we could ask to fold it into our current Git lesson. It's a fork from the Git lesson - it adds two episodes. Once we know who the active Git maintainers are...
          3. Toby: we could ask Nathaniel to submit this for review via the LC Lab, and then have instructorstry teaching it as part of review process. 
          4. Phil: could ask folks at Edinburgh to see if they want to teach the new lesson
          5. Ultimate goal would be to merge these two Git lessons
          6.  Action item: Phil will connect with Nathaniel to see if we can connect with some LC instructors to try this out and give feedback.
            1. Possible instructors: Cody might try this in the Fall 2023 as part of a planned online LC workshop
      3. Starting points for OR lesson in checkout (Liz via Slack) 
        1. Right now only loading data is included for starting points at instructor training checkout demo https://carpentries.github.io/instructor-training/demo_lessons/index.html
        2. The checkouts will be changing in the future, but we can open up more episodes for use in the demos. 
        3. Action item: Tim can look into this and respond to suggest starting points; the idea would be to look out for dependencies;
      4. Adopting new lessons:
        1. Intro to AI for GLAM https://carpentries-incubator.github.io/machine-learning-librarians-archivists/
          1. UCLA teaching a pilot in May
          2. Need to review lesson, flag issues, and evaluate 
          3. Goal to ultimately move it from Incubator to LC repo
        2. Intro to Computational Thinking (via Belinda Weaver)
          1. Website: https://weaverbel.github.io/intro-computational-thinking/
          2. Backend: https://github.com/weaverbel/intro-computational-thinking
          3.  She is retiring and interested if it would make sense to move it into LC;
          4. Phil will ask his Elearning team if there are folks who are interested and have capacity to port this over into Carpentries infrastructure; 
          5. Toby: had a conversation with Belinda about trying to help her transfer the lesson over, and Toby can offer some support; Sounds like she's working on it;
          6. Tim is in a good time zone for meeting with Belinda, so he could follow up to see if he can get some support
        3. Is there a good place to start with migrating lessons to new workbench?
          1. Toby: there's an automated script, but it won't be run until after the official launch.
          2. Toby: best page is https://carpentries.github.io/workbench/transition-guide.html
        4. Data curation for Repro
          1. Tim - haven't heard back from lead author, need to follow up with other authors
        5. Toby: LC-CAC will get the updated list of maintainers for each of the LC lessons, along with an account of who has stepped away; probably won't share comments since they didn't get permission, but might be able to summarize in some way

      2023-01-12 UTC 16:00


      https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230112T1600

      Sign-in: 


      Toby Hodges, he/him/his (lurking for now; will join the call in ~30 min)
      Cody Hennesy, he/him
      Tim Dennis, he/him, UCLA
      Phil Reed, he/him, Manchester
      Annajiat Alim Rasel

      Notetaker: Cody

      Agenda


      1.  Review https://github.com/LibraryCarpentry/curriculum-advisors/blob/main/policy/lesson-adoption.md for adoption, please read and let's vote in meeting for adoption with suggested edits.
        1. Will wait for Toby 
          1. Toby: I put my edits in as a pull request - I'm happy with what's there now+
          2.  One more thing to add: unlike the Carpentries Lab process - a lesson in the Incubator belongs to the Lesson authors, so even if it goes into the Lab it still belongs to authors; but if it goes into LC it belongs to the Carpentries - the copyright notice changes, for example, to say it's the Carpentries. License terms shouldn't change, but attribution would change. 
          3.  There are no formal voting requirements; It's in LC-CAC's power to decide if we want to implement this; also currently in our power to decide what are voting requirements are. Carpentries staff would not get a vote.
          4. If people can attend: vote in person; if not vote on a github issue;
          5.  If we're all present vote in person; because Mark isn't present we'll vote on an issue
          6. Recruitment:
            1. Carpentries will reach out to everyone to see who wants to continue on CAC into year two
            2. We could wait until Carpentries reaches out
      2. Web scraping lesson (https://librarycarpentry.org/lc-webscraping/) update - Cody emailed with Thomas Guignard and Kim Pham who would like to retire this lesson. Interest in developing a new lesson?
        1. Could reach out to Rochelle Terman for porting some of her previous work:
        2. https://github.com/rochelleterman/scrape-interwebz 
        3.  There aren't other Incubator lessons on web scraping
        4.  The Python LC lesson has some issues - how would it fit with the Python lesson - should be a part of some path;
        5. Python dicts aren't taught in current Python
        6.  Should we develop a new lesson for the new lesson template/framework/workbench
          1. Cody will look at Collaborative Lesson Development Training Workshop (from Toby) for next steps - https://carpentries.github.io/lesson-development-training/
      3. IMLS Open Science - Call for Proposals, promote to constituents
        1. https://ucla-imls-open-sci.info/  - $5,000 for awardees plus attending online summer workshop
        2. Intention is to put these in the incubator and contribute to LC as relevant
        3. Carpentries blog forthcoming 
        4. Due date for proposals 1/31 
      4. Update on  Introduction to Data Curation for Reproducibility and Intro to AI for GLAM lessons (Tim)
        1. Tim emailed Thu Mai Christenson (1/11) - the lead author on Data Curation - about coming to our next meeting and about meeting the Carpentries Labs guidelines 
        2. Waiting to reach out to AI for GLAM - they just have a few items left to address before moving out of incubator. Tim will reach out and connect them with Toby for next steps once the checklist is complete.
        3. Annajiat taught in a workshop where this lesson was included. It was included by request so there is some demand/interest. 
      5. Lesson audit update (Cody and Phil) (https://docs.google.com/spreadsheets/d/192j2nRgusL1S75OZxDcivFtQZ1EedRj6ZARA7u3N80A/edit#gid=0)
        1. Determine if there are active maintainers - if not, we can help find new maintainers
          1. Both the Github and website maintainers should be contacted. Update the repo maintainer list
        2. Ask if they want help on Bug BBQ or Code Spring
        3.  Ask Alpha or Conceptual lessons if they want help moving up and into LC paths
        4. We could move some of the alpha lessons to Incubator to attract more attention
        5. Phil will follow up on this after holiday
        6. If current maintainers are interested in bringing other maintainers on board we can help recruit and being to organize the work - if you're interested in becoming a maintainer, open an issue and let us know
      6. Possible lesson paths (https://github.com/LibraryCarpentry/curriculum-advisors/issues/4) 
      7. Update: Retirement of XML and Top 10 FAIR Data & Software Things (Phil and Toby)
        1. LC-XML has been transferred to the Incubator and I have added a notice to the lesson site and the repository README flagging up that it is unmaintained and looking for a new owner. There is a placeholder repository at the old location (https://github.com/LibraryCarpentry/lc-xml), which exists to redirect visitors from the old lesson site URL to the new one.
          1. What did we decide to do about the lesson's listing on https://librarycarpentry.org/lessons/ ? I opened a pull request to remove it from that page: https://github.com/LibraryCarpentry/librarycarpentry.github.io/pull/170
        2. Top 10 FAIR Things is more complex than I first thought. It is not a lesson site (it does not use The Carpentries lesson template), and as such it does not belong in the Incubator. I would prefer to explore alternative options for this one. A couple of suggestions, some of which could be combined:
          1. we could remove the listing from the lessons page but not do anything with the repository (i.e. leave it where it is)
          2. we could update the associated Zenodo entry, so that it contains the most recent version of the document (I have little insight to offer in terms of how difficult that would be, nor do I know who owns the Zenodo record). 
          3. we could archive the GitHub repository, which would make it read-only
        3. Need to retire the Webscraping lesson as well ok
          1. Toby will retire the Webscraping lesson
          2. Phil will create a new table on the Lessons page (replacing the table where Top Ten Things is currently listed) that will list TopTenThings and Webscraping, with blurb before the table explaining that the lessons there are unmaintained. 
          3. Toby will make the TopTenThings repository read-only.
          4. Retire this but still mention it on the lessons page: A new table for Retired Lessons that would include Web Scraping and Top 10 FAIR Things
      8. New workbench styles breing trialled for selected lessons, should we ask to test a LC lesson?



      2022-11-03 UTC  16:00:00        


      https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221103T1600

      Phil: my calendar invite puts this at UTC 16:00, not 15:00. - Cody: Just updated the link/header above, thanks Phil!

      Zoom: https://umn.zoom.us/j/95977528401?pwd=MUxVcTY5VExobUdQS2Z6NDA2c1RpZz09
      Sign-in: 
      * Tim Dennis, UCLA, he/him 
      * Cody Hennesy, U Minnesota, he/him
      * Phil Reed, University of Manchester, he/himoni
      * Toby Hodges, The Carpentries, he/him
      * Annajiat Alim Rasel, Brac University
      * Mark Laufersweiler, he/him, Univ of Oklahoma Libraries

      Agenda


      Notetaker: Cody
      Timekeeper: 

      1. What fictional family would you most like to join?
        1. Tim - Gemstones, but as distant cousin 
        2.  Cody - um, not the Sopranos
        3. Phil - Jetsons
        4. Toby - the Cohens from the OC, I guess?
        5. Mark The Bundy's 
        6. Annajiat - Bennet - Pride and Prejudice
      2.  Policy on adding lessons to the LC curriculum (10 min) 
        1. Tim has started a first draft of a policy and will need help with feedback and structure
          1. Tim is looking for help on drafting this - 
            1. we can point to Labs for most of the process, but CAC should focus on the lesson's potential fit for LC and any other LC-specific items
          2. Idea to use Carpentries Lab as process for onboarding new lessons in our curriculum
            1. Current lab process has a checklist that includes whether lesson has been taught, getting feedback from others, series of editorial checks, then review phase, authors respond to reviewer comments. Same process could work for LC - move to LC repo instead of Labs. 
          3. https://github.com/LibraryCarpentry/curriculum-advisors/blob/main/policy/lesson-adoption.md 
          4. Need to work out mechanically how to migrate approved lessons to LC repo
          5.  Question from Toby: how involved does CAC want to be invovled in the Labs process? Should we contribute to editorial or reviewing the lessons?
            1. CAC should help find reviewers - take on the role of Editor
            2.  First step would be to ascertain whether it's a good fit for LC - editorial checks are fairly low intensity: some accessibility checks (there will be automation eventually). Editorial checks only take about one hour. Wrangling reviewers takes more time.
            3. Mark: Does CAC want to take that responsibility? Do the Carpentries feel ok with us having final say? Do we make a recommendation to Carpentries? 
              1. Toby's response: LPGC should have they ultimate say about new lessons to add/remove; Carpentries can support and assist, but the decision is not up to Carpentries curriculum team; 
        2. Ideas for elements of this document - a TOC
      3. Toby introduced the new LPGC (governance committee) structure - LCAG is likely to transform into an LPGC; see https://docs.carpentries.org/topic_folders/governance/lesson-program-policy.html#lesson-program-governance-policy and https://docs.google.com/presentation/d/1h4eY-UZT2awQ2_T7PnPEdguwRmB1auBEkp30QEqqJzA/edit#slide=id.p
        1. LPGC structure will be introduced between Jan - Mar 2023
        2. Every lesson program will have separate Lesson Program Governance and Curriculum Advisory committees (though they may choose to merge)
          1. from the policy, the Lesson Program Governance Committee:
          2. "Determines the curriculum and core curriculum for (each of) the Lesson Program’s workshop(s), together with the corresponding Curriculum Advisory Committee or by delegating curriculum decisions to the corresponding Curriculum Advisory Committee."
          3. "Decides if and when new lessons are added to or removed from the Lesson Program or delegate the decision of adding or removing a lesson to the corresponding Curriculum Advisory Committee."
          4. Current model - CAC chair can invite themselves to LPGC and will be expected to attend when invited.
          5. Toby: LC-CAC should still go ahead with current work on adopting Labs model for vetting new lessons
      4. Existing lesson submissions (can we move forward before we suss out the policy?):
        1. Introduction to Data Curation for Reproducibility  https://curating4reproducibility.org/cure-carpentry-01-intro/
          1. Phil: I have added this to the audit sheet below, missing fields repository URL and maintainers
        2. Intro to AI for GLAM https://carpentries-incubator.github.io/machine-learning-librarians-archivists/ 
          1. Annajiat: I like the lesson, I use it almost every semester
          2. Annajiat: Still need to fix keypoints and remove FIXMEs: "There is 4 TODO and 7 FIXME. So, should we wait for those?"
            1. These would be picked up in the editorial part of the Labs review.
            2. Once a lesson enters beta, it makes sense to move it to website.
            3. If you're teaching the lesson, open issues, etc. so there's evidence of engagement
            4. Toby propose: when a lesson is beta, list it on LC site, and then when they have sufficient feedback they can list it for review.
          3. Seems like a good fit, and is very close to ready
        3.  How should we triage with these two groups? Can we move into saying these can be part of LC curriculum? 
          1.  Mark: We already moved GLAM lesson from alpha to beta, should we advertise it to LC communities so they can teach it. We should promote it. 
            1. Do we also move it to Labs process now?
            2. Tim: When do we put it on our website?
              1. Phil: what heading should we put it in?
              2. Mark: the website is where people will look for lessons.
          2. Mark: We should walk the Data Curation lesson from alpha to beta - can we meet with them to walk them through the process? 
          3. Tim will review the curation lesson and will email the Data Curation folks to invite them to a CAC meeting to advise on moving from alpha to beta
          4.  Toby: "in short: alpha means the authors are testing their lesson; beta means that people who aren't the main authors are testing it"
      5. Lesson archive update (LC Top Ten FAIR, XML, PR for removing from website) (5 min) 
        1.  Annajiat: vote for XML but would like to vote against removal of LC FAIR
        2. Phil will handle retirement of XML - Toby can help - Phil doesn't have authority to archive - 
          1. Toby is working on a retirement process - we might move this out of LC and into Incubator instead of archiving so that it's more visible in case others want to develop it. Phil will email team@carpentries.org and suggest it moves to the Incubator. 
          2. Instead of moving it off website, will create a new heading for Retired Curriculum where we list them.
        3. Cody will email Liz to clarify which FAIR lesson is intended to be retired. - Liz confirmed it was the Top 10 FAIR Data & Software Things
      6. Status of Lesson Audit spreadsheet & next steps: https://docs.google.com/spreadsheets/d/192j2nRgusL1S75OZxDcivFtQZ1EedRj6ZARA7u3N80A/edit#gid=0
      7. Lesson paths progress: https://github.com/LibraryCarpentry/curriculum-advisors/issues/4 
      8.  Scheduling 2023 meetings (Cody) - should we move periodicity to every other month? 
        1.  CAC should meet every other month. Review processes should be also available by request - we could try to have ad hoc meetings to support reviews for alpha to beta.
        2.  Cody will check with Liz on timing and if this works we'll stick with UTC  16:00:00 as a meeting time

      2022-07-29 UTC 01:00:00


      https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220729T0100

      Zoom: https://umn.zoom.us/j/96739206118?pwd=bmpUUHU5M2hUdkxYZml5TmkwdWlWdz09
      Sign-in: 

      Apologies: Phil Reed

      Agenda


      Notetaker: Cody
      Timekeeper: Liz! (lol)

      1. Icebreaker/intros 
      2. Proposal: Adopt Carpentries Lab for adding new LC lessons to the curriculum (TIM)
        1. Tim met with Toby in May! 
        2. LC would be first lesson program to adopt Labs as a required process for including new lessons
        3. It would provide a structured process for vetting and improving lessons prior to adoption
        4. Toby & Carpentries infra can help move lesson to our github org (including redirects)
        5. CAC would need to review or recruit reviewers for the lessons - CAC would know the potential audience and could recruit relevant reviewers;
        6. CAC would need write up policy for website and governance
        7. Need to let lesson authors know and steps to follow
        8. Current candidate lessons: Intro to AI for GLAM & Curation for Reproducibility
        9. Lessons would first be submitted to CAC and we would decide if it's relevant to LC, if it would make sense to begin the Labs process.
        10. Would be an interesting use-case for the community - using the pathway to approve lessons for inclusion in LC
        11. Tim can write this up as a formal proposal - where should we put it? Somewhere on GitHub? Will eventually need to update it on the website. 
          1. Erin: we should put the proposal here: https://github.com/libraryCarpentry/curriculum-advisors; if we want conversation and back and forth would be good as an issue; if it's just something to vote on just a PR; 
          2.  Liz: maybe first we want some community feedback and conversation; 
          3. If we decide to go this route, when we submit lessons to Lab we would do a PR; 
          4. CAC can decide internally how we decide and workflow for a new policy; would also be our decision to approve lessons for Lab submission eventually;
          5. For CAC to decide: Is Lab the full approval process? Or is it only a part of the review process and CAC has other guidelines that we follow before or after?
            1. Possible workflow: Step one contact CAC who can determine if it fits LC
            2. what would be teh least obtrusive process?
            3.  step 1 - if interest contact the cac - step 2 see guides (CAC has a short rubric to determine if the lesson is relevant to LC)-  step 3 curriculum review goes into labs where the quality of the lesson will be reviewed according to the peer review process
            4. important to keep short and show process on out website.
      3. Retiring the LC FAIR data and software (Liz) and XML lesson (Phil)
        1.  Energy  better spent on new lessons; can test retirement process (which might not exist)
        2.  General practice: to archive on GitHub; CAC update website;
        3. Do we want to push up to Zenodo first? For credit, etc.? Not sure about the usefulness of this - for preservation? But how useful? To support career reviews - but archived GitHub repos are still viewable, so probably no need to add to Zenodo? It will still be accessible in GitHub (as long as Github exists and is open, which is not in our control)
      4. LC Lesson audit (Cody, for Phil): "Cody and Phil will identify key LC lessons (those active and frequently taught). LC-CAC will then reach out to maintainers of those lessons to arrange for Sprints or Bug BBQs to help resolve outstanding issues/PRs. https://docs.google.com/spreadsheets/d/192j2nRgusL1S75OZxDcivFtQZ1EedRj6ZARA7u3N80A/edit?usp=sharing&urp=gmail_link
        1. for maintiners wokring with lessons on their own - how do they handle the retirement question?
        2. CAC can decide how to make decisions to retire other lessons where people don't self-identify their own lessons for this consideration
        3. CarpentryCon skill up session on GitHub for maintainers - could be relevant (how to archive)
        4. Questions from Phil and Cody - how to get a handle on which lessons are being taught? there are 4 key questions or categories we can summarise these lessons for next steps:
          1. Lessons we know ppl want to retire - easy fix
          2. These lessons look good and there's no communication required
          3. Quality lessons to follow up with maintainers and how to help out
          4.  Most complex: is this really ok to be associated with LC? Eg webscraping is one which has often been forked and drastically changed. 
          5. Erin: how do we know these are being taught? We only know this at the curricular level, not yet at the lesson level. Erin could take it to the developer level if it would be helpful to track at a more nuanced level. Yes, CAC would be interested - lesson subsets of lessons are built in for DC in GitHub template, would be great if it's in LC. CAC would need to define what those subsets or what those packages are. Having individual lesson tags wouldn't work necessarily with the current set up. 
          6. We might want to reach out to LC channels for feedback on whether or not they're teaching certain lessons. 
          7.  Would it be useful for CAC to identify some "packages" of lesson (e.g., archiving, collection mgmt, data skills)? We could make decisions easier for hosts. 
            1. Those packages can help prepopulate the set up instructions for you.
            2. would also be practical for building website
            3.  How else about new lessons not necessarily part of a package? Could CAC recommend packages?
            4. Could help people choose high quality lessons if we're creating packages
            5. We might want to be less modular and bespoke at this point
            6. The packages or subsets or paths could be designed for sub-audiences
            7. CAC should draft a package outline as an issue in our repo - Liz will take the lead on this. Erin notes the terminology to 

      1. Quick update: LC lessons don't have working anchor tags for subheadings, which will be addressed by Carpentries when they update LC lesson styles/infrastructure in early 2023.
        1. See comments on original issue:  https://github.com/LibraryCarpentry/lc-spreadsheets/issues/126; Also: https://github.com/orgs/LibraryCarpentry/teams/lesson-maintainers/discussions/1?from_comment=1
        2. Don't need to worry about it bceause people are working on it and will be irrelevant with the workbench
        3. Full update for maintainers: https://carpentries.org/blog/2022/01/live-lesson-infrastructure/#for-maintainers-getting-the-latest-features
      2.  Reminder about CarpentryCon session on LC curriculum on  Thursday, August 4, 2022 at 16:00:00 UTC https://pad.carpentries.org/cc2022-library-carpentry-curriculum Yay! 2 x audiences - other CACs, and LC maintainers. May break out to 2 seperate groups.
        1. We should invite the all CACs mailing list (Cody will do this)
            1. curriculum-advisors-all@lists.carpentries.org
      3. UCLA got a grant from IMLS to work on Open Science Lessons for Librarians, https://twitter.com/liber8er/status/1552760719426199553


      2022-05-05 UTC 15:00  


      https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220505T1500
      Zoom:  https://umn.zoom.us/j/94346756772?pwd=VGgrUkpPdlM0YmoybkpmVTdJOVRkQT09
      Sign-in: 
      Name, Institution, email, handle (github)
      Tim Dennis, UCLA, tdennis@library.ucla.edu, @jt14den
      Cody Hennesy, U Minnesota, chennesy@umn.edu, @chennesy, he/him
      Phil Reed, University of Manchester UK, phil.reed@manchester.ac.uk, @PhilReedData, he/him
      Mark Laufersweiler, Univeristy of Oklahoma , laufers@ou.edu, @laufers, he/him
      Annajiat Alim Rasel, Brac University, annajiat@gmail.com, @annajiat, he/him
      Guest: Mike Trizna, Smithsonian Institution, triznam@si.edu, MikeTrizna
      Guest: Daniel van Strien, British Library, daniel.van-strien@bl.uk, davanstrien

      Apologies: Liz Stokes

      Agenda


      Notetaker: Cody
      Timekeeper: 

      Icebreaker/intros 



      Intro to AI for GLAM Lesson


      Status: refer to CAC issues


      LC Lessons status:



      How to teach with Participatory Live Demonstration


      Random asynchronous contribution. Recently on the trainers slack channel the question of "Why are we learning to run participatory live coding if we're librarians and only need to show people how to use open refine and spreadsheets?" was reported by a trainer at their recent Instructor Training. Sarah M Brown has created an issue for further discussion - seems legit to bring it to LC-CAC attention. https://github.com/carpentries/instructor-training/issues/1363

      Next meeeting: 2022-07-29

      NOTES:

          1. Host the workshop for another group with different instructors (Tim Dennis and Cody Hennesy both interested)
          2. Lesson devs: resolve issues from checklist
          3. Check in with Toby about steps for moving from incubator to LC, through Alpha/Beta/Stable, and possibility for Labs?
          4. Recommend creating instructor notes (https://carpentries-incubator.github.io/machine-learning-librarians-archivists/guide/index.html)

      Status: refer to CAC issues
      Tim will close hanging issue. 
      Cody will double check that label is available in all lessons/github repos

      LC Lessons

      Live-coding requirements (https://github.com/carpentries/instructor-training/issues/1363)




      Meeting 1: Fri 11 Mar 2022 UTC 1:00am (see in your timezone): 


      https://www.timeanddate.com/worldclock/fixedtime.html?msg=LC-CAC+Mar+2022+%28mtg+1%29&iso=20220310T19&p1=159&ah=1&am=30

      Zoom link: https://umn.zoom.us/j/96513448749?pwd=OWdhUTVFckpDbm5udnVRVUxDMmlhZz09

      Attending:


      Liz and Cody attended and so held a short meeting; adjourned around UTC 1:20;

      Agenda:


      Chair: Liz Stokes
      Secretary: Cody Hennesy
      Notetaker:
      Timekeeper:

      Introductions (10 mins)


      Purpose of this committee (15 mins) 


      Issues and pull requests tagged to the CAC on GitHub (10 mins)


      https://github.com/LibraryCarpentry/lc-data-intro-archives/issues/7
      Last comment Aug 2021

      From the incubator (possibly relevant)
      https://carpentries-incubator.github.io/machine-learning-librarians-archivists/
      https://carpentries-incubator.github.io/tei-xml/
      https://carpentries-incubator.github.io/python-text-analysis/

      Requests (10 mins)


      Cody: https://www.imls.gov/grants/available/laura-bush-21st-century-librarian-program

      I've been talking with Tim Dennis at UCLA about a second round proposal they're working on for an IMLS implementation grant related to developing modular open science lessons for librarians. (Chris Erdmann & AGU are also closely involved) 

      In short, the program would fund the creation of 14 new open science lesson modules, following the Carpentries lesson development process and philosophy. Tim wondered if I would be able to serve on a nine-person committee to support the project (if it's funded) as a representative of the current LC-CAC. They'd want to ensure that lesson development through the grant was coordinated with input from LC-CAC. The (grant) committee would also develop program objectives, the scope of lessons, the CFP, and then review lesson proposals. I'd be happy to work on this, but we wanted to check in first with both LC groups for any input. 
      The next round of proposals is due soon - March 25 - so any thoughts or advice is welcome.
      Upcoming changes to software or changes in practice occurring in the field that should be considered by CAC.


      Housekeeping (10 mins)






      Meeting 2: Mon 14 Mar 2022 UTC 8:00pm (see in your timezone): 


      https://www.timeanddate.com/worldclock/fixedtime.html?msg=LC-CAC+Mar+2022+%28mtg+2%29&iso=20220314T15&p1=159&ah=1&am=30

      Zoom link: https://umn.zoom.us/j/92035608679?pwd=dWFEUDBaWnlOR0NVYWZWbW9MNEFYdz09

      Attending:


      - Annajiat Alim Rasel
      - Cody Hennesy
      - Liz Stokes
      - Phil Reed 
      - Tim Dennis +
      - Toby Hodges (Carpentries Curriculum Team Liaison)

      Agenda:


      Chair: Liz Stokes
      Secretary: Cody Hennesy
      Notetaker: Toby Hodges
      Timekeeper: Cody

      Introductions (10 mins)


      who we are and what we are hoping to get out of the CAC
      - Liz: hoping to pass on the Chair role to someone else, excited about CAC changing the direction of LC curriculum.
      - Phil: U Manchester Library, UK. Looking forward to insurance & reassurance of longevity for LC curriculum. Tie off some loose ends.
      - Tim: looking forward to harmonising lessons & lesson objectives. making sure core lessons are up to snuff, charting a course for new material relevant to libraries. exciting to have an active CAC, work on lesson Incubation going on. want to make sure all that is working together.
      - Cody: U Minnesota Libraries, USA. Looking forward to learning how it all works with Carpentries curriculum. Bringing core lessons up to speed. 
      - Annajiat: Brac University, Bangladesh. Looking forward to looking at lessons in various different stages of development, seeing how they are going and whether we are meeting needs.  Specially, lessons in the incubator, Webscrapping, FAIR data, text analysis, xml, wikidata etc.
      Toby - Director of Curriculum - actingas Liaison to this committee - based in Heidelberg, Germany, some meetings may not suit me - but advantages of distro team other members in Pacific time we shoudl be able to send one to one of the two meetings. Here to support and guide in decision making - most looking forward to seeing these convos happen. Things touched on from the LCAG and reinvigorting some of the LC community around core topics. Eg how to recruit new maintainers to core lessons.



      Purpose of this committee (15 mins) 


      Issues and pull requests tagged to the CAC on GitHub (10 mins)


      (likely a regular standing item) Liz looked through all the LC lessons, looking for issues with the 'status:refer to cac' label. this was the only one.
      https://github.com/LibraryCarpentry/lc-data-intro-archives/issues/7
      Last comment Aug 2021
      Annajiat: a few things that should be added to the checklist:
      Toby: checklist is from https://docs.carpentries.org/topic_folders/lesson_development/lesson_release.html, associated with lesson publciation process. But that process is goig to be redeveloped.
      Annajiat: Lesson Publication Task Force has been discussing lesson publication process, among other things.
      Toby: part of a larger question for this CAC about whether you want to bring this lesson into core curriculum/somehwere else, how this fits into the wider vision you have for LC curriculum.
      Tim: this lesson is in alpha - we should ask the maintainers to check if they have gone through the other steps required to move into beta, as described in https://cdh.carpentries.org/the-lesson-life-cycle.html

      Liz: perhaps we should communicate with Maintainers to make sure they know to use this label? What should be our convention for responding to things that we are tagged on in GitHub?
      Tim: I think we should feel free to respond individually, perhaps confer via Slack/other channel when needed.
      Liz: best contact is through TopicBox that we already have set up. 
      Topicbox: 
      GitHub team for LC-CAC:
      https://github.com/orgs/LibraryCarpentry/teams/curriculum-advisors so you can all be tagged as LibraryCarpentry/curriculum-advisors - this is the method Maintainers should be recommended to use.

      Action? contact Maintainers and remind them to do this.

      Liz: appendix to this agenda includes a list of lessons. We could assign ourselves to lessons in earlier stages of development to help them move these lessons forward? Anyone want to volunteer to do this for lc-data-intro-archives?
      Cody: should we audit these lists first, to identify which are in-demand and are being actively maintained.
      Tim: could move orphaned lessons into Incubator? might bring more attention to them.
      Cody: that makes sense to me.
      Liz: +1
      Phil: we talked about this last year in an LCAG meeting, someone raised concerns about whether they would be better kept as conceptual lessons in LC. But seems neater to me.
      Liz: inactive for 12 months = orphaned?
      Tim: and are not being taught.
      Toby - could move the lesson repo into the incubator, and mechanisms to new maintainers to incubator lessons, while still listing them on the LC lessons website? Probably solves problem whether people will find them more or less via Incubator or LC lesson page. Locus of activity in incubator
      Phil: will we do this for all conceptual lessons?
      Liz: beta FAIR lesson is a little different from other lessons. FAIR Data & Software lesson is an attempt to create something more like a "Carpentries-style" lesson.
      Phil: is "conceptual" synonymous with "pre-alpha"
      Tim: I can't remember but +1 to treating them as the same.
      Phil: are we ready to figure out today which lessons should be moved?
      Need criteria - a commit in the last 12 months, but always need a step for contacting the maintaines before LCCAC doing the transfer. If going to move a bunch in the incubator, but also moving incubator lessons out and into the lessons, so detrmining the meta-workflow. I have thoughts to share on this, but it's a big discussion to have at another meeting. Incubator = find lessons in active development. Set up the Carpentries Lab for peer review process, and then lessons for wider distributions. But what does that look like for lessons in the lesson programs that aren't neccessarily in that pipeline. LC-CAC may need to work out the broader goals of curriculum design and the agreed leadership of the group / direction of LC-CAC.
      Redirection from the lesson pages will need placeholder redirects. see https://github.com/carpentrieslab/python-aos-lesson as an example.
      Liz: maybe someone can volunteer to look through the lessons and prepare a list of candidates for moving to the Incubator for next time.

      Annajiat: We might be interested to add CARE principles as a lesson or merge with FAIR, https://www.gida-global.org/care

      Phil: the following lessons may be quiet: Webscraping, maybe Python, and will retire XML.

      From the incubator (possibly relevant)
      https://carpentries-incubator.github.io/machine-learning-librarians-archivists/ +1+1+1+1
      https://carpentries-incubator.github.io/tei-xml/
      https://carpentries-incubator.github.io/python-text-analysis/ +1 +1+1+1+1

      Requests (10 mins)


      Cody: https://www.imls.gov/grants/available/laura-bush-21st-century-librarian-program
      I've been talking with Tim Dennis at UCLA about a second round proposal they're working on for an IMLS implementation grant related to developing modular open science lessons for librarians. (Chris Erdmann and AGU are also closely involved) 
      In short, the program would fund the creation of 14 new open science lesson modules, following the Carpentries lesson development process and philosophy. Tim wondered if I would be able to serve on a nine-person committee to support the project (if it's funded) as a representative of the current LC-CAC. They'd want to ensure that lesson development through the grant was coordinated with input from LC-CAC. The committee would also develop program objectives, the scope of lessons, the CFP, and then review lesson proposals. I'd be happy to work on this, but we wanted to check in first with both LC groups for any input. 
      The next round of proposals is due soon - March 25 - so any thoughts or advice is welcome.
      Upcoming changes to software or changes in practice occurring in the field that should be considered by CAC.


      Phil: any overlap with existing LC lessons? what kinds of topics are you aiming for?
      Tim: conceptual content around Open Science, teaching advocacy and eductational role for librarians, slightly different objective to LC. We'd like to use some similar infrastructure to The Carpentries but recognise the learning curve involved.
      Tim: rough draft - https://docs.google.com/document/d/1WnXWzUsBHNsYAnm4XtOsqDWBHacdKLLRjWOBn43WTpo/edit# Focus is on librarians and libraries in the USA, but hope they will be broadly shared.
      Liz: is it worthwhile making an effort to align LC with Open Science more generally? E.g. guide our curriculum development?
      Cody: to me it fits in with the project I've been working on with others, to identify and acknowledge the other curriculum out there that is relevant (see, e.g., https://github.com/LibraryCarpentry/governance/issues/36 and https://github.com/LibraryCarpentry/governance/issues/35). include these in some way, e.g. point our audience to those materials.
      Annajiat: I think Open Science falls in the purview of LC.

      Phil: need to be cogniscent that framing LC with science can be alienating to thsoe in other domains e.g. humanities.
      Tim: idea is to be able to connect with other groups developing these standards and be responsive to it.
      Liz: seems like we approve this involvement.

      Housekeeping (10 mins)




      2022 Appendix


      Stable lessons
      These lessons are mature and ready to be taught. Most have been taught multiple times. The content is well-established, but minor changes and improvements (e.g. better explanations, spelling/grammar corrections, improved exercises) are always welcome.

      Alpha lessons
      These lessons are under active development and may not be ready to teach without additional preparation and background knowledge. Further development work is strongly encouraged - please get in touch or check out outstanding issues on GitHub to find out what is needed.

      Beta lessons

      Conceptual + Pre-alpha
      These lessons are still in the conceptual phase where community members have just started to discuss general ideas , learner profiles, goals, summative and fomative assessments, concept maps, software and data to be used, how long the lesson should be, and connecting the dots before moving to the alpha phase.


      Library Carpentry Curriculum Advisory Committee (2018)



      3 October 2018

      Attending
      - Chris Erdmann
      - Erin Becker
      - Mark
      - Carmi
      - Katrin
      - Erika

      Notetaker
      - Carmi

      Agenda:
          Guidance from Erin on summary letter of agenda items:
              
              Good morning, day, evening to all of you!

      It was great seeing everyone and thank you for a lively discussion!

      We spent some time discussing what constitutes a Library Carpentry. Most members have been in favor of being more inclusive and being flexible so that we encourage more people to enter the LC community. What is helpful is that the Governance Group and the community have identified the core lessons for us:

      https://librarycarpentry.org/blog/2018/08/07/what-is-a-workshop/
      https://librarycarpentry.github.io/lc-overview/

      In brief, they are: Intro to Data, Shell, OpenRefine, Git

      During our incubation period to become a full-fledged Carpentry, LC needs to demonstrate a set of core lessons. What signals to The Carpentries that we are serious is that we have formalized/published the lessons via Zenodo. We can do this now, but one of the priorities we highlighted is that we need to do QA on the lessons before we do this. I think this is where we need Erin's guidance, so I will share with her this challenge so that she is prepared to outline the steps we can take to move this forward.

      Having said this, as part of my grant, I need to formalize 7 of the LC lessons and have chosen Git to work on first, so I will most likely lean on members of this group for guidance. I guess I can also be the guinea pig for all of us.

      We also talked about addressing modularity in the lessons. I myself don't know how to quite address this one and I think it is also something we can ask Erin about. However, we came up with a practical solution which is to include one/all of us on a thread when modularity comes up in the community. 

      Highlight:
      We have a lot of questions around maintainers and how issues and PRs are coordinated in the lessons. There are some very basic things we can do to start which is to send out a message to the maintainers with a list of questions:

      Is how we list maintainers sufficient and what ideas might they/we have for providing more information about them? Website
      What are the processes/workflows surrounding lesson maintenance? Handbook
      Do our maintainers want to rotate out and others rotate in? Spreadsheet
      Would it be good to host a 1-hour session around lesson maintenance? And who should be invited? Maintainers and CAC to start? Plus the Governance Group? Or should we make it open to the community? Webinar? 
      What is the history behind the lessons? It was lost when the lessons moved from the data lessons organization. Maintainers Meeting (All or by lesson?)
      What should the coordination of lesson maintenance look like? Handbook (Maintainer Lead?)

      https://carpentries.github.io/maintainer-onboarding/ 
      https://datacarpentry.org/images/blog/Report-maintainer-interviews-2017-public-version.pdf 
      Previous application form (please make a copy for edits): https://docs.google.com/forms/d/1puzeeBRh8apsiBmCGrOzFg0Tk7dtm3bkmuH-j-vByfQ/edit 

      This is most likely something else that we should ask Erin about though.

      Last, of all, there are two easy items on our list. One is a homework assignment, to read Teaching Tech Together and share your feedback in the Etherpad. Tim brought up the Venn diagram, so we can do an exercise where we all brainstorm what a diagram with LC would look like and then share it with everyone. There is no rush to do this, so we may want to wait until we talk to Erin and have 2 or 3 meetings in the books. 

      This is what I captured from the meeting. Let me know if I missed anything or if that is on target? I will send a Doodle poll to in the next day or two to everyone so that we can plan our next meetings.

      Thanks, everyone!!!
      Chris

      Additional items:
          Chair selected - Katrin Leinweber
          Call for Maintainers
          https://docs.google.com/spreadsheets/d/18rNY0LOf8zUzMMilWzh-vmhukL_Ty6hu3_nngkyCmus/edit#gid=0
          Review LC website
          https://librarycarpentry.github.io/test/
          Carpentries Venn Diagram
          https://github.com/LibraryCarpentry/governance/issues/8
          Handbook : Maintainers
          https://docs.carpentries.org/topic_folders/maintainers/index.html
          Teaching Tech Together Progress?

      Notes:
          Questions from last meeting for Erin:
              -number of maintainers per lesson? minimum 3
              -letting people know who is maintaining lesson? List on top of ReadMe.md files!
              -recruiting for more maintainers, relieve previous maintainers - in progress https://docs.google.com/spreadsheets/d/18rNY0LOf8zUzMMilWzh-vmhukL_Ty6hu3_nngkyCmus/edit#gid=0 - people have had questions about what is involved so onboarding would be helpful - Mark: suggests handover to help transition
              -how to manage new lessons - need to establish expectations through onboarding
              -do lessons require publication e.g. Zenodo - not necessary
              -onboarding new maintainers - Erin: 3x 1hour onboarding sessions (now a requirement in the Carpnetries over the last year) - recommends doing this to assist in building community (social and tech support) https://carpentries.github.io/maintainer-onboarding/. Katrin has done this for R Novice lesson - useful in terms of discussing unresolved issues. Chris suggests Tim & Carmi organise these sessions. Erin suggests doing this as early as possible.
              -how to manage issues in lessons - Erin: anything that changes full structure of lesson should go to CAC. Can use GitHub tags to highlight issues that should be raised in CAC. Can create a team and use @ symbol so that people on the team get an email notification.
              -Mark: scheduled announcements/release of updates - Erin: 6 month publication cycle in SWC, however this is manually intensive which is being streamlined. Genomics group looking at a 2 year period for major changes. Must be in stable state (no bugs). Erin: Chris will need to do any releases.

      Thanks to Erika for Venn diagram.

      Chris: review new website https://librarycarpentry.github.io/test/ - our lessons https://librarycarpentry.github.io/test/lessons/
      Thanks to Katrin for volunteering to be Chair of CAC.

      6 August 2018

      Attending:
          - Chris Erdmann
          - Erika Mias
          - Katrin Leinweber
          -  Carmi Cronje
          - Mark Laufersweiler
          - Tim Dennis
          
      Agenda:
          
          Lesson study, figure out modular points?
          
          What are the top 3 items that you think the LC community needs for the CAC to address during the first year?
         
      * td 





      About migrating GitHub repositories: https://help.github.com/articles/about-repository-transfers/