Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: domain of mcintyre.a@gmail.com
 designates 209.85.132.247 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=PnwD9ipAUV40EgVYVLgDSrdqP0J28TZ1aV4LYGcieuhYCp+PeEnuhGBUun7COmXUL0Es0V4Fqa9OskkvDNjGubE1NYcBBbIBA1KWc7xG3LQrxo9Hb3dmkyShoo/Us02tNJK8DrDmyOgsbiR38qWhlX6ScpQuF6dDonFgaYDYYA0=
Message-ID: <54ac72d70703021100g729efbcegc8a6e506a13cae87@mail.gmail.com>
Date: Fri, 2 Mar 2007 11:00:39 -0800
From: "Andrew McIntyre" <mcintyre.a@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: I need help to delete files attached to a wrong JIRA issue
In-Reply-To: <x1o37itz32h5.fsf@sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <59c2e1ec0703011554p6b248220j2257cde1ca94b2aa@mail.gmail.com>
	 <54ac72d70703011658p6d1842e8h239a362c5226cf8f@mail.gmail.com>
	 <9f40b500703011700m193ad69n7d038b00ec55d60b@mail.gmail.com>
	 <45E8672A.4030307@apache.org> <x1o37itz32h5.fsf@sun.com>

On 3/2/07, Dyre.Tjeldvoll@sun.com <Dyre.Tjeldvoll@sun.com> wrote:
>
> Is there really a contradiction here? I don't think anyone argues that
> old versions of patches should be deleted. I'm sorry, but I can't see
> how editing an unclear comment or spelling mistake destroys the
> history. Or for that matter removing a patch that was attached to the
> wrong issue by mistake.

The problem is that there is no granularity to JIRA's delete
privilege. If you can delete a comment, you can delete attachments or
whole issues.

> I find the current policy rather draconian and I think a
> common sense approach with clear guidelines cautioning against
> destroying the history would work just as well.

While that holds true for community members, does it hold true for
anyone on the internet with access to JIRA? Probably not.

Until recently, granting delete power was all-or-nothing.
Conveniently, a recent JIRA update introduced the idea of project
roles. With a little work, project roles (PMC member, committer,
contributor) can be assigned, thus restricting delete power to a
reasonable set of community members. I just haven't had time to go
through the derby-developers group in JIRA and assign project roles to
each member. I'll let you know once I do (or Jean or Rick can try and
beat me to it) and you'll be able to delete comments and attachments
again.

andrew