search

rpietro / OlecranonFracture

This study describes an interobserver agreement study about image interpretation of olecranon fractures
1 stars 1 forks source link

simplifying versioning for our researchers #3

Closed rpietro closed 12 years ago

rpietro commented 12 years ago

have been thinking a lot about how to simplify the use of github for our researchers. it's a great tool, but not easy to learn. so, one imperfect solution would be:

  1. all the people in the analysis comfortable with github will do it the geek way -- terminal or through a client
  2. researcher who is not comfortable with it will (a) fork the script (takes on click on the web interface), (b) download the script, (c) run it locally on his/her computer (i've posted some videos on this on g+), then (d) go back to github and see whether somebody has made any changes to the script while he/she was working on it.
  3. if the answer is no, the researcher will just click edit on the script and paste the new version in there and pull the file back into the master file (can also be done with one click on the web interface).
  4. if the answer is yes (somebody else made a change), then the researcher can just look for the differences, manually consolidate the two, and then paste the combined version

then, once they feel ready they can start learning how to use it for the benefits that versioning provides http://goo.gl/s4qs2 we can teach them how to use a regular git client

if this works, i will create a video from their perspective, but the reality is that all it takes is two actions done through the web interface: fork (which they only have to do once during the project lifetime), checking the file history, and pulling. probably safe to assume that editing, copying/pasting, and comparing the two manually is something that everybody already knows how to do

Adelia, can you give the steps above a run? you can use one of Elias' projects

adelia commented 12 years ago

Yes, i can do it, so later, I am going to a training at UEM this morning just now and when back will do it

adelia commented 12 years ago

Ricardo

You just to cofirm, you mean:

1) Open a project from Elias 2) Download the script (via RStudio??) 3) Run locally (via RStudio??) 4) Do some changings 5) Go to GItHub and look for changings done by others
If no changings was done
6) Paste my local code to GitHub and pull
7) Finish the operation
if some changing was done by another people
8) Copy the chaging
9) Paste into my local script
10) Go to 5

rpietro commented 12 years ago

no, everything manual. so, download the file and then open in RStudio, not directly. run via Rstudio. as for #8, if somebody did do some changes while you were working locally, then you would have to compare your file with the latest one on github and make the two compatible. for example:

  1. download a file that has lines: a b c
  2. you work locally and add d: a b c d

3, when you go back to upload your modified file you notice that the latest version now looks like a b c z

  1. now you have to decide whether you want to include z or not. if you do, it would combine the two, which would be: a b c d z

makes sense?

adelia commented 12 years ago

Yes, you drew literally points for me 8-)

It is very laborious, somethings got wrong trying again

adelia commented 12 years ago

I think I translated it wrong, the correct phrase is: "Literalmente você desenhou isso pra mim" or "you literally drew this for me"

Now I understand it better

rpietro commented 12 years ago

if you look at it, it's a simple process. the only more complicated issue is if somebody else has done any change in between. that's where the versioning system helps big time

adelia commented 12 years ago

Ricardo

I did this test:

Elias:

My changings were there

rpietro commented 12 years ago

Adelia, I am going to test gdrive as we had discussed, and so closing this issue