[04:30:28] 6Phabricator, 10MediaWiki-Extension-Requests, 10Possible-Tech-Projects: MediaWiki extension to embed Phabricator content in wiki pages - https://phabricator.wikimedia.org/T90432#1696104 (10Haritha28) Thanks @Aklapper . I would like know who are the mentors assigned for this particular project. [09:38:58] 6Phabricator, 10MediaWiki-Extension-Requests, 10Possible-Tech-Projects: MediaWiki extension to embed Phabricator content in wiki pages - https://phabricator.wikimedia.org/T90432#1696475 (10Aklapper) >>! In T90432#1696104, @Haritha28 wrote: > I would like know who are the mentors for this particular project.... [10:21:16] 6Phabricator, 10MediaWiki-Extension-Requests, 10Possible-Tech-Projects: MediaWiki extension to embed Phabricator content in wiki pages - https://phabricator.wikimedia.org/T90432#1696590 (10Qgil) The main use cases would be * Queries of Maniphest tasks to be inserted in wiki pages of projects or other techni... [12:08:38] 6Project-Creators: Clarify #Phabricator project confusion - https://phabricator.wikimedia.org/T112040#1696741 (10Aklapper) Uh, and there is also #acl*phabricator adding more ingredients to the mix, sigh [12:20:11] 6Project-Creators: Clarify #Phabricator project confusion - https://phabricator.wikimedia.org/T112040#1696756 (10Krenair) Wouldn't it be helpful if you could list policies referring to an object and find out what uses those policIes? I imagine someone with database access could manage it... [16:05:29] 6Project-Creators: Clarify #Phabricator project confusion - https://phabricator.wikimedia.org/T112040#1697397 (10greg) >>! In T112040#1696741, @Aklapper wrote: > Uh, and there is also #acl*phabricator adding more ingredients to the mix, sigh Is that redundant with Phab Admins as well? But it also seems like tha... [16:50:29] andre__afk, qgil: anyone knows why I can't edit security settings for tasks anymore? [17:00:21] task as an example? [17:13:02] chasemp: https://phabricator.wikimedia.org/T100803 i think [17:13:06] we just talked about that too [17:13:20] yup [17:13:26] so in this case we want to let some people from WMDE have access too [17:13:36] it was easy for me to add Jan because he already has WMF nda [17:13:43] but how should we go from there [17:14:36] someone from the security group showed me that he can still influence the permission like before, so he would be able to add to view permission "people who are cc-ed" [17:14:54] i was able to do that also before, but it seems something changed [17:15:18] i added Abraham as subscriber but not sure if that means he can see it now [17:15:18] mutante: you should still have that dropdown under edit task [17:15:27] no he can't see it [17:16:13] yes, it's "Other confidential issue". that drop down , right [17:16:29] no the permissions dropdown not the securrity extensions one [17:16:33] or you talking about the custom policy [17:16:39] yes that one [17:16:54] there is an option for "people who are cc-ed" [17:17:15] ok, i'm adding Abraham as an individual user to the custom policy [17:17:27] it just seemed better to use a group [17:17:33] but we dont have one that applies here [17:17:45] and there already is a user specific custom policy ..shrug [17:18:41] it's the reporter who is allowed as an individual user [17:19:26] yes i think that is the work of the wmf security extension [17:21:48] so yea,we could add a rule to just allow subscribers, but is that good idea? [17:27:20] mutante: I think it is fine if you trust everyone who can see the ticket to not add people who should not be added [17:29:57] jzerebecki, you're a member of WMF-NDA but can't edit task policies? [17:30:06] Krenair: yes [17:30:13] jzerebecki: yes, so i would do it on a ticket with 3 other subscribers but here it's many dozens who are not really related [17:30:33] just let me know who else to add and i'll do it. mid-term let's make a WMDE group or something [17:30:54] Might be that it's just admins and security who can edit those [17:31:09] You need to open a project request for a WMDE ACL group [17:31:21] mutante: err I don't want an WMDE group [17:32:00] mutante: WMDE-domains would be ok [17:32:03] jzerebecki: don't call it WMDE then, call it PeopleWhoDealWithStuffThatNeedsWMFandWMDE [17:32:33] jzerebecki: if there is going to be more than this one ticket, yea [17:32:51] let's start with if WMDE even wants these domains [17:33:05] and still manages all domains related to WLM [17:33:09] yup [17:33:22] Are you planning to make a new restricted project? [17:33:39] Krenair: not yet. but possibly. [17:34:39] because there are people in wmde that don't have an wmf nda (most of wmde) and need access to things that might need to be non-public [17:35:50] but I really dislike making such things organization centric because it leads to processes that make it harder for volunteers to be included [17:38:29] If only more people thought like that... [17:38:39] To be clear, I'm not advocating for or against such a project. [17:38:53] Just that the proper process for ACL projects be followed if that happens. [17:42:04] jzerebecki, this is one of the reasons I don't like how everything seems to have to revolve around a Team. [17:43:47] yea will follow the wiki page on how to request a project if that comes up [17:43:57] thanks [17:44:33] I just edited the definition of that type a bit, the previous wording was hard for me to parse [17:54:36] jzerebecki: Krenair: ever heard of "border-wikipedia.de" before? [17:54:47] i just disabled that [17:55:08] it was wikipedia.org in DNS but not configured on webservers [17:55:15] and probably in there for years [17:55:36] what was the point of the "border" part of the name in the first place [18:03:23] mutante: you also need to allow him in the view policy, only edit doesn't help [18:05:56] jzerebecki: oops, fixed! [18:06:01] thx [18:07:15] got pulled into a meeting and missed all the fun but looks settled? [18:13:27] chasemp: i think it's still open what exactly changed recently [18:13:35] that changed things for jan [18:14:27] regarding this: Krenair> jzerebecki, you're a member of WMF-NDA but can't edit task policies? [18:15:42] chasemp: yes that^^ is true and thus still open [18:16:08] wmf-nda can view confidential issues but is not granted policy management by default [18:16:11] only security and ops [18:16:16] and without teh ability to do subgroups it's all explicit [18:20:30] ok thx [23:35:41] 6Project-Creators, 10Beta-Cluster, 6Release-Engineering-Team: Identify / separate out software issues found *on* Beta Cluster versus issues with Beta Cluster itself - https://phabricator.wikimedia.org/T114486#1699007 (10greg) Adding #project-creators to log this. [23:35:51] 6Project-Creators, 10Beta-Cluster, 6Release-Engineering-Team, 15User-greg: Identify / separate out software issues found *on* Beta Cluster versus issues with Beta Cluster itself - https://phabricator.wikimedia.org/T114486#1699009 (10greg) a:3greg