-
Notifications
You must be signed in to change notification settings - Fork 10
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
Extending Library Carpentry #34
Comments
Hi @acabunoc I'd like to change the GitHub Repo field for this project to https://github.com/data-lessons/librarycarpentry as that repo's README is where I have listed all the info thus far for the project - the README has the plan of work, the license, who can participate, the code of conduct etc. Not sure personas, a separate roadmap, or data reuse etc are relevant to what we are trying to do - I am leaving the project pretty fluid so people with different needs for the materials can develop what suits them, but happy to hear differently if you think I'm wrong. Thanks Belinda |
Thanks @weaverbel! This looks great 👍 I updated the issue & added you to the repo so you should be able to keep updating. Thanks again! |
I am new to this so apologize if I am asking in the wrong place. There are a few of us who are interested in working on this remotely from Caltech in California. I've forked some of the data-lessons repositories we interested in contributing to. Do we just submit pull requests at the end of the sprint? Thank you, Robert |
Hi @rsdoiel - yes that would be great. We can also use the etherpad - which you've found - to discuss actions http://pad.software-carpentry.org/bris-sprint. There are a stack of other people involved - can you please send me your email address and I'll hook you and @pitviper6 into that thread. My email is b.weaver AT qcif.edu.au |
Hi @weaverbel - would love to join this effort. Will come to UQ. Exciting! |
Looking forward to it - I'm holding an LC workshop the week of 7/18 and am Juliane On Fri, May 27, 2016 at 3:26 AM, njsimons notifications@github.com wrote:
|
Hi @acabunoc I've added a CONTRIBUTING.md file to https://github.com/data-lessons/librarycarpentry as well as a Code of Conduct. Along with the README, that should be enough to get people going. Looking forward to kicking it off in under 12 hours! |
FYI: I am creating an intermediate lesson around shell, curl and web API. The repository I am working from is https://github.com/caltechlibrary/library-shell-curl-and-api |
I will help with the code of conflict as well |
[ Project Lead ] @weaverbel
[ GitHub Repo ] https://github.com/data-lessons/librarycarpentry
[ Track ] Tools: you are building a tool others can help you build, Open Educational Resource: you're collaborating on curriculum or other educational resources
[ Level ] Intermediate
Description
The aim is to expand and extend the existing Library Carpentry materials created by James Baker (github.com/LibraryCarpentry) We are hoping to add new exercises and multiple choice questions, add in different datasets for different audiences, e.g. digital humanities, and also add an SQL lesson to the existing curriculum. There are five existing repositories to hack on - library-sql, library-openrefine, library-git, library-shell, and library-data-intro. They are all based in the data-lessons repo on GitHub, having been forked from James's original repo.
Want to Contribute?
Join us at the Global Sprint June 2-3. Leave a comment in this issue to let the project lead know you're interested in contributing during #mozsprint 2016!
Note to the Project Lead
Congrats, @weaverbel! This is your official project listing for the Mozilla Science Global Sprint 2016. To confirm your submission, please complete the following:
Do you want to become a featured project? 🎉
Here are some exercises that will help your project be more inviting to new contributors. We hope you'll try to complete some of these as you prepare for #mozsprint.
If you complete all the exercises, your project will be eligible to be featured in our collection of open source science projects! Once you've finished this list, contact @acabunoc to submit your project for review.
The text was updated successfully, but these errors were encountered: