Here are my ideas from 2006, slightly updated:
1) Provide GNOME desktop hooks which would allow sunray utactions
(specifically java card removal) to do something useful such as:
Tell GAIM instant messenger that you are away.
Tell screensavers, stock tickers, clocks and other visually active
applications to stop updating the screen for a while.
Tell other GNOME applications to go into a low resource usage mode.
A variation on this is to provide a way to reliably and quickly suspend
a GNOME session and restore it so that the user context is not lost.
2) Write a porting tool which would allow customizations of desktop
files and gconf key to be migrated automatically to newer GNOME releases.
(GNOME has become more stable over the years, but migrating from GNOME
2.6 to 2.Whatever-will-be-in-Solaris-next, will probably take some work.)
3) Make nautilus understand zfs, including snapshots and rollbacks.
(I think much of this has been done, but additional work may be
necessary once GNOME replaces gnome-vfs with gvfs.)
And here are some new ideas:
4) GNOME-Light. Try to figure out what kruft and bloat in GNOME can be
removed without impacting the user experience. Figure out why a small
GNOME 2.22 application binary consumes more memory than the same
application built for GNOME 2.6. Make sure features which rely on CPU
or GPU horsepower have an off button in gconf. Find out which GNOME
processes can be shared between users (e.g. gconfd, dbus-daemon?).
5) Database filesystem. Have nautilus make use of mysql to present a
filesystem view similar to that which was in BeOS.
6) Implement an efficient database backend for gconf.
Darren Kenny wrote:
> FYI - any one got any ideas for the desktop side of things?
>
> Now is the time to start thinking about this and we can start submitting next
> week...
>
> Darren.
>
>
> ------------------------------------------------------------------------
>
> Subject:
> [summerofcode] GSOC 2008 is on
> From:
> Rob Giltrap <rob at kiwihq.com>
> Date:
> Tue, 26 Feb 2008 07:01:05 +1300
> To:
> summerofcode at opensolaris.org
>
> To:
> summerofcode at opensolaris.org
>
>
> Hi All,
>
> The announcement is out. GSOC 2008 is on.
>
> Here are the list of critical dates.
>
> February 25: Program announced. Life is good.
> March 3: Mentoring organizations can begin submitting applications to
> Google (~12 noon PST/19:00 UTC).
> March 12: Mentoring organization application deadline (12 noon PDT/19:00
> UTC).
> March 13-17: Google program administrators review organization applications.
> March 17: List of accepted mentoring organizations published on
> code.google.com/soc/ <http://code.google.com/soc/> (~12 noon PDT/19:00 UTC).
> Interim Period: Would-be student participants discuss application ideas
> with mentoring organizations.
> March 24: Student application period opens (~12 noon PDT/19:00 UTC).
> March 31: Student application deadline 5:00 PM PDT/00:00 UTC April 1, 2008.
>
> I'll work with Glynn to get the mentoring submission in over the next
> few days, and a message out to the main lists asking for mentors and ideas.
>
> Cheers, Rob.
>
>
> _______________________________________________
> summerofcode mailing list
> summerofcode at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/summerofcode
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris.org
>
