15:01:45 #startmeeting modularity_wg 15:01:45 Meeting started Tue Feb 21 15:01:45 2017 UTC. The chair is nils. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:45 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:45 The meeting name has been set to 'modularity_wg' 15:01:45 #meetingtopic Bi-weekly Meeting of the Modularity Working Group 15:01:45 #chair dgilmore langdon mikedep333_ tflink 15:01:45 Current chairs: dgilmore langdon mikedep333_ nils tflink 15:01:57 #topic Roll Call 15:02:02 .hello nphilipp 15:02:03 nils: nphilipp 'Nils Philippsen' 15:03:02 .hello jkurik 15:03:03 jkurik: jkurik 'Jan Kurik' 15:03:17 .hello asamalik 15:03:20 asamalik: asamalik 'Adam Samalik' 15:03:21 * asamalik will be here in 3 minutes 15:03:28 .hello tflink 15:03:30 tflink: tflink 'Tim Flink' 15:03:56 hi all 15:04:16 can we please call the meeting fortnightly 15:04:25 bi-weekly is such a weird odd term 15:04:37 .hello langdon 15:04:38 langdon: langdon 'Langdon White' 15:04:44 dgilmore: wanna put that on the agenda :o) /jk 15:05:07 I just want a fort to have my meetings in 15:05:12 haha 15:05:21 * langdon not j/k 15:05:28 ;) 15:05:47 anyway, I guess we're all here now 15:06:02 #topic Agenda 15:06:03 #info website has been published! (mostly announcement, maybe feedback?) (asamalik) 15:06:13 anything that needs to be added? 15:06:46 * asamalik is here 15:06:47 Boltron doc soon 15:07:09 Like the one for flock 15:07:13 shall we discuss fortnight vs. bi-weekly in open floor? 15:07:20 But will find link in a few 15:07:22 :) 15:08:11 Ok I don't see anything being added to the agenda... 15:08:23 #topic website has been published! (mostly announcement, maybe feedback?) 15:08:26 #chair asamalik 15:08:26 Current chairs: asamalik dgilmore langdon mikedep333_ nils tflink 15:08:29 Nils ^^^ 15:08:45 mkay 15:08:47 #undo 15:08:47 Removing item from minutes: 15:09:01 #info Boltron doc soon 15:09:13 #topic website has been published! (mostly announcement, maybe feedback?) 15:09:16 nils: may I ask you please to add the voting: https://pagure.io/modularity/tickets/issue/1 ? 15:09:31 okay 15:09:35 #undo 15:09:35 Removing item from minutes: 15:09:55 #info Voting permission for people present on Modularity WG meetings 15:10:02 but now for reals 15:10:05 #topic website has been published! (mostly announcement, maybe feedback?) 15:10:06 ha 15:10:16 #link https://docs.pagure.org/modularity We have published the new documentation website! 15:10:17 asamalik: take it away 15:10:51 and it was all done by hand because I'm still working on integration, huzzah! 15:11:02 and every wiki page has been deleted - or rather the content has been replaced with a banner saying "we have moved here: link" 15:11:47 #info To edit the documentation, just click the Edit button which is on every page - it will take you to the source repo, and send a PR with your changes there. 15:12:32 any questions, comments? :) 15:12:57 asamalik, i have one but it should wait till a different agenda item 15:13:24 i will add that i think the video shold be more "above the fold" 15:13:34 and i think we need a comm blog post about it 15:13:46 agree 15:13:58 nils: I guess that's all for my topic 15:14:01 okay 15:14:10 asamalik, can we shorten the header? 15:14:18 and make less "blue space" .. to pull the video up 15:14:32 langdon: we can do anything! ;) 15:14:35 everything 15:14:35 ha 15:14:36 whatever 15:14:56 should we add #actions? 15:15:15 ill just file issues! 15:15:20 haha 15:15:22 langdon: I guess that i we make the video more "above the fold" it will make sense to pull it up 15:15:45 langdon: just file issues! 15:15:45 speaking of issues.. a link to the issues would be nice ;) 15:16:15 * langdon notes none of his issues have been resolved yet :/ 15:16:27 langdon: haha click the edit button on every page - but yes, good point - can you please create an issue that you don't know where to put issues? 15:17:05 #link https://pagure.io/modularity/issues Issue tracker for the Modularity documentation website. 15:17:43 alright, that should be it for websites I think :) 15:17:55 nils: yeah :) 15:18:08 #topic Boltron doc soon 15:18:12 langdon? 15:18:17 #chair sct 15:18:17 Current chairs: asamalik dgilmore langdon mikedep333_ nils sct tflink 15:18:25 * langdon is busy filing issues! 15:18:32 ok.. quickly... 15:18:44 by the next meeting we should have https://fedoraproject.org/wiki/Modularity_Working_Group/releases/Flock_2016_Release 15:18:47 for boltron 15:19:09 does anyone have any comments/thoughts/requirements on that doc? 15:20:10 ok.. if you do, file a ticket! but at https://pagure.io/modularity/tickets/issues 15:20:11 :) 15:20:20 we can move on if you like 15:20:34 we may have a preview by the office hours next week 15:20:42 langdon: It's very developer-centric 15:21:07 describes deliverables and talks about fedora contributors, 15:21:10 probably true 15:21:30 one of the items is to build a quick start guide for boltron though 15:21:35 should "outcomes" be there? 15:21:38 I was wondering if it would be appropriate to include some general usability testing in the planning too. 15:21:42 or do you think we need more in the "requirements" side 15:21:47 It's not exactly a deliverable 15:21:58 but it's still a chunk of work for the group to plan 15:22:05 oh.. i think i have that 15:22:19 like some docs re: how to use it + how to provide feedback 15:22:31 Right 15:22:35 is that what you mean? or more like "use cases that boltron should meet"? 15:22:42 but also something like perhaps a test day 15:22:49 ahh thats a good idea 15:22:53 i didn't think of that 15:24:14 ok.. sct will file an issue! :) 15:24:17 next topic? 15:24:21 Will do. :) 15:24:32 ok 15:24:40 #topic Voting permission for people present on Modularity WG meetings 15:24:44 #chair jkurik 15:24:44 Current chairs: asamalik dgilmore jkurik langdon mikedep333_ nils sct tflink 15:24:48 proposed #info with the lazy concensus applied we now have approved to vote on meetings with the people who are present, even these are not "Voting members" as stated in https://fedoraproject.org/wiki/Modularity_Working_Group 15:25:10 any comment on this ? 15:25:14 * nils adds an "if" 15:25:21 "even if these" 15:25:32 i didn't realize i hadn't voted 15:26:03 langdon: https://pagure.io/modularity/tickets/issue/1 15:26:14 jkurik, yeah.. done already 15:26:35 dgilmore, can you vote? 15:27:05 jkurik, i read your comment as "these people have voted in the meeting" vs a "tag, please review" 15:27:16 sct, you too 15:27:25 sct, ha.. just saw yours 15:27:27 langdon: Yep, just did 15:28:34 langdon: sorry was distracted 15:28:37 on what? 15:28:48 dgilmore: https://pagure.io/modularity/tickets/issue/1 15:29:12 sure 15:29:13 and that should be quorum, i think 15:29:30 can not say I had seen that before :( 15:29:37 asamalik, speaking of tickets, do you think the publishing one is now resolved? 15:30:25 langdon: it's been published, so yes :) 15:31:02 * langdon doesn't know how to close an issue :/ 15:31:21 langdon: yes, I do 15:31:34 what issue do you want to close ? :) 15:31:58 jkurik, i think i got it #2 15:32:04 go to the metadata and change the status to closed 15:32:18 jkurik, yeha.. i was expecting a "resolve button" 15:32:36 dgilmore, you good with that ticket? 15:33:19 langdon: thats what my sure was earlier 15:33:26 +! 15:33:28 +1 15:33:31 is that better? 15:33:35 ha 15:33:41 i thought you would put it in the ticket :) 15:34:03 can do 15:34:33 ok.. next topic? are there more? 15:34:48 proposed #agreed with the lazy concensus applied we now have approved to vote on meetings with the people who are present, even if these are not "Voting members" as stated in https://fedoraproject.org/wiki/Modularity_Working_Group 15:34:58 ^^this 15:35:20 jkurik, ticket is updated as well 15:35:27 and +1 to your agreed 15:35:32 ok, thanks 15:35:33 #agreed with the lazy concensus applied we now have approved to vote on meetings with the people who are present, even if these are not "Voting members" as stated in https://fedoraproject.org/wiki/Modularity_Working_Group 15:35:34 +1 15:35:39 cool 15:35:48 nils: you can move on, thanks :) 15:35:52 that leaves us... 15:36:00 #topic Open Floor 15:36:16 So, dgilmore doesn't like "bi-weekly". Anybody else weigh in? 15:36:19 :D 15:36:31 bi-monthly! 15:36:46 Haha 15:37:00 The agenda would get awfully long then, wouldn't it? 15:37:02 paycheck driven? 15:37:17 whatever that means ;) 15:37:21 bi-monthly is like bi-weekly.. it means both twice a month and every two months 15:37:36 in the US paychecks are often distributed fortnightly 15:37:49 I mean, I'm all for calling it "fortnightly" if that's more specific. 15:38:01 Or even just "nicer". 15:38:02 langdon: we got this beautiful word "forthrightly" in Europe ;) 15:38:21 asamalik, we use that too.. but only to indicate rude people ;) 15:38:28 langdon: haha 15:38:30 Don't be so forthright. 15:38:44 fortnightly is just uncommon here.. but most people know it.. if they dig in their brains 15:38:55 Which is not a bad thing. 15:38:56 it is significantly less confusing 15:39:16 In that case, let's change it. I hear nobody objecting anyway. 15:39:19 jkurik, are you gonna close #1 ? 15:39:32 where is this "change"? fedocal or something? 15:39:35 langdon: yes, once I will get meeting minutes from this meeting 15:39:42 jkurik, ack.. no worries 15:40:18 proposed #agreed call the meeting "forthnightly" instead of "bi-weekly" to be less confusing 15:40:43 isn't it fortnightly? 15:40:48 yes it is 15:40:50 nils: fortnightly 15:40:51 I will object to the change. IMO bi-weekly is more descriptive what it means 15:40:59 no h in it 15:41:10 jkurik: for real? 15:41:13 dgilmore: yeah, got confused by the convo about forthrightly 15:41:19 dgilmore: sure 15:41:28 jkurik: bi-monthly is like bi-weekly.. it means both twice a month and every two months 15:41:32 jkurik, problem is.. in the US it means both "once every two weeks" *and* "twice in one week" 15:41:52 jkurik: I realy despise the word bi-weekly. to me it an an american arogant statement that I find offensive 15:42:02 can we change the language then ? 15:42:07 fortnightly is much nicer, global and clearer 15:42:19 I'll call it zweiwöchentlich then, gotcha. 15:42:27 nils: +1 15:42:28 dgilmore, LOL.. tell us how you really feel! 15:42:39 langdon: will do 15:42:39 what if we say "once every two weeks"? :-) 15:42:45 you know i always hold back 15:42:55 asamalik: doesn't roll of the tongue that well 15:43:06 asamalik, how about once every 336h? 15:43:31 How about we keep mum about it? 15:43:35 "Regular meeting" 15:43:49 Look in the calendar, if you're so inclined ;). 15:43:55 langdon: or halfce every 168h :P 15:44:16 anyway 15:44:18 asamalik: My brain is starting to hurt and I'm making you responsible. :P 15:44:20 i would make it written out.. "once every two weeks" personally.. its not like we are paying by byte 15:44:26 yeah 15:44:27 I did not mean to send us off in the woods 15:44:43 we're already there, look at the trees! :D 15:44:46 I can live with langdon's proposal 15:45:05 technically, asamalik's 15:45:09 Alright, I'll update the pirate pad then. 15:45:15 * tflink doesn't care much either way :) 15:46:03 which makes the meeting topic "Meeting of the Modularity Working Group (once every two weeks)" in the future. Good? 15:47:12 proposed #action jkurik to update Fedocal for this meeting, replacing "bi-weekly" with "once every two weeks" 15:47:19 +1 15:47:21 +1 15:47:23 +1 15:47:27 #action jkurik to update Fedocal for this meeting, replacing "bi-weekly" with "once every two weeks" 15:48:24 okay, piratepad template is updated, too 15:48:38 anything else for open floor? 15:48:56 proposed #endmeeting :) 15:49:02 +1 15:49:12 no other words we want to beat to death? 15:49:20 +1 15:49:24 i just used "bug" and had to provide the newspaper definition 15:49:27 langdon: How about "unbeknownst"? 15:49:30 tflink, that was to me, right? 15:49:34 :) 15:50:02 antidisestablishmentarianism? 15:50:03 langdon: multitasking poorly, that was with the word mongering around weeks 15:50:10 ha 15:50:16 langdon: that sounds like it's hard on the stomach 15:50:25 ok.. im +1 on closing the meeting too 15:50:29 good 15:50:34 thanks everybody! 15:50:37 #endmeeting