[01:59:53] 6Phabricator: pick up ticket mentions from !log lines - https://phabricator.wikimedia.org/T108720#1530347 (10scfc) Is `!log` => SAL no longer done by #morebots? In theory, that already has code for example to output to Twitter, so adding a Phabricator output should be "easy" (IIRC @gerritbot is written in Pytho... [04:06:37] 6Phabricator: Consider using the Badges application for a few special roles to highlight those users' comments - https://phabricator.wikimedia.org/T106924#1530496 (10Peachey88) We now have the following rubbish: * [[ https://phabricator.wikimedia.org/badges/view/4/ | Tea Lover]] (DESCRIPTION: This user loves tea... [04:20:03] 6Phabricator: Consider using the Badges application for a few special roles to highlight those users' comments - https://phabricator.wikimedia.org/T106924#1530512 (10Deskana) I do not agree with the rationale provided in the description. People demonstrate that they are worth listening to without the need for sp... [04:20:49] 6Phabricator: Consider using the Badges application for a few special roles to highlight those users' comments - https://phabricator.wikimedia.org/T106924#1530513 (10Deskana) >>! In T106924#1530496, @Peachey88 wrote: > We now have the following rubbish: > * [[ https://phabricator.wikimedia.org/badges/view/4/ | T... [05:38:14] 6Phabricator, 6Collaboration-Team-Backlog: Only add the Collaboration-Team-Backlog project if it's not in Collaboration-Team-Current - https://phabricator.wikimedia.org/T108393#1530594 (10Mattflaschen) >>! In T108393#1525853, @Aklapper wrote: > but (unrelated and off-topic) I have no idea why a sprint like #Co... [06:47:04] 6Phabricator: Consider using the Badges application for a few special roles to highlight those users' comments - https://phabricator.wikimedia.org/T106924#1530728 (10Qgil) Allowing all users to create badges is even a step further. [07:16:52] 6Engineering-Community, 10MediaWiki-extensions-Newsletter, 3Google-Summer-of-Code-2015: Goal: Newsletter extension for MediaWiki - https://phabricator.wikimedia.org/T76199#1530781 (1001tonythomas) [07:22:23] 6Engineering-Community, 10MediaWiki-extensions-Newsletter, 3Google-Summer-of-Code-2015: Goal: Newsletter extension for MediaWiki - https://phabricator.wikimedia.org/T76199#1530835 (10Qgil) [10:29:33] 6Phabricator: Ensure that all phabricator tasks are crawled by search engines - https://phabricator.wikimedia.org/T76991#1531142 (10Nemo_bis) 5stalled>3Open > just search google for the task id: T102920 for example, is indexed I'm not going to perform 100k Google searches, it's going to take ages with throt... [10:29:40] 6Phabricator: Ensure that all phabricator tasks are crawled by search engines - https://phabricator.wikimedia.org/T76991#1531154 (10Nemo_bis) a:5Nemo_bis>3None [11:32:25] 6Engineering-Community, 10MediaWiki-extensions-Newsletter, 3Google-Summer-of-Code-2015: Goal: Newsletter extension for MediaWiki - https://phabricator.wikimedia.org/T76199#1531240 (10Tinaj1234) [11:39:00] 6Phabricator: Ensure that all phabricator tasks are crawled by search engines - https://phabricator.wikimedia.org/T76991#1531265 (10Aklapper) Thanks a lot for clarifying! I can reproduce this, indeed. [11:39:10] 6Phabricator: Not all Phabricator tasks are crawled by search engines - https://phabricator.wikimedia.org/T76991#1531266 (10Aklapper) [13:51:48] 6Project-Creators: Create new Testing Initiative 2015 tag - https://phabricator.wikimedia.org/T108724#1531573 (10Aklapper) > If a tag is not appropriate for this, we can probably get by with an epic parent task. It's sort of a shame that the only way to get a workboard is through a restricted process This sound... [14:03:48] 6Project-Creators, 10ImportUsers: Create a project for the "ImportUsers" extension - https://phabricator.wikimedia.org/T108574#1531594 (10Kghbln) [15:04:22] 6Project-Creators: Create "Human Resources" project - https://phabricator.wikimedia.org/T284#1531775 (10Aklapper) [15:05:22] 6Project-Creators: Create "Human Resources" project - https://phabricator.wikimedia.org/T284#1531785 (10Aklapper) @Pine: Is there a reason why the Phabricator project #Human-Resources at https://phabricator.wikimedia.org/project/profile/22/ has an Edit Policy restricted to "Allow users: @GYoung, @Pine"? Also, t... [15:06:38] andre__, can't we lock down project policies like we do task policies? [15:06:53] tons of projects have crazy edit policies [15:21:34] It is possible to go through all of them with an unprivileged account and python [15:26:31] we have guidelines. [15:26:43] people are supposed to read them [15:26:51] if they don't do we'll have to think about that. [15:27:01] that's all I can say right now as I'm on my way out for today, sorry [15:30:41] Krenair: it might be possible. I thought we had projects locked down to a project creators group which were educated about this stuff [15:33:11] so we do and they are not really [15:33:19] I believe [15:33:50] originally I had wanted to designate project creators for teams and so an onboarding thing [15:34:02] that has completely degraded I believe [15:37:59] chasemp, degraded? [15:38:54] gone down hill :) [15:42:41] adds hr-learn-to-tango [15:53:41] admittedly even I have failed to follow the guidelines on a few things (repository naming, partially by mistake and partially rebellion against short-names) but regarding project edit policies, the default edit policy is set to all users. Should the edit policy be set to the same as the project creation policy? [15:55:10] that must have changed at some point [15:55:19] or no I'm sorry [15:55:36] the intention was for all users to edit all projects unless //very specific need// [15:55:42] whatever that would mean [16:00:09] 6Phabricator: Unclear what the point of tokens in Phabricator is - https://phabricator.wikimedia.org/T899#1531902 (10mmodell) https://phabricator.wikimedia.org/token/leaders/ can show a list of popular, or perhaps unpopular tasks. Only slightly amused by the fact that this task is the current leader. [16:11:59] twentyafterfour, chasemp, mutante: https://phabricator.wikimedia.org/P1872 [16:12:36] wut is #bug-report [16:13:17] mmodell changed the edit policy of this Project from "All Users" to "Phabricator (Project)". [16:19:45] https://phabricator.wikimedia.org/P1873 [16:23:43] 6Phabricator: Consider using the Badges application for a few special roles to highlight those users' comments - https://phabricator.wikimedia.org/T106924#1531964 (10mmodell) I uninstalled the application since it is apparently not enforcing policies. [16:28:56] 6Phabricator: Consider using the Badges application for a few special roles to highlight those users' comments - https://phabricator.wikimedia.org/T106924#1531979 (10Krenair) 5Open>3declined a:3Krenair [16:33:54] 6Project-Creators: Create new Testing Initiative 2015 tag - https://phabricator.wikimedia.org/T108724#1531993 (10dduvall) >>! In T108724#1531573, @Aklapper wrote: > This sounds like a misunderstanding? A //tag// is a subclass of a project so I hope you wanted to write //project// when you wrote //tag//. Only //t... [16:41:11] 6Phabricator: When adding a bug to a sprint you also have to add it to the product - https://phabricator.wikimedia.org/T93124#1532000 (10Jdlrobson) 5Open>3declined You'd have to setup a herald rule for every newly created sprint and that doesn't seem feasible. If you could create sub projects then that might... [17:25:48] 6Project-Creators: Create new Testing Initiative 2015 tag - https://phabricator.wikimedia.org/T108724#1532094 (10ggellerman) I changed the tag to a goal with the color orange. [17:33:04] 6Engineering-Community, 3ECT-August-2015: Email to Chapters List: ECT documentation, support and available resources - https://phabricator.wikimedia.org/T108647#1532098 (10NiharikaKohli) @Aklapper, thanks. I am not too sure what kind of benefit the chapters can derive from these mentorship programs, but I'll... [17:39:11] 6Engineering-Community, 3ECT-September-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Write a blog post summarizing Wikimedia's participation in GSoC 2015 (and Outreachy 10) - https://phabricator.wikimedia.org/T108054#1532112 (10NiharikaKohli) >>! In T108054#1528579, @Qgil wrote: > Post for the Wi... [17:55:06] 6Engineering-Community, 10MediaWiki-extensions-Newsletter, 3Google-Summer-of-Code-2015: Goal: Newsletter extension for MediaWiki - https://phabricator.wikimedia.org/T76199#1532136 (10NiharikaKohli) Great. @Tinaj1234, please write up a short description of the project when you get time for the blog. Also add... [18:05:05] 6Engineering-Community, 3ECT-August-2015: Email to Chapters List: ECT documentation, support and available resources - https://phabricator.wikimedia.org/T108647#1532155 (10Rfarrand) My idea was that maybe people from different wikimedia chapters would be interested in mentoring someone in a project. They might... [18:15:18] Krenair: which policy did I edit? [18:15:47] chasemp: I think the problem with all users can edit is that all users can change the policy [18:16:01] yeah [18:16:07] no separation as in the task case [18:16:09] which is sorta weird [18:16:18] I'm not sure why we should allow all users to edit projects [18:16:26] there isn't much in a project that needs editing, usually [18:16:53] oh this conversation happened a few times [18:17:08] afaik it's the drama of 'why is this locked down' [18:17:13] I have no real feelings on the matter [18:17:21] other than I think the default open is good [18:17:34] we need to tighten up the project outliers though [18:17:40] yeah but if default open allows anyone to change the policy ,.... [18:18:10] I agree default open is good in theory but edit implies edit policy almost always in phabricator [18:18:33] I have no objection to locking it down or leaving it be (though it adds work to clean things up) [18:18:38] just relaying prevoius outcomes [18:18:52] teh cost was determined worth teh risk ig uess [18:19:08] I really have no strong opinion either way [18:19:23] but we shouldn't allow anyone to edit policy and then be surprised or upset when they do [18:19:33] so true [18:19:35] My default preference for projects is "any member of the project can edit it" [18:19:55] ostriches: unfortunately there isn't a default like that [18:20:03] that would make too much sense ;) [18:20:05] * ostriches sets it on all projects he's in [18:20:35] I could randomize it [18:20:37] then no one is happy [18:21:00] take the king solomon approach that's my policy [18:21:06] lol [18:21:18] chasemp: you'd make a great king [18:22:19] https://www.youtube.com/watch?v=2SF1iLXSQto [18:22:22] I should !bash that [18:22:40] how about making a survey about that first [18:22:43] * mutante hides [18:23:05] ostriches, for that policy to be any use you also have to restrict joining [18:23:24] at which point you've made the project invite-only [18:23:37] No it doesn't. It just raises the barrier and makes drive-by vandalism less likely. [18:23:51] no biggie, if i want to invite my friend i just temp. change the policy [18:23:53] Any bad edits to projects I've seen have been on projects that had it editable by anyone [18:25:38] trust club is a valid method I think [18:27:36] can't we just lock down project policy editing to phab admins? [18:28:19] Or the project creators group, perhaps [18:28:25] Oh, policy editing [18:29:00] policy and general editing are not separate [18:29:01] in thsi case [18:30:06] https://phabricator.wikimedia.org/applications/view/PhabricatorManiphestApplication/ [18:30:18] "Can Edit Task Policies" is Custom Policy [18:30:30] but there's no such ability in https://phabricator.wikimedia.org/applications/view/PhabricatorProjectApplication/ [18:31:09] I have an upstream task somewhere about fixing "Custom Policy" to mean something [18:32:13] https://secure.phabricator.com/T6802 [18:32:41] I bet we could ask for the separation [18:32:44] I may have already I don't remember [18:33:02] editing policy should be a separate capability on all apps but it isn't, currently [18:33:14] would definitely make more sense to consistently support that [18:33:18] imop [18:33:20] imo [18:33:23] agreed [18:33:38] projects have metadata just like tasks that need updating [18:33:47] but it's separate from policy work in general [18:34:03] it would simplify all of this to just fix it [18:34:06] let's ask? [18:34:15] it would be fairly simple to write a patch for it I think [18:35:00] if they are receptive I might find time to make a patch...but it may be more involved than I am thinking it is [18:44:05] not terribly receptive ;) [18:44:33] epriestley asked us to describe the problem in maniphest [18:44:40] er in a task [19:41:31] 6Project-Creators, 6Team-Practices: Create #201516-Q1 project in phabricator - https://phabricator.wikimedia.org/T106752#1532451 (10ksmith) [20:02:35] 10Gitblit-Deprecate, 6Release-Engineering: Update mediawiki.org templates to link to Diffusion, not gitblit - https://phabricator.wikimedia.org/T108864#1532501 (10Spage) 3NEW [20:25:56] 6Phabricator, 6Team-Practices, 7Epic: [EPIC] Gather requirements from teams for Phab project management feature requests - https://phabricator.wikimedia.org/T105404#1532568 (10MBinder_WMF) After chatting in our "How to drive Phab" meeting, we decided that this should remain a wishlist, as opposed to umbrella... [20:58:44] 6Engineering-Community, 3ECT-August-2015: Email to Chapters List: ECT documentation, support and available resources - https://phabricator.wikimedia.org/T108647#1532670 (10Qgil) Like any email sent to a mailing list, we need to keep it short, and linking to the resources where the extended explanations are pro... [21:42:28] 6Phabricator, 5Release: Next Phabricator Upgrade: on 2015-08-19 - https://phabricator.wikimedia.org/T108142#1532836 (10mmodell) [21:43:22] 6Phabricator, 5Release: Next Phabricator Upgrade: on 2015-08-19 - https://phabricator.wikimedia.org/T108142#1513380 (10mmodell) Moving back to next week since there are currently no blocking tasks or other known issues with the current revision of phabricator. [21:45:44] 6Phabricator: Not all Phabricator tasks are crawled by search engines - https://phabricator.wikimedia.org/T76991#1532842 (10mmodell) But searching for [[ https://www.google.com/search?q=T842&ie=utf-8&oe=utf-8#q=phabricator+T842 | phabricator T842 ]] works for me [21:48:21] 6Phabricator, 6Team-Practices: Add support for task types - https://phabricator.wikimedia.org/T93499#1532857 (10mmodell) There really isn't any reason you couldn't do all of this with phabricator's custom field support. One custom field can be hidden or shown based on other fields. I'm not entirely sure how t... [21:56:19] https://phabricator.wikimedia.org/project/profile/57/ [21:56:28] Edit policy is a single user who has left [22:00:40] 6Phabricator: "Edit details" button on uneditable projects without workboards is enabled when on /tag/name - https://phabricator.wikimedia.org/T108881#1532894 (10Krenair) 3NEW