Comments on: Introducing the Release Plan http://blog.symbian.org/2009/03/12/introducing-the-release-plan/ Fri, 12 Mar 2010 11:13:03 +0000 http://wordpress.com/ hourly 1 By: Reviewing the Release Plan « Symbian Foundation Blog http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-1431 Reviewing the Release Plan « Symbian Foundation Blog Thu, 30 Apr 2009 10:36:57 +0000 http://blog.symbian.org/?p=396#comment-1431 [...] Reviewing the Release Plan By David Wood One of the most important threads of activity running through the inaugural meetings last week of all four Symbian Foundation Councils was a multi-angle review of the content of the release plan of forthcoming Symbian platform releases. [...] [...] Reviewing the Release Plan By David Wood One of the most important threads of activity running through the inaugural meetings last week of all four Symbian Foundation Councils was a multi-angle review of the content of the release plan of forthcoming Symbian platform releases. [...]

]]> By: Craig H http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-766 Craig H Sun, 05 Apr 2009 13:06:27 +0000 http://blog.symbian.org/?p=396#comment-766 @prom1, thanks for your comment! I am preparing the Symbian Foundation roadmap for the security technology domain, based on input from the package owners. Multi-factor authentication, such as the RSA token you describe, is indeed a valuable feature for enterprise use and on-line banking. It's one of the subjects I plan to cover over on the <a href="http://sfsecurity.wordpress.com/" rel="nofollow">SF Security blog</a> sometime soon, also covering biometrics as a third type of authentication: something you know (password), something you have (token) and something you are (biometrics). One of the interesting challenges for the Symbian Platform, compared to end-to-end service providers like RIM or, to some extent, Apple, is that we only implement one side of a conversation. The email client on the device will be talking to someone else's server, so the client has to be implemented using a published protocol to communicate with the server. This leads me to a question for you: do you know which published protocols support this two-stage authentication to the email server? The Symbian Platform does currently support POP and IMAP protocols, but it may be that support for two-stage authentication is only in a later version of the specifications. One last thought - as I have repeated elsewhere, the foundation doesn't have any product development engineers; the roadmaps for the various technology domains are entirely dependent on outside organisations or individuals stepping up and contributing their effort. If you know of an organisation that has this sort of technology, I would be happy to discuss with them the benefits they can get by contributing it! @prom1, thanks for your comment! I am preparing the Symbian Foundation roadmap for the security technology domain, based on input from the package owners.

Multi-factor authentication, such as the RSA token you describe, is indeed a valuable feature for enterprise use and on-line banking. It’s one of the subjects I plan to cover over on the SF Security blog sometime soon, also covering biometrics as a third type of authentication: something you know (password), something you have (token) and something you are (biometrics).

One of the interesting challenges for the Symbian Platform, compared to end-to-end service providers like RIM or, to some extent, Apple, is that we only implement one side of a conversation. The email client on the device will be talking to someone else’s server, so the client has to be implemented using a published protocol to communicate with the server.

This leads me to a question for you: do you know which published protocols support this two-stage authentication to the email server? The Symbian Platform does currently support POP and IMAP protocols, but it may be that support for two-stage authentication is only in a later version of the specifications.

One last thought – as I have repeated elsewhere, the foundation doesn’t have any product development engineers; the roadmaps for the various technology domains are entirely dependent on outside organisations or individuals stepping up and contributing their effort. If you know of an organisation that has this sort of technology, I would be happy to discuss with them the benefits they can get by contributing it!

]]> By: prom1 http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-750 prom1 Sat, 04 Apr 2009 22:52:48 +0000 http://blog.symbian.org/?p=396#comment-750 For Symbian N^2/3 when hardened, I'd like to see some integration or downloadable add-on service pack supporting RSA 2stage logon support for corporate mail. Many corporate national banking institutions use RSA's HardToken distribution to end users to have them access Exchange OWA or iNotes WebAccess for corporate mail. This allows the corporation much more security in utilizing a PIN + TokenCode (which changes every 60seconds randomly and encrypted and to be in sync with their servers. I'm not asking for Nokia or Symbian Foundation to license the connection to RSA's servers, but to allow for this 2nd stage logon. I've worked with 2 corporations - 1 public a bank & the other private - an associate corporate restructuring company (McKinsey & Company); where use of RSA Software Token was intregrated into laptops to allow iNotes access remotely. Unfortunately with RoadSync, Mail for Exchange, and Lotus Traveler on ANY platform there is no direct support or solution to this. IF Symbian Foundation & Nokia wish to take on the corporate business market from RIM they really need to consider this option. For Symbian N^2/3 when hardened, I’d like to see some integration or downloadable add-on service pack supporting RSA 2stage logon support for corporate mail. Many corporate national banking institutions use RSA’s HardToken distribution to end users to have them access Exchange OWA or iNotes WebAccess for corporate mail. This allows the corporation much more security in utilizing a PIN + TokenCode (which changes every 60seconds randomly and encrypted and to be in sync with their servers. I’m not asking for Nokia or Symbian Foundation to license the connection to RSA’s servers, but to allow for this 2nd stage logon. I’ve worked with 2 corporations – 1 public a bank & the other private – an associate corporate restructuring company (McKinsey & Company); where use of RSA Software Token was intregrated into laptops to allow iNotes access remotely. Unfortunately with RoadSync, Mail for Exchange, and Lotus Traveler on ANY platform there is no direct support or solution to this. IF Symbian Foundation & Nokia wish to take on the corporate business market from RIM they really need to consider this option.

]]> By: A touching welcome in Las Vegas « Symbian Foundation Blog http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-598 A touching welcome in Las Vegas « Symbian Foundation Blog Wed, 01 Apr 2009 07:19:34 +0000 http://blog.symbian.org/?p=396#comment-598 [...] to indicate a simple approach required for Symbian Foundation to succeed in the US,“If you, release it they will [...] [...] to indicate a simple approach required for Symbian Foundation to succeed in the US,“If you, release it they will [...]

]]> By: How To Build A Symbian Foundation Smartphone | CNN Showbiz http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-553 How To Build A Symbian Foundation Smartphone | CNN Showbiz Sun, 29 Mar 2009 14:25:07 +0000 http://blog.symbian.org/?p=396#comment-553 [...] graphics that David provides, it’s rather clear. Essentially, the Symbian Foundation releases (Detailed here) will be modular - made up of various specific modules. A contacts module, a calendar module, a web [...] [...] graphics that David provides, it’s rather clear. Essentially, the Symbian Foundation releases (Detailed here) will be modular – made up of various specific modules. A contacts module, a calendar module, a web [...]

]]> By: E71 user http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-541 E71 user Sun, 29 Mar 2009 02:55:24 +0000 http://blog.symbian.org/?p=396#comment-541 Sorry if this question has already been answered to, I did read this long thread but not all of it word by word (similar questions were though) So about that question. I just bought Nokia E71 - 1 which has s60 3rd edition FP1 as you know. Anyway after I heard of this news, I first was thinking that this is just great. But is there a chance to upgrade my E71 OS to this new version? After all E71 is quite popular I think.. Also one other thing comes to my mind. Theres been lot talk about QT for S60 with C++, but will these new releases of Symbian allso give Python even better support that there was earlier? Maybe some decent Python-QT support and tools for programming.. Sorry if this question has already been answered to, I did read this long thread but not all of it word by word (similar questions were though)

So about that question. I just bought Nokia E71 – 1 which has s60 3rd edition FP1 as you know. Anyway after I heard of this news, I first was thinking that this is just great. But is there a chance to upgrade my E71 OS to this new version? After all E71 is quite popular I think..

Also one other thing comes to my mind. Theres been lot talk about QT for S60 with C++, but will these new releases of Symbian allso give Python even better support that there was earlier? Maybe some decent Python-QT support and tools for programming..

]]> By: Building phones « Symbian Foundation Blog http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-489 Building phones « Symbian Foundation Blog Wed, 25 Mar 2009 10:32:23 +0000 http://blog.symbian.org/?p=396#comment-489 [...] Every six months, the Symbian Foundation identifies a group of these packages as working together particularly well (with specified versions): this group forms a Symbian platform release, with a name such as Symbian^2 or Symbian^3 - in general, Symbian^N, or S^N for short.  Not every package features in every platform release.  There are also packages of software that are hosted outside the foundation altogether (shown in pink in this picture).  Some of these will be commercially licenced software. [...] [...] Every six months, the Symbian Foundation identifies a group of these packages as working together particularly well (with specified versions): this group forms a Symbian platform release, with a name such as Symbian^2 or Symbian^3 – in general, Symbian^N, or S^N for short.  Not every package features in every platform release.  There are also packages of software that are hosted outside the foundation altogether (shown in pink in this picture).  Some of these will be commercially licenced software. [...]

]]> By: jaded moon studios » Blog Archive » What the Nokia E71x and the Symbian Foundation could mean for the E71 http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-454 jaded moon studios » Blog Archive » What the Nokia E71x and the Symbian Foundation could mean for the E71 Sun, 22 Mar 2009 23:26:36 +0000 http://blog.symbian.org/?p=396#comment-454 [...] the Symbian Foundation announcing their release plan for 2 releases of their platform each year, again I wonder if this indicates more software updates [...] [...] the Symbian Foundation announcing their release plan for 2 releases of their platform each year, again I wonder if this indicates more software updates [...]

]]> By: Lu http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-416 Lu Fri, 20 Mar 2009 01:04:02 +0000 http://blog.symbian.org/?p=396#comment-416 David, I would like to thank you for a reply to some questions and concerns I have about the Symbian Platform. You mention that we can upgrade the operating systems on our phones using s60 3rd but yet at the same time we can't. I would believe that statement if I would be able to upgrade to s60 FP2. Now that is Nokia's doing for what ever reason they may have but given the "Symbian Foundation" is an organization in itself it should not follow that method. I hope you have taken notice of a following theme here that a lot of symbian users in the future would like to be able to upgrade the OS with a current phone that they may be using at the time instead of having to buy a whole new phone just to attain the new version. Also I would think that any new upgrades of the OS would come from Symbian Foundation allowing a user on their own to upgrade and not come from the manufacturer of the handset, the manufacture of the handset what should do is just update the bios on the handset for any tweaks or problems there are. Just like windows and all the other computers out there. Let developers freely create programs for the Symbian. Symbian signed though was meant to protect users it create a mess not only for developers but for end users such as myself and has allowed to developers to go elsewhere in support of other platforms. (thats how it feels like in the U.S. anyways) Hopefully the GUI of future Symbian is newly designed and allowed to be more personalized but the user (IE font changes, back ground pictures, start up animation, cosing animation etc) . I hope well for it but look at other OS's out there and start letting people use current handset to update s60 (sort like a min standard of phone hardware to run the newest s60 platform). Coming from the 6620 to N95-3 though there were some changes such as a stand by apps and a new multimedia menu I feel like it was the same old OS underneath. Also bewilderment with why there is a FP1 and FP2 rift has left a bad taste in my mouth with symbian. Don't do this in the future, if a phone is running symbian n^2 allow it to upgrade to the latest updated tweaked version, it's not like Microsoft made everyone get a whole new computer to run XP Service Pack 3. David,

I would like to thank you for a reply to some questions and concerns I have about the Symbian Platform.

You mention that we can upgrade the operating systems on our phones using s60 3rd but yet at the same time we can’t. I would believe that statement if I would be able to upgrade to s60 FP2. Now that is Nokia’s doing for what ever reason they may have but given the “Symbian Foundation” is an organization in itself it should not follow that method. I hope you have taken notice of a following theme here that a lot of symbian users in the future would like to be able to upgrade the OS with a current phone that they may be using at the time instead of having to buy a whole new phone just to attain the new version. Also I would think that any new upgrades of the OS would come from Symbian Foundation allowing a user on their own to upgrade and not come from the manufacturer of the handset, the manufacture of the handset what should do is just update the bios on the handset for any tweaks or problems there are. Just like windows and all the other computers out there.

Let developers freely create programs for the Symbian. Symbian signed though was meant to protect users it create a mess not only for developers but for end users such as myself and has allowed to developers to go elsewhere in support of other platforms. (thats how it feels like in the U.S. anyways)

Hopefully the GUI of future Symbian is newly designed and allowed to be more personalized but the user (IE font changes, back ground pictures, start up animation, cosing animation etc) . I hope well for it but look at other OS’s out there and start letting people use current handset to update s60 (sort like a min standard of phone hardware to run the newest s60 platform).

Coming from the 6620 to N95-3 though there were some changes such as a stand by apps and a new multimedia menu I feel like it was the same old OS underneath. Also bewilderment with why there is a FP1 and FP2 rift has left a bad taste in my mouth with symbian. Don’t do this in the future, if a phone is running symbian n^2 allow it to upgrade to the latest updated tweaked version, it’s not like Microsoft made everyone get a whole new computer to run XP Service Pack 3.

]]> By: EVVJSK http://blog.symbian.org/2009/03/12/introducing-the-release-plan/#comment-399 EVVJSK Thu, 19 Mar 2009 14:08:24 +0000 http://blog.symbian.org/?p=396#comment-399 David, Something that is somewhat related to upgrade cycle (or maybe that may provide functionality that would bridge the gap until an upgrade is available) is functionality provided by Skyfire mobile browser. I love the functionality that Skyfire browser adds to my E71. I would be interested to know if you plan to partner with Skyfire in any way (to insure they continue to bring functionality to Symbian/Nokia that currently can't be handled by Symbian developers) or if you see them as a technology that hinders new phone sales? An example of Skyfire technology is the ability to display full Flash content on Symbian devices (as Flash Lite doesn't seem to getting wide support from sites). Keep up the good work! David,
Something that is somewhat related to upgrade cycle (or maybe that may provide functionality that would bridge the gap until an upgrade is available) is functionality provided by Skyfire mobile browser. I love the functionality that Skyfire browser adds to my E71. I would be interested to know if you plan to partner with Skyfire in any way (to insure they continue to bring functionality to Symbian/Nokia that currently can’t be handled by Symbian developers) or if you see them as a technology that hinders new phone sales? An example of Skyfire technology is the ability to display full Flash content on Symbian devices (as Flash Lite doesn’t seem to getting wide support from sites). Keep up the good work!

]]>