Weekly chat
This document contains agenda and minutes of SDK management chat teleconference meeting on 20101005 15:00 GMT.
Conventions of this document
- AP: = Action point agreed on this meeting
- yyyymmdd AP: = Action point agreed on previous meeting
- yyyymmdd AP yyymmdd: = Action point agreed on previous meeting with a deadline
- yyyymmdd AP DONE: = Action point done
- yyyymmdd AP CANCELLED: = Action point cancelled
- AGREE: = Item that has been agreed by the team
- POSTPONED: = Agenda item postponed from last meeting
- OLD: = Info from previous meeting (delete during the meeting)
Attendees
- Veli Kaksonen, Bob Spencer
Agenda and minutes
- AGREE: Bob will initiate a Architecture Subteam (Bob)
- Installation
- Emulation / Virtual machines
- QEMU VM
- Device sensor control
- QtCreator plugin architecture
- Architecture document
- MADDE restructuring in plan
- Request for high-level ideas. Where / / how to evolve SDK. Ideas to the wiki (Bob)
- 20100928 AP: Create email discussion on OVI / AppUP store. Requirements for ISVs, messaging. (Bob)
- Competition (apple sdk)
- 20100921 AP: Take a look at collaborate (All)
- AP: Google docs about major deliverables for 1.1 (Veli)
- AP: Create a wiki page about open items that we need agreement on? (Veli)
- 20100928 AP DONE: Presentation of MeeGo SDK approved by Nokia/Intel (Bob to create)
- 20100928 AP: Check the presentation (All)
- Nokia SDK plans for commercial support / partners.
- 20100928 AP: Setup meeting on use of SDK by Intel/Nokia (Bob) Invitees: Veli, Ville, Bob, Mark Skarpness
Working together
- 20100928 AP: Make sure that we have installer proposal (Veli)
- Intel installation engineer: John (Zhang) Chen
- Competition (Apple SDK, Android SDK)
- 20100921 AP: Share the studies (Veli)
Postponed
- AP: View the requirements (Bob)
- How to ensure that we are working towards the same goal
- Bugzilla
- Project plan
- Roles & Responsibilities
- Workshops
- Something ASAP
- Conference workshop
- Decision making
- Who do we need for decision making?
- 20100928 AP: Create a proposal about subteams (Veli)
- Subteams
- Documentation
- QA
- Releasing & Packaging
- Toolchains
- API ?
- Individual tools as subteams or a "tools" subteam that has them all ?
- WRT / Web SDK
- Marketing ?
- Anything else?
- Tools
- Installer
- QEMU
- Device emulation (sensors, such as GPS, Camera, etc). Based on device.
- QtCreator
- UI Designer, QML GUI builder
- MADDE
- compliance checker tool
- tool running on target
- Testing tools
- Windows port
- Mac port
- 20100928 AP: Create a proposal about working groups (Veli)
Releasing
- Where are the components released?
- developer.meego.com or something else?
- Channels (build, tested, stable)
- What version of Qt SDK will be used?
Extending the SDK
- Plugin architecture
- e.g. we can't have skins for all the devices
- does QEMU cover all the supported devices (and which images will be provided for developers)?