5:02 p.m.
Hi all,
I have a third part OEM layer.
According to the oFono architecture and standards can any one *suggest* the
good *approach* to use the third part OEM layer @ oFono.
Regards,
Satya.
5:58 p.m.
Hi Satya,
I have a third part OEM layer.
According to the oFono architecture and standards can any one suggest
the good approach to use the third part OEM layer @ oFono.
oFono is licensed under GPL v2 and as long as your OEM layer is
compatible with GPL v2 you can use it.
Regards
Marcel
4:41 p.m.
Hi Marcel,
In this case is it required to make the third part OEM layer as OPEN-SOURCE.
Thanks,
-- Satya.
Hi Satya,
I have a third part OEM layer.
According to the oFono architecture and standards can any one suggest
the good approach to use the third part OEM layer @ oFono.
oFono is licensed under GPL v2 and as long as your OEM layer is
compatible with GPL v2 you can use it.
Regards
Marcel
2010/6/25 సత్య కిషోర్ <satyakishore.kalva(a)gmail.com>
Hi all,
I have a third part OEM layer.
According to the oFono architecture and standards can any one suggest the good approach
to use the third part OEM layer @ oFono.
Regards,
Satya.
8:03 p.m.
Hi Satya,
a gently reminder that this mailing list doesn't like top posting.
In this case is it required to make the third part OEM layer as
OPEN-SOURCE.
Yes, every plugin, driver or extension of oFono has to be released as
open source under a GPL compatible license. As in general you have to be
compatible with the license of the project. If in doubt ask a lawyer.
Only the client applications, like the dialers etc., are except from
this. They use D-Bus as communication protocol.
Regards
Marcel
4465
days inactive
4468
days old
3 comments
2 participants
participants (2)
-
Marcel Holtmann -
సత్య కిషోర్