Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 59DDACB26 for ; Fri, 16 Jan 2015 07:10:53 +0000 (UTC) Received: (qmail 71369 invoked by uid 500); 16 Jan 2015 07:10:55 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 71320 invoked by uid 500); 16 Jan 2015 07:10:55 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 71310 invoked by uid 99); 16 Jan 2015 07:10:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jan 2015 07:10:54 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pierre.smits@gmail.com designates 209.85.217.173 as permitted sender) Received: from [209.85.217.173] (HELO mail-lb0-f173.google.com) (209.85.217.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jan 2015 07:10:28 +0000 Received: by mail-lb0-f173.google.com with SMTP id b6so4281585lbj.4 for ; Thu, 15 Jan 2015 23:10:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=f0JjXWWGmrrkPRmBVOIxw2Ki0GCK6wOEDW68eNqiS7M=; b=Dn3qaEvMt+H0KZa8W7te844a/JEjARcgcio2KNBn7sfP4sXxbqjUvmEMOoXCd2rQmp T3QxarRdS7Go8APeGa91XBnW0VBChqB1YeTKo+nrKGxS3VvFrFNx7t7f6E1GG3060Skj d/xBx7fCxqALfo58ncNlNRNXQTubTCJuZd/A6riwwouEatJr1r+TE/gkLyvGIQPoiaqN 37F5SEh3b357geiGA2gFE2wJCj7jju+42xdWEW9rfBVy2CH47iiHVH3LZ2/JrlgsugCt QXP858Wyw1CLcq2ihpuV4mjtK/u9I4Got/I5em6Qav02rZJap+GAjk7pQ+vTWzo4ECeL F7LA== MIME-Version: 1.0 X-Received: by 10.152.88.44 with SMTP id bd12mr7793325lab.88.1421392226979; Thu, 15 Jan 2015 23:10:26 -0800 (PST) Received: by 10.25.73.213 with HTTP; Thu, 15 Jan 2015 23:10:26 -0800 (PST) In-Reply-To: <54B892D2.1070801@gmail.com> References: <8D5F7E3237B3ED47B84CF187BB17B66611A64798@SHSMSX103.ccr.corp.intel.com> <8D5F7E3237B3ED47B84CF187BB17B66611A64B2B@SHSMSX103.ccr.corp.intel.com> <54B7C673.8050808@gmail.com> <8D5F7E3237B3ED47B84CF187BB17B66611A64F96@SHSMSX103.ccr.corp.intel.com> <54B892D2.1070801@gmail.com> Date: Fri, 16 Jan 2015 08:10:26 +0100 Message-ID: Subject: Re: [Kerby/Haox] About committing codes for contributors From: Pierre Smits To: Apache Directory Developers List Content-Type: multipart/alternative; boundary=001a11c33a78c695c8050cbfaa43 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c33a78c695c8050cbfaa43 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I believe that the general consensus within the greater ASF community is that non-committing contributors can't assign issues to themselves, but still can work on their own issues (changing specific fields, including closing the issue), and that committers can. But, I must confess that I have limited experiences, so I might be mistaken. If we want them to be able to reassign (and be able to execute other actions not associated with the role) , we should consider inviting them to be committers. In general I say: the more the better for the project and its works. Best regards, Pierre Smits *ORRTIZ.COM * Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Fri, Jan 16, 2015 at 5:25 AM, Emmanuel L=C3=A9charny wrote: > Le 16/01/15 03:43, Zheng, Kai a =C3=A9crit : > > Oh, I see. We need extra step to add somebody in the contributors list > so that he/she can be picked up in the possible assignee list in the JIRA= . > > > > I noticed Lin Chen was able to assign issues to herself today. That > makes sense because it looks like she would continuously work on the > project (quite a few patches already). > > > > For new contributors, perhaps we would use the similar approach, say if > he/she has already come up more than 3 patches, then we could ..., make > sense? > > For JIRA contributors, we should add them to the list of contributors no > matter what. > > --001a11c33a78c695c8050cbfaa43 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I believe that the general consensus within the greater AS= F community is that non-committing contributors can't assign issues to = themselves, but still can =C2=A0work on their own issues (changing specific= fields, including closing the issue), and that committers can. But, I must= confess that I have limited experiences, so I might be mistaken.

If= we want them to be able to reassign (and be able to execute other actions = not associated with the role) , we should consider inviting them to be comm= itters. In general I say: the more the better for the project and its works= .

Best regards,
Pierre= Smits

Services &= amp; Solutions for Cloud-
Based Manufacturing, Profe= ssional
Services and Retail & Trade
=

On Fri, Jan 16, 2015 at 5:25 AM, Emmanuel L= =C3=A9charny <elecharny@gmail.com> wrote:
Le 16/01/15 03:43, Zheng, Kai a =C3=A9crit :
> Oh, I see. We need extra step to add somebody in the = contributors list so that he/she can be picked up in the possible assignee = list in the JIRA.
>
> I noticed Lin Chen was able to assign issues to herself today. That ma= kes sense because it looks like she would continuously work on the project = (quite a few patches already).
>
> For new contributors, perhaps we would use the similar approach, say i= f he/she has already come up more than 3 patches, then we could ..., make s= ense?

For JIRA contributors, we should add them to the list of contributor= s no
matter what.


--001a11c33a78c695c8050cbfaa43--