proposals icon indicating copy to clipboard operation
proposals copied to clipboard

Published 20 hours ago • verified publisher icon carpentries-incubator

Collaborative Distributive Version Control with Git and Remotes

Open go-bears opened this issue 5 years ago • 4 comments

Thank you for your interest in developing and sharing lesson materials! To submit lesson materials or suggest a topic for future curricular development, please answer the questions below. Our Curriculum Development Team will follow up to suggest next steps in your lesson's trajectory. Questions? Please email [email protected].

  1. What is the topic of your lesson or lesson proposal? collaborative coding with Git and Remote hosts or Collaborative Distributive Version Control with Git and Remotes Hosts

  2. Do you already have a draft of your lesson? You're welcome to share materials at any stage of development. If you already have drafted materials, please include a link.

https://go-bears.github.io/git-collaborative/

(If you answered "No" to question 2, you can skip the remaining questions. Thank you for your lesson idea!)

  1. Do your materials conform to our Code of Conduct? Yes

  2. Are your materials already on GitHub and do they use The Carpentries lesson template? (you can visit our lesson example to learn more about how to use our template). Yes

  3. If you answered "No" to either part of question 4, would you like our Curriculum Team to create a repository for you in The Carpentries Incubator?

  4. If you answered "Yes" to both parts of question 4, would you like to transfer your repository to The Carpentries Incubator? You will have Write access to the repository. Yes

  5. If you answered "Yes" to either question 5 or 6, list the GitHub handles for people who should have Write access to your lesson. If you don't know how to answer this question, don't worry! We can always add collaborators later. go-bears

  6. Any other information you would like us to have or questions you have for us? This lesson is being adapted from Code Refinery's lesson for an upcoming SWC workshop in Sept at the FlatIron institute. The workshop organizers specifically and explicitly requested collaborative coding and best practices with branches and pull requests/code review process that is not yet currently available as an official lesson.

Code Refinery builds on top of SWC's work and this workshop can be adapted to SWC licenses and references in short order and then integrated with the Novice Git lesson over time.

I did not write these lesson but forked the repo from Code Refinery, and I am in the process of making the updates to the Code Refinery references to the SWC references as well as re-think/ re-imagine the instructor setup for a repository with pull request & write accesses & it would be great to have some insights on how to do that with the carpentries community.

Thank you for sharing your lesson with The Carpentries community!

go-bears avatar Aug 14 '20 02:08 go-bears

Hi @go-bears, thanks for sharing this lesson proposal. Before I can help you transfer this material into the Carpentries Incubator, the lesson needs to be set up to use our lesson template. At the moment it uses the Code Refinery template, which is related to the Carpentries template but not identical. If you'd like work towards transferring the material into the Incubator and need help with adapting the project to directly follow our template, please let me know and I or another member of the Curriculum Team will be happy to assist you.

tobyhodges avatar Aug 24 '20 09:08 tobyhodges

thank you for your note @tobyhodges! Would love to have more guidance in how to make this lesson a mainstream SWC carpentry lesson! I do need help & would appreciate any guidance or hands to do so. Thank you!

go-bears avatar Aug 29 '20 17:08 go-bears

Would the first step be to change the css file from code refinery and the base.html layout to the ones found in the swc lesson templates?

go-bears avatar Aug 29 '20 18:08 go-bears

Hi @go-bears I just want to apologize for the wait because Toby reached out to me (representing CodeRefinery) and I have been extremely slow responding. I will discuss this with Toby on Tuesday. Within CodeRefinery we are of course super interested if this lesson gets more exposure and uptake. One thing that we need to carefully think about is how to avoid that this lesson diverges if it is maintained in two places. I will also discuss this with the CodeRefinery team.

Another development on CodeRefinery side is that we are porting some lessons from Jekyll to Sphinx but we may reconsider this if this complicates uptake by Carpentries.

We will discuss these points, I apologize that this stalled a bit because of me.

bast avatar Sep 24 '20 17:09 bast