16:04:46 #startmeeting 16:04:46 Meeting started Wed Feb 4 16:04:46 2015 UTC. The chair is h01ger. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:04:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:05:11 #chairs MoC intrigeri 16:05:14 #chair MoC intrigeri 16:05:14 Current chairs: MoC h01ger intrigeri 16:05:15 ready too. 16:05:21 #topic agenda 16:05:29 so what topics do we have to discuss? 16:05:43 * h01ger is happy to chair but equally happy if someone else does... 16:06:35 I don't think I have much to put on the agenda. Except maybe: 16:06:54 next steps for the navigation reorg and then re-evaluating it. 16:07:24 MoC: ? 16:07:33 reading the plans for the next 2 weeks. 16:08:03 oh 16:08:12 i am here. 16:08:39 so what shall we discuss? 16:08:43 agenda++ plans for next weeks 16:08:44 i have some questions regarding the navigation 16:08:51 yay 16:09:04 so "wiki / navigation" is one topic.. 16:09:13 anything else? sounds like a short meeting 16:09:18 and about my quick triggered new profile bug mails 16:09:35 and next 2 weeks 16:10:04 shall we start with the navigation? 16:10:46 yep 16:10:52 #topic wiki navigation based on user stories 16:11:08 ok, so, intrigeri, thanks for your initial review, first of all 16:11:22 I can redo it whenever we feel it's the right time. 16:11:35 yes 16:11:46 you suggested that we delete the page PackageMaintainers 16:12:21 i have then indeed split up this page into MergeFromUpstream and ImportProfileFromExtra 16:12:44 but then I realized that i still have the Packaging with dh_apparmor part to put somewhere 16:12:53 replied over email already :) 16:13:00 (10 minutes ago, sorry) 16:13:14 oh let me read this quickly then 16:14:00 oh ok 16:14:01 * h01ger vaguely plans to test the pages to/when fixing tbl for wheezy-bpo but then i dont see me doing this anytime really soon 16:14:21 intrigeri: so, indeed we need to have a page for an initial packaging 16:14:34 how should i call that page? 16:14:39 seems useful indeed 16:14:46 I think that's the "Ship an existing AppArmor profile confining software S in the Debian package that ships S" user story 16:15:00 exactly 16:15:24 intrigeri: and right now i do not have a dedicated page for that one 16:15:27 Contribute/InitialProfileImport? Contribute/ImportExistingProfile? 16:16:45 I have Contribute/PackageMaintainers (which should be renamed i guess). what about Contribute/FirstTimeProfileImport or Contribute/FirstTimeProfilePackaging? 16:17:06 Contribute/ImportExistingProfile seems a bit too generic, i dunno 16:17:07 ACK Contribute/FirstTimeProfileImport 16:17:13 ok 16:17:52 * intrigeri has 11 wiki pages open. wow. hopefully I'm not missing some more. 16:17:59 arf :)))) 16:18:32 so, we would habe Contribute/FirstTimeProfileImport and a page called Contribute/ShipProfile? 16:18:37 or not? 16:18:50 what would the latter say? 16:18:51 not necessary maybe.. i can link to everything from Contribute 16:19:04 not sure what user story ShipProfile would be about. 16:19:21 ok, yes, i am simply confused about this part, nevermind 16:19:39 then, you answered my question about this part 16:19:42 cool 16:19:45 next thing: https://wiki.debian.org/AppArmor/Contribute/ImportProfileFromExtra 16:19:55 what is the strategy to adopt here? 16:20:03 I say postpone that to the latest weeks. 16:20:10 #agreed move PackageMaintainers to Contribute/FirstTimeProfileImport 16:20:12 and, there's good doc about this on the Ubuntu wiki iirc. 16:20:34 maybe we can simply point to it. 16:20:54 intrigeri: i thought that this page is about taking a profile from the Debian package apparmor-profiles-extra to my own package? 16:21:05 yes. 16:21:06 or should this be coordinated with Ubuntu then? 16:21:12 * h01ger really prefers to have consistent documentation in one place then pointing elsewhere. obviously this has limits, but as a general rule... 16:21:22 hmmm. well, Ubuntu has no -extra package. 16:21:29 correct 16:21:29 ubuntu also might ship a new version tomorrow 16:21:46 s/then/than/ 16:22:07 intrigeri: i'll try to read the Ubuntu documentation then and we can postpone this discussion 16:22:12 OK. at least it'll be a good source of inspiration, it deals with conffiles moving around and all. 16:22:22 agreed 16:22:26 #agreed postpone content discussion of https://wiki.debian.org/AppArmor/Contribute/ImportProfileFromExtra 16:22:29 #save 16:22:41 next topic then? 16:22:53 yep. 16:22:54 #topic follow-up on new-profile tagged bugs 16:23:02 so, i've now seen that you answered my email 16:23:03 congrats for following-up 16:23:08 thanks :) 16:23:08 * h01ger nods intrigeri 16:23:12 :) 16:23:21 but i should have made you read the follow up first i think 16:23:30 there are always some people who prefer unusual things 16:23:33 well, no big deal. 16:23:34 that's fine. 16:23:52 ok 16:24:04 MoC: I'm actually glad that you felt at ease doing it without asking us first. 16:24:13 MoC: IMO that's part of the "moving from mentoring to team work" process. 16:24:18 hehe :) 16:24:19 yay 16:24:23 intrigeri: great 16:24:29 true indeed 16:24:36 but i think i should resend it to -submitter@b.d.o 16:24:41 at least once 16:24:46 bounce? 16:24:49 +1 16:24:54 h01ger: what does that mean? 16:25:21 #agreed MoC should resend the new-profile follow up email to the actualy bug submitter 16:25:21 re-sending the mail but bcc:ing the new addressant 16:25:34 instead of changing to:+cc: headers 16:26:16 something i've only learned to do after almost 20y of using email 16:26:19 well, i wont resend it to the bts again anyway, right? 16:26:37 bounce = only bcc? 16:26:40 :) 16:26:42 the replies will go to the bug, if the person just presses reply 16:26:47 oh 16:26:50 no need to change headers 16:27:08 i should read the doc about this or ask you again later then 16:27:40 in my MUA its a special way for forwarding... feel free to ask later :) 16:27:43 more to say on this topic? 16:27:48 shall i'll send you the email over the mailing list first before sending it? 16:28:01 sure, why not 16:28:05 over the ml? 16:28:42 #agreed MoC should ask h01ger later about email bounces so the submitters reply will still go the the BTS 16:29:04 then we can rediscuss the contents of the email i guess 16:29:09 sure, why not. i'd also trust you to send good mails without though.. 16:29:27 but i'm happy to review if you prefer thi 16:29:28 s 16:29:40 well, i should have explained better why / who i am to send this email and things like this 16:29:43 which i did not 16:29:56 but, thanks btw for your encouragements about making mistakes :) 16:30:04 next topic ? 16:30:11 not needed imo 16:30:11 especially given my current latency.. 16:30:16 intrigeri: ok 16:30:21 MoC: please make more new mistakes! :-) 16:30:25 :) 16:30:42 intrigeri: i can check that with h01ger, too 16:30:47 hmm 16:30:50 wrt. the navigation thing 16:30:53 yes? 16:31:05 I'd like to know if/when I should schedule time for re-doing a full pass on the user stories / navigation 16:31:11 during the next two weeks, or later? 16:31:18 intrigeri: in about a week 16:31:20 #topic next two weeks 16:31:25 OK 16:31:28 :D 16:31:42 ok, so i already updated the todo list a bit earlier 16:32:01 i will finish the navigation, ask you for review again, then move to the udd query 16:32:02 what else for the next two weeks? (besides next meeting, which shall be the final topic :) 16:32:18 #info < MoC> i will finish the navigation, ask you for review again, then move to the udd query 16:33:18 then i have import my upstream bugfixes on pidgin-prefs to the apparmor-profiles-extra package through Git 16:33:18 scheduled that navigation pass. 16:33:38 good priorities order imo. 16:33:59 * h01ger nods 16:33:59 imo top prios indeed are navigation and usertags notifications. 16:34:10 #info < MoC> then i have import my upstream bugfixes on pidgin-prefs to the apparmor-profiles-extra package through Git 16:34:11 the pidgin profile thing can wait 16:34:18 the migrate profile doc too 16:34:27 the bzr branch thing can wait too 16:34:30 i rescheduled the migrate profile doc 16:34:43 and will reschedule the 2 other things too then 16:34:57 cool 16:35:20 * h01ger things thats nothing for # info but YMMV 16:35:26 thinks.. 16:35:37 I've nothing to add on this topic. 16:35:39 i'll ask questions about the navigation in the wiki when i'm done with the pages 16:35:46 and nothing to add to the topic either 16:36:03 next topic = next meeting? 16:36:10 yup 16:36:15 ok 16:36:17 #topic any other business 16:36:22 or that :) 16:36:27 OK 16:36:30 but if we have nothing... 16:36:31 I've none. 16:36:42 none 16:36:45 #topic next meeting 16:37:20 what about the 15th,17th, 18th for the next meeting? 16:37:22 Feb 17-19 work for me. 16:37:23 today in two weeks is suboptimal, but absolutly doable. tuesday would be a tiny bit better, so is thursday 16:37:40 i have a preference for after the 17th 16:37:47 go for the 17th 16:37:57 wednesday the 19th then? 16:38:14 i was about to suggest the 18th :p 16:38:19 haha. 16:38:32 can we roll a dice? 16:38:33 works for me 16:38:45 17, 18, 19 work for me. 16:38:47 18th, 18oo CET? 16:38:55 18th, 18h CET is good 16:39:12 17CET? 16:39:17 ok 16:39:20 18 is fine, 17 is better for me. 16:39:42 I mean 17cet is better for me. 16:39:47 oh ok :D 16:39:56 h01ger: what about you? 16:39:58 h01ger: ok? 16:40:05 #agreed next meeting 18th february, 1600 UTC 16:40:11 #save 16:40:16 yay 16:40:19 cool 16:40:23 cheers! 16:40:26 then we're done? 16:40:27 that's all, right? 16:40:30 that was quick! thanks! 16:40:33 +take care! :) 16:40:34 #endmeeting