Projects/Solid/Meetings/Akademy2010

When? Where?

• Part 1
  • Wednesday, July 7th, 9:30-10:30
  • Akademy 2010, Demola, Area 4

• Part 2
  • Wednesday, July 7th, 15:00-17:00
  • Akademy 2010, Demola, Area 2

Attendees

In alphabetical order, these are metalworkers expected to be at Akademy 2010:

• Alex Fiestas
• Kevin Ottens
• Michael Zanetti
• Sebastian Kügler
• Dario Freddi (remote)
• Will Stephenson (remote)
• Paulo Rômulo (remote)
• Pino Toscano (remote)

Please also declare which days/timeslots you will be around: Doodle Meeting Planner

Topics For Discussion

• Deprecating libsolidcontrol
  • Current state in bluetooth, network, power, etc.
  • Breaking out in tasks to get there

• Narrowing/strengthening libsolid API
  • Finding features we duplicate from the Qt API itself
  • Finding (almost) unused or useless frontend interfaces

• Adopt a backend session

• Bluetooth integration in libsolid
  • Discuss AVRCP integration into the RemoteControl part

• Plans for 4.6
  • Bluetooth
  • Network
  • RemoteControl
  • PowerDevil

• Building a maintenance team

• if people can be available via audio conferencing
  • (Paulo) GSoC2010, UPnP support in libsolid

• KDE Hardware wiki

Workshop, get your hands dirty

Kevin can show you how to get started in writing your own libsolid backend. A mini-hackfest for that could be nice. Put your name in front of a backend to adopt it:

• Alsa
• BlueZ
• fstab/mtab, network shares only
• UDev, for "other" devices (camera, mediaplayer, etc.) (Dario: I can help in the creation, but I'd like somebody else to step up as a maintainer; Pino, maybe)
• UDisks
• UPnP (Paulo, Friedrich)
• UPower (Dario; Pino, maybe)

Minutes

make the allDevice() and friends async versions deprecate the sync ones bluetooth can't automatically detect add/remove of devices

libsolidcontrol deprecation:

- document our xml D-Bus interfaces
- generate the documentation out of those xml (what the name of the tool?)
- provide compatibility guarantees

- Network
  - kill knetworkmanager ASAP, defunct anyway since the D-Bus menu entered the game
  - 4.6: moving network out of libsolidcontrol, move in kdebase (same folder), fix issues (Sebas, Will, Lamarque)
  - 4.7: flatten up network libsolidcontrol relicates (Sebas, Will, Lamarque)
  
- Bluetooth: Green, can remove today (Alex)

- Power: ??? (Dario)
  - 4.6: moving power out of libsolidcontrol, fucking great "I resumed" signal, thanks, kiss, love
  - 4.7: flatten power libsolidcontrol relicates
  
- Remote Control: (Michael)
  - 4.6: moving remote control out of libsolidcontrol
  - 4.7: flatten remote control libsolidcontrol relicates

libsolid bluetooth integration

- exposing StorageAccess devices

Plans 4.6:

~ Power: get more information about the battery (boring stats)
~ Power: if resume signal, start using it in applications
   - Fix the clock, including current timezone
   - Kick in dataengines to update applets
~ Power: show external batteries in the UI
~ Power: KCM needs usability reviewing
~ Network: System wide network connections
- Network: see above
- Network: ModemManager support
- RemoteControl: Bluetooth support (depends outcome of post-BoF discussions)
- Bluetooth: Rewritten from scratch, provide daemon
- Bluetooth: Alsa support
- Bluetooth: comes with KCM
- Bluetooth: ioslaves (listing devices, file transfer)
- Bluetooth: Plasmoid similar to the network one

nice for 4.7

- Network: NetworkManager 0.8 support
- WiiMote support

Wiki pages on userbase, describing what we support

Backend adopters:

- Alsa 
- BlueZ (Alex)
- fstab/mtab, network shares only (Friedrich)
- UDev, for "other" devices (camera, mediaplayer, etc.) (Dario: I can help in the creation, but I'd like somebody else to step up as a maintainer; Pino, maybe) 
- UDisks (Michael?, Kevin)
- UPnP (Paulo, Friedrich) 
- UPower (Dario; Pino, maybe)