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 candidates as
interns here at Ontodia as we're part of the NYU-Poly incubator. One
stumbling block we often encounter as we try to groom SMW developers is
Gerrit.
You see, these interns value their GH profile as its now an integral part
of their CV.
Gerrit is optimized for the MW workflow, in their primary mission of
maintaining Wikipedia. With Jeroen's approach, we get the best of both
worlds - the i18n benefits of the Gerrit workflow, and making SMW
development more accessible to the wider developer community.
Just one suggestion though if we are going the GitHub way. Please let's
eat our own dogfood and stay away from GitHub wiki for documentation :)
My 2 cents,
Joel
===
Think Different! (http://en.wikipedia.org/wiki/Think_different#Text)
Imagine Different! (http://www.youtube.com/watch?v=H5tOgRD4EqY)
On Sun, Nov 3, 2013 at 3:09 AM, Nischay Nahata nischay...@gmail.com wrote:
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 confusion was that there would be documentation in two directions.
MW.org would state that I could clone SMW from Gerrit and submit a change
whereas smw.org would suggest GitHub. If you are supporting both (as you
clarified) there is still this confusion, but at least one can still
progress in any direction. The confusion can be removed if we keep the
documentation about Gerrit and suggest GitHub as an *easy* alternative.
However, we have to be extremely careful that we don't end up in a
push/merge conflict mess. It sounds like you will be merging both ways
between Gerrit and Github, since you are still accepting changes (not just
the i18n ones) in Gerrit. Isn't this going to lead to a merge conflicts?
On Sun, Nov 3, 2013 at 3:43 AM, Markus Krötzsch
mar...@semantic-mediawiki.org wrote:
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
find out if this works well for us and for our (current and future)
developers. So I am definitely in favour of trying this now (and thanks
for clarifying the proposal).
Cheers
Markus
--
Android is increasing in popularity, but the open development platform
that
developers love is also attractive to malware creators. Download this
white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
--
Cheers,
Nischay Nahata
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
