search

stat157 / questionnaire

Stat 157 Questionnaire Data Wrangling
1 stars 23 forks source link

Submitting the project and git workflow #29

Closed sunnymh closed 10 years ago

sunnymh commented 11 years ago

In the instruction, it says we should turn in the homework by doing a git push. However, which repository should we push to?

Also is there some suggested team collaboration pattern for this project? Should one of our members fork from stat157/questionnaire and let other people fork from this member so that this member behaves like a administrator of the group? This method seems to be pretty advanced and I don't think we can master it in a day. (http://stackoverflow.com/questions/7244321/how-to-update-github-forked-repository).

Otherwise, can we just fork one copy of stat157/questionnaire and let everyone work on it? I'm not even sure if we are familiar with git enough to deal with merging conflicts and committing/pushing the project properly. So the version control might take us more time than the project itself.

teresita commented 11 years ago

One of my vertical group members created a repository for the group; she made us all collaborators so we have write access.

Also, in terms of workflow, I imagine this project would be the best time to start learning git since collaborating on code is pretty much exactly its intended use-case. The instructors have been encouraging us to challenge ourselves as a way of building our skills; I think working with each other to figure out the nuances of git is probably a great way to do so :]

aculich commented 11 years ago

@sunnymh As you suggest with the stackoverflow reference, keeping a forked repository up-to-date is not trivial (unfortunately a weak part of the git/github workflow).

However, as @teresita points out, creating a repository and adding collaborators is a great way to proceed since that will give everyone direct write access to the repository. Since you all have a high degree of trust working together with each other, this is a good situation. On the other hand, if there were strangers contributing to your repository you generally don't want to give them push access unless you know them as a collaborator. Over time, strangers earn trust by contributing code and being a good steward of the project, and sometimes repository owners add them as collaborators with write access (even if they have never met in person).