15:01:34 #startmeeting 15:01:34 Meeting started Wed Dec 9 15:01:34 2009 UTC. The chair is quaid. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:55 hi 15:02:01 #topic Summer Coding SIG - another working meeting to get organized? :) 15:02:38 actually, with sankarshan here, progress on the process stuff makes sense 15:03:11 I haven't been able to put in the time I hoped to so far this last few weeks, 15:03:24 so we don't have much yet to help scale what we are doing 15:04:40 * quaid pulls up the minutes from last time 15:04:51 * sankarshan looks at them as well. 15:05:04 #link No Plan. 15:05:07 oops 15:05:21 #link http://meetbot.fedoraproject.org/fedora-meeting/2009-12-02/fedora-meeting.2009-12-02-15.30.html 15:06:12 OK, so I'm going to start editing stuff in to 15:06:21 #link https://fedoraproject.org/wiki/Summer_Coding_SIG 15:06:55 the full log showed a bit more schedule, let me start with that 15:07:47 I understand from the earlier "let's gather around the campfire" meeting that we wanted a stronger and structured way to work as an umbrella organization. 15:08:52 yes 15:09:04 on an aggressive schedule 15:09:17 so those are the to things in parallel - the schedule and the process/structure 15:09:27 #link https://fedoraproject.org/wiki/Summer_Coding_SIG#Schedule 15:09:27 Yes. 15:10:32 so what are the elements of that structure 15:11:13 this is all pre-Melange, right 15:11:32 i.e., we need to cook up our on tooling or process as needed here. 15:11:52 We already have a coordinator for the project/org with the organizers. What we do need to look at is how to set up a group of people who can be the fiduciaries of project proposals from developers/mentors and, help build up the proposals to acceptable shape and form. 15:12:06 I assumed that this is *before* we hit Melange. 15:12:10 yes 15:12:12 it is before 15:12:50 one caveat is, we discussed not really soliciting _proposals_ from mentors 15:12:52 An important part here is to ensure that we have proposals/projects that are [1] do-able and, [2] reasonable/pragmatic. Not something that isn't going to see light of the day later. 15:13:23 having ideas is fine, but the key is to be ready to work with interested students on the student's ideas. 15:13:46 Yes. The proposal isn't meant to get the student do what the mentor did not have time/tasking for. 15:14:28 so that is here my brain is having a harder time ... does our team vetting mentor/orgs just gather and organize the interested people with some pointers to a few raw ideas 15:14:32 ? 15:15:44 I thought about it a couple of days back, and, here's what I was thinking along. The mentors would be assured to see that there are a group of folks who are interested in taking up the raw idea and, turning it into a product idea which can then be offered to potential candidates to provide approaches_to_solution. 15:16:23 The folks vetting actually have a harder job of ensuring that the ideas for the proposals are absolutely relevant in terms of what augments the Fedora story being incubator of great products. 15:17:41 hmm, not sure that can be done ... 15:17:56 that is 15:18:09 we aren't always going to be able to sort wheat from chaff 15:18:29 I would say we would be able to in a larger number of the cases. 15:18:56 going on the idea of legitimate peripheral participation 15:19:22 Are you indicating that it is contrary to the notion of LPP ? 15:19:22 what may seem to a core team as not very interesting or valuable, well, we don't know its future. 15:19:30 :) 15:19:40 I'm saying that we have to accept ideas that seem peripheral to e.g. Fedora or JBoss 15:20:11 I agree that some ideas are going to be more clearly "yay, winner" 15:20:50 I do not disagree. What I did mention was that the folks vetting it have to be sure that the idea is feasible. An idea, that although peripheral and attractive does not result in a prototype at the end of a GSoC tenure has a greater chance of not being viral and, hence petering out. 15:21:01 so I think we should be careful about making too much of the charter about vetting the raw ideas, use case 15:21:16 ok, I think I get you 15:21:23 setting a bounding limit 15:21:34 "no matter what your idea, it needs to be containable in the time allowed" 15:22:13 Most aptly put. I need to note that down. :) 15:22:15 thank you 15:24:24 The other part (which could be considered process in a way) is to look at pre-qualifying candidates. That is, solve or, approach_to_solve "this" (hence learn the basic hygiene if you are new) and, thereon propose to solve "the idea" 15:24:43 ok 15:25:51 How does this fit into the standard SIG structure that is available within Fedora ? 15:26:22 SIG structure is fluid, it flows to work for us, aiui 15:26:29 My understanding, fairly vague, of a SIG is that they are accountable to produce a framework and, process that would enable them to meet the genesis objectives. 15:27:36 I think it's looser than that -- it's literally whatever the SIG needs to get whatever they think they want to get done 15:28:07 I think we encourage frameworks because they have been successful for SIGs before, but not required. 15:28:52 then it brings us to the bread-n-butter part of the story - what are the actions we should be targeting at in these coming weeks ? 15:29:15 I think I'm seeing: 15:29:31 #action organize the mentor vetting committee 15:30:02 #action strawman, finish, announce new process 15:30:08 #action schedule 15:31:47 * sankarshan will work on a note and send it to quaid before hitting the wiki : aimed at covering the aim of the vetting, mentor interaction and pre-qualification. If that helps in anyway. 15:32:10 here, one sec 15:32:23 take a look at the wiki again 15:32:30 I captured (most) of what we said 15:32:45 how'zat? 15:33:07 that's the awesome. who do you manage to do that is something i need to learn !! 15:33:17 s/who/how 15:35:09 * quaid was trained as a writer, so is able to convert ideas to words in real time :) 15:35:58 :) 15:36:16 To organize the committee/group - do we need to approach the board ? 15:36:35 Or, in other words, how does one select the first bunch. 15:37:08 oh, we just do that 15:37:13 I mean, it's just part of the SIG business 15:37:25 but how select ... eek 15:37:34 :) 15:37:37 I'm hoping, to be honest 15:37:44 that the usual call for mentors works as well this time 15:37:48 and this time we have more for them to do 15:37:52 me too ... 15:37:56 so some of them volunteer to work this 15:38:40 Sounds fair. 15:39:57 Are we ready to quickly call for mentors so that the group gets more time to bond and, get things going ? 15:41:57 hmm 15:42:00 almost 15:42:07 which is why I keep having this urgency to what I'm doing 15:42:30 I think we need to have the process and schedule ready 15:42:35 so we are very close 15:43:08 Do we need to have a FAQ of any sort ? Anticipating mentor questions like - What changes ? What does (s)he need to do ? 15:43:41 good 15:44:17 I'll jot down a couple that come to my mind and, wiki-fy them 15:44:25 cool 15:44:43 put in a new == FAQ == section on that page, OK? 15:44:55 I will. 15:45:00 quaid: Hey, just an FYI loupgarablond and some other people at FUDCon were interested in driving some content-repository work as a GSoC effort. 15:45:04 * quaid makes a save, then works on the sub-section instead 15:45:22 abadger1999: sounds interesting 15:45:28 Thinking of talking to Creative Commons, deviantart, and other orgs about maybe being the place for that effort. 15:45:32 is this an existing sub-proj/SIG need? 15:45:42 ic 15:45:46 I don't think we have an existing SIG. 15:46:06 Although we could have one -- there's been enough people interested in it over the past year. 15:46:34 how does it differ from e.g. deviantart? 15:46:49 or would the work be driven up in to such a project 15:47:06 I think that's the idea. 15:47:09 ah 15:47:19 Find out if deviantart or CC would be interested in hosting the eventual results. 15:47:30 Then work with them to build something that we can use as well. 15:48:04 By "as well" I mean use their resources :-) 15:48:17 But make it easy for Fedora people to get the content from them. 15:48:55 cool 15:50:18 Coming back (since I need to go get my dinner), we need to write out the process bit and, send it to the list before hitting the mentors with a Call for Mentors. 15:50:53 exacty 15:50:57 ly, too 15:51:05 heh ! 15:51:24 ok, I'll keep working on these items this morning 15:52:06 I'll join up through my day tomorrow. 15:52:21 ok 15:52:26 Is it alright if I drift away now ? :) 15:52:31 go on, thx 15:52:35 thx for the visit :) 15:52:38 thank you. :) 15:52:41 I'll finish up and send out the log soon, too 15:52:48 * sankarshan goes afk 15:53:02 ok, I'm going to end the meeting so I don't get distracted and forget 15:53:10 #endmeeting