I continue to think one of the best uses of a summer student would be to take a look at LXDE as if coming into it fresh, and see what getting-started and ongoing management tools are expected.
This is a little more than coding feverishly. You do not want to end up with a bloated thing that replicates everything available in GNOME or KDE. This is part of what in my view has gone wrong with Xfce in its latest release. If people want the comforts of GNOME or KDE, they should run GNOME or KDE. You want sufficient finesse to give people what they need, such as a way to configure their input devices, without overdesign. It would require getting familiar with what's available in the competitive DEs and making intelligent choices. One possible output of that would be a configuration application that pulls together the existing several tools into a single one that probably has buttons you can drill down into to set different things. Then in each area, you design a lightweight yet sufficient parameter setting application. And a getting started HOWTO that takes care of answering most of the questions a new user would have about how to do things. The other observation I would make is that putting ten coders on a project produces far more code than we would want in LXDE. At some point soon, LXDE will be sufficiently fleshed out to be called "done" in the sense that adding things to it erodes the lightness in an undesirable way. We have also talked about redoing the internals of GPicView on top of the ImageView library same as Viewnior uses, which would be a nice little project for someone, but might be too easy to challenge someone for an entire summer. On 03/23/2010 10:25 AM, Shae Smittle wrote: > I hope to apply as a student. I will hopefully be able to work a little > more on lxde after my round of mid-term exams tomorrow. I would love to > discuss ideas for what to do for SoC. > > Shae > > > > On Tue, Mar 23, 2010 at 6:19 AM, Arne Bleckert <[email protected] > <mailto:[email protected]>> wrote: > > Mario Behling schrieb: > > Dear all, > > > > we are in the preparation phase for the GSoC program. > > > > 1. MENTORS > > Right now, we need to form a team of mentors. > > a) We need primary mentors who can take care of students during > the summer. > > b) We need backup mentors in case primary mentors are temporarily > absent. > > Please reply to this email if you would be able to support the program > > with mentorship or know somebody who could be a mentor. > > > > 2. MORE IDEAS > > We need more ideas on the idea page. It would be good if we can give > > students some choices. Prospectus students should also add their ideas > > here, please: http://wiki.lxde.org/en/Google_Summer_of_Code_2010 . > > There is also an older page of LXDE to dos. Maybe you can get some > > ideas here as well: http://wiki.lxde.org/en/LXDE_To_Do > > > > 3. STUDENT APPLICATIONS > > Who is interested to apply as a student for LXDE? It would be a good > > idea to start discussing ideas on this list. Personally, it would be > > great if we could also support contributors, who have been already > > active in the LXDE community. > > > > 4. ALLOCATION OF STUDENT SLOTS > > Students slots will be allocated by Google according to the percentage > > of all applications to all projects in GSoC. This means the more > > applications we get, the more choice we have to take students in and > > the more students we can actually take in. > > Since I don't have much time this summer due to my bachelor thesis I > normally wouldn't apply. But if the Mentors are choosing the students(?) > I could just apply to increase perceantage. What do you think? > > > > > > I am looking forward to your replies. > > > > All the best, > > > > Mario > > > > > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Lxde-list mailing list > > [email protected] > <mailto:[email protected]> > > https://lists.sourceforge.net/lists/listinfo/lxde-list > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Lxde-list mailing list > [email protected] <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/lxde-list > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > > > > _______________________________________________ > Lxde-list mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lxde-list ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
