[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [dsdp-pmc] Code contribution
|
Title: Code contribution
Hi,
The reason to try to bundle those binaries with MTJ is that
if we don't, then MTJ cannot be used as such with Nokia terminals. You cannot
deploy sw to terminal without those binaries.
Answers to your questions:
So everybody would use these if they ever plan to deploy to
Nokia device.
Every developers can use those, but of course if they want
to deploy to a phone they have to have a phone. With these libraries/binaries
any Nokia phone will work.
They can get, but it is not straight forward and fully
manual thing to do.
Other route is that developers should download those
binaries separateley from Nokia (or in case an other vendor from somewhere
else) and take them "out" from Nokia PC Suite and put them to right places etc.
This is just quite an hassle for developers and we are thinking that if we could
put those binaries (and hopefully we would get similar binaries from other
terminal vendors also) to MTJ it would work kind of out of the box without
developers to go and start to get missing pieces from here and
there.
And this is planned feature of MTJ. Every device vendor can
develop a plug-in to connect MTJ to their devices. Some vendors don't want to
open up those interfaces so we have to have possibility to have drivers in both
source and binary format so that we wouldn't exclude people/companies who don't
have or don't want to provide interface spec/source code to access
devices.
And just to highlight: Target is to really help
developers using MTJ and there is no other Nokia benefit than MTJ would work
with Nokia terminals.
Licensing: We most likely would have internal problem with
those licenses. My unit is not producing those and we have had quite a long
discussion to even get those binaries internally. I quess that EPL would be
possible, but unfortunately it most likely would take something from half a year
to year to do all internal Nokia stuff to get that done.
mho
From:
dsdp-pmc-bounces@xxxxxxxxxxx [mailto:dsdp-pmc-bounces@xxxxxxxxxxx] On Behalf
Of ext Oberhuber, Martin
Sent: 27 September, 2006
11:19
To: DSDP PMC list
Subject: RE: [dsdp-pmc] Code
contribution
Hello Mika,
What kind of users would you expect to use these
binaries?
Can every ordinary user get such a Nokia terminal easily,
and use it for programming?
Can ordinary users download these libraries from some
Open Nokia server right now?
I'm wondering whether the Open Source Eclipse Framework
is the right place for such vendor specific programs. In my understanding, the
charter of the Eclipse foundation is to create Frameworks and Exemplary tools
to support vendors creating their specific tooling.
As such, I'd rather not expect vendor specific binaries
in Open Source. There is an exception, of course, if you think that these
libraries would provide a very good example to show ISVs how the APIs can be
used in order to extend the framework. Was that your
intention?
Your
license also talks about "Source Form". Would you include the sources for your
libs with the contribution?
The
license does read similar to the EPL. Do you see a chance that Nokia would
proivde these libs under EPL?
Cheers,
--
Martin Oberhuber
Wind River Systems,
Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
Hi,
I would like to get your vote to include two
binaries to MTJ so that we can start due diligence process.
Those binaries are CONA.jar and COnnJNI.dll and
they are used to connect MTJ to Nokia PC suite, which is needed in deploying
applications to Nokia terminals.
I.e. without these binaries it is not possible to
move application from Eclipse to a terminal.
Those binaries are owned by Nokia and copyright
text is listed below.
-------------------------------------------------------------------------
Copyright (c) 2005 - 2006, Nokia
Corporation. All rights reserved.
Redistribution and use in
source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
- Redistributions of source code
must retain the above copyright notice, this list of conditions and the
following disclaimer.
- Redistributions in binary form
must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials
provided with the distribution.
- Neither the name of the NOKIA
nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE
COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE."
--------------------------------------------------------------------------
Could you please make your vote.
mho