Re: [SMW-devel] Moving SMW development to GitHub

2013-11-03 Thread Joel Natividad
I think its worthwhile to move forward as Jeroen proposed. In the semantic-mediawiki.org site development documentation, we should just direct SMW developers to use GH as their primary repo, and Gerrit is primarily just used for i18n. We have the benefit of being able to tap NYU-Poly MS CS candid

Re: [SMW-devel] Moving SMW development to GitHub

2013-11-03 Thread Nischay Nahata
Hi, One important thing Jeroen pointed out is : "Most interest in SMW is coming from outside the core MediaWiki community, and for them the current workflow is not only confusing, it is a big hassle." If this is true, then its one BIG reason to support GitHub - getting more contributors. My con

Re: [SMW-devel] Moving SMW development to GitHub

2013-11-02 Thread Markus Krötzsch
Hi Jeroen, making a writable secondary copy on GitHub is fine. It first sounded as it you wanted to abolish our gerrit repo completely (I think this is what people have replied to). We can also discuss this, but that will need a bit more time. The secondary GitHub repo will be a nive way to fi

Re: [SMW-devel] Moving SMW development to GitHub

2013-11-02 Thread Jeroen De Dauw
Hey, > To me it seems that the coordination of two source control tools seems to be a lot of work. We already have multiple copies of the repo. Every clone is a copy of the repo. GitHub will just be another copy. Furthermore there is little difference between changes on a branch on a remote or ch

Re: [SMW-devel] Moving SMW development to GitHub

2013-11-02 Thread Markus Krötzsch
Hi Jeroen, thanks for your proposal. It's very useful to revisit our infrastructure from time to time. Since people seem quite critical so far, we should probably have a bit more discussion To be honest, I think that the (positive as well as negative) impact of this decision is not as big as o

Re: [SMW-devel] Moving SMW development to GitHub

2013-11-02 Thread Jeroen De Dauw
Hey, Thanks all for your feedback. Since there is apparently a good degree of apprehension on changing this workflow, which is not all to surprising, I'll slightly alter and reframe the proposal. Rather then "switching" to GitHub, we'll just have the new repo on GitHub via which we access pull r

Re: [SMW-devel] Moving SMW development to GitHub

2013-11-02 Thread Niklas Laxström
2013/11/2 Jeroen De Dauw : > The current canonical repo would be kept where it is and become a manually > updated mirror. If people submit patches against it, we can still review > those via gerrit or redirect them to GitHub as we see fit. Since > TranslateWiki does not support GitHub at present, w

Re: [SMW-devel] Moving SMW development to GitHub

2013-11-01 Thread Nischay Nahata
Hi, Are there similar plans for the SMW-related extensions? Wouldn't it be confusing if some work is on Gerrit (MW and many other extensions) while SMW work is on Github? I assume anyone who goes to the extent of submitting a patch to SMW would also like to keep the master version of MW which wil

[SMW-devel] Moving SMW development to GitHub

2013-11-01 Thread Jeroen De Dauw
Hey, After discussions with the active contributors to the SMW project and asking attendees at last weeks SMWCon, I'd like to propose moving SMW development to GitHub. == Details == The canonical git repo would be at https://github.com/SemanticMediaWiki/SemanticMediaWiki Trusted contributors ge