[14:16:56] hi [14:17:03] how can i create a personal dashboard in phab [14:21:15] Les4353: you need to ask for it to be created because permissions, see my https://phabricator.wikimedia.org/T418726 [14:22:10] Raine: ohh... [14:22:37] and i looks like missing some perms that had by most members [14:22:44] is my feeling true? [14:23:18] I don't know, I also don't have permissions to create a lot of things [14:23:29] yea [14:24:20] dude [14:24:24] Raine: you are sre dude [14:24:44] truly you have very very very so much perms i have not [14:25:25] this is true :D but specifically on phabricator, I can't create projects and dashboards for example [14:25:43] yes I know I can put them into the database by hand :D but that's not what I mean :D [14:26:26] Raine: :) hah, also, what is 'Trusted Contributor'? [14:27:50] Les4353: I'm not really sure tbh, I don't know all that much about the volunteer side of things [14:28:08] Raine: are u wmf staff [14:28:28] Les4353: yes [14:28:34] ohh wow [14:33:56] im trying to renicking to codex for listening some related stuff in the sussy feed [14:34:03] and fails [14:34:15] hh [15:50:23] Les4353: See https://www.mediawiki.org/wiki/Phabricator/Help linked from the Phabricator frontpage [15:50:38] andre: ok, and hi [15:50:51] Most things are documented :) [15:51:46] yes [15:52:13] andre, do u know why some patches took 1 monthes or more to merge, and even it just pending on the list more than 1y [17:53:52] Les4353: That feels normal. The vast majority of patches gets quick handling, a small part does not. See https://www.mediawiki.org/wiki/User:AKlapper_(WMF)/Code_Review for a number of factors. [17:53:59] hmm, they left [18:12:39] hi [18:12:45] anyone can handle this? [18:12:50] !phab T435338 [18:12:51] T435338: Create User-Les4353 project - https://phabricator.wikimedia.org/T435338 [18:12:55] thanks deeply [19:01:14] Les4353: Some patches waiting for long feels normal. The vast majority of patches gets quick handling, a small part does not. See https://www.mediawiki.org/wiki/User:AKlapper_(WMF)/Code_Review for a number of factors. [19:01:45] Also, there is no need to ping on non-urgent tasks 4h after creating them. [19:02:33] a [19:02:43] i know that [19:02:47] now [19:02:51] im working on a edge project [19:03:06] and core projects may faster and faster than edge projects [19:03:22] thanks for that deply [19:04:35] not necessarily. [19:06:38] but i can confirm mediawiki/core is really faster in basiclly any patches than design/codex [19:06:40] hah [19:13:54] Les4353: define "faster" [19:14:20] which data is that based on? [19:14:30] andre: clearly, most core patches WILL NOT wait a month in the pending review list [19:14:51] because core is used by 1 billion users [19:15:21] that's irrelevant [19:15:46] and "most" sounds like percentage. I can imagine that this isn't the case in absolute numbers though [19:15:51] lol, you should see my patches [19:16:06] They often spend much more than a month awaiting review [19:16:17] relatively* [19:16:48] The experience you will have with submitting patches to core can vary a lot depending on what area you are working on [19:17:51] if I have more important/urgent things to do than reviewing contributed patches, so it is, unfortunately. My day only has 24 hours. :-/ [19:18:07] me too [19:18:33] and im trying to make codex better, the important step is let the patch faster to merge [19:18:57] no. [19:19:04] and im requesting for +2 privillege for it, i think my joining can let the entire project be better [19:19:06] andre: dude [19:19:09] Which problem is solved by "faster"? [19:19:18] in many standards and books [19:19:34] the time between a good idea created and it be delivered to end users [19:19:39] Les4353: We are after quality. We are not after "faster". Sorry. [19:19:39] is a critical metric [19:19:44] andre: yes [19:19:49] Les4353: you are requesting +2 on core? [19:19:53] i did not say we can ignore quality [19:20:08] bawolff: not core, only design/codex (and maybe design/codex-php) [19:20:14] oh [19:20:29] andre: we should speedup with the same or even better quality before [19:20:32] Les4353: We do not give out +2 to reduce bottlenecks. We give out +2 to folks who very well know the bigger picture and the codebase. [19:20:33] I was going to say, you have no merged patches to core, so it would be a bold move to request +2 :) [19:20:55] andre: i agree that [19:21:01] There is a lot to learn before receiving +2. [19:21:20] yes [19:21:43] I personally don't think two months of working on a codebase are sufficient for +2. [19:21:44] so im still learning and accept any suggestions, this is opensource i guess [19:21:54] it definitely is :) [19:22:02] basiclly i knew what is "open source" in codex [19:22:11] before codex, i only maintained some project with 0 or 1 stars [19:22:15] hah [19:22:21] I don't know what stars are. [19:22:30] andre: u do not use github? [19:22:35] andre: look out at sky. see sun. it star [19:22:52] Les4353: I sometimes pull stuff from it. Apart from that, I have GitLab. [19:23:10] andre: ohh, github is the largest programming community in this planet dude [19:23:14] Didn't WMF decide to drop maintenance of codex? I at least am a lot more sympathetic to requests to be +2 when the previous maintainer has walked away [19:23:15] perryprog, is very dark and cloudy on this side of the planet right now :D [19:23:33] bawolff: wmf never decide to abandon codex [19:23:55] andre: dang guess you will never see star :( [19:23:55] codex steering committee is still active, it even instead of design system team dude [19:23:59] Les4353, I am aware what Github is, as I had already said. No need to give me a feeling of explaining with "dude". [19:24:03] codex is the next generation design system, it will replace ooui [19:24:13] andre: oh [19:24:14] ok [19:24:26] please see what I had written before :) [19:24:42] ok... [19:24:54] I just don't care about "stars" on GitHub, it seems. :) [19:25:39] of coruse, based on you behavior, :) [19:25:56] I highly doubt codex will ever replace OOUI. https://xkcd.com/927/ and all [19:26:14] it will, i believe that [19:26:21] like ooui replaced jquery ui [19:26:46] except all the places we're still using jqueryui? [19:26:52] let's just delete all the themes but monobook and call it a day [19:26:55] and the fact MW still ships it? [19:27:10] In any case, thanks for your work on Codex. [19:27:31] perryprog: dude. monobook is really ugly, vector, vector... [19:27:40] Subjective! [19:27:40] Also, codex is not really a 1:1 replacement for OOUI. [19:27:46] Opinions. What the internet has been made for. [19:27:50] andre: Thanks. I am also deeply thanks you working in WMF for many many years! [19:28:02] sheesh, but of newbs. Use the Standard skin the way mediawiki was intended to be used :P [19:28:22] * andre gets some popcorn and tries to walk away [19:28:31] * Les4353 huh [19:28:36] (To be clear though I'm Timeless for life) [19:28:51] perryprog: good meme [19:28:53] Les4353: I'm just trolling. Standard was the skin before monobook. It was really ugly [19:29:11] bawolff: yep [19:29:12] i know [19:29:15] :) [19:30:27] do the correct thing [19:31:55] andre: and the other thing i confuse is why you are suber of every and any task [19:33:23] See https://www.mediawiki.org/wiki/Bugwrangler (though that's a bit outdated by now) [19:34:32] andre, say, I've always meant to ask you—do you have phabricator email notifications on for comments? [19:35:12] perryprog: clearly no, if yes, his inbox will be very fat, :) [19:35:12] perryprog: yes I have. But I also have many mail filtering rules. [19:35:21] andre: wow, brave. [19:35:39] not really. amount of mail is irrelevant, filtering is relevant.