GSoC FAQ - pgRouting/pgrouting GitHub Wiki
- Q: What does the weekly report must have?
- Q: How to write emails with links?
- Q: How to update your fork?
- Q: What does fork mean? What does clone mean?
A: The following is a template based on:
- OSGeo GSoC Recomendations for students -> Weekly reports section
<Greetings section>
* What did you get done this week?
<short summary of work done (2 or 3 lines)>
Details can be found in [1]
Set of pull requests can be found in [2]
* What do you plan on doing next week?
<short summary of a general plan (2 or 3 lines)>
Details of possible sub tasks can be found in [3]
* Are you blocked on anything?
The wiki page can be found in [4]
The repository can be found in [5]
[1] <link to wiki page corresponding section of the week>
[2] <link to wiki page corresponding section that has the link to the PR>
[3] <link to wiki page containing possible tasks for next week>
[4] <link to the wiki page>
[5] <link to the corresponding gsoc branch in main repository>
A: Please don't send it with a dot at the end see [1], because it takes you to nowhere. the correct name is [2]. Normally in email lists it's done by referencing. Like this answer.
[1] https://github.com/pgRouting/pgrouting/wiki/GSoC-FAQ.
[2] https://github.com/pgRouting/pgrouting/wiki/GSoC-FAQ
A: Fetch the changes from the upstream, Merge them in your branch and then push them to your fork.
git fetch upstream
git checkout <branchname>
git merge upstream/<branchname>
git push origin <branchname>
A: Clone is in your computer but fork is on Github. You have a clone in your computer, and the origin part is from your fork and the upstream part is main repository. So in your one clone you can access main repository and your fork.