-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overview check-in #49
Comments
Hi Cody, thanks, this would be great. I think we need a bit of coordination, so I'll look forward to the possibility to discuss with CAC. I think I can make it to the LC-CAC on May 18. Do you need us to RSVP or anything? |
Sounds good, thanks Jesse!
All: If you can attend on May 18th, let me know your preferred email
address and I'll share the zoom link with you.You can find me directly at
***@***.*** to leave your email off of the issue thread. Or if the
18th doesn't work and you'd like to take part, let me know and I can look
for a better time for us all.
…On Wed, Mar 29, 2023 at 5:06 PM Jesse Johnston ***@***.***> wrote:
Hi Cody, thanks, this would be great. I think we need a bit of
coordination, so I'll look forward to the possibility to discuss with CAC.
I think I can make it to the LC-CAC on May 18. Do you need us to RSVP or
anything?
—
Reply to this email directly, view it on GitHub
<#49 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANCQPB7BDX5TQIE3ZWAHYDW6SW6XANCNFSM6AAAAAAWK4XYXM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Cody Hennesy (he/him)
Journalism & Digital Media Librarian
University of Minnesota Libraries
***@***.***
|
I can also attend on May 18. I may already be attending that same meeting because of discussions about the LC Git lesson. I will write you on Carpentries Slack. |
Hi @chennesy et al - I'm afraid I missed the May 18 meeting. Was there anything discussed, and any outcomes we should know about? Apologies for missing it, I think it just didn't make it to my calendar. But I July 20 may be another option for me. Would it be worth trying to attend then? -JJ |
Hi @morskyjezek - No problem! I just added the meeting minutes as a PR so feel free to peruse. I think the main takeaways are that @emcaulay will be working on general plans for some major changes to the LC Git and LC Overview lessons over the next few months. We're planning to discuss again with LC-CAC during the July 20 meeting. I'm sure Lisa would welcome help working on plans for those lessons if you're up for it and/or I'd be happy to add you to the July meeting. -Cody |
Hello All, As a follow-up from the July 20, 2023 Library Carpentry Curriculum Advisory (LC-CAC) meeting, @chennesy, @tobyhodges , and I met today and agreed upon the following recommendation that @chennesy will take to the September LC-CAC meeting:
|
Thanks @emcaulay! Maintainers: let me know on the Carpentries Slack if you'd like to attend the next LC-CAC meeting (Sept 21) to discuss this proposal, and I can send you the details. |
Thank you to @emcaulay for taking on the revision work - in my opinion, it is beyond the scope of the regular work of maintainers since it involves significant revision of content and structure, which impact the assumptions and plans that support the rest of the curriculum, so it is so helpful and critical to have the CAC input on this. |
Quick note: I agree that "Jargon Busting" needs some refresh. And in most (all?) of the LC workshops that I've taught, we have begun with the spreadsheets lesson (ie, "Tidy Data"), I'm not sure it would help that lesson to have the Jargon Busting there. It is intended as an icebreaker, which may or may not lead into the spreadsheets lesson. Another common starting point is the RegEx lesson, which could also use a refresh but would be an equally logical place for the episode. As such, I would actually suggest leaving it in the Overview as an optional icebreaker for anyone who wants to use it. |
@morskyjezek , totally agree with you that this is not a maintenance task, but a curricular revision. CAC are leading direction, and I am volunteering for this special job. I welcome help, but it's definitely not maintenance. LC-CAC meets tomorrow (9/21), so I'm refreshing my memory on 9/20 by catching up on this thread. |
@chennesy another topic for tomorrow could be -- retitle this issue? Is this the issue for taking action or making decisions? What factors will lead to being able to close this issue? |
Thank you for taking this on! I have to apologize because I teach Thursday mornings and will likely miss the meeting. Apologies, again. That said, I want to support this effort to revise the lesson as much as I can, so please let me know of there's additional work or changes I can help with. 🙌 |
Thanks, @morskyjezek ! I really value your opinions shared here! @chennesy and I will report out here. I will be in meetings all day after the CAC meeting so my comments won't come in until 9/22. |
We had a good discussion today. And I will link to notes tomorrow. |
I think a good action (leaving this as a note to myself, mostly) will be to close this issue and start opening new ones to document the archiving process. |
I am in the process of extracting all the recommendations in the comment from 2023-08-18 into discrete issues. I will keep this issue open until I complete that work. |
Hi LC-Overview maintainers! @morskyjezek @emcaulay @r2c0der
The @LibraryCarpentry/curriculum-advisors were recently discussing the Overview lesson and we were all happy to hear that you are all interested in continuing as maintainers! We wanted to see if you would have time to join an upcoming LC-CAC meeting to discuss opportunities for this lesson. Specifically, the CAC talked about some possible future goals related to:
We're definitely open to other topics too!
Here are a few upcoming LC-CAC meetings - let me know if these work for you. If not I'd be happy to put together a smaller meeting at another time.
thanks!
Cody
The text was updated successfully, but these errors were encountered: