From kde-core-devel Mon Apr 16 19:46:57 2007 From: Allen Winter Date: Mon, 16 Apr 2007 19:46:57 +0000 To: kde-core-devel Subject: Re: FW: [REMINDER] Upcoming KDE 4.0 Milestones + Nepomuk Message-Id: <200704161546.57671.winter () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=117678983830565 On Monday 16 April 2007 1:04:06 pm Sebastian Trüg wrote: > So today is monday? Can we agree on a solution? Should we wait for another > week and try to solve the windows and cmake problems first? > FYI: I added kdereview to the EBN processing today. Krazy found quite a few issues http://englishbreakfastnetwork.org/krazy/reports/kdereview/kdereview/nepomuk-kde/index.html The apidox tool will run later tonight. Probably should wait until next Monday and try to solve these plus the windows and cmake problems in the meantime. > Cheers, > Sebastian > > On Monday 09 April 2007 18:34:53 Allen Winter wrote: > > Just in case some core developers missed these messages on kde-devel. > > Please also notice that aseigo discusses Nepomuk in kdelibs 4.0 down > > below. -Allen > > > > ---------- Forwarded Message ---------- > > > > Subject: [REMINDER] Upcoming KDE 4.0 Milestones > > Date: Monday 09 April 2007 > > From: Allen Winter > > To: kde-devel@kde.org > > > > Howdy, > > > > A little reminder of the KDE 4.0 milestones that are coming within the next > > month. Comments? Concerns? > > -Allen > > > > > > Milestone: kdelibs Hackathon Week, 15 Apr - 21 Apr > > ---------------------------------------------------------------------- > > Goals: > > kdelibs polishing and fine-tuning. > > Full API review of Phonon and Solid (Oslo meeting) > > ->The Hackathon Week is not a week of free-for-all-fun in kdelibs. > > -> It is intended for polishing, scrubbing, cleaning the API. > > -> The BIC Monday rule is still in effect > > > > Milestone: Alpha Release + kdelibs soft API Freeze, 1 May > > --------------------------------------------------------------------------- > >---- Goals: > > The kdelibs API is frozen. This means that the classes and interfaces are > > not allowed to change, except with permission of the core developers. To > > make an API change, post a kdelibs API exception request to the > > kde-core-devel mailinglist with an explanation and the code. If there are > > no objections after a week, the change can be committed. NOTE: all affected > > modules must continue to compile and work as expected. > > > > Milestone: New Application Freeze and Usability and Accessibility Review, 8 > > May > > --------------------------------------------------------------------------- > >---------------------------------- Goals: > > All applications expected to be released with KDE 4.0 must: > > use the new cmake buildsystem > > compile with Qt4.3 and kdelibs 4.0. (Using Q3Support and/or kde3support is > > ok, though not desired) have a handbook (that at least describes what the > > application does) New applications must be committed into kdereview for > > review > > Resurrected applications must be committed back into their KDE main module > > Start Application Usability and Accessibility Review continuing until the > > start of the Beta Cycle > > > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to > > >> unsubscribe << > > > > ------------------------------------------------------- > > > > ---------- Forwarded Message ---------- > > > > Subject: Re: [REMINDER] Upcoming KDE 4.0 Milestones > > Date: Monday 09 April 2007 > > From: "Aaron J. Seigo" > > To: kde-devel@kde.org > > > > On Monday 09 April 2007, Allen Winter wrote: > > > A little reminder of the KDE 4.0 milestones that are coming within the > > > next month. Comments? Concerns? > > > > i'd like to see nepomuk be merged in. we're past the "new module" deadline, > > however i'd like to see it make it in because: > > > > - if we want to see apps in 4.1 make use of it, realistically we'll need it > > in kdelibs > > - dolphin already (conditionally) uses it > > - there's a SoC project for nepomuk integration > > - nepomuk has been in dev for a while and it would be generally > > advantageous for both projects imho to ensure proper integration sooner > > rather than later > > > > this would entail something like the following: > > > > - create a kdelibs/kmetadata (or a kio/kmetadata, and add libkmetadata to > > libkio?). contents would include: > > - knepomuk/ for libknepomuk, currently in backbone/knepomuk > > - kmetadata/ for libkmetadata, currently in kmetadata/kmetadata; add the > > nepmuk specific subclasses of widgets in kdeu/metadata/ > > - ontologies/ > > - rcgen/ for kmetadata_rcgen binary, which creates classes from > > ontologies; needed in kdelibs rather than kdebase as libkmetadata needs it > > to build - tests/ (self explanatory) > > > > - create kdeui/metadata and add the non-nepomuk classes from > > kmetadata/tools such as cloud widget. ktagdisplaywidget would go into > > dolphin for now with an aim to 4.1 as it isn't mature enough yet; > > kblocklayout and kautoscrollarea do not need to be exported or made part of > > the public API > > > > - create kdebase/runtime/metadata which would contain code for the > > knepdaemon and knepcoreservices binaries > > > > -- > > Aaron J. Seigo > > humru othro a kohnu se > > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > > > Full time KDE developer sponsored by Trolltech (http://www.trolltech.com) > > > > ------------------------------------------------------- > > -- KDEPIM Developer I accept PayPal payments to awinterz@earthlink.net