Hi Sam! Here’s my lab’s GitHub organisation: https://github.com/WhitakerLab There aren’t many things to see except for me because a) I have a very new lab and b) most people I work with are anxious about public project management.
-
-
Replying to @kirstie_j @samhforbes
So I have chosen to go with a bunch of private repos: https://help.github.com/articles/applying-for-an-academic-research-discount/ … I know it isn’t perfect but I think it’s really hard for folks who aren’t used to GitHub to “air their dirty laundry” while they’re learning.
1 reply 1 retweet 2 likes -
Replying to @kirstie_j @samhforbes
My philosophy is to focus on the in lab training and build up confidence so they can make later projects open if they’d like.
1 reply 1 retweet 3 likes -
Replying to @kirstie_j @samhforbes
The number of notifications is really tough. So keep having lots of conversations about how to best communicate. There are GitHub options to manage notifications but they require some common ways of working (knowing when to tag etc) that only humans can determine
1 reply 1 retweet 2 likes -
Replying to @kirstie_j @samhforbes
My other big recommendation is to remember that *git* and *GitHub* are very different skill sets. I know lots of people who are git wizards but don’t know how to do a pull request and don’t use issues. So train for both skills
1 reply 2 retweets 4 likes -
Replying to @kirstie_j @samhforbes
What I mean by “not using issues” is the use of them as a project management tool, or a place to have discussions and get feedback. Most folks think of them only for bugs. I think you’re missing some functionality if you only use issues for bugs but that’s a lab decision :)
1 reply 1 retweet 4 likes -
Replying to @kirstie_j
This is amazing, thanks
@kirstie_j. The number of notifications could be a big deal for us, so we will have to manage that. Also the advice about issues is great. Thanks so much!1 reply 0 retweets 1 like -
Replying to @samhforbes @kirstie_j
FWIW I code in private (often) & then publish the public repo. For various reasons, including to avoid confusion and to avoid including files that should not be there. Also why code in public anyway if you are new to coding? Can imagine it to be scary AF for newbies.
1 reply 0 retweets 3 likes -
Also... In the same way you don't make your feedback to your mentees writing (imagine comments on their manuscript) public why make all coding public?
1 reply 0 retweets 1 like -
There is a lot of value in coding publicly of course too.
2 replies 0 retweets 1 like
Also just to be clear, I think within-lab repos should be visible to everybody in the lab. This helps collaboration and also avoids people being code-isolated (you can check in on them) and it helps if they leave the lab (you have easy access to their code if need be).
-
-
Replying to @o_guest @kirstie_j
Yes, I was thinking about using teams, but for mentions purposes, not for access purposes.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.