[FFmpeg-devel] [RFC] Trac issues policy

Michael Niedermayer michaelni at gmx.at
Thu Apr 28 02:07:33 CEST 2011


On Wed, Apr 27, 2011 at 02:43:08PM -0800, Lou Logan wrote:
> On Thu, 28 Apr 2011 00:34:18 +0200
> Stefano Sabatini <stefano.sabatini-lala at poste.it> wrote:
> 
> > Hi,
> > 
> > how do you prefer to manage issues? Is acceptable to let the reporter
> > close the bug (assuming she will reply in a reasonable amount of
> > time), or Carl/the committer should do it?
> 
> I'm used to bug trackers that allow the reporter, and any other
> registered user, to close a bug. Seems to work fine. I can't think of a
> good reason to limit this functionality. Bugs can always be re-opened
> if they are mistakenly closed.

ive seen both the positive and negative sides of allowing anyone to
change anyzthing on a ticket.
Currently what seperates developers & normal registered users is just
TICKET_MODIFY

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The bravest are surely those who have the clearest vision
of what is before them, glory and danger alike, and yet
notwithstanding go out to meet it. -- Thucydides
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20110428/d6a7823e/attachment.asc>


More information about the ffmpeg-devel mailing list