[Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists)

Nicolas Ferre nicolas.ferre at atmel.com
Fri Jul 31 13:09:43 UTC 2015


Le 16/07/2015 18:52, Steven Rostedt a écrit :
> On Thu, 16 Jul 2015 09:24:56 -0700
> Tim Bird <tim.bird at sonymobile.com> wrote:
> 
> 
>> That's really good feedback.  I've often assumed that if you saw something
>> that needed fixing, you had a responsibility to properly format a patch
>> so as not to burden the maintainer.  I've labeled my own "best-effort,
>> but-probably-not-mainlinable" patches as [RFC PATCH..].  Would it be
>> worth having a convention for that sort of thing?
> 
> At a minimum, the patch should not be html, an attachment, nor have
> broken whitespace where the patch doesn't apply. But other than that,

Le me just react on the "no attachment" statement:

As a maintainer, I accept patches as attachments, rework them and
properly submit them.
For a newcomer, it's sometimes very difficult to find a way to send
patches with git or using a "patch/plain-text-friendly" SMTP server.

This mostly apply for company employees and breaking this barrier could
allow us to have more "gifts" in Neil Brown words.

When I recall how difficult it can be to gain a properly configured SMTP
server for my Mainline activities in a former company, I completely
measure the barrier for contribution it can be.

> just report the bug and say "this fixes it for me". And if it is a real
> bug, the maintainer should take it.

[..]

-- 
Nicolas Ferre


More information about the Ksummit-discuss mailing list