Apr 27 01:02:04 I want to know that since last time jreznik said that splitting will be mostly done by package maintainers and KDE sig people Apr 27 01:02:39 so the student would be left with building the spin only. Right? Apr 27 01:03:01 rrix, May i do my own project for fedora? Apr 27 01:03:26 adimania: correct Apr 27 01:03:55 dhastha: You are allowed to submit your own ideas, correc,t you only have to get in contact with someone willing to mentor it i think Apr 27 01:05:01 rrix: okay. And apart from remastering experience what are the things you are looking for in a potential student? Apr 27 01:05:21 and packaging :) Apr 27 01:05:44 a good eye for what would work on a netbook, i suppose :) Apr 27 01:06:45 may be I should check out some net books OSs and see what they are offering. Apr 27 01:07:20 rrix, What an organisation expecting from a student to do project? Apr 27 01:07:33 rrix: what if the KDE SIG people are not able to split the required packages within the timeline? Apr 27 01:08:03 dhastha: Unlike GSoC we don't have multiple orgs here Apr 27 01:08:18 its only fedora and related projects :) Apr 27 01:09:01 dhastha: please take a looka t https://fedoraproject.org/wiki/Summer_Coding_2010#You_are_a_student Apr 27 01:10:09 * rdieter (~rdieter@fedora/rdieter) has joined #fedora-summer-coding Apr 27 01:10:26 rrix: hiya Apr 27 01:10:51 heyyy Apr 27 01:11:16 rdieter: adimania is wondering what happens for the KDE netbook FSC if we are not able to get the packages split, sicne that will be more of a group effort Apr 27 01:12:29 I think it's not a pass/fail thing, it'll be more like: how much progress will we make? Apr 27 01:13:20 there's more to making things netbook-happy, that pkg splits, no? Apr 27 01:13:24 than... Apr 27 01:13:36 * pilhuhn is now known as pil-afk Apr 27 01:14:55 rdieter: then how the project will be evaluated? Apr 27 01:15:23 I mean how are we going to decide the milestones? Apr 27 01:16:31 ok, fair question. such evaluatable milestones will need to be made then. I'm not privy to any existing plan of attack here. Apr 27 01:16:36 rrix: is there one yet? Apr 27 01:16:51 rdieter: can you please elaborate "there's more"? I am looking for that. Apr 27 01:17:02 basically, we're splitting, the student will be putting together a spin Apr 27 01:17:24 getting it through FESCo spins process Apr 27 01:17:34 and doing a lot of spitshine on it Apr 27 01:17:37 rrix: ok, if sizing, optmizing for a netbook spin is the only goals here, then that's that. Apr 27 01:17:49 kk Apr 27 01:18:04 so if they have to block on us, it wouldn't affect them negatively Apr 27 01:18:52 is there any size goal, constraints spec'd yet? Apr 27 01:19:14 We should target some spec and then think of the build. Apr 27 01:19:16 or... as long as it fits on a livecd... ? Apr 27 01:19:48 of course, livecd's are largely silly for netbooks, since most netbooks don't have a cd. Apr 27 01:20:25 so... something like an install footprint of... something like 3-4 Gb? (smaller? bigger?) Apr 27 01:20:35 If the live cd size and config is the only constraint then we can strip down the existing spin and configure it on the way. Apr 27 01:21:49 that would be a good first pass, sure. Apr 27 01:22:58 preconfiguring stuff to largely work out of the box... Apr 27 01:23:11 coming up with test plans new splits and features Apr 27 01:23:14 I have kind of done that already. Instead of stripping it was adding stuff to create a live dvd :) Apr 27 01:23:16 test plans for.... Apr 27 01:23:34 so, in the end, largely an iterative process Apr 27 01:24:15 maybe involve testing and evaulating competitors netbook-targeted products, see if there's any good ideas to steal/borrow Apr 27 01:24:21 rdieter: There /will/ be a size goal, etc I thnk Apr 27 01:24:36 I am hoping < 1gb install footprint Apr 27 01:24:41 little to no gtk deps Apr 27 01:24:48 rrix: oh boy. ouch that's small. Apr 27 01:24:50 :) Apr 27 01:24:52 ;) Apr 27 01:25:03 it's targeting the early eeepc-type models with 3g-4g ssd Apr 27 01:25:24 ok, not sure if that's doable, but it's a noble goal. :) Apr 27 01:25:46 set the bar high (or low in this case). Apr 27 01:26:54 * dhastha has quit (Quit: Leaving) Apr 27 01:27:08 rrix: rdieter: Maybe I can try to strip a live cd first. This will give us a maximum limit of the install footprint. Apr 27 01:27:53 ok, then identify best targets for pkg splits, to save more space? Apr 27 01:28:21 anything which I will build from the splitted packages has to be smaller than it. Apr 27 01:28:39 yup Apr 27 01:28:42 rdieter: +1 Apr 27 01:31:01 we might have to eliminate some heavier apps and replace it with similar less memory using apps. Apr 27 01:32:51 Apr 27 01:34:21 rrix: rdieter: anything else I should know? Apr 27 01:34:45 idk, don't think so Apr 27 01:35:17 that's a good start... once the size-related pain-points are identified, the real fun starts. splitting and testing things Apr 27 01:35:52 rrix: cool! I'll ping you again if I come up with something. Apr 27 01:36:20 cool indeed! Apr 27 01:36:25 rdieter: yup yup! Apr 27 01:36:49 rrix: rdieter: I will try to strip the live cd before the application period closes so that I can include the maximum size in my proposal. Apr 27 01:37:18 k-rad