Last modified: 2011-06-22 02:10:45 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T24370, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 22370 - Change bugzilla logo and favicon from default to customized
Change bugzilla logo and favicon from default to customized
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Bugmeister Bot
http://meta.wikimedia.org/wiki/Wikime...
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-03 14:12 UTC by Danny B.
Modified: 2011-06-22 02:10 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Danny B. 2010-02-03 14:12:32 UTC
We should not use the default logo/mascot and favicon. (It's been suggested in bug 221756 comment #0 as well.)

There was a neat proposal on http://meta.wikimedia.org/wiki/Wikimedia_Forum/Archives/2008-09#Bugzilla_logo_change for example (needs still some touches though).

----

Or should we for the time being use old favicon (I can't find it online ATM, but have cached one, if necessary.) and old logo/mascot (<http://commons.wikimedia.org/wiki/File:Bug.png>) ?
Comment 1 Danny B. 2010-02-03 14:14:08 UTC
Bug 22175 of course... ;-)
Comment 2 Happy-melon 2010-02-08 20:10:07 UTC
Why shouldn't we use the bugzilla bug?  It's free content, and it's way cuter than anything I've seen proposed.
Comment 3 JeLuF 2010-03-27 11:49:13 UTC
Please come back and reopen this ticket as soon as there's consensus about the logo to install.
Comment 4 Danny B. 2010-03-27 14:06:15 UTC
(In reply to comment #2)
> Why shouldn't we use the bugzilla bug?  It's free content, and it's way cuter
> than anything I've seen proposed.

Couple reasons, for example:
* Favicons exist to help to differ tabs and bookmarks. Imagine I have access to other bugzillas of other projects which did not set the logo. It is real PITA to find the correct tab (I usualy have 50+ opened) if you have more than one project's bugtracker opened. Not speaking about bookmarks. Imagine all Wikisources/Wiktionaries/Wikibookses... had [[<sunflower>]] same MediaWiki logo, just because it runs on free software thus it has "free content"...
* And logo? It's all about marketing - having default logo says "we are lamers who can't even make ourn own logo" and "we don't care about our users, they are not worth to set something customized". By the way - we strongly encourage users of MediaWiki with text-overwritten default logo to load their own too... See? The same issue...

I'm not saying anything about those logos & favicons, which one should be set - it's a question of poll probably. However, definitely there must be any other than the default.

(In reply to comment #3)
> Please come back and reopen this ticket as soon as there's consensus about the
> logo to install.

Well, I haven't seen any consensus to change it from previous orange/brownish bug as logo and some kind of black/grey fly on white as favicon. Just for the record...

Since it is actually NOT resolved, I'm keeping it open, otherwise it will remain forgotten. Resolved/later status should be set, if previous logo and favicon were set back and the discussion on new would be held somewhere. This did not happen.
Comment 5 JeLuF 2010-03-27 14:17:22 UTC
That one? 
http://www.thegeekstuff.com/wp-content/uploads/2008/10/bugzilla-logo-260x300.png

That was the default logo of an older version. And with the upgrade of bugzilla, the new default logo has been installed.


PS: Warning: the new version of ViewVC also comes with a new logo.
Comment 6 p858snake 2011-06-22 02:10:45 UTC
WONTFIXing this, never got consensus or a suggestion for a better logo and/or favicon combo and there is no point having it sit around in LATER for no reason all this time.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links