Leo> In terms of the optimal git workflow, if I understand correctly, Leo> Github recommends forking the project (and then sending pull Leo> requests). One minor drawback of this approach is that forked Leo> branches don't show up in search on github. It is also possible to Leo> clone the existing project, create a /new/ github project and push to Leo> it -- but I'm guessing that would make it impossible to submit a pull Leo> request to the upstream repository (DMG or anyone more knowledgeable Leo> -- please correct me if I'm wrong on this).
I agree with Leo that we need to look at potential workflows. The main challenge, as we speak, is that it is very difficult to integrate work across our branches. We can all work with git except Denis. That is possible. In fact, the upstream branch that I created tracks his repo commit by commit (it is behind two commits as we speak). So we could always try to rebase our changes to this branch, and they will cleanly apply to his repository. I have a couple of questions for Denis in this regard: - Coding standards. Denis, what makes a 'good patch', and when you edit/fix a patch. Can it be done by the author, so it can be easier to integrate? In other words, you review, the author fixes, you integrate? It might also reduce your workload. - Plans. Do you have a roadmap of patches/features that you would like to see integrated? -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Xournal-devel mailing list Xournal-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xournal-devel
