What people normally do in other projects I'm involved with is that they
make the API key a configuration option and pass a sample API key.  That
way, anyone who uses the application is required to get an API key for the
application from the third party, and the developer does not have to worry
about his key getting misused.  The instructions for installing the app then
include details about how each user goes out and gets their own API key.

By doing it this way, you don't have keep anything secret and you should be
able to upload all the source into free.

Personally, I've avoided the religious wars about different open source
software licenses, and I'll leave that and other questions to people with
stronger opinions on these topics.

Aldon
http://www.orient-lodge.com/N900

  -----Original Message-----
  From: maemo-developers-boun...@maemo.org
[mailto:maemo-developers-boun...@maemo.org]on Behalf Of Sanjeev (EIPI)
  Sent: Saturday, February 06, 2010 2:29 PM
  To: maemo-developers@maemo.org
  Subject: [New Developer]: Questions - Python Packaging / Free or Non-Free
/ Software Licensing


  Hello,

  I am developing a python/QT application for Fremantle.  This is my first
application for Maemo, so I have been on a steep learning curve for the past
2 weeks for things related to the SDK, python, QT, etc.  I finally have it
(mostly) working within scratchbox, and on the device, but it is not yet
packaged.  I am using a proprietary API within the code which requires my
personal credentials to be passed.  The credentials are in the form of a
unique alpha-numeric string.  The company that has issued these credentials
has asked that they are not to be made public.  I am able to use their API
so long as I adhere to this and a few other restrictions that they have in
place.  Some questions I now have:

  1. I am researching how to package my python application for maemo.org
Extras-devel.  Due to the restrictions placed on the API login credentials,
I am unclear whether the app can use the 'free' distribution.  I am not at
all worried about exposing the source code, but am not sure if that can be
done without revealing the API credentials.  Is there any way to distribute
my application in 'free', or does it have to be under 'non-free'?

  2. If it is 'non-free', am I correct in my understanding that none of the
source code gets uploaded to maemo.org?

  3. I have seen both pypackager and py2deb being mentioned in the wiki
articles on python packaging.  Which one should I use?  I understand that
pypackager does not have a GUI for Fremantle yet - should I wait for that?

  4. Do I use the Extras Assistant [1] after creating my package?  Does it
allow for both free and non-free?

  5. Software licensing - I know nothing about this.  What are my options
for free and for non-free?  I understand that Mauku is non-free, and is
therefore under copyright by its developer.

  Sorry if any of this is very basic.  My interest in Maemo is now growing
into the area of application development, and that is something that I do
not do professionally.  In fact, I am very far from this area in my day job.

  Many thanks,

  Sanjeev

  [1] https://garage.maemo.org/extras-assistant/index.php


  --
  EIPI
  Mobile Tablets! Blog: http://mobiletablets.blogspot.com

_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Reply via email to