Last modified: 2013-02-03 21:04:34 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 T40543, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38543 - kowikisource: set $wgLogo to be the local Wiki.png
kowikisource: set $wgLogo to be the local Wiki.png
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
wmf-deployment
All All
: Normal normal (vote)
: ---
Assigned To: jeremyb
http://ko.wikisource.org
: community-consensus-needed
: 39300 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-21 06:04 UTC by sotiale
Modified: 2013-02-03 21:04 UTC (History)
6 users (show)

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


Attachments

Description sotiale 2012-07-21 06:04:51 UTC
Good to see you. I'm not english speaker, If I have a mistake, please understand me and re-ask about it. I don't know this bug category is correct. (If it is not, I'm so sorry. Please let me know.)

I'm Korean Wikisource administrator. Our community want to change logo. We hear that local logo changing function exist and can apply bugzilla. For this reason, We request local logo changing function on. Thank you in advance.
Comment 1 sotiale 2012-07-21 06:26:41 UTC
Plus, logo already uploaded and protected. please check [[s:ko:File:Wiki.png]]. Thank you.
Comment 2 p858snake 2012-07-21 06:31:52 UTC
Please link to the local community consensus for this change.
Comment 3 sotiale 2012-07-21 07:42:54 UTC
Can I ask you a question? consensus means function active, or means logo changing? We collect opinion about 'logo must change', but support and oppose consensus do not exist yet. If it needed, I will start support and oppose about it. please wait a few days and cancel it. Thank you for your hard work.
Comment 4 sotiale 2012-07-21 08:19:11 UTC
related discussion about logo changing is [[s:ko:위키문헌:사랑방#로고]] and [[s:ko:위키문헌:사랑방#로고 변경 요청]]. recently discussion is [[s:ko:위키문헌:사랑방#로고 논의]]. I open new discussion about using function. If it needed, please a few days.
Comment 5 Alex Monk 2012-07-21 14:06:35 UTC
Changing the logo (or another configuration setting) for a Wikimedia wiki works something like this:

You make a proposal on the wiki.
If it gets accepted, you create a bug with a link to where the discussion took place.
A volunteer will create and commit the configuration change and then upload it to Gerrit, the code review system.
A WMF employee can then review, approve and deploy the change to Wikimedia servers.
Comment 6 jeremyb 2012-07-23 05:04:13 UTC
Looks like there has been very little response to the proposal? (and I'm still not clear on what the proposal actually says)

We need to have a clear English translation or summary of the consensus discussion and I don't think we've received that yet? Maybe I should hunt down a Korean native.

(In reply to comment #5)
> A WMF employee can then review, approve and deploy the change to Wikimedia
> servers.

s/WMF employee/user with shell access/
Comment 7 sotiale 2012-07-23 08:17:27 UTC
I opened new discussion about this request, 22 July. I'm so sorry, would you please wait a few days or cancel it? It is sure that our community want to change logo, but support and oppose discussion didn't exist. therefore, I opened new discussion. plus, plain English translation added. Because our community's consensus condition is at least 1 week, please a few days. If it cannot, please cancel this request. Again, I'm so sorry, I arouse criticism.
Comment 9 jeremyb 2012-12-16 17:13:13 UTC
The google translate's kinda fuzzy but it looks like there probably was consensus. Would prefer a native weigh in but otoh people have had more than enough time to object and no one did?

submitted in I96eeeec384ccacebfdd
Comment 10 Dereckson 2012-12-22 18:38:10 UTC
Deployed.
Comment 11 Alex Monk 2013-02-03 21:04:34 UTC
*** Bug 39300 has been marked as a duplicate of this bug. ***

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


Navigation
Links