11:57:10 #startmeeting OSEM Milestone 1 planning 11:57:10 Meeting started Mon Jul 28 11:57:10 2014 UTC. The chair is KalabiYau. Information about MeetBot at http://wiki.debian.org/MeetBot. 11:57:10 Useful Commands: #action #agreed #help #info #idea #link #topic. 11:57:18 #chair KalabiYau 11:57:18 Current chairs: KalabiYau 11:57:28 #chair KalabiYau differentreality gopesh henne 11:57:28 Current chairs: KalabiYau differentreality gopesh henne 11:57:47 #topic Decide with deadline for Milestone 1 11:58:47 seems we need to explicitly set a deadline for first test milestone. Henne got a proper vision how to structure work, so it can be observable via waffle and GH, but we need to plan our milestone more closely. 11:59:15 my suggestion is to make first milestone 2 weeks from today 11:59:28 that way it is not so far away, not so close 11:59:34 sounds reasonable 12:00:01 then it is 12:00:03 2 weeks 12:00:28 catching! 12:00:44 11 aug it will be a reflection meeting with next planning 12:01:00 #info 11 aug it will be a reflection meeting with next planning and end of Milestone 1 and start of Milestone 2 12:01:14 we need names! 12:01:18 milestone names 12:01:23 otherwise this isn't fun! 12:01:28 i would go for periodic elements :) 12:01:36 first one is Hydrogen and so on :) 12:01:36 I would go for Freestyle 12:01:50 no strong feelings here, let it be 12:02:18 updated 12:02:31 now 11 Aug, codename Freestyle 12:02:46 he you misunderstood ;) 12:02:52 henne ;) 12:03:06 I would go for naming Milestones in free style 12:03:18 for example? 12:03:33 Quacamole 12:04:00 it is fine with me 12:04:02 https://github.com/openSUSE/osem/issues?milestone=1&state=open 12:04:12 gopesh, differentreality you guys can now look at this? 12:04:32 differentreality, do you think what is listed is deliverable by you personally until 11th? 12:04:52 gopesh, would be great to see your tasks which you think you can deliver until 11 12:05:18 this includes Epics and what not 12:05:47 i think epic - as a big task should not be a part of milestone 12:06:03 * henne neither 12:06:14 as it is like a big holder for everything and smaller tasks which popped up from it - they are part of Milestone 12:06:23 I love Quacamole as a name :D (and food too) 12:06:56 speaking of food, tried gyros for the first time recently, was cool :) 12:07:11 so next name i would reserve to Gyros :) 12:07:24 anyway, differentreality what would you say about the link and tasks? 12:07:35 heh, but you *have to* try it in Greece. It's different... 12:07:39 * henne loves Gyros Pita 12:07:57 yes I can do the tasks. Besides Roles/Authorization is the second part of my GSOC, it has to be done in 2 weeks anyway :) 12:08:08 differentreality, tried in Greek restaurant here in NUE 12:08:13 and I think user deletion will come into place too, in time 12:08:22 differentreality: this is about stuff you can _FINISH_ untill the 11th of august 12:08:51 henne: yeap.. 2 weeks 12:09:02 from my side i can tell that CI Cycle will be tranformed to EPIC right away 12:09:52 okay then we should add new issues with concrete tasks for the stuff 12:10:10 what do you have to implement to make user deletion possible? 12:10:39 henne: we need to agree on the implementation. Which I see you have positively replied to my comment for 'keep user record, delete data' 12:10:53 yeah 12:11:12 then what? 12:11:45 then, change the destroy function in users controller, some changes for authorization in the users view page 12:12:50 what about the migration? 12:14:11 in #333 12:14:19 that should be fixed too 12:14:28 ah yes, the migration. The thing is that from our live instance, the users are already deleted anyway... So the 'normal' plan doesn't reallly work here. 12:14:43 yes #333 is part of the whole thing for sure 12:15:06 so, can you take 333 into Milestone? 12:15:16 or we postpone it to the next MS ? 12:15:19 uhm yes, definitely 12:15:24 MS -> MileStone 12:15:29 alright: https://github.com/openSUSE/osem/issues/383 12:15:30 no I think it's part of the MIlestone 12:15:44 differentreality, so 333 to MS#1 12:16:02 #info issue#333 moved to MS#1 12:16:29 so what concrete steps do you have to do for Roles&Authoriation? 12:16:37 cool! Are we going to include this migration to osem or just run it for us (openSUSE live instance)? 12:17:03 differentreality, i think we should include migration, as people deployed has same problem 12:17:04 let's discuss details afterwards 12:17:10 alrighty 12:17:13 or else this meeting is going until christmas 12:17:13 authorization 12:17:27 I have switched to using a single Ability model 12:17:36 seems to be doing pretty good now :) 12:17:49 What do you still need to do until August 11th? 12:17:50 Several tests are already in place (based on henne's tests, along with additions) 12:18:36 More testing, some bugs I got, role assignment page 12:18:50 okay 12:19:23 then settled for differentreality 12:19:32 I might have to do a couple of more changes to naming we use inside the app, so that things get set automatically by cancan 12:19:49 okay 12:20:00 https://github.com/openSUSE/osem/issues/372 12:20:34 where it goes ? 12:20:59 https://waffle.io/opensuse/osem 12:21:16 are we going to make any kind of role assignment from users list? 12:21:29 details later please 12:21:36 If not, this has nothing to do with role assignment. The issue is addressing a menu thing anyway 12:21:50 #info #383, #339, #333, #330 are commited by differentreality 12:21:54 is that right? 12:22:07 or #372 too? 12:22:21 henne, are commited tasks should be moved to Ready? 12:22:58 #372 is a menu thing, if we move forward with it, it is related to #304, as it mentions, which is Chris's implementation 12:23:01 yes they should 12:23:21 so, differentreality do you think 372 should be added to current MS ? 12:23:23 differentreality: #372 is about the interface you're trying to build 12:23:50 henne: it is actually about the position of 'Users' link in the admin menu 12:24:10 which is an issue, regardless of me making it possible to assign roles from 'Users' page or not 12:24:14 #383 is in ready, #339 and #333 are PR's 12:24:29 my interface part goes into role assignment (where that assignment might happen) and is of course definitely into my tasks 12:24:30 #330 is an EPic 12:25:18 differentreality: the only reason to move the User list from it's current position somewhere else is role assignment 12:25:39 ok, i want to settle differentreality list for this MS 12:25:52 differentreality: that's why this #372 is now yours to come up with the interface :) 12:26:14 383 and 372 are in ready for MS, what should be added ? 12:26:29 adding 339 12:26:35 339 is a PR 12:26:47 yup 12:27:00 do you think we should not track em" 12:27:04 ? 12:27:08 PR's should go to "in progress" :-) 12:27:15 when they are related to a Milestone 12:27:18 ok, done 12:27:26 this happens automatically for new PR's BTW 12:27:38 btw roles issue is https://github.com/openSUSE/osem/issues/23 12:27:39 ok 12:28:14 #23 is an Epic 12:28:45 Epics don't go to milestones. They serve as basis for concrete tasks 12:28:59 okay 12:29:08 so, we are missing specific tasks for this epic ? 12:29:18 the concrete task is the PR to merge your stuff (which is in progress) and the issue #372 which is about creating the interface 12:29:43 ok 12:29:59 alroght 12:30:10 we can move on to gopesh I think 12:30:20 yeah, if he would be here 12:30:23 please give me a minute to fetch chris 12:30:27 okay 12:31:08 #info KalabiYau commited to finish 382, 381, 363, 353, 362 in MS Quacamole 12:32:17 then let's continue with Chrisbr if gopesh isn't there 12:32:24 hi, Chrisbr 12:32:29 hi all 12:32:43 Chrisbr: we are currently talking about what we are going to do in the upcoming milestone 12:32:49 okay 12:32:53 for the next two weeks 12:33:38 Yep, I think my tasks will be the refactoring of the admin menu so far ... 12:33:52 there is an issue for this right? 12:34:09 https://github.com/openSUSE/osem/issues/304 12:34:19 I think this one describes it best 12:34:31 and I already added it to the milestone I believe 12:34:43 Yes as this is the Epic behind it :) 12:34:49 we need concrete tasks 12:34:54 so we can see progress 12:35:07 Ah okay, so we have to split it up in several small tasks? 12:35:08 you said to me you are going to do this step by step 12:35:27 let's create issues for every "big topic" in the menu 12:35:28 Yes, currently I'm working on the conference basics, contact and photos 12:35:46 okay 12:36:04 btw, you guys can make this together later on 12:36:12 or wanna do now? 12:36:15 now 12:36:17 hello 12:36:20 ok, go on 12:36:22 gopesh, hi 12:36:25 so we all learn what's going on 12:36:27 srry I am late 12:36:29 we are planning first Milestone now 12:36:44 yes what's there for me to do 12:36:49 gopesh, what tasks which are not epic labeled you think you can deliver until 11th of Aug? 12:37:00 checking out 12:38:03 gopesh, it is about what you are sure will be finished 12:39:01 Chrisbr: you think you can finish everything until 11th of august? 12:39:27 I hope so... 12:39:33 ok 12:41:18 well I think I can handle #385 #386 #387 12:41:33 and #388 12:41:48 as there are already there 12:42:06 I just need to segregate it from conference#settings 12:42:13 those are chris tasks 12:42:57 and are about reworking the admin interface 12:43:09 then I can take up deleting users 12:44:18 gopesh, 385 taken by Chrisbr 12:44:22 https://waffle.io/opensuse/osem 12:44:23 what about your own gsoc tasks? 12:44:58 well mine email notifications are over 12:44:59 gopesh, basically everything you've mentioned is taken by Chrisbr 12:45:15 gopesh, https://waffle.io/opensuse/osem 12:45:19 look at left column 12:45:20 KalabiYau: np I can take up deleting users 12:45:27 gopesh, which task it is? 12:45:35 that one is taken by differentreality 12:45:52 383 12:46:01 oops 12:46:06 ok wait.. 12:46:44 what about the tasks left for your GSoC project? 12:47:03 the notifications thing i discusses with James 12:47:11 he said no redis 12:47:16 #info Chrisbr commited to finish tasks #389, #388, #387, #386, 385 12:47:33 and without node and redis 12:47:50 it would be useless to implement in-house notifications 12:48:49 so what are you planing to do in the next two weeks? 12:48:53 henne: if you want some other feature then I can take up that 12:49:04 gopesh, you decide, what you want to do 12:49:10 take a look at https://waffle.io/opensuse/osem 12:49:13 I am left with some pending issues for splash 12:49:21 like implementing keynote speakers 12:50:05 and fix splash layout a bit 12:50:32 can you do #380? 12:50:47 KalabiYau: yes 12:51:00 but that I guess too small for 11 august 12:51:20 gopesh, can #377 be resolved? 12:51:25 closed or merged until 11th? 12:51:38 gopesh: it's about what you can do _until_ 11th of august 12:51:44 gopesh: you could do a million small things 12:52:01 henne yes right 12:52:16 KalabiYau: yes this will be merged within this week I guess 12:52:24 so can you fix #380 in this milestone? 12:52:37 waiting for james 12:52:49 henne: yes I can take up fix#380 12:52:51 :) 12:52:51 ok 12:53:09 ok, i think for now it is enough? 12:53:31 IF someone is done with his work on MS, just take something else, but be sure to finish until end of MS 12:53:33 make sense? 12:53:47 yes 12:53:59 KalabiYau: yes 12:54:05 henne, any commitments from you? 12:54:29 #info gopesh commited to finish #300, 164, 380, 377 12:54:42 cool 12:55:04 I commit to do #336 12:55:43 and I commit to do #243 12:55:45 ok 12:55:51 freezing? 12:56:08 wait 12:56:12 ok 12:56:17 I have an issue with pull requests 12:56:29 we all should commit to get the current open ones closed 12:56:45 by either working in suggestions, rebasing, reviewing etc 12:56:54 i agree 12:57:01 any objections? 12:57:06 we have way too many dangling 12:57:16 meaning all PRs should be closed 12:57:19 henne: yes mine are dangling I know 12:57:22 or removed 12:57:42 #info agreed to close all open PRs until MS#1 deadline 12:57:59 henne, freezing your commitment? 12:58:10 yepp 12:58:16 #info henne commited to finish #243, 336 12:58:58 #action KalabiYau should assign owners to open PRs and move them to 'in progress' tab at waffle 12:59:10 then guys, we are good to go, i think 12:59:43 please, take first a very close look to your PR 12:59:56 if you are not sure it is not deliverable until 11th - close it 13:00:04 if yes, please fix and finish it 13:00:10 questions? 13:00:31 and please don't hesitate to start discussion on something of your concern 13:00:37 let me explain where you can look for what now 13:00:51 please do 13:01:13 Goto https://waffle.io/opensuse/osem 13:02:02 The cards in the "Ready" column are what you have committed to do until August 11th 13:02:28 If you start to work on something, put the card into the "In Progress" column 13:02:48 Pull requests from you will end up there automatically 13:03:13 once you have finished something move it to the "Done" column 13:03:19 henne: we could have also used trello 13:03:30 just a thought 13:03:32 gopesh, nope, as it is not connected to github 13:03:35 merged pull-requests will appear there also automatically 13:03:37 but waffle is 13:03:43 KalabiYau: cool 13:04:06 well then I think I should have used waffle to manage my gsoc progress :P 13:04:18 alright 13:04:23 that is how we work from now on 13:04:56 so whenever something pops up in "In progress" that isn't related to the milestone you should blush! 13:05:03 #info work is tracked via https://waffle.io/opensuse/osem 13:05:22 except you have finished all the cards you have commited to do. then it's okay 13:05:36 please obey these rules. thanks 13:06:14 cool 13:06:19 cool :) 13:06:20 anything else, guys? 13:06:51 KalabiYau: I think this trend will be followed after gsoc too 13:07:11 this is a great way to track progress :) 13:07:43 okay, then we are done 13:07:46 happy hacking! 13:08:04 KalabiYau: one thing my build for #377 is failing 13:08:16 #endmeeting