Google Summer of Code

[Adam Gołębiowski]

On Sat, Feb 17, 2007 at 02:22:41PM +0100, Adam Gołębiowski wrote:
> On Sat, Feb 17, 2007 at 01:34:07PM +0100, Jakub Piotr Cłapa wrote:
> > Jacek Konieczny wrote:
> > > Hello,
> > > 
> > > Last time we missed it, maybe this time we could participate as a Mentor
> > > Organisation. Yeah... what organisation? ;-). But we could try. And no, 
> > > I am not volunteering for the "single administrator" position. ;-)
> > > 
> > > http://google-code-updates.blogspot.com/2007/02/speaking-of-summer.html
> > 
> > I think that's a good idea. Who tried to get us enrolled last year? 
> > Maybe that e-mail could be reused? ;-)
> 
> I remember asking google about our participation in SoC 2006. I can do
> this again. 

Mentoring organizations should apply to SoC 2007 between 5-12 March,
2007. I will take care about the process (if you want to do this, stand
up). 

We have just a few days left, we really should think of any projects that we
would like to propose for this year's edition. I looked through SoC 2006
thread that took place here and nothing much changed since then:

* GUI for poldek

* an installer that does not look like one from Slackware 3.0 age

* sparc rescue/live cd  - hmm, jackass did something like that, yet it
  failed to boot on my ultra 5


And here's what I think could be useful:

* pld stats 

  client / server collecting information about users' preferences, or
  better, packages popularity. I see it as an additional package which
  user has to enable himself (default configuration == do nothing),
  which would generate some sort of system's unique id and would
  frequently sent a bunch of information to the server:
   - architecture
   - detailed hardware info (no of cpu, memory, hdd)
   - list of packages installed 
   - IP (for GeoIP localisation (country only))
   - ...
  User could choose which information to send.

* pld/freebsd (if trojan agrees)

  work on PLD's port to freebsd (to be specified), a working port could
  attract some potential users/developers.

* pld infrastructure redesign

  re-write or extend builder's infrastructure so that requires almost no
  interaction from RM. I know there are some TODOs (like hold an upgrade
  until a package is built on all architectures). That could be part of
  the project - other ideas include adapting bug tracking system to our
  needs (like...  automatically assigning a bug to last commiter of the
  given package), or some rss feeds of new packages.

  buildlogs redesign - there was some ideas on one of the devel lists,
  yet there was no response. 

* network manager (don't know how appropriate that one is)

  adapt NetworkManager to PLD's /etc layout (if it needs it) or design a
  new one from scracth (gtk/qt based). Project aims on creating an
  easy-to-use tool for network configuration.

* ...

I will also start a thread on pld-users-pl / forum concerning SoC, maybe
our users have some great ideas.

Anything else? And what's more important, who would like to be a mentor?

-- 
 http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer    | Everybody needs some solid rock, I know I do.