From: Enno B. <enn...@gm...> - 2014-02-14 17:16:58
|
Jerome, > If I understand right, we could ask any contributors and translators, > to fork gramps.git into their u/<username> git repo under SourceForge > via the Fork button[1] (no need javascript). > > Via the web interface: > > 1. log in into the u/<username> account > 2. go to the Admin item, Tools section > 3. 'Set default branch', 'Refresh Repository' and maybe 'Set > Permissions'? > > Then, either download complete git fork or download their translation > files and maybe the 'gramps.pot' template for translators. > > Once, they think this could be merged with gramps, they use the web > interface or send to updated translation file. Does this mean that I can forget about the readonly part of introduction to git on the wiki? Right now, I have a hacked 3.4.8 on my desktop PC, with every personal hack saved as a local commit, which I never push, because that would require that everyone likes that hack, or make it optional, which I don't like, after reading the 10 year old article that you mentioned earlier. Problem with that hack is that I can only have the same 3.4.8 on my laptop by copying the Gramps folder there, and keeping it in sync with the folder on the desktop PC. That is not nice, and the advice to set up a local repository looked a bit frightening. It also means that I only have a local backup. When I create a fork on SF, I can push everything, forget about patch files, and pull from SF to my laptop, right? Which means that there is a backup too. Nice. But here comes the silly question: How do I get fixes that are made to the main to my fork? Do I need to log on to SF and pull from main to fork? And why is it that I feel confused by the term pull request, which seems to look like a move in the opposite way? If anyone else can explain, please do. thanks, Enno |