13:01:38 #startmeeting 13:01:38 Meeting started Fri May 13 13:01:38 2016 UTC. The chair is ChrisBr. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:38 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:01:43 hello 13:01:47 hello 13:01:48 hello everyone :) 13:01:48 * RichiH raises hand 13:01:59 welcome to our first openSUSE GSoC mentor meeting 13:02:07 * RichiH pokes differentreality 13:02:07 hello, Arte 13:02:10 m is here 13:02:40 brb in 2' 13:02:49 as an update: 13:02:54 We have 6 projects under openSUSE 13:02:59 https://summerofcode.withgoogle.com/organizations/4794149198888960/#projects 13:03:11 and additional 1 project under FOSDEM 13:03:17 https://summerofcode.withgoogle.com/organizations/6340195892854784/#projects 13:03:29 differentreality and RichiH are responsible for the FOSDEM project 13:03:56 #topic Next steps 13:04:06 can we make a round call? 13:04:13 who is here for the GSoC meeting? 13:04:17 * henne is 13:04:21 * ChrisBr is 13:04:22 * imobach is 13:04:28 * ancorgs is 13:04:42 * KalabiYau is 13:04:45 * mssola is 13:05:17 anyone else? :) 13:05:22 \me is 13:05:25 * hernansp is 13:05:26 haha 13:05:28 haha 13:05:50 AFAIK differentreality is back in a few minutes 13:05:56 * differentreality here 13:06:20 okay so who is missing? 13:06:35 * RichiH roll calls again, just for good measure 13:06:47 josef 13:06:55 antonio 13:06:57 antlarr is missing but he told me that he has no time 13:07:00 josef is sick 13:07:04 cornelius 13:07:42 cornlius is lost in the USA 13:08:01 okay coo. on to next steps 13:08:03 cool* 13:08:24 Is everyone subscribed to the gsoc-mentors mailing list? 13:08:29 If not, please do so! 13:08:45 @suse ? 13:08:51 just send a mail to gsoc-mentors+subscribe@opensuse.org 13:08:54 opensuse 13:08:56 @opensuse 13:08:58 thanks henne 13:10:04 * RichiH is subscribed now 13:10:05 We plan to have another mentor meeting around midterm and final evaluation of GSoC. The purpose is to establish a mentor community within opensuse and help each other with problems etc 13:10:42 addtional we plan to have a meetup at oSC 16 in Nuremberg as we expect that a lot of the mentors and students will be there! 13:11:18 and if you think there is a need to talk about something feel free to kick off other meetings on the mailing list 13:11:56 any questions so far? 13:12:07 question about students on oSC 16 13:12:09 regarding mailing list: it's non-public and will always stay non-public, correct? 13:12:15 how many we will have from abroad? 13:12:15 yes 13:12:19 RichiH: yes 13:12:21 k 13:12:41 KalabiYau: abroad from where exactly? :-) 13:12:52 not from EU 13:12:59 my student is from brazil 13:13:23 KalabiYau: we don't know yet! We advised them to apply for TSP. TSP will announce around end of May who they can fund 13:13:33 got it, thanks 13:13:50 but this is independent from GSoC. Beeing a GSoC student does not mean that TSP will fund you ;) 13:14:03 that's clear 13:14:15 however, awafaa is aware that some students applied for TSP and tries to fund a few of them ... 13:14:21 but it means they will give you some kind of prio... 13:14:27 henne: exactly 13:14:43 ( awafaa is currently head of TSP) 13:15:04 in a funny hat as usual, I guess 13:15:20 hey, if he wears a hat it's a start 13:15:27 * henne shudders 13:15:51 more questions? 13:16:19 only if we can keep a tighter schedule while in meeting ;) 13:16:41 okay, next topic then 13:16:48 #topic Blogging / Marketing 13:16:56 We expect at least three blog posts of the students 13:17:01 Beginning blog post (by June 1), one midterm blog post (by July 10) and final blog post (by August 23) 13:17:17 Doug created a nice guideline for us 13:17:18 Guideline: https://docs.google.com/document/d/1LjG0lzDDDzpn9N-axMvfJFbwQlE5Z09NfcDvWCDhccw/edit?usp=sharing 13:17:38 Students should have their own blog, I'll write a guideline after the meeting to the students and we will redistribute it on news.o.o 13:17:48 We expect this as mandatory for the students 13:18:24 this is about marketing we can do for openSUSE and for the projects 13:18:46 and of course for students and mentors 13:19:00 Yes, please also blog as mentors :) 13:19:32 * ancorgs will probably use the YaST team blog for that 13:19:40 this is independent of any "reporting" the students have to do 13:19:57 this will be another topic later in this meeting :-) 13:20:51 questions? 13:22:24 next topic 13:22:29 #topic Reporting 13:22:49 We expect that you have regular contact with your student! 13:23:19 That means we expect e.g. daily standups and longer discussions at least once a week 13:23:32 Also that you track the progress in eg a trello board 13:23:43 ^ fair point 13:24:10 If you encounter problems, please contact me or henne asap 13:24:17 ChrisBr: it's a bit hard for me to do daily standup, considering the differences on timezones :) 13:24:26 problems with student responsiveness that is 13:25:02 mssola: right! However, you can eg write daily short mail update etc 13:25:03 mssola: if you can't make it daily meet as often as possible 13:25:11 sure 13:25:20 and if it can't be a meeting it can be a mail 13:25:32 mssola: or us it as an excuse to spend summer in Brazil 13:25:34 We see communication as one the most important parts of GSoC 13:25:44 ancorgs: haha, good idea :P 13:25:44 *use it 13:26:13 to make sure: is this expected of fosdem as well? and does that mean student -> mentors, mentors -> student, or both? 13:26:24 however you do it. it's just very important that you set up regular milestones in your plan that get reviewed and celebrated by you and your mentee. 13:26:33 agreed 13:26:54 as we believe that talking as often as you can is what builds the relationship and bonding with your mentee. 13:27:09 or, to phrase it differently: i would be surprised if the student will be able to work on osem every single day, so that frequency seems to be the better way to judge update frequency 13:27:15 and that is essentially what GSoC is all about. forming a relationship with your student 13:27:22 (barring actual problems like "he disappeared", of course) 13:27:26 also, your student has not much experience, they maybe fear to contact you too often and annoy you! 13:27:34 RichiH: GSoC is supposed to be a full-time job 13:27:37 RichiH: from my personal experience as a student of gsoc, I did work every day on the project 13:27:43 ok 13:27:46 same here 13:28:22 I agree with differentreality and mssola! This is also stated in all GSoC FAQ of fosdem! Students should expect to work 40 hours/week on their project 13:28:46 there were bits in the mentee docs that said "if you are aware for some time, don't sweat it but communicate", which is the reason i asked in the first place 13:29:06 Having some period of time (university course etc) where they're not able to focus full time on gsoc is fine, but they have to communicate that! 13:29:09 but that was then obviously referring to being ill or something 13:29:18 kk 13:29:19 yeah 13:29:28 RichiH: correct! That's what I mentioned! 13:29:59 https://developers.google.com/open-source/gsoc/faq#how_much_time_does_gsoc_participation_take 13:30:00 s/aware/away/, but you prolly guessed as much 13:30:05 There are certainly times where they can't focus full time on GSoC! As long as they communicate it with the mentor and it's just a short period of time it's fine 13:30:49 anyway. back to the topic. please make sure you track your students progress 13:31:06 and communicate, communicate, communicate! 13:31:12 questions? 13:32:37 how are you guys feeling on having your student send reports to the openSUSE community? 13:32:56 in previous years we had them send weekly mail to opensuse-project 13:33:10 I'm not very clear on the usefulness of those mails 13:33:47 henne: honestly I'd just tell him to send emails on a monthly basis or something like that 13:33:55 henne: you mean usefulness for the students or for the community? 13:34:01 ancorgs: both 13:34:09 if they are short and mostly links to other resources, they would create a nice form of positive pressure; at a set frequency 13:34:32 * RichiH sees that as a benefit the mentee, not the community at large, mind 13:34:33 I am not a big fan of the whole weekly reports / emails 13:34:43 I think that publishing in a blog is enough 13:34:48 imobach: +1 13:34:56 imobach: +1 13:35:12 mssola: monthly basis == almost blogging 13:35:14 but more often that three times in the whole project 13:35:28 ancorgs: yes 13:35:33 ChrisBr: yeah, I was just thinking out loud :) 13:35:41 the 3 blogs we were talking about earlier are for news.opensuse.org 13:35:42 than we can change the blogging guideline to blogging once a month? 13:36:16 you can call them 'reporting' but this is more like marketing fufu. not so much technical 13:36:50 this is for the openSUSE project. not the individual projects the people work on like YaST or OSEM 13:37:26 I also think that "work report" style mails don't have much value for the students or for the community 13:38:03 I would rather have my student blog on http://osem.io when we have finished some important milestone 13:38:25 henne: it makes sense 13:38:38 okay, to sum up: 13:38:55 the initial 3 blog posts are for news.o.o 13:38:56 if you keep track in a (almost) daily basis with trello or something similar 13:38:58 +1 henne, I like that too. That way we can end up with useful information about features and not just a repetition of I did this, and I will do that. 13:39:08 reporting as such shouldn't be needed 13:39:17 plus once a month a blog post on their own blog? 13:39:26 yah, i think i also prefer henne's suggestion 13:39:45 at least monthly sounds fair to me 13:40:30 everyone agrees? 13:40:37 at least monthly and a notification to gsoc-mentors@opensuse.org so Chris and I can pick it up 13:40:45 and spread it further 13:40:52 henne good idea 13:41:14 to sum it up: monthly on their own blogs and then we ping you 13:41:18 is that right ? 13:41:20 yep 13:41:39 plus the three blog posts for news.o.o we mentioned at the beginning of the meeting 13:41:45 yes 13:42:01 ah ok 13:42:20 will they have accounts to blog there, or how things would go ? 13:42:52 henne, doug or I will do that 13:43:00 they can just email us the blog post for news ? 13:43:09 they would send it to us and we will put it on news.o.o 13:43:14 ah ok 13:43:17 cool 13:43:19 I can also create author accounts there 13:43:26 then we can also take care that we don't flood news ;) 13:43:38 but sending us something is the prerequisite 13:43:53 no need to tie that down right now, though 13:43:56 got it 13:44:48 questions? 13:44:59 I'll sum it up for a follow up mail! 13:45:32 Next topic would be oSC but we already spoke about it at the beginning of the meeting so I think we can skip it! 13:46:03 Or has anyone more questions regarding GSoC and oSC16 in Nuremberg? 13:46:42 please encourage your student to go 13:46:46 and please come yourself :-) 13:47:07 hehe, yeah :) oSC is fun :) 13:47:13 it will be awesome to meet each other and kick off more good mentoring things 13:47:51 okay, next topic 13:47:55 # Timetable 13:48:04 We're almost at the end of community bondig period 13:48:19 On 23 May Coding period begins 13:48:31 That means students officially start coding on their project! 13:48:52 If you haven't, please have a look at our openSUSE mentoring guidelines: http://101.opensuse.org/ 13:49:02 which also means you should have a plan of what they should do 13:49:49 please remember that this is about the students 13:49:59 Next milestone is 20 June - 27 June: Midterm evaluations 13:50:46 It's mandatory to fill out the midterm evaluations, otherwise your student will fail and openSUSE will lose a slot for the mentor summit 13:50:47 about their needs. not yours or the projects needs. so come up with a plan that make them free software developers at the end of GSoC 13:52:10 Start by checking the basics with them. Do they know how to operate github? Is their development environment set up? 13:52:41 do they know the git basics? 13:52:45 etc. etc. 13:53:30 also explain to them how your community works 13:54:06 GSoC is as much about behavior in a community, knowing what you want, and the ability to convey this to others as it is about pointers, gcc macros and git command line options. 13:54:53 make sure to check that they know these things that you might take for granted 13:55:33 and make sure that you develop the students competence AND character 13:56:49 if you clear this up at the beginning I'm sure it's way easier to be successful at the mid-term weed out :-) 13:57:58 thanks henne 13:58:01 any more questions? 13:59:05 okay, then I'll close the meeting! If you have more questions, feel free to write to the gsoc-mentors mailinglist or to me or henne 13:59:11 you can find everything that Chris, Cornelius and I think makes a good mentor here: http://101.opensuse.org/#mentor 13:59:22 thanks everyone for participating! 13:59:22 Thanks for all the info! 13:59:27 thank you 13:59:30 thanks 13:59:38 And remember to have a lot of fun.... 13:59:39 ciao 13:59:40 :-) 13:59:44 thanks 13:59:48 see you 13:59:50 cya 13:59:53 thanks! 13:59:53 #endmeeting