Branch: refs/heads/master
Home: https://github.com/jenkinsci/gerrit-code-review-plugin
Commit: 5333012f14721c34d2f4f81895272c68150550fd
https://github.com/jenkinsci/gerrit-code-review-plugin/commit/5333012f14721c34d2f4f81895272c68150550fd
Author: Luca Milanesio <luca.milane...@gmail.com>
Date: 2018-11-06 (Tue, 06 Nov 2018)
Changed paths:
M CONTRIBUTING.md
Log Message:
-----------
Require contribution through Gerrit Code Review
I am super-thrilled by the amount of contributions received
on this project, which is super-exciting. I am as well
deeply worried by the GitHub code-review workflow that, even
for the initial set of contributions, is lacking some of the
basics of a proper contribution and code review lifecycle.
Move the code-review to GerritHub.io and, for those who
are not familiar with Gerrit (strage, if you are willing to
contributing to this plugin you should aware of what Gerrit is)
we still accept pull-requests and import into GerritHub with
the pull-request importer.
By using Gerrit and Jenkins for validation, start a virtuous
"dog-fooding" cycle using *this* plugin for validating the
contribution to *this* plugin, we will eat every day our own
dogfood.
**NOTE:** This service has been marked for deprecation:
https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
