[SailfishDevel] [Minutes] SailfishOS community meeting 03 June + planning for next one 10 June

2014-06-03 Thread Sebastian Meyer
Hi,

Thanks to everyone who attended todays's meeting. Minutes/logs:

Minutes:
http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-03-10.00.html
Minutes (text):
http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-03-10.00.txt
Log:
http://merproject.org/meetings/mer-meeting/2014/mer-meeting.2014-06-03-10.00.log.html

Next meeting will be on 2014-06-10 @ 15:00 UTC. Meeting Chair will be
cybette unless someone volunteers until then. Please propose discussion
topics, with some content/details at:
http://piratepad.net/SailfishOSSMeetings

(add your name/nick if you suggest a topic and will present the topic at
the meeting, or name someone who should present. Indicate how much time
approximately you will need for the topic so we can timebox the meeting
accordingly)

NOTE: Propose your topic by Friday 06 June. Any topics added after that
will be considered for the following meeting. This is so that people
involved can prepare for the discussions before the meeting.

Thanks,
 netzvieh
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org


Re: [SailfishDevel] [Minutes] SailfishOS community meeting 03 June + planning for next one 10 June

2014-06-03 Thread Sebastian Meyer
For those who don't want to delve into the meeting logs, here the full
description of Basil Semuonovs topic from the Pirate Pad:

Harbour  SailfishOS apps compatibility
Statement: Problem with SailfishOS fragmentation is coming.
Harbour/Store is not prepared for it.
Description: Now we have 1 device running official SailfishOS - the
Jolla Phone. And one major SailfishOS version running on devices. One
day Jolla will release another device. Also, SailfishOS targets to be on
android devices, and once SailfishOS will be ported, lots of supported
devices will appear. This will cause fragmentation in terms of 'base'
specs of devices. To make it clear, i'm not talking about 'this
smartphone have an attachable DVD-ROM, and that will have ultra-3D-touch
surface'. I'm talking about screen resolution  aspect, CPU  GPU
performance, amount of RAM. Most of devices will have 1gb+ ram, 2+
cores, 16:9/16:10 aspect.
Of course, SailfishOS versions will be different on all devices, since
there are some hardware problems, or just timeframe related
'complication' issues during new SailfishOS version release time.
Every-day apps like notes/music player/etc will probably work just fine.
Some of 3d enabled games will. But most of gorgeous apps would break the
leg here: some should not be runned on square resolultion, some require
atleast 2gb of RAM to work as expected and provide neat user experience.
Or imaging 'streaming apps', that require LTE support for fast connection.
Also, SailfishOS is rapidly developing. Dont you say that you will
always use Qt 5.2 core libs? What if Qt releases 6.x in a month with
'breaking quantum-state-processor support', and it will installed in
every 2 of 3 flagship phones. What will happen to all already published
apps, if you change some of core packages to new major version?
Possible solution:
  SailfishOS: Introduce core meta packet(s) with sfos version, which,
maybe, depend on target device(or its specs), so apps can depend on it.
  Harbour: Add target SailfishOS version/device specs for application,
while publishing.

Best regards,
  netzvieh
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org