2013/11/2 Jeroen De Dauw <jeroended...@gmail.com>: > 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, we'll have to periodically > merge the translation updates from the WMF repo to the GitHub one.
This sounds like a potential for a mess, merging stuff into both directions. > People will thus continue to be able to use a clone of the WMF repo, which > will at the very least be updated for each release. From my point of view, you would lose visibility of development, pre-testing (some of the extensions) at translatewiki.net as well as having new releases with fewer translations, because translators have less or no time to translate new strings. With this scheme it can take two releases to fix an i18n problem and having a good translation for it (fix in next release, translations in next+1 release). Don't get me wrong, I respect your efforts to not have everything entangled deeply in MediaWiki or WMF. But I think that also lot of good things come with that, like translatewiki.net, code review, general maintenance etc. My feeling is that you change you are planning to make is disruptive, exchanging some known good things for unclear benefits. I assume the main thing would be more contributions via GitHub, but are there anything to justify this expectation and give an idea how much it could be. You also have consider that once someone has learned to contribute to extensions hosted in WMF infra, they can easily contribute to any such extension because they work similarly. You would be breaking that, rising barriers elsewhere while trying to lower them here. Nischay also already mentioned that submitting patches via GitHub is getting easier. I would like to see more clearly reasoned issues and less disruptive ways to achieve them without losing the good things. Who knows, the solutions could benefit other projects as well, for example better GitHub support in translatewiki.net. -Niklas -- Niklas Laxström ------------------------------------------------------------------------------ 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=65839951&iu=/4140/ostg.clktrk _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
