Can you explain why you're using hardcoded styles instead of using a template, why you're calling the header template twice, why the style section mixes spaces and tabs, and why it's using tabs at all? I was under the impression that the reasons to not do all of these things was discussed weeks ago. Now I'm discovering that you've seemingly completely disregarded everything you were supposed to learn and have made a large mess. I'm lost. --MZMcBride 19:59, 3 December 2010 (UTC)
- That particular style was designed by Kaldari (including the hard code and the extra header call) In creating new vesions i have been copying because it has been easiest for me. As we have started to settle on that style for the US cleaning up the code into a template is not illegitimate and your concerns are obviously valid however to say that I am 'disregarding everything you were supposed to learn' is neither fair or correct. If you have concerns please say them, and you are right the code should be cleaned up at this point, I had, however, not placed it as a high priority given the amount of work that has to be done and the fact that I will be out most of next week for surgery. To be honest I believe that was the right decision.
- Also, in the future PLEASE do not change live pages if they are working. A mess that works is far better then a cleaner page that accidentally has a stray tag or comma breaking a live donation page. I do not expect that you would generally cause such errors but at this point I would like to err on the side of safety. Jalexander 20:16, 3 December 2010 (UTC)
- We had a conversation with the intent of specifically avoiding spreading out code to various individual pages rather than keeping it centralized. We had a conversation about not using tabs in browser textareas. We didn't have a conversation about not calling the same template twice, though I think that's fairly obvious. It's your account in the page history, so only your account can be responsible for the edits it makes. Not Kaldari or anyone else.
- You can complain about editing live pages when there's (a) some indication that they're live; (b) when the code isn't so horrible that I stop lazing to fix it; and (c) when I break something. Erring on the side of safety would mean checking this code before putting it live. Erring on the side of safety would mean putting safety checks in place, like templates. Erring on the side of safety would not be putting badly written code live and hoping it all works out and that nobody notices. --MZMcBride 20:26, 3 December 2010 (UTC)
Assorted fundraising comments and questions
Does "GC" stand for something? If so, the full term (in CamelCase, if you prefer) should be used. (I googled "GC payment system" but didn't see anything off-hand.) --MZMcBride 03:04, 3 September 2011 (UTC)
- Sorry, GC is Global Collect a new payment system we're trying out because of a lot of added payment options. The GC.css is a page they can call to allow us to change the view of pages that are hosted by them and was probably not the best choice in names (I was in a hurry and wanted a spot to store it for now). This specific url is going to be fairly temporary (we'll probably move it to another server eventually) and changing the name requires them to update it on their side which takes a while. Because of that I'd rather not rename it for now but I'll clarify the name on the page for others who see it like you did. Jalexander 20:51, 7 September 2011 (UTC)
- Oh, sorry. I didn't fully read your comment until I moved the page and deleted the redirect. I'm not sure it can break much, though, as it didn't/doesn't contain any directives. --MZMcBride 22:12, 7 September 2011 (UTC)
Old page protections
Hi. You have some old page protections here (from November 2010):
- Nope, I'm fine with all of those being unprotected now. Thanks! Jalexander (talk) 23:08, 19 April 2012 (UTC)
Hi. I'm working on cleaning up this wiki a bit. I've proposed the following pages for deletion. I'm notifying you as you're listed in the page history. Without objection, the pages listed below will be deleted in about a month. Thanks for all of your work here. --MZMcBride (talk) 21:37, 16 March 2013 (UTC)
- Keep Wikipedia Free/temp
- Holding/Personal appeal
- User:Jalexander/Blog share
- Monthly donations/en/test
- Test/L11 1107 US Alan/en/US
- L2011 JWJN001/en
- L2011 JWJN001/en/MX
- L2011 JWJN001/es/MX
- L2011 JWJN001/sw/TZ
- L11 0209 Alan-a/en
- L11 0209 Jimmy/en
- Holding/Hear from KartikaA/en
- Holding/Hear from Kartika/en
An important message about renaming users
I am cross-posting this message to many places to make sure everyone who is a Wikimedia Foundation project bureaucrat receives a copy. If you are a bureaucrat on more than one wiki, you will receive this message on each wiki where you are a bureaucrat.
As you may have seen, work to perform the Wikimedia cluster-wide single-user login finalisation (SUL finalisation) is taking place. This may potentially effect your work as a local bureaucrat, so please read this message carefully.
Why is this happening? As currently stated at the global rename policy, a global account is a name linked to a single user across all Wikimedia wikis, with local accounts unified into a global collection. Previously, the only way to rename a unified user was to individually rename every local account. This was an extremely difficult and time-consuming task, both for stewards and for the users who had to initiate discussions with local bureaucrats (who perform local renames to date) on every wiki with available bureaucrats. The process took a very long time, since it's difficult to coordinate crosswiki renames among the projects and bureaucrats involved in individual projects.
The SUL finalisation will be taking place in stages, and one of the first stages will be to turn off Special:RenameUser locally. This needs to be done as soon as possible, on advice and input from Stewards and engineers for the project, so that no more accounts that are unified globally are broken by a local rename to usurp the global account name. Once this is done, the process of global name unification can begin. The date that has been chosen to turn off local renaming and shift over to entirely global renaming is 15 September 2014, or three weeks time from now. In place of local renames is a new tool, hosted on Meta, that allows for global renames on all wikis where the name is not registered will be deployed.
Your help is greatly needed during this process and going forward in the future if, as a bureaucrat, renaming users is something that you do or have an interest in participating in. The Wikimedia Stewards have set up, and are in charge of, a new community usergroup on Meta in order to share knowledge and work together on renaming accounts globally, called Global renamers. Stewards are in the process of creating documentation to help global renamers to get used to and learn more about global accounts and tools and Meta in general as well as the application format. As transparency is a valuable thing in our movement, the Stewards would like to have at least a brief public application period. If you are an experienced renamer as a local bureaucrat, the process of becoming a part of this group could take as little as 24 hours to complete. You, as a bureaucrat, should be able to apply for the global renamer right on Meta by the requests for global permissions page on 1 September, a week from now.
In the meantime please update your local page where users request renames to reflect this move to global renaming, and if there is a rename request and the user has edited more than one wiki with the name, please send them to the request page for a global rename.
Stewards greatly appreciate the trust local communities have in you and want to make this transition as easy as possible so that the two groups can start working together to ensure everyone has a unique login identity across Wikimedia projects. Completing this project will allow for long-desired universal tools like a global watchlist, global notifications and many, many more features to make work easier.
If you have any questions, comments or concerns about the SUL finalisation, read over the Help:Unified login page on Meta and leave a note on the talk page there, or on the talk page for global renamers. You can also contact me on my talk page on meta if you would like. I'm working as a bridge between Wikimedia Foundation Engineering and Product Development, Wikimedia Stewards, and you to assure that SUL finalisation goes as smoothly as possible; this is a community-driven process and I encourage you to work with the Stewards for our communities.
Protection of Template:Staff and contractors
- HR has asked me to do so and they own that page. While this is a wiki it is also the public face of the WMF and, like any wiki, there are some pages that are more sensitive. If you have questions I would point you to ALantz (WMF) and Jlohr. Jalexander (talk) 01:52, 8 July 2015 (UTC)
Links to Meta for translated versions
About this edit: maybe needs to apply this way for another translatable pages? As example,
- Cookie statement > to meta:Cookie_statement
- Frequently asked questions > to meta:Fundraising 2012/Translation/FAQ (maybe this better time for rename this page to more "years-independend" pagename ?)