User talk:Krinkle

Rendered with Parsoid
From Wikitech
Latest comment: 9 months ago by Triciaburmeister in topic Reverted consolidation of Main Page

Server list/yaseo

I can't remember what was here, but is being outdated a reason for deletion? If a template is not enough you could blank it. If there wasn't any meaningful info in the history ignore this message. Thanks! Nemo bis 00:01, 22 February 2012 (UTC)Reply

I did this as a follow-up to the earlier deletions related to Yahoo by User:RobH, such as Yf1014, List of yaseo servers, Yahoo cluster and more. And Server list/pmtpa (also subpage from the same list) was also deleted and Server list in general seems to be superseeded by Server roles and Category:Cluster/ Category:Servers --Krinkle 23:04, 24 February 2012 (UTC)Reply
I see. Looks like being outdated is considered a reason for deletion on this wiki. :-) By the way, all your maintenance work on this wiki is amazing. ;-) Nemo bis 18:46, 27 February 2012 (UTC)Reply
Yeah, I wasn't entirely sure about it myself. I attempted undeletion but then I saw that a whole bunch of other pages related to Yahoo were deleted as well. I guess outdated in general isn't a deletion reason, but the Yahoo cluster is no longer relevant to WMF so I guess that's what triggered the mass deletion back then. I cleaned up some left overs last week. You're welcome! --Krinkle 02:13, 28 February 2012 (UTC)Reply
Now all those pages are lost... :( --Nemo 09:47, 9 March 2013 (UTC)Reply

suggesting racktables parameter in server template

Template:Server#Requested_parameters. Dzahn 09:44, 29 June 2012 (UTC)Reply

Thanks!, replied on talk page. Krinkle 09:52, 29 June 2012 (UTC)Reply

Template fixes

Thanks for correcting my templates! I don't have much experience with wikitext aside from obvious formatting of prose, so I'm making quite a lot of mistakes. I'm gratified that you fixed a bunch of them. Thanks! --ori 03:06, 27 August 2012 (UTC)Reply


Do you remember what's the correct revision here? There's some importing mess in the history. Thanks, Nemo 09:47, 9 March 2013 (UTC)Reply

There is an interesting history indeed, but there is nothing wrong with it now. Krinkle (talk) 23:55, 10 March 2013 (UTC)Reply

Some stroopwafels for you!

Thanks for the docs updates. :) Quiddity (talk) 20:00, 28 November 2017 (UTC)Reply

Application servers changes

re: Those are not dcops things, that's service ops. I was a bit surprised that my own docs were suddenly not on the application server page anymore. And we use the term runbook already for something a bit different, how to react to Icinga alerts like those in Category:Runbooks. dzahn (talk) 15:18, 26 March 2020 (UTC)Reply

@dzahn: Oops, okay. I assumed hardware was DC Ops. Thanks for pointing it out. For Performance, we use "runbook" like a handbook, for all common tasks (including deployments), not just alert/incident response (see Performance/Runbooks). But no problem, I've moved it back. --Krinkle (talk) 22:20, 26 March 2020 (UTC)Reply

Mcrouter changes

Just wanted to let you know my bookmarked URL Mcrouter#Generate_certs_for_a_new_host was broken by a redirect/page move. dzahn (talk) 23:46, 24 March 2021 (UTC)Reply

@Dzahn Ack, understood. I adjusted it because there were also uses of it where I think the follower expected the general overview instead. It's ambigous either way. I've improved it in two ways now. First, the overview that the Mcrouter redirect points to now has an explicit reference to where the Mcrouter runbooks are (previously it said "See also", now it says "For runbooks, see"). Second, the Mcrouter redirect now jumps to the Mcrouter part of the overview page so that you immediately see that hatnote, instead of feeling lost and having to find the hatnote later down the page. --Krinkle (talk) 00:08, 25 March 2021 (UTC)Reply
Thank you, that sounds good. dzahn (talk) 18:36, 30 March 2021 (UTC)Reply

A barnstar for you!

The Original Barnstar
For authoring & working on the X-Wikimedia-Debug browser extension. Amazing work. Thank you :) Alangi Derick (talk) 00:16, 30 April 2021 (UTC)Reply

XML Dumps and data persistence infrastructure

I initially removed Dumps from the Data persistence group on the Infrastructure template, thinking that it had been assigned to the wrong Team by mistake: fearing that Ariel would think we took over their work. I later realized that it was not organized by team, but by topic. I am unsure where to classify it- for now I have put it under MediaWiki: The main reason is that database backups perform copies at MySQL level, while dumps use Mediawiki as the abstraction layer.

While they are very similar in the kind of operations performed (reading lots of rows), Ariel is very vocal (and I really support them, because _they have a point_) that xml exports are not backups. I understand that from an external view all is "data stored somewhere". I really don't have a strong suggestion of where to classify everything, but wanted to raise the issue with you and maybe we could think of a better classification that helps rising awareness about the difference between the 2. CC @ArielGlenn: -- Jcrespo 14:27, 19 May 2021 (UTC)Reply

I added these links as part of cleaning out Portal:Wikitech where these have been grouped together under "Backups" for many years. I do think topical grouping is preferred for the new structure as well. But, I actually departed from that by accident for this link when I placed "MariaDB" and "Backups" together under what is clearly a team ("Data persistence"), and then other Backup-related things naturally slipped in. Happy to group it any way you like, e.g. we could do "MariaDB", "Backups" and "Public dumps" as three separate groups. --Krinkle (talk) 15:32, 19 May 2021 (UTC)Reply

Low priority Navpop JS update request

Hiyo! Please could you make a fresh copy of w:en:MediaWiki:Gadget-popups.js into our MediaWiki:Gadget-popups.js. No particular reason, just 12+ months since last pull. Ty! :-) Quiddity (talk) 22:19, 10 October 2021 (UTC)Reply

Done! diff. Krinkle (talk) 02:54, 11 October 2021 (UTC)Reply


Hello. I am an editor in this wiki. I need the shell user rights for Toolforge.Md Tanbir Islam (talk) 03:21, 3 April 2022 (UTC)Reply

krinkle-redirect tool review

Hi, we're doing a review to make sure as many tools meet a minimum standard. I noticed krinkle-redirect tool doesn't have a description on toolsadmin, licence or a published repo. Could you add these information to this tool? Thanks! Komla Sapaty (talk) 00:13, 7 April 2023 (UTC)Reply

Reverted consolidation of Main Page

I think I understand your motivation in consolidating the Main Page content in Special:Permalink/2084432, but I disagree that it is desirable to have a very compact listing of the many and various Cloud Services areas. If you think there is a serious problem with the current layout I would appreciate discussion of goals of a redesign with myself and @Triciaburmeister before implementing it. Mostly I would like to avoid making things harder to find for new visitors for the benefit of frequent visitors. -- BryanDavis (talk) 20:21, 12 June 2023 (UTC)Reply

@BryanDavis: Okay, no problem. To clarify, I wasn't motivated by frequent visitors like myself. I believe those tend not to use the main page for navigation. Rather, I was motivated by new staff and management finding their way around to how teams and services are organised, and to learn how and whom to contact based on those pages. This was more of a "be bold" approach in case it's unviserally seen as improvement. But, as this might negatively impact new contributors to WMCS, I'll leave that for now, and think about it a bit more.
I've re-applied the description change for the production link only, I hope that's still useful. Should I make that shorter? With the reverted CSS change, I see the text gets close to the lines. This was fix for a pre-existing issue on narrow viewports, that with the slightly taller description, started effecting wider viewports. Krinkle (talk) 20:38, 12 June 2023 (UTC)Reply
> I was motivated by new staff and management finding their way around to how teams and services are organised
This makes sense to me. I don't think that this has been an explicit use case that we have worried about for Main Page before and you are likely correct that we can do better to support them. I think the w:WP:BOLD approach is fine for this page like pretty much any other on this wiki. This particular change just triggered me into the revert + discuss steps of that philosophy. :)
> With the reverted CSS change, I see the text gets close to the lines
I guess mostly I reverted that change because it felt related to the Main Page changes. I do not have any objections to Special:Diff/2084429 being partially or completely restored at your discretion. -- BryanDavis (talk) 20:54, 12 June 2023 (UTC)Reply
I think Special:PermanentLink/2084432 is a good revision. It makes the Cloud Services offerings easier to scan, and more clearly differentiates the sets of content on Wikitech by their likely audience. Decisions like this are often hard because the wiki content is serving multiple use cases, but I would say staff and management finding how teams and services are organized should be a lower priority use case for Wikitech than other use cases, like enabling SREs, devs, and prospective users/contributors to find technical info. That said, I think the structure of the content in the @Krinkle's revision makes the overall content landscape easier to parse as far as this entry point is concerned. We can also continue to iterate on this as we work on revising or improving other landing pages. Triciaburmeister (talk) 14:50, 14 June 2023 (UTC)Reply
I've been working on this redesign and would love your feedback and input to help finalize it. See Triciaburmeister (talk) 17:46, 21 August 2023 (UTC)Reply