GUADEC proposal

[Sami Wagiaalla <swagiaal at redhat dot com>]

Strange this email didnt make it to the list last night:

I have look at the GUADEC proposal submission procedure.
It is very hip and very open, I like it very much.

You basically fill in the form which, creates a page that people
can view, and comment on. You can edit that at any time.

Here is what I would like to submit- any comments ?- :

_*Title*_

   Frysk: a Modern Debugger and Execution Analysis Tool

_*Track*_

   The *Topaz* track will contain visions, guesses, plans, alpha
   developments and anything related to the future.
   The *Catwalk* track will contain showcases, presentations,
   demonstrations - anything related to the present.
   The *Tangle* track will tackle tricky issues, controversial
   problems, and long-standing cross-discipline knots that need a broad
   effort.

   Which one does frysk fit in ?

_*Point of View*_

   *The Developer*.
   "Sessions about... development :), languages, platforms, libraries,
   standards, bugs and the GNOME project workflow. Closure and social
   event at the end, with a possibility of a KDE-GNOME rematch, this
   time on basketball."

_*Type of Session:*_

   15' Presentation ?

_*Summary*_

   Frysk is a new object oriented debugger and execution analysis tool
   written in Java using the Java-GNOME bindings. The goal of Frysk is
   to solve usability, and functionality problems with traditional
   debuggers, making it possible to debug and analyze large scale multi
   threaded applications.

_*Full Description*_ (I feel this section is a bit lacking... what more 
should i put here ?)

   Frysk is an execution analysis tool. The Frysk core creates and
   maintains an event driven, interactive Domain Object Model of the
   operating environment and its composing elements, such as hosts,
   processes and threads. The model allows clients to observe, analyze
   and manipulate processes and threads in that system. This is
   utilized to enable developers and system administrators to solve
   higher level problems such as monitoring the execution of a system,
   monitoring the use of locking primitives, exposing deadlocks,
   gathering data, and debugging a given process. Frysk is also
   intended as an always-on monitoring tool which allows the user to
   set up nets to catch certain problems and get a chance to analyze
   them as soon as they occurs and as the process is still alive.

   The Frysk GUI is designed to provides users with high level view
   hiding away noisy intricate details until they are requested. This
   high level overview in combination with correct and live modeling of
   a problem is what programmers seek when they choose the use of print
   statements and avoid traditional debuggers.


Sami Wagiaalla