I have no problem with that, as long as everyone with +2 keeps his access
This should already be the case for the main iOS engineers, but I've made a ticket https://phabricator.wikimedia.org/T106547 to make sure people don't slip through the cracks.
Oh, and when
it syncs with phabricator tickets....
Phabricator ticket sync is something we're sad to lose, but it's part of the trade-off we're making. That said, it was only slightly beneficial as we relied more on cards being in a "Code Review" column (w/ a WIP limit) than looking at the gerrit updates on the cards themselves (which aren't visible from the board view). Not that GH will make this any easier, but we're not losing too much here, IMHO.
On Wed, Jul 22, 2015 at 8:01 AM, Derk-Jan Hartman < d.j.hartman+wmf_ml@gmail.com> wrote:
I have no problem with that, as long as everyone with +2 keeps his access and someone manages developer account additions and removals. Oh, and when it syncs with phabricator tickets....
DJ
On Wed, Jul 22, 2015 at 1:39 PM, Petr Bena benapetr@gmail.com wrote:
Good job, you aren't the only one. Huggle team is using it for quite some time. To be honest I still feel that github is far superior to our gerrit installation and don't really understand why we don't use it for other projects too.
The GitHub's pull requests are more compliant with original git philosophy of Linus, see this video: https://www.youtube.com/watch?v=4XpnKHJAok8 and would be sufficient replacement to our current "git-review" mechanism, which is very complex and unfriendly to new developers who probably find it very difficult to use.
On Wed, Jul 22, 2015 at 12:40 PM, Brian Gerstle bgerstle@wikimedia.org wrote:
Hey everyone,
I'm writing with plans for the Wikimedia iOS engineering team to move
its
workflow to GitHub with Travis CI, much like RESTbase.
The Wikimedia iOS engineers have been maintaining their own CI and
build
server and using Gerrit for code review. The more time efficient and commonplace approach for open source iOS software development leans
heavily
on GitHub with Travis CI instead (e.g., WordPress[0][1] and
Firefox[2][3]).
By using GitHub with Travis CI, the team believes it will work faster, improve testing, grow developer confidence in making code changes, and, most importantly, deploy fewer bugs to production.
For builds requiring sensitive information (e.g., prod certs), will continue to run on WMF's Mac Mini. As is done for Android, when betas
are
pushed, the team will notify mobile-l.
Feel free to reply or email me directly with any questions or comments.
Regards,
Brian
0: https://github.com/wordpress-mobile/WordPress-iOS 1: https://travis-ci.org/wordpress-mobile/WordPress-iOS 2: https://github.com/mozilla/firefox-ios 3: https://travis-ci.org/mozilla/firefox-ios
-- EN Wikipedia user page:
https://en.wikipedia.org/wiki/User:Brian.gerstle
IRC: bgerstle _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l