Conversation

Notices

1. Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 17:10:29 UTC Danyl Strype

   • Maggie
   @maenad thanks for this, it seems very sensible http://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.1001745
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 17:14:36 UTC Danyl Strype

     in reply to

     • Maggie
     @maenad are people really still emailing chunks of code to each other when Git exists?!?
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 17:29:20 UTC Danyl Strype

     in reply to

     • Maggie
     @maenad a shame they promoted Google Code, I guess they weren't to know it would shut down about a year after they published their article
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 17:32:00 UTC Danyl Strype

     • Maggie
     @maenad woah. Send them this. It taught me #Git basics in a few days, and got me excited about it
     https://www.learnenough.com/git-tutorial
     (-(-_(-_-)_-)-) repeated this.
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 17:34:02 UTC Danyl Strype

     • Rysiekúr Memesson
     • Maggie
     @rysiek @maenad I'm a total noob at running servers, but I can't imagine trying to push a team's change to a production server without #Git
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 17:38:44 UTC Danyl Strype

     • Maggie
     @maenad what excited me about learning #Git wasn't coding, but that I could immediately see myself versioning texts for a book with it
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 17:39:42 UTC Danyl Strype

     in reply to

     • Maggie
     @maenad it's just as useful for a team working on the text of an academic paper as it is for a team working on a piece of code
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 17:42:04 UTC Danyl Strype

     in reply to

     • Maggie
     @maenad check out #Authorea for a platform based on the concept of drafting papers over #Git
     https://www.authorea.com/aboutus
     (-(-_(-_-)_-)-) likes this.
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 17:59:28 UTC Danyl Strype

     • Maggie
     @maenad I wouldn't use #DropBox or #Slack either, when #NextCloud and a plethora of free code team chat apps are available
     (-(-_(-_-)_-)-) repeated this.
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 18:16:49 UTC Danyl Strype

     in reply to

     • Maggie
     @maenad I'm not necessarily recommending #Authorea (when I last checked it had some proprietary bits), just using it as an example
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 18:25:24 UTC Danyl Strype

     in reply to

     • Maggie
     @maenad point is pitching Git as a tool for managing text files (including code), rather than as a coding tool, might make it more appealing
   • Danyl Strype (strypey@quitter.se)'s status on Wednesday, 28-Feb-2018 18:34:51 UTC Danyl Strype

     in reply to

     • Maggie
     @maenad BTW do you use the documentation tools described in that 'Best Practices for Scientific Computing' article? I'd like to know more
   • Danyl Strype (strypey@quitter.se)'s status on Monday, 12-Mar-2018 09:47:53 UTC Danyl Strype

     • Jonne Arjoranta
     @jaranta  #Git is a back-end. Yes, it needs front-ends with much better #UX for mass adoption, but it can be learned by mere mortals as is
   • Danyl Strype (strypey@quitter.se)'s status on Monday, 12-Mar-2018 09:49:57 UTC Danyl Strype

     in reply to

     • Jonne Arjoranta
     @jaranta my point was if busy academics see Git as a multi-use tool, they may be more willing to put in a few hours to learn it for code use