[11:44:32] qgil, thanks [11:44:45] :) [11:46:32] qgil: Guten Tag :-D [11:46:53] Bonjour le matin (well, not quite le matin anymore) [11:47:03] unsurprisingly I have a Phabricator question for you. I was wondering whether a project could have sub-projects with their own wall of cards [11:47:34] to welcome someone in the afternoon we would just say "bonjour" ('good day') [11:47:58] and if we say bye someone during the afternoon we might just say "bonne après-midi" ( 'good afternoon' ) [11:48:07] as of today, "subprojects" can and will have their own workboards... [11:48:08] but [11:48:09] but we never good afternoon to welcome someone. French is scary [11:48:47] the problem is that they are not really subprojects, but projects with "a similar name" or something. Meaning: they are not connected in a relationship [11:49:03] My Phabricator use case would be to have a super project "Continuous Integration" that would itself have sub projects such as "Maintenance" "Isolating boxes" etc [11:49:34] in practice, as of today this means that you have all these projects, and then you can assign tasks to one or more at the same time. No "sub". [11:50:14] so I would end up with several projects [11:50:30] and eventually can fake a parent / umbrella project by making sure all tasks are also in the super project? [11:50:37] We have this setup (and this problem) with the Phabricator projects ourselves [11:51:28] We started doing this, but at the end we avoided duplication because it was not very practical [11:51:43] I can imagine [11:51:47] what we have now is a Phabricator project that acts a default umbrella: https://phabricator.wikimedia.org/tag/phabricator/ [11:51:57] so I guess in my main project, I would fill in a task that reference another project [11:52:27] then specific tasks that can fit to projects like bugzilla-migration or code-review, are moved there [11:52:28] or to say it otherwise, my parent project would only have tasks tracking other projects status [11:52:47] yes, this is what we are kind of doing (still improvising) [11:53:47] "Launch Wikimedia Phabricator Day 1" https://phabricator.wikimedia.org/T174 is in three different projects, because in order to complete this task we need to complete the three projects [11:53:55] would you say that the PHabricator project is a the default entry point for new tasks which are then triaged ? [11:53:55] It's not perfect, but kind of works [11:54:38] as long as it is not too complicated / cumbersome it works for me :] [11:54:49] last Q: when the hell can I migrate!??!! BBQ :-]]]]]]] [11:55:25] fun apart, I am under the impression the whole project has been properly managed since the start. So kudos to everyone involved [11:55:29] I think for your case what we have now will work well [11:55:53] it is more annoying for sprints, having to create new projects with the same settings every week or so [11:55:55] yeah but I will need folks to be able to comment on tasks eventually. So I better wait for the official opening of user registrations [11:56:21] for spring, folks can still prefix the task title with the sprint number [11:56:24] Sprint 5: do stuff [11:56:39] which make it obvious on the project wall of card [11:57:48] hashar, relevant: https://phabricator.wikimedia.org/T100 [11:57:52] (and dense) [11:58:17] Ideally, we would prefer to open the gate of creation of new projects AFTER the Bugzilla migration... [11:58:39] There is so much to do and to pay attention right now, and so much pressure to get it out [11:59:53] understandable :] [12:00:16] anyway, bon jour ou bon après-midi, mais je n'ai pais mengez encore (that is my Catalan badly dressed as French) [12:00:33] maintenant [12:00:34] that is accurate :] [12:00:38] bon appétit! [12:00:39] :) [22:17:28] what the mother.... 70 messages from phab :) [22:25:53] <^d> real all the messages. [22:25:58] <^d> *read [22:26:01] <^d> dammit, snark ruined. [22:28:20] are they about activating mail from phab?:) [22:31:51] greg-g: you won the metadata lottery [22:31:59] all your tickets should be fixed up...ish [22:36:36] chasemp: :) [22:37:09] turns out you do stuff and have a lot of them [22:37:14] who knew....;) [22:51:23] :P [22:55:26] twentyafterfour: did you get a chance to test the oauth provider with tagging in a branch? [22:59:45] chasemp: no but I can have that done in a few minutes [23:05:16] if you want to update to HEAD and then do that in a branch and tag it w/ whatever that issue is [23:05:31] (assuming checkout/tag works w/ that) [23:05:52] dude landed the herald rule ordering so I want to update anyway [23:07:50] you have to tag all 3 repo's w/ the same tag [23:07:54] they are track together, fyi [23:19:56] <^d> twentyafterfour: I got the password reset for that list. I'll take care of the noreply@phab thing tomorrow for you. [23:20:31] password reset? [23:27:09] chase: I'm tagging the newest upstream versions, will push my tags shortly [23:27:18] k [23:27:32] w/ auth in a branch? [23:35:12] <^d> twentyafterfour: I responded to your e-mail earlier today. I had forgotten the pw to wikibugs-l :p [23:44:28] chasemp: yes [23:44:42] I just pushed an tag called wmoauth to phabricator and libphutil [23:44:46] thinking on it....not sure git::install works w/ a branch [23:44:57] it's not a branch it's a tag [23:45:26] you cherry picked those into master and rebased in upstream? [23:46:05] no I did arc patch and rebased that onto master, then tagged it [23:46:17] arc patch is like a cherry pick from differential [23:47:59] it should be the same thing as upstream/master with the oauth stuff cherry-picked at the tip of the branch [23:48:52] if git-install handles tags it shouldn't care about branches ... tags are distinct and independant from branches [23:51:08] well...what happens if you try to checkout a tag that doesn't exist in the local repo? [23:51:24] as in the revision in a branch only on remote [23:51:30] but immaterial if you are putting it all in master