14:02:00 #startmeeting Rally 14:02:03 Meeting started Mon Oct 5 14:02:00 2015 UTC and is due to finish in 60 minutes. The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:08 The meeting name has been set to 'rally' 14:02:33 ping andreykurilin oanufriev 14:02:45 hey hey 14:03:17 hi 14:03:46 o| 14:03:50 e0ne: rvasilets hi 14:03:54 Hi all 14:03:57 temujin_: hi 14:04:24 seems like this meeting will be quite short 14:04:44 #topic [boris-42] Bug reports housekeeping 14:04:54 okay guys we need to do something with bugs 14:05:15 we have like 72 bugs https://bugs.launchpad.net/rally -3 that are fixed is like 69 14:05:18 which is bad 14:05:54 part of bugs are forever in-progress status 14:06:16 so I believe we should detect those and finish patches 14:06:30 so we will reduce size of patch queue and amount of bugs in project 14:06:45 +1 14:07:17 +1 14:07:51 so the another thing that I did was 14:07:56 We could ask every 2 weeks about status of bug for example 14:08:01 refactoring all bugs 14:08:11 so they have now tags 14:08:22 and you can pick bugs from area that you know better 14:08:39 cool 14:08:51 rvasilets: we may but it will be better just to fix them ;0 14:08:59 rvasilets: and keep like less then 30 open bugs 14:09:40 ok 14:10:30 so that is all from my side 14:11:19 let's finish meeting if there is no more questions for few minutes 14:11:36 Who would be manage bugs? 14:12:02 rvasilets: I will ask ilyakhudoshin 14:12:42 Lets imagine that community filled 40 bugs in a week what is our action on this? 14:13:24 We will fix bugs immediately or by situation? 14:14:18 sorry i late 14:14:19 rvasilets: we will try to fix asap bugs 14:14:34 did you decided where to store rally config and database by default? 14:14:36 redixin: for other side it doesn't look like real situation 14:14:47 rvasilets: we should triage bugs asap 14:14:58 rvasilets: and fix them based on it's priority 14:15:12 redixin: so sqlite does work with many wirtters 14:15:16 redixin: so we did just 777 14:15:26 redixin: which will work for everybody 14:15:27 go+w it is the same as 777 14:15:47 redixin: hm 14:15:55 so your patch does not change much 14:16:00 redixin: hm 14:16:05 redixin: let me check 14:16:13 it is not actually same, but almost same 14:16:24 there is write permissons to everyone 14:16:32 redixin: so this is what we need 14:16:38 redixin: write permission for everybody 14:16:52 go+w gives write to everyody 14:17:12 777 just add executable by everybody 14:17:57 no. I don't think so because 'go+w' not equal to 'a+w' and 777 it like 'a+rwx' 14:18:22 with go+w we got 'rwxrw-rw-' 14:18:34 with 777 we got 'rwxrwxrwx' 14:18:35 redixin: rvasilets so the truth is that with 777 install_rally.sh works 14:18:41 redixin: with go+w doens't work 14:18:54 this is weird 14:18:59 because it was like 664 access 14:19:04 what does 'x' bit for sqlite file? 14:19:15 you forgot about 'u' 14:19:23 its about the owner of the file 14:19:24 redixin: so guests were able to read only 14:19:30 777 include it 14:19:33 go+w no 14:19:38 I think so 14:20:02 and also matybe some issues with reading 14:20:07 *maybe 14:20:46 http://dpaste.com/1Q73RBY 14:21:08 redixin: so I don't know LOL 14:21:44 probably sqlite uses x bit somehow 14:22:10 redixin: you can spend some time and investigate it 14:22:25 ok 14:23:38 redixin: in any case guys from community dislike the idea of putting db file to home dir in case of sys wide inslattaion 14:23:46 rvasilets, there is 'rw' permissons for user by default (man umask) 14:25:57 redixin, ok 14:26:32 so as we finished all topics 14:26:47 let's finish meeting 14:27:04 #endmeeting