14:05:36 #startmeeting 14:05:36 Meeting started Wed Jun 18 14:05:36 2014 UTC. The chair is suzanne. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:05:36 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:06:33 #topic regular meeting schedule for the summer. How often? And on what communication medium? 14:06:52 so far so good :) 14:06:56 lol 14:07:01 * joanie nods 14:07:23 now the hard part... deciding when to meet :) 14:08:03 yes, I am pretty open in the summer. Who has time constraints? 14:08:25 I have time constraints, but the schedule should not be hindered by that. I plan to be a resource for y'all. 14:08:34 I have time demands, but not constraints... 14:08:49 I am pretty open most of the summer, except for some short Workshops/Conferences in July and August 14:08:52 So even if I'm not free at your meeting time, I can be reached pretty easily when/if you need me. 14:08:53 so... lot's to do, but when I do it is somewhat flexible 14:09:13 yes, me too. Not many meetings, just lots of work 14:09:23 yeah Mohsen 14:09:27 Hi 14:09:37 I still have the wrong address :) 14:09:39 Hi Mohsen, we are discussing when we should meet and how often tihs summer 14:09:49 foss2server instead of foss2serve :) 14:09:58 ok 14:10:00 that was my typo... sorry 14:10:05 no worry 14:10:15 typing server too often :) 14:10:32 So how often should we meet? Every two weeks? Once a month? 14:10:55 I would pick what works for suzanne, Mohsen_, and alex_rmezei 14:11:03 +1 hjackson 14:11:34 Silly question: Do you have concrete tasks and goals, etc.? As I think that would dictate how often to meet. 14:11:39 I am wideopen especially middle of the weeks 14:11:44 i'm sure heidi, joanie (as she already said), and I will be around 14:13:35 Alex and Mohsen, are you flexible this summer as well? 14:13:44 As I said, I am 14:13:45 We are getting there Joanie! 14:14:02 yes, for most of the time 14:14:03 during the day middle of the week is preferred 14:14:22 almost any time works for me 14:15:37 Great! Let’s say our next meeting is Wednesday, July 9th at 10am? 14:16:17 Sounds good to me 14:16:27 works for me too 14:16:36 Cool! Let me record it. 14:17:13 #info next meeting is July 9th at 10am 14:17:27 10am EDT? 14:17:38 do we have different timezones in this group? 14:17:53 #info next meeting is July 9th at 10am EDT 14:17:55 I am still in CST 14:17:59 for the summer 14:18:23 #topic next steps, goals and milestones for the group 14:18:40 before you move on... 14:18:57 are you planning to schedule each meeting as you go?... 14:19:05 or are you thinking something more regular? 14:19:54 We can schedule every two weeks for now if that works for everyone? If we find we need to meet less we can change it? 14:20:44 sounds good to me... others? 14:20:57 sounds good to me as well 14:21:53 #info meetings will be held every two weeks Wednesdays at 10am EDT starting July 9th 14:22:00 excellent! :) 14:22:08 thanks Stoney! 14:22:14 * joanie updates her calendar 14:22:40 Now on to the even harder part. What are our goals, etc? 14:22:47 * hjackson marks his too 14:24:24 sounds good to me 14:24:53 One of my goals is to integrate POSSE labs into my software engineering class in the fall. I have over 40 students. 14:25:43 I would like to get my students working the the VM as we did together as a possible first lab 14:25:47 same with me 14:26:14 common goals... love it :) 14:26:18 I'll be teaching master's level software engineering course and would like to have different open source activities for them 14:27:08 Ok, so one of our tasks should be to write up what we did together and test it to make sure we can repeat it - we can turn that into a lab 14:27:42 great 14:27:58 just like the one we already started which was about the set up 14:28:05 yes 14:28:28 we need to define some sort of hierarchy of activities first, shouldn't we? 14:28:41 after set up 14:28:45 yes 14:29:01 So, Joanie , what do you suggest? 14:29:06 set up is the first lab that we can write up and test now 14:29:19 then we need to come up with the next labs 14:29:35 what do you want your students to learn next after setup 14:29:35 ? 14:29:39 does cloning and building a module count as part of the setup? 14:30:23 if students are new to Linux, just getting the VM working and familiar with how to use it as an end user might be a full lab. 14:30:37 but hjackson asks an important question :) 14:30:41 Absolutely joanie 14:30:56 I think just setting up the VM and exploring is a lab. 14:31:12 the cloning and building a module is lab 2 14:32:03 well, we need to make sure our students have the right environment and capable of doing common activities 14:32:22 so, set up and cloning and building modules are considered labs 14:32:22 yes 14:32:55 so let me try and document what we are saying. Let me be sure first. Lab 1 - VM set up 14:34:35 #info We are working on what labs we wish to develop for our course. 14:34:59 #info We are working on a list of labs 14:35:07 #info Lab 1 - VM Set up 14:35:17 cool... where will it live while you are developing the list? 14:35:56 you could put it on an etherpad, a wiki, etc. 14:36:11 good idea Stoney 14:37:54 What do you think @Mohsen and @alex_rmezei? Should I create a titanpad right now? We can move to a wiki later? 14:38:24 fine with me 14:38:57 sure :) 14:39:58 anyone know how? LOL! I am looking at the one we used but dont see the create new option 14:40:12 just type anything you like into the urel 14:40:14 url 14:40:38 so titanpad.org/BLAH-BLAH creates a pad called BLAH-BLAH 14:41:21 (titanpad.com... sorry) 14:41:24 lol 14:42:26 #info titanpad link: https://titanpad.com/POSSE-Summer 14:43:02 #link titanpad link: https://titanpad.com/POSSE-Summer 14:44:28 #info We will use this titanpad link to document our lab list. 14:45:28 How many labs would you like to come up with for the Fall term? 14:46:19 We should come up with our homework for the next two weeks 14:46:54 How long(ish) is a Lab in terms of 1) any lecture 2) the students actually doing the task? 14:47:44 I like to think of them about an hour long. My labs are about 2 hours and I leave plenty of room for exploring and messing up 14:48:12 It is the students doing the task. 14:48:27 so git 101 might be a full lab 14:48:36 building a cloned module might be another 14:48:38 absolutely 14:48:42 nothing JustBuilds(tm) :) 14:49:18 Making a change to the code in a dev branch and creating a patch could easily be a 3rd 14:50:06 bugzilla, etc. may or may not be lab-worthy. But it's something students need to know. 14:50:43 I think writing a good bug report that is repeatable is an important skill. 14:50:52 * joanie nods 14:50:56 They need to learn to communicate 14:51:12 I get a lot of “it doesn’t work” emails. LOL 14:51:43 you'll get even more in a *nix dev environment ;) 14:52:05 #info List of labs that we are working on can be found on our etherpad: https://titanpad.com/POSSE-Summer 14:52:33 for bug reports... there are some good articles online they can read.... then they could review existing reports... then they could write one 14:53:02 maybe first try to confirm a bug? 14:53:13 ooo... that's a good one 14:53:27 also could test a patch 14:53:30 reading it is one thing. Trying to process it and identify what the heck the reporter is reporting is another task entirely. 14:53:42 hjackson I like the test a patch 14:54:00 Let the students suffer what we suffer. I mean, let them learn fun new stuff! ;) 14:54:12 joanie: lol 14:54:19 Should the testing a patch be apart of Lab 4 or 5 or do you think it could be a separate lab? 14:54:25 because test a patch is a good pre-requisite to create your own patch 14:54:47 OK, I’ll switch Lab 4 and 5 14:55:58 Do we want to keep these meetings to an hour? If so, we need to wrap up and come up with a task list 14:56:14 (I can go either way) 14:56:28 to "testing a patch" you could add "reviewing a patch".... i.e., what makes a contribution good/bad/ugly 14:56:55 an hour is probably good 14:58:10 that list is looking good 14:58:12 :) 14:58:20 indeed it is 14:58:48 #action Dig up the VM Set-up notes we have from the other titanpad and start to formalize into a proper lab. 14:59:05 suzanne: usually actions have an assignee 15:01:36 thanks joanie, does anyone have the titanpad url that we used for the VM set up? I was on another computer and can’t find it at the moment. We can document here. 15:01:49 #action Dig up the VM Set-up notes we have from the other titanpad and start to formalize into a proper lab. @suzanne 15:01:53 suzanne: I can grep through irc logs 15:02:16 thanks joanie, if you could post it on the pad when you find it. 15:02:46 https://titanpad.com/POSSE-GNOME 15:02:53 i'll put it in the pad too 15:03:10 #link https://titanpad.com/wAD3OD6ysC GNOME groups pad at POSSE 15:03:55 @Mohsen_ and @alex_rmezei - what would you like your action items to be for the next two weeks? 15:03:57 although I don't see the link for the activity there 15:04:06 hjackson: on which? 15:04:21 the one I posted has the vm steps/notes we wrote and tried to follow 15:04:34 though what worked for me didn't work for others :-/ 15:04:46 ah... that's even better 15:04:54 didn't see your post sorry joanie 15:04:55 :) 15:04:59 I am a bit behind preparing my CS 2 course. I plan to use some activities related to POSSE there. But I am not yet sure what. 15:05:25 CS 2... data structures? 15:05:26 I would like to try to follow the instructions again and clean them up. I will then hand them over to Mohsen and Alex to test further. And Joanie and Stoney can test if they feel like it :) 15:06:03 CS 2 includes data structures, yes :0 15:06:08 suzanne: I think something important might be to verify they work as expected for all platforms (OS X, Windows, Linux) 15:06:30 Because I assure you, my steps worked fine -- just not for non-Linux folks 15:06:36 I can also help testing 15:07:01 yes, I am on a mac, I believe Alex can test for windows, etc 15:07:07 cool beans 15:07:22 I can test for windows and maybe ubuntu too 15:07:40 I am still debating between ubuntu and fedora 15:07:42 alex_rmezei: I think there is a group working on identifying datastructures in HFOSS projects; you might want to get in touch with them 15:07:54 that would be great 15:08:25 alex_rmezei: for a host OS, up to you. For the dev guest, if you're doing GNOME stuff I'd suggest Fedora 15:08:36 #action @alex_rmezei Test Lab 1 instructions on Windows and possible Fedora - add hints for different platforms as needed 15:08:43 the *buntus mix and match and heavily patch 15:09:05 i had some challenges installing the drivers on Fedora 15:09:16 sound and gpu drivers 15:09:27 but that's the host (right?) 15:09:31 or was it the guest? 15:09:36 yes, that was the host 15:09:42 though I'm deep diving. /me shuts up 15:10:31 I am very interested in Fedora, but it may not be as friendly as ubuntu for a starter 15:12:00 We have our friend Brian at red hat that will be willing to help us. He sent me an email that he would not participate in our project/meetings but he is available for questions etc 15:12:21 are you all going to divvy up the rest of the labs and take a first stab at the activities/subtasks therein? 15:12:32 it might impact the final order of the labs 15:12:59 that is what I was hoping Joanie 15:13:47 So pick your victims and assign labs ;) 15:13:51 @alex_rmezei and @mohsen, if you could pick a lab to work on for the next two weeks. We could then swtich off and test them 15:14:05 (I'm still here... but I'm getting distracted... ping me if you need me) 15:14:39 I can test LAB 01 on two host OS's 15:16:13 Alex - that is great, but I wanted to clean it up first. Do you want to take a stab at another one to get it started? Once all three of us have a first stab at labs we can all switch off and test on our platforms. What do you think? 15:16:54 sure 15:18:03 LAB 02 would be next :P 15:18:22 I just lost my connection to titanpad.com 15:18:27 me too 15:18:27 Cool Alex. You can get most of the info from what we learned in Stage 1 15:18:44 aha it's back 15:18:48 I lost the connection too 15:18:59 I just got back too 15:19:17 * joanie mutters "technology" and rolls her eyes 15:19:31 #action @alex_rmezei Lab 2 rough draft to be ready for testing on July 9th 15:20:16 if memory serves me Mohsen_ was doing well at the face-to-face with cloning and building 15:20:21 maybe he'll take lab 3? 15:20:44 What do you think @Mohsen? Are you up for lab 3? 15:22:03 What do you think @Mohsen_? Are you up for lab 3? 15:24:22 suzanne: you could just give him that action item now and if he doesn't like it trade later 15:24:32 exactly 15:25:29 #action @Mohsen_ Lab 3 rough draft - Bullding a Cloned Module - Mohsen, if you want to switch to another lab let us know. 15:26:57 #info We have assigned our first three labs and are planning to write them for our student audience. On or before July 9th, we will switch off and test each other labs and add information, test for different platforms, etc. 15:27:39 #info on July 9th we will divide up labs 4,5,6 and come up with more labs. 15:27:59 #info Joanie tends to lurk here, so if you have any difficulties in accomplishing your action items you should ping her. 15:28:30 sorry , I was on the pad :) 15:28:35 #info in the meantime please use our etherpad to communicate, add what you want to see to each lab etc. 15:28:56 I will start lurking here for fun 15:29:02 :) 15:29:21 Anything else before I close the meeting? 15:29:52 I will owrk on lab3 15:29:54 work 15:30:01 excellent Mohsen! 15:30:42 shalll I end the meeting? 15:30:53 end it, end it! 15:30:56 heh 15:31:01 lol 15:31:06 #endmeeting