Last modified: 2013-01-30 12:34:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 26993 - wgLogo should be globally Wiki.png
wgLogo should be globally Wiki.png
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 26992
  Show dependency treegraph
 
Reported: 2011-01-27 21:04 UTC by Antoine "hashar" Musso (WMF)
Modified: 2013-01-30 12:34 UTC (History)
10 users (show)

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


Attachments

Description Antoine "hashar" Musso (WMF) 2011-01-27 21:04:08 UTC
Handling logo changes through bugzilla and requiring shell access is a bit long. Instead we could set $wgLogo to Wiki.png for ALL wikis, shell access will no longer be required and communities will be able to change it quickly.

Task 1:
On new wiki creation, upload a default Wiki.png file and protect it. This can be handled by a script, and surely need an update of our wiki creation documentation.

Task 2:
Look at all wgLogo, contact the communities and ask them to switch to Wiki.png. Or we could use a script which move the existing logo, protect it and leave a redirect.
Comment 1 Casey Brown 2011-01-27 21:10:44 UTC
We used to have a large percentage of the logos set to $stdlogo, but this was changed when the v2.0 Wikipedia logos were rolled out.  So...

Task 0.5: ask the Usability Team if they're ready for us to move all of the v2.0 logos to the local wikis so that they can be managed via Wiki.png again instead of Commons.

(In reply to comment #0)
> Task 1:
> On new wiki creation, upload a default Wiki.png file and protect it. This can
> be handled by a script, and surely need an update of our wiki creation
> documentation.

New wikis should already have a logo when they're requested, so we shouldn't need to upload just a default -- we can upload the real thing.  I'm pretty sure that the language committee has "create a logo" on their pre-bug checklist.
Comment 2 MZMcBride 2011-01-27 21:14:16 UTC
This bug is very closely related to bug 24078.
Comment 3 Huji 2012-02-17 17:05:17 UTC
I don't agree with the solution suggested here, because if a project decides to disallow local uploads (and rely on a shared repository of images), then handling logos will become an issue (example: bug 34476).

A better approach, in my humble opinion, is to have a MediaWiki message dedicated to the image path. It can contain a reference to a file (e.g. "File:Wiki.png") in which case MediaWiki will automatically find the find (locally or on a shared repo) and use it, or it can contain a URL (starting with http://, https:// or //).
Comment 4 Nemo 2012-02-17 17:10:08 UTC
(In reply to comment #3)
> I don't agree with the solution suggested here, because if a project decides to
> disallow local uploads (and rely on a shared repository of images), then
> handling logos will become an issue (example: bug 34476).
> 
> A better approach, in my humble opinion, is to have a MediaWiki message
> dedicated to the image path. It can contain a reference to a file (e.g.
> "File:Wiki.png") in which case MediaWiki will automatically find the find
> (locally or on a shared repo) and use it, or it can contain a URL (starting
> with http://, https:// or //).

Unless we steal this bug, though, this is a separate a MediaWiki feature request.
Comment 5 Huji 2012-02-17 21:10:08 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > I don't agree with the solution suggested here, because if a project decides to
> > disallow local uploads (and rely on a shared repository of images), then
> > handling logos will become an issue (example: bug 34476).
> > 
> > A better approach, in my humble opinion, is to have a MediaWiki message
> > dedicated to the image path. It can contain a reference to a file (e.g.
> > "File:Wiki.png") in which case MediaWiki will automatically find the find
> > (locally or on a shared repo) and use it, or it can contain a URL (starting
> > with http://, https:// or //).
> 
> Unless we steal this bug, though, this is a separate a MediaWiki feature
> request.

Yes, and I'm sorry that I wasn't clear enough in my comment; what I'm trying to suggest here is to move this bug to MediaWiki product bugs, and fix it here.
Comment 6 MZMcBride 2012-02-17 22:44:03 UTC
(In reply to comment #3)
> A better approach, in my humble opinion, is to have a MediaWiki message
> dedicated to the image path. It can contain a reference to a file (e.g.
> "File:Wiki.png") in which case MediaWiki will automatically find the find
> (locally or on a shared repo) and use it, or it can contain a URL (starting
> with http://, https:// or //).

A long-term goal is to _remove_ configuration from the MediaWiki namespace. This would be a step in the opposite direction.

This bug would be solved by a proper configuration interface. ^demon says such a configuration interface is slated for May 2012. Probably makes sense to wait for that.
Comment 7 Hazard-SJ 2012-04-13 02:29:13 UTC
(In reply to comment #3)
> I don't agree with the solution suggested here, because if a project decides to
> disallow local uploads (and rely on a shared repository of images), then
> handling logos will become an issue (example: bug 34476).
> 
> A better approach, in my humble opinion, is to have a MediaWiki message
> dedicated to the image path. It can contain a reference to a file (e.g.
> "File:Wiki.png") in which case MediaWiki will automatically find the find
> (locally or on a shared repo) and use it, or it can contain a URL (starting
> with http://, https:// or //).

We can simply use CSS for that.

I agree with MZMcBride above in comment #6:
> A long-term goal is to _remove_ configuration from the MediaWiki namespace.
> This would be a step in the opposite direction.

I believe that it would be best only to have localisation messages in the MediaWiki namespace, not configurations.
Comment 8 Antoine "hashar" Musso (WMF) 2013-01-30 12:34:08 UTC
So that was not a so good idea after all. We want to be able to have per wiki logos as well as some pointing to commons.  I am thus abandoning this bug.

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


Navigation
Links