Library Carpentry is a volunteer organisation whose members teach software and data skills to librarians. Housed on GitHub, all Library Carpentry lessons are open source, with an open contribution model, and lessons are collaboratively created and maintained by volunteers.
I have worked as co-maintainer of the XXX Library Carpentry lesson for YYY years. This work equates to the role of an associate editor at a journal - someone who evaluates submissions and helps shape a journal’s direction and content. Lesson maintenance involves discussing and resolving issues raised about the lesson, managing corrections and updates to material, and implementing larger directional and content upgrades.
Working as a lesson maintainer has sharpened my skills in the following ways.
• developed excellent version control skills and experience with git and GitHub
• broadened my strategic thinking and decision-making capabilities
• gained valuable experience managing a collaborative project – both the technical aspects and managing
interpersonal interactions with a wide range of community members
• gained useful teaching insights and perspectives by working so closely on a specific lesson
• developed transferable skills in software development and teaching
• volunteered my time to help teach others these skills because I believe in the importance of these skills to
• learned better time management to stay on top of all my commitments.
library-python-introcourse, and was hoping someone could clarify whether the course is to be taught entirely in Anaconda/Spyder, or if it will use Jupyter Notebooks? The 'setup' section seems to suggest the former, but I see references in the lessons to Notebooks. Should these be removed? Cheers, S
@schuyberg Welcome Schuyler! Would be great to have some more contributions to the Python lesson. @c-martinez is a maintainer too. We have been slowly working through the lesson. I primary focus so far has been to make the content more library and less math. Since the Sprint earlier in the year we've slowed a bit on development, but I'm going to endeavor to ramp up again in a week or so.
If you want to have a more in depth chat about it anytime please let me know. I can fill you in on a discussion I had a while back with @elliewix and @elainewong about its future direction.
I'm hoping it might get some love via @chodacki 's grant too.
To answer your question about Spyder or Jupyter, it was decided we would use Spyder, so yes, the setup needs fixing. If you want to do that and PR it that would be awesome :)