20:05:23 #startmeeting 20:05:23 Meeting started Tue Sep 2 20:05:23 2014 UTC. The chair is TheSnide. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:05:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 20:06:39 Nothing much happened these days. 20:07:32 That's not true ;) 20:07:41 The gallery is finished :) 20:07:59 oh. yes. :) 20:08:12 did you managed to launch it on contrib.git ? 20:08:22 When will you setup vhost on project server? 20:08:46 ssm: < dipohl:#munin> When will you setup vhost on project server? <-- for gallery 20:10:55 TheSnide: scripts are ready for git.munin 20:11:11 I have not started work for git.contrib 20:11:50 ok 20:12:33 dipohl: actually http://gallery.munin-monitoring.org works 20:13:08 ah, nice >:) 20:13:19 but this is not the last version 20:13:38 please fetch last version from git 20:17:27 TheSnide: Concerning the "updates" category for the pending updates plugins. How about a new category "security" ? 20:19:16 dipohl: actually, i don't have access to that account :-/ 20:19:46 dipohl: so, i still need that ssm adds me to the list i can sudo to. 20:19:46 ssm is responsible? 20:20:16 dipohl: yes. he said he'll be busy these days, so he might be slow to answer. 20:20:47 #action ssm should add TheSnide to the list of sudo users for an update of the gallery plugins 20:21:00 #action ssm should add TheSnide to the list of sudo users for an update of the gallery plugins 20:21:48 TheSnide: Is the chair the only one who can give commands to the meetbot? 20:22:22 and I made an error in last #action 20:22:31 #undo 20:22:31 Removing item from minutes: 20:22:33 not gallery plugins but gallery _scripts_ 20:22:41 yes, only chaif AFAIK 20:22:46 chair 20:23:40 #action ssm should add TheSnide to the list of sudo users so that he can update the gallery scripts to recent version 20:24:50 TheSnide: Do you agree to the new category "security" and my proposal to move the plugins "yum", "apt" a.s.o. thereto? 20:26:03 #action ssm should add TheSnide to the list of sudo users so that he can update the gallery scripts to recent version 20:26:13 ok for security 20:26:22 it feels better than "update" 20:26:36 fine :) 20:26:55 --> less generic 20:27:12 but more generic than "yum" :) 20:27:15 yup 20:27:44 What went wrong with the build today? 20:27:53 trac ci hiccup 20:28:24 1 build did fail, due to failure in buildvm 20:28:36 i relaunched it and it passed. 20:28:37 I checked the commit that you merged, but found no reason 20:28:44 i c 20:28:53 happens sometimes. 20:29:06 it happens much less than before. 20:29:55 do we have a check of POD contents, because I saw something that looks like this? 20:30:15 in the build protocol 20:30:27 oh 20:30:53 i think we launch the pod2man building 20:32:18 "t/critic.t ................. skipped: set TEST_POD to enable this test" 20:32:34 is it disabled always? 20:32:50 no, there is a switch to enable it 20:33:09 "t/no-fixes.t ............... skipped: set TEST_POD to enable this test" 20:33:11 but i admit that i don't know 20:33:23 export TEST_POD=1 ? 20:33:26 "t/pod-spelling.t ........... skipped: set TEST_POD_SPELLING to enable this test" 20:33:46 it would be good to check the POD, because we have a lot of files with charset errors 20:38:05 Here the collection of broken POD pages: http://pastebin.com/EffxL0v4 20:39:45 #action The following plugins have POD pages with errors, likely because they need to be converted to utf8: http://pastebin.com/EffxL0v4 20:41:26 TheSnide: are you still here in the meeting? 20:56:29 .. 21:04:07 TheSnide: I started the scripts for contrib.git now and the first numbers are 21:04:29 269 times POD page created 21:04:50 727 times no POD content found 21:06:05 245 categories found 21:07:44 so only every fourth referenced plugin portrait page will have content :( 21:08:09 ah every third page 21:09:25 I don't think that we will get a lot of acceptance from the user then unless we set a high-light / marker to plugin pages with content.. 21:19:58 .. 21:20:18 dipohl: sorry, was away 21:21:11 I have one important issue 21:21:29 dipohl: we need to have a way to offer some content even if no POD is found 21:21:40 It looks like the plugins in the /core-tree/ are not of high quality in every case 21:21:50 maybe via comment parsing, the one that shows the env vars 21:22:02 I vote for a review in this tree also 21:22:23 and exclude / move old / less quality plugins to contrib tree 21:22:44 we cant move plugins from core to contrib. 21:23:00 The plugins we distribute should meet a minimal standard 21:23:20 better raise their level, than leave then out 21:23:27 i know. but still. 21:23:59 I am sure there are plugins that nobody uses 21:24:30 will you continue to deliver those? 21:26:28 * Bushmills@freenode is probably the person with those plugins nobody uses 21:27:38 e.g. https://github.com/munin-monitoring/munin/tree/devel/plugins/node.d.hp-ux 21:27:47 the measureware plugins 21:28:05 the author himself says they are "quick'n dirty" 21:28:11 no description 21:28:45 no autoconf capability 21:29:51 I would say we need a rating tool for the plugins 21:31:32 Bushmills: can you tell some examples? 21:32:11 lo-qual or medium-qual example? 21:32:18 lo-qual 21:32:25 let me check ... 21:34:51 hmm, 21:35:20 might work out 21:35:39 have to go, will think more about i- 21:35:41 it 21:35:52 ok. see you next week then :) 21:36:13 shall we make an entry to meetbot about this issue? 21:36:26 "plugin review" in core collection 21:36:31 #action TheSnide will see how to increase signal to noise ratio of our plugins 21:36:43 yup 21:36:54 #endmeeting