> That's definitely good news, and something that we should look at
once 
> there is a proper 1.6 release. The current version needs a bit of 
> cleanup I think and the user's guide document at least needs to be 
> updated before I'm comfortable having PuTTY in the Ovi Store. However I 
> really think it should be handled by one of the active developers so 
> that it can be supported properly in case there are any problems, and 
> I'd also like to understand if there are any promises we'd need to give 
> in terms of support, quality, localization etc that could be problematic.

Petteri,

Understood. Here's how it's going to look like:

- first you guys will have to apply for Ovi Publisher's ID. That's pretty fast 
but costs 50 euro. A private person can do it, you don't have to be a company
- then you will have to apply for the dev cert. They will send you 5 UIDs , a 
cert an a key file. Details in the link given in my first post.
- once you update docs, finish your development, etc etc, you will submit the 
unsigned .sis file and one of the UIDs to Ovi, they do the signing for 
distribution.
- you would have to give them a support email ( but that only goes to their QA 
team, not to the customers ) and promise to respond within 48 hours. 
  You also will have to give them a support webpage but you already have that.
- localization & quality are non-issues. I am sure putty will easily pass their 
QA.

It appears Nokia is finally starting to see the light - recently they've been 
actively loosening all the restrictions that plague your average Symbian C++ or 
J2ME dev.

best,

L. 


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
s2putty-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/s2putty-developers

Reply via email to