[ug-bosug] Bosug meet for Feb/2008

Manish Chakravarty manishchaks at gmail.com
Tue Feb 5 02:48:01 PST 2008


Hi Shiv,

This sounds like a good idea.
I will prepare material to be presented on the lines of what you asked.

Thanks
Manish
On Tue, 2008-02-05 at 16:10 +0530, S h i v wrote:
> On Feb 5, 2008 3:36 PM, Manish Chakravarty <manishchaks at gmail.com> wrote:
> >
> > Shiv,
> > Should we then take the Qt session off the agenda?
> > Given the time constraints, if we start from the basics and go upto
> > Qt/C++ probes, it would be very cursory.
> >
> > Speaking from a numbers/interest perspective , I think we should do a
> > basic DTrace session and keep the C++/Qt stuff for the hackathon , or do
> > it offline.
> >
> 
> I wouldn't call it a Qt session. What we need is a cursory overview of
> KDE codebase:
> 1. How the KDE Code Base is structured.
> 2. What are the logical components?
> 3. How do they map to physical components (files/dirs)? - At a broad level.
> 4. To insert probes (look at it as logs/traces for now) which sections
> of the code are most suitable? A small number of critical sections.
> These are the components/daemons/ that are either known to have too
> many issues OR known to hold information during run-time - this
> information if known can resolve issues.
> 
> This should be a conceptual and a cursory overview of about 30-45 mins.
> Shouldn't talk about Qt/GUI programming, Needn't talk about developing
> ones own KDE app.
> Needn't cover all KDE apps. Need to look at a small section of
> base/important packages.
> 
> Without these inputs, deciding on the scope of the hackathon becomes
> difficult and all of us will be clueless :)
> 
> We can have a look at the actual code at the hackathon. What say?
> 
> ~Shiv



More information about the ug-bosug mailing list