From: cpebenito@tresys.com (Christopher J. PeBenito)
Date: Fri, 27 Jun 2014 10:45:38 -0400
Subject: [refpolicy] ANN: Reference Policy moved to GitHub
In-Reply-To: <20140626220704.6194100a@gentp.lnet>
References: <5395CAA0.4010900@tresys.com> <20140626220704.6194100a@gentp.lnet>
Message-ID: <53AD8392.1030608@tresys.com>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

On 6/26/2014 4:07 PM, Luis Ressel wrote:
> Dear Maintainers,
> 
> I see you've incorporated commits from an Github pull request for the
> first time [1]. I personally think this could be problematic, as there
> hasn't been any announcement/discussion of these commits on the mailing
> list.
> 
> Could you please clear up your opinion towards pull requests - whether
> they will be accepted or not and whether mailing list patch submission
> or pull-requests are prefered.
> 
> I personally would propose that pull requests should be either
> 1) disallowed, so that patch submission is only possible on the ML
>     (This approach is also taken by Git itself and by Linux, to name
>     prominent examples) or
> 2) allowed, but with the requirement that the patches or at least an
>      announcement is also posted on the ML.

Patch submissions via pull requests will be allowed, though you do make
a good point about discussion.  If you have concerns about missing
something, you should use GitHub's "watch" function on the repo to get
notifications.

I'll look in to GitHub's webhooks to see if we can have pull request
notifications sent to the list.  Failing that, I'm leaning towards #2.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com