![]() ![]() Less noise and less diffing required for future upgrades. It turned out that 16 out of 22 files could be removed since there was no sufficient difference to upstream’s default CSS code (Bugzilla falls back to loading the default CSS file from /skins/default if no custom CSS file is found in /skins/custom). In late November of 2013 I started cleaning up Wikimedia Bugzilla’s custom CSS which was copied about five years ago and not kept in sync. Some reasons for upgrading can be found in this Bugzilla comment. ![]() Among many other tasks, I spent the last few months preparing the upgrade of Wikimedia’s Bugzilla instance from 4.2 to 4.4. Though we currently also evaluate Wikimedia’s project management tools, we will have to stick with our current infrastructure for a while. This post explains the technical details and challenges. Furthermore, proper configuration management for this software was set up. The software behind Wikimedia’s website for tracking software issues and feature requests was recently updated to a newer version and moved onto a new machine in a different datacenter. spamming over public holidays when most people are not on duty), the Wikimedia Foundation Operations team has a dedicated Bugzilla account.The original publication of this blog post can be found here. In order to be able to edit/ban Bugzilla accounts and/or hide Bugzilla comments in emergency cases (e.g.The insidergroup group is currently () set to consist of the admin and security groups. Marking comments and attachments as private and accessing comments and attachments marked as private requires membership in the insidergroup group.Specific Wikimedia Bugzilla configuration (Thanks to Byran Jones (:glob) for input.) The list above is not necessarily complete. viewing the generated SQL query by using the &debug=1 URL parameter. ![]() editing Bugzilla field values and custom fields.deleting attachments (instead of just marking them as private).in case of violations against the code of conduct policy (this is inherited from editusers group membership: editusers group membership de facto means admin group membership, as an account with editusers group membership can edit his/her account and set admin group membership.) editing or blocking Bugzilla accounts, e.g.Membership in the Bugzilla admin group is required for the following tasks: Tasks which require being an administrator If admin group membership is handed out to individuals who are not employees of the Wikimedia Foundation it is required to sign an indefinite non-disclosure agreement first, due to legal requirements (e.g. This also helps avoiding a large number of Bugzilla administrators and related coordination issues. When none of the tasks listed below under "Tasks which require being an administrator" are to be executed by a specific Bugzilla user, a combination of other, more specific Bugzilla group memberships should be handed out instead of handing out admin and/or editusers group membership. Furthermore, having a large number of administrators can create coordination issues. Without guidelines why a user is an administrator, this can create mistrust. Some users at have administrator rights and hence more powers than other users. This document describes when to hand out administrator rights in Wikimedia Bugzilla. Purchasing and disbursements procedures.Guidelines covering pluralism, internationalism, and diversity in hiring.Confidentiality agreement of the Board of Trustees.Code of conduct of the Board of Trustees.Code of conduct for Wikimedia technical spaces, including events.Please note that in the event of any differences in meaning or interpretation between the original English version of this content and a translation, the original English version takes precedence. This policy or procedure is maintained by the Wikimedia Foundation and applies to Foundation activities. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |