[FFmpeg-devel] [RFC] Submit a Logo Wiki Page

Michael Niedermayer michaelni at gmx.at
Sun Jul 1 00:51:44 CEST 2012


On Sat, Jun 30, 2012 at 12:10:41PM -0800, Lou Logan wrote:
> On Sat, 30 Jun 2012 14:10:18 +0200
> Michael Niedermayer <michaelni at gmx.at> wrote:
> 
> > On Sat, Jun 30, 2012 at 01:35:36PM +0200, Stefano Sabatini wrote:
> > > On date Friday 2012-06-29 14:42:19 -0800, Lou Logan encoded:
> > > > On Mon, 25 Jun 2012 23:25:48 +0200
> > > > Michael Niedermayer <michaelni at gmx.at> wrote:
> > > > 
> > > > > On Mon, Jun 25, 2012 at 11:28:18AM -0800, Lou Logan wrote:
> > > > > > On Mon, 25 Jun 2012 14:16:00 +0200
> > > > > > Stefano Sabatini <stefasab at gmail.com> wrote:
> > > > > > 
> > > > > > > On date Saturday 2012-06-23 23:43:45 +0200, Alexander Strasser encoded:
> > > > > > > > Hi Stefano!
> > > > > > > [...]
> > > > > > > >   Not sure what you are aiming it. Of course tickets should be closed
> > > > > > > > when the contest is over. Or if the purpose of the ticket is to create
> > > > > > > > a specific artwork, the ticket should be closed when that work is
> > > > > > > > considered finished.
> > > > > > > > 
> > > > > > > >   For accumulating everything in one ticket. Not sure if it should
> > > > > > > > is always for the better. If we do it like this year, it could have
> > > > > > > > benefits. The news entry could be created when the contest is started,
> > > > > > > > and a link to that ticket collecting the submissions could be provided
> > > > > > > > there to make it easy for artist to simply upload their work there. 
> > > > > > > 
> > > > > > > Yes my main concern is having tickets with generic names
> > > > > > > (e.g. "summertime logo") which give no indication about when the
> > > > > > > ticket can be considered "closed", and I tend to be pretty "puristic"
> > > > > > > (pedantic?) when terminology is abused and leads to confusion.
> > > > > > 
> > > > > > I'd close the currently open art tickets (and update the titles to
> > > > > > something less generic), but I hesitate to do so without an additional
> > > > > > "close as" option that's more appropriate for completed art other than
> > > > > > fixed, worksforme, invalid, won't fix, duplicate, need more info.
> > > > > 
> > > > > if people want more "closed" states, i just need to know what the
> > > > > new state should be called
> > > > 
> > > > How about "completed art" and/or "archived art"? In #ffmpeg-devel,
> > > > Stefano suggested "archived art" for unfinished/abandoned submissions,
> > > > and "completed art" for finished art, but I'd prefer one closed art
> > > > state for no reason other than keeping the number of closed states from
> > > > growing too much. If two closed art states are ok with others then I'd
> > > > be fine with that. I'd also be fine with using "archived art" for both
> > > > states if that makes sense.
> > > 
> > > I'm fine with two states (completed/archived) or just one "archived"
> > > which emcompasses both situations (completed and incompleted but
> > > closed anyway).
> > 
> > 
> > for incomplete, its easy to use closed/invalid (an invalid submission
> > of a logo as its not complete)
> > or closed/needs changes, (as its unfinished and would need some
> > changes)
> 
> If you add "completed (art)" I'll clean up the current art tickets and
> use closed/invalid for incomplete submissions with a comment indicating
> that it is incomplete.

done

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I am the wisest man alive, for I know one thing, and that is that I know
nothing. -- Socrates
-------------- 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/20120701/178af10a/attachment.asc>


More information about the ffmpeg-devel mailing list