Hi all, Really thanks so much for your contributions.
Cam, before we leave the discuss list, I'd be happy to coordinate a 2-day sprint in late August or early September if people wanted to join in to help develop the lesson that is starting to take shape from these discussions. We've seen both the R and Python SWC lessons going through major overhauls in the last year or so, maybe now is the time to tackle git/GitHub? Let's continue the discussion about a sprint at https://github.com/swcarpentry/git-novice/issues/277 as Cam suggested. Kind regards, Anelda On Mon, Jul 31, 2017 at 5:36 PM, Cameron Macdonell < [email protected]> wrote: > Hello again! > > > > To clarify, I should’ve written “I think we should end this discussion **on > the Discuss list* *at this point.” > > Usually, we move such discussions over the github issues. There is an > existing discussion along this line. To avoid duplicate issues, I think > Issue #277 is the best place to continue to discussion. Here’s the link, > > https://github.com/swcarpentry/git-novice/issues/277 > > Of course, if there is interest to enhance the git-novice lesson or create > git-novice-gapminder, pull requests are welcome and appreciated! > > > > Sincerely, > Cam > > > > *From:* Discuss [mailto:[email protected]] *On > Behalf Of *Cameron Macdonell > *Sent:* Monday, July 31, 2017 9:13 AM > *To:* Software Carpentry Discussion <[email protected]> > *Subject:* Re: [Discuss] Git lesson alternative > > > > Hello, everyone, > > > > Thanks for all the comments and discussion. I think we should end this > discussion at this point. > > Anelda, if you need additional information, or if you've found an > alternative novice-level lesson, please follow-up. > > > > Sincerely, > > Cam > ------------------------------ > > *From:* Discuss <[email protected]> on behalf > of Tom Wright <[email protected]> > *Sent:* Monday, July 31, 2017 8:56:16 AM > *To:* Greg Wilson; Software Carpentry Discussion > *Subject:* Re: [Discuss] Git lesson alternative > > > > +1 for starting with an existing repository. With more advanced users, I > have used a repo containing the data used in other lessons. It's nice if > the data has been modified at some point so the history can be checked. New > data can be added as the course progresses which gives a really nice > introduction to collaboration. > > > > On Mon, 31 Jul 2017 at 10:38 Greg Wilson <[email protected]> wrote: > > +1 to using a paper outline in Markdown as a motivating example - it'll > be easier to introduce people to Markdown than to any particular > programming language... > > Cheers, > > Greg > > > On 2017-07-31 10:25 AM, Konrad Förstner wrote: > > Hi, > > > > in a recent class we replaced the Dracula/Wolfman story with the > > situation to write collaboratively a manuscript with very basic > > markdown. Maybe that could be a general, programming language agnostic > > solution with a scenarion that is releveant for many participiants. > > > > Cheers > > > > Konrad > > > > On Mon Jul 31, 2017 at 03:05:53PM +0200, Lex Nederbragt wrote: > >> Hi, > >> > >> Adding a thought: if the ‘Dracula/Wolfman’ story in the git lesson is > >> to be > >> changed to some actual programming, we run into the ‘in what > >> language’ issue: > >> we sometimes teach workshops where we teach unix + git + R instead of > >> unix + > >> git + python. A python-based git lesson would be useless for such > >> workshops... > >> > >> Lex > >> > >> > >> On 29 Jul 2017, at 16:04, Mateusz Kuzak <[email protected]> > >> wrote: > >> > >> Hi all, > >> > >> Anelda, thank you for starting this discussion. Teaching Git > >> lesson have > >> been on my mind quite a lot lately. I have also discussed it with > >> other > >> instructors and gathered feedback from the learners. Here are my > >> observations: > >> > >> * The Dracula and Wolfman content of the lesson is too far away > >> from the > >> programming situation. While in theory it should make it easier to > >> understand git concepts without focusing on the programming part, > >> I find > >> that it confuses learners even more. I believe there is a need for > >> more > >> real life example and we should opt for teaching Git lesson after > >> introducing basic programming. > >> > >> * Version Control is like backups, people know they need it (once > >> they > >> understand what version control is) but it’s very hard to get them > >> excited > >> about it. On the other hand it’s very easy to “sell” git as a > >> collaboration > >> tool, via GitHub. Learners are usually very excited when going > >> through > >> forking, pull requests and online reviews. In my opinion showing > >> how things > >> work via the web interface and only after introducing command line > >> equivalents works better. I’m not saying it’s better in general, > >> but we > >> have to keep in mind our learners just started using the command > >> line a day > >> before and have been using the web and web application for years. > >> > >> best, > >> Mateusz > >> > >> On 10 Jul 2017, 15:15 +0200, [email protected], wrote: > >> > >> Hi Anelda, > >> > >> I replace the Dracula example with Python code at > >> https://github.com/rgaiacs/swc-git-novice-euroscipy2016. This > >> was for > >> Git Workshop last year during EuroScipy. > >> > >> > >> I've been wondering how we can simultaneously give a broader > >> exposure > >> to GitHub GUI as I (since I'm not a software developer but > >> often > >> collaborate with others on GitHub) mostly use GitHub and > >> haven't > >> had to > >> use git command line probably for a year now because I > >> could do > >> everything I needed in the GUI. Not that I am promoting not > >> teaching > >> the command line way of using git, but for people who've > >> never ever > >> encountered version control it might be more accessible to > >> first > >> build > >> a mental model by learning GitHub and then going to the > >> next step > >> of > >> learning the command line tool. > >> > >> > >> If you are teaching Git for non-developers you can probably > >> stay with > >> the online GUI provided by GitHub/GitLab/Bitbucket/... but if > >> you are > >> teaching Git for developers you will need to teach the the > >> command line > >> or any local GUI since otherwise they will not be able to > >> share their > >> changes easy. > >> > >> > >> I've been wondering if there is something that can come > >> before the > >> git-novice lesson to help the target audience of our > >> workshops > >> understand the value of version control and tools like > >> GitHub. Any > >> pointers to something that is even more foundational to > >> help build > >> mental models and create a interest to learn version > >> control would > >> be > >> very welcome. > >> > >> > >> My impression is that the students never program before or > >> only hack > >> some small scripts they don't have experience to give the > >> correct value > >> to version control since Google Docs and similar do a great job. > >> > >> On this line, my last own experience teaching Git showed me > >> that we > >> should use at least two files to make more clear for > >> instructors why > >> version control is important. For example, you can use Dropbox > >> to share > >> code with your collaborator but one day you change the code > >> and your > >> collaborator change the configuration file and next morning > >> the code > >> doesn't work. How do you make the code work again? With Git, > >> you will > >> know of the merge when you two sync and check the differences. > >> > >> Kind regards, > >> Raniere > >> _______________________________________________ > >> Discuss mailing list > >> [email protected] > >> http://lists.software-carpentry.org/listinfo/discuss > >> > >> _______________________________________________ > >> Discuss mailing list > >> [email protected] > >> http://lists.software-carpentry.org/listinfo/discuss > >> > >> > > > >> _______________________________________________ > >> Discuss mailing list > >> [email protected] > >> http://lists.software-carpentry.org/listinfo/discuss > > > > _______________________________________________ > > Discuss mailing list > > [email protected] > > http://lists.software-carpentry.org/listinfo/discuss > > -- > If you cannot be brave – and it is often hard to be brave – be kind. > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/listinfo/discuss > > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/listinfo/discuss >
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
