One problem with #2 is that it means the contributor need not have created an account on the ASF JIRA.
Generally I think of this as an advantage, since making yet another account is a pretty high bar for participation from casuals. But! We rely on the information in JIRA for authorship when making release notes, right? I usually rely on git commits for authorship/review information when judging things like community activity, but maybe others are relying on JIRA? On Sep 28, 2016 09:37, "Casey Brotherton" <cbrother...@cloudera.com> wrote: > Hello, > > In walking through the code, I had seen a couple of places where a minor > change > would be beneficial to the overall project. > > ( Clarifying a log message, adding a log message, etc ) > > What would be the best vehicle for encouraging contributor patches for > small improvements? > > Discussed offline, these seem to be two approaches: > > 1) Ask the contributor to open a full jira, attach the one line diff. > Pro: This provides a solid record of why the code is changed. > Con: Somewhat heavy weight for the occasional contributor. > > 2) Open a Github pull request > Pro: Very simple for a casual contributor > Con: May lack some of the documentation of why something was changed. > May be even more heavy weight for committers. > > Currently the ASF GitHub Bot is not enabled for the YETUS project. > > > Is there a preference on one of these. Is there a third option not yet > listed? > > Thanks, > Casey >
