[dev] Jira cleanup

2017-03-30 Thread Dave Thaler
I would add "Other" for anything that's specific to another OS that's not fully 
supported (e.g. macosx work).

From: Christian Gran [mailto:g...@lynxtechnology.com]
Sent: Thursday, March 30, 2017 6:41 AM
To: Dave Thaler 
Cc: iotivity-dev at lists.iotivity.org
Subject: Re: [dev] Jira cleanup

Hi Dave,

major OS sounds good.
Is this the list we want to start with?
Ubuntu, Windows, Tizen, Android

Updated: https://wiki.iotivity.org/jira_proposed_changes?

[dev] 答复: About supporting threadX OS

2017-03-30 Thread Thiago Macieira
On quinta-feira, 30 de mar?o de 2017 18:18:54 PDT sunlf wrote:
> Hi, All,
> 
> About OS and compiler, such as ThreadX OS, IAR compiler, are there any plans
> that IoT will support? Now IoT support Microsoft Visual Studio, GCC and
> Clang, but for embedded system, these are not enough.

Hello Jason

The plans to support any new compiler are the plans for anyone to contribute 
such a support. If you are interested in the support, we welcome your 
contribution to make it happen.

If no one volunteers, then it will not be supported.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



[dev] Request to postpone IoTivity 1.3-rel branch date from April 7th to April 17th

2017-03-30 Thread Mitch Kettrick
Hi Nathan,



I don't think pushing this out one week will impact PF #12 too much.
Vendors will still have one week to integrate v1.3 if they choose.



I would rather have as many security CRs implemented in v1.3 than trying to
rush and miss out on some key features.  As Nathan said, so many of the
security CRs are related to and dependent on each other.  Trying to pull out
one or two of the CRs that Nathan is working on will potentially make the
whole thing fall apart.  Putting it back together will most likely require
normative spec changes that should be avoided when possible.



This is not my decision but I don't think Nathan's request sounds
unreasonable.



Mitch



From: Heldt-Sheller, Nathan [mailto:nathan.heldt-shel...@intel.com] 
Sent: Thursday, March 30, 2017 4:51 PM
To: iotivity-dev at lists.iotivity.org; oswg at openconnectivity.org;
security_os_tg at openconnectivity.org
Cc: ???(Uze Choi) (uzchoi at samsung.com); Mitch Kettrick; ??? ?? OCF Sec
Subject: Request to postpone IoTivity 1.3-rel branch date from April 7th to
April 17th



Hello OSWG, IoTivity-dev and OSWG Security TG,



As many of you know, being a volunteer project, we've been short-handed on
developers, and struggling to find resources for several Security features.
I've been asking for months for additional help with a few features, but
being unable to find volunteers, I have picked up implementation of these
myself.



However just after returning from the Amsterdam F2F, I learned that one of
our key development resources was moving on to another job.  I'm not able to
pick up this slack, since I'm already overloaded.   And because of the
inter-dependent nature of these features, although myself and others have
tried, it has been infeasible to cut out any additional CRs from the
Security Spec. to do so would be more work than just implementing what we
have (not to mention significant normative CRs).



The good news is that just today I've gotten some temporary resource
commitment from inside Intel, to pick up these newly-ownerless tasks.
However I think because of the time lost over the past few weeks, and
spin-up required, it would greatly increase our odds of success to have
another week of development time before creating the 1.3-rel branch.
Moreover, at the last OSWG Security TG meeting, I believe Dongik Lee
mentioned that their team would like a little more time (if possible) to
implement a couple additional items they're working on.


TLDR; if there is not a hard-stop reason why we need to branch next Friday
April 7th, I propose we take an additional work-week (plus the weekend for
those of us who need to work through it) and create the 1.3-rel branch on
Monday April 17th.



Uze, I think the decision is yours ultimately, but I'm sending to the entire
list to gather feedback in case there are folks counting on this April 7th
date for a reason we're not aware of.



Thanks,
Nathan Heldt-Sheller

OSWG Security TG Chair





---
This email has been checked for viruses by AVG.
http://www.avg.com
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170330/049f4e67/attachment.html>


[dev] About supporting threadX OS

2017-03-30 Thread Thiago Macieira
On quinta-feira, 30 de mar?o de 2017 17:36:01 PDT sunlf wrote:
> Hi IoT devs,
> 
> Now I want to use a WIFI module(threadX OS) to run OCF code.
> 
> Does IoT support threadX OS now?

Hello Jason

According to Wikipedia[1], ThreadX is a real-time operating system. If I'm 
reading the page correctly, this would be a target for IoTivity-Constrained, 
not Standard.

There's no port for ThreadX right now. If you want to use this OS, you'll need 
to write that platform-specific code yourself. It shouldn't be too difficult: 
take a look at the other ports in the aptly-named "port/" subdir of the 
Constrained source code. If you have difficulty in writing the code, please ask 
and we'll do what we can to help you.

[1] https://en.wikipedia.org/wiki/ThreadX

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



[dev] IoTivity building for ARM architecture

2017-03-30 Thread Thiago Macieira
On segunda-feira, 27 de mar?o de 2017 14:10:09 PDT Mats Wichmann wrote:
> > Should I remove all flags('-pthread') in OCF scripts? Here will be a lots
> > things to do then.
> > 
> > Do you have any suggestions?
> 
> what is your target OS?  is there some reason why it doesn't support
> pthreads?

I think the question is "what compiler is that". The -pthreads argument is 
interpreted by the compiler.

IoTivity only supports building with Microsoft Visual Studio, GCC and Clang. 
If you have another compiler, we need you to contribute a port to IoTivity 
first.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



[dev] Should IoTivity Arduino support be dropped?

2017-03-30 Thread Thiago Macieira
On quinta-feira, 23 de mar?o de 2017 14:47:23 PDT Gregg Reynolds wrote:
> ok, i'll bite. what are the duties of the Arduino sub-maintainer?  I'm
> interested but may not have the time.

First, write the port for IoTivity-Constrained to Arduino.

After that is done, work with IoTivity-Constrained maintainer (Kishen) to keep 
it working. When there are new features being added in Constrained, they may 
need functionality in the platform-specific code.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



[dev] Make OCProcess( ) needed only on single threaded platform

2017-03-30 Thread Way Vadhanasin
ailto:iotivity-dev at lists.iotivity.org>

https://lists.iotivity.org/mailman/listinfo/iotivity-dev





[cid:image001.gif at 01D2A936.3B022490]

[http://ext.samsung.net/mail/ext/v1/external/status/update?userid=jw0213.jung=bWFpbElEPTIwMTcwMzI5MDcxOTA2ZXBjbXMxcDUwZDFhMjg1MDgwZTAzMTBlMWJkZWIzZDIzZTlkNTE2MiZyZWNpcGllbnRBZGRyZXNzPVdheWFrb3JuLlZhZGhhbmFzaW5AbWljcm9zb2Z0LmNvbQ__]
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170330/d36c3fc7/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13402 bytes
Desc: image001.gif
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170330/d36c3fc7/attachment.gif>


[dev] liboctbstack.so - right email

2017-03-30 Thread Natalia Theologou


Hello,


I follow these instructions - Sample Application:


<https://wiki.iotivity.org/security_resource_manager>
https://wiki.iotivity.org/security_resource_manager
security_resource_manager [Wiki] - 
wiki.iotivity.org<https://wiki.iotivity.org/security_resource_manager>
wiki.iotivity.org
Security Resource Manager (SRM) provides management of Secure Virtual Resources 
(SVRs) and access control based on policies defined by SVRs. SVRs are defined 
in a ...

but when I execute the

$ ./ocserverbasicops &

command in the terminal it returns the error:

./ocserverbasicops: error while loading shared libraries: liboctbstack.so: 
cannot open shared object file: No such file or directory

However the liboctbstack.so is in the folder /out/<...>/release  
and I have executed the $ export 
LD_LIBRARY_PATH=/out/<...>/release  command.



Have you got any idea on how to solve this?


Thank you in advance,
Natalia
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170330/30ed725d/attachment.html>


[dev] onGET Response error: 29

2017-03-30 Thread Natalia Theologou
Hello,


I follow these instructions - Sample Application:


<https://wiki.iotivity.org/security_resource_manager>
https://wiki.iotivity.org/security_resource_manager
security_resource_manager [Wiki] - 
wiki.iotivity.org<https://wiki.iotivity.org/security_resource_manager>
wiki.iotivity.org
Security Resource Manager (SRM) provides management of Secure Virtual Resources 
(SVRs) and access control based on policies defined by SVRs. SVRs are defined 
in a ...

but when I execute the

$ ./ocserverbasicops &

command in the terminal it returns the error:

./ocserverbasicops: error while loading shared libraries: liboctbstack.so: 
cannot open shared object file: No such file or directory

However the liboctbstack.so is in the folder /out/<...>/release  
and I have executed the $ export 
LD_LIBRARY_PATH=/out/<...>/release  command.



Have you got any idea on how to solve this?


Thank you in advance,
Natalia
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170330/cf2fd041/attachment.html>


[dev] onGET Response error: 29

2017-03-30 Thread Natalia Theologou
Hello,


I would like a little bit help.

I am following these instructions:
https://www.iotivity.org/documentation/linux/getting-started
Getting Started | 
IoTivity<https://www.iotivity.org/documentation/linux/getting-started>
www.iotivity.org
Source code. There are 2 methods to get the source code. Downloading most 
stable source from here. Getting source directly from gerrit. Gerrit is a 
web-based code ...


(I downloaded the iotivity source code and didn't followed the five steps)
When I execute the
$ ./simpleclient
command in the terminal it returns in the end the error:


Found another resource, ignoring
onGET Response error: 29

and can't execute GET, PUT.
Simpleserver is in another terminal.


Have you got any idea on how to solve this?


Thank you in advance,
Natalia
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170330/f49e7651/attachment.html>


[dev] Jira cleanup

2017-03-30 Thread Christian Gran
Hi,

looks like everyone likes the own project idea :-)
Updated the wiki: 

[dev] Jira cleanup

2017-03-30 Thread Christian Gran
Hi Dave,

actually the list was just taken from the list of IoTivity projects:
https://wiki.iotivity.org/projects_and_functions

Totally agree that there is some overlap between bridging in general and the 
more concrete bridges.
The idea is simply that - when a new issues is created - it can be correlated 
to the source code,
which in general resides in a sub folder of one of these ?projects?/bridges.

I hope this does explain, why there is a proposal to have one component per 
?project? listed on the IoTivity projects page.
It shall help to assign issues/bugs found to the correct maintainers.
But may be this is a wrong idea and this would not help in assigning bugs at 
all?

thanks
  Christian


On 29 Mar 2017, at 20:12, Dave Thaler mailto:dthaler 
at microsoft.com>> wrote:

Under proposed components, the wiki page shows:
* Bridging (Todd Malsbary)
* UPnP Bridge (Rick Bell)
* AllJoyn-Bridge (Todd Malsbary)

I don't understand the distinction between the first one and the others, it may 
just be a naming thing.
In the OCF bridge spec, the term "bridge" is the term for a device independent 
of protocol, and
"translator" is the term for a protocol-specific plugin in a bridge.

So would "Bridging" include any translators or not?  Shouldn't "AllJoyn-Bridge" 
be "AllJoyn translation"
or something similar, if it's a separate JIRA component?   Or we could combine 
translators into a common
Bridging component in JIRA.  But if we break them out then we should 
consistently break out a new component
for every translator for every protocol (which might seem excessive).

Dave

-Original Message-
From: iotivity-dev-bounces at 
lists.iotivity.org<mailto:iotivity-dev-boun...@lists.iotivity.org> 
[mailto:iotivity-dev-
bounces at lists.iotivity.org<mailto:bounces at lists.iotivity.org>] On Behalf 
Of Mats Wichmann
Sent: Tuesday, March 28, 2017 9:20 AM
To: Christian Gran mailto:gran at 
lynxtechnology.com>>; iotivity-
dev at lists.iotivity.org<mailto:dev at lists.iotivity.org>
Subject: Re: [dev] Jira cleanup

On 03/27/2017 11:31 PM, Christian Gran wrote:
Hi,

is there still something that needs to be changed here?
https://wiki.iotivity.org/jira_proposed_changes
https://wiki.iotivity.org/jira_how_to_use


thanks
 Christian

I'd like to see the "proposed changes" page implemented, doesn't mean we
have to be completely done with the other discussions.  Were there answers
for the bits with questions? (mainly whether to have any presence of iotivity-
constrained and iotivity-node). The updated/added components would be
helpful in categorizing.



___
iotivity-dev mailing list
iotivity-dev at lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170330/85ddbbf7/attachment.html>


[dev] Jira cleanup

2017-03-30 Thread Christian Gran
Hi Dave,

major OS sounds good.
Is this the list we want to start with?
Ubuntu, Windows, Tizen, Android

Updated: https://wiki.iotivity.org/jira_proposed_changes?

[dev] liboctbstack.so - right email

2017-03-30 Thread Mats Wichmann
On 03/30/2017 07:38 AM, Natalia Theologou wrote:
> 
> 
> Hello,
> 
> 
> I follow these instructions - Sample Application:
> 
> 
> 
> https://wiki.iotivity.org/security_resource_manager
> security_resource_manager [Wiki] - 
> wiki.iotivity.org
> wiki.iotivity.org
> Security Resource Manager (SRM) provides management of Secure Virtual 
> Resources (SVRs) and access control based on policies defined by SVRs. SVRs 
> are defined in a ...
> 
> but when I execute the
> 
> $ ./ocserverbasicops &
> 
> command in the terminal it returns the error:
> 
> ./ocserverbasicops: error while loading shared libraries: liboctbstack.so: 
> cannot open shared object file: No such file or directory
> 
> However the liboctbstack.so is in the folder 
> /out/<...>/release  and I have executed the $ export 
> LD_LIBRARY_PATH=/out/<...>/release  command.
> 
> 
> 
> Have you got any idea on how to solve this?

you shouldn't even need to export LD_LIBRARY_PATH.

try:

ldd ocserverbasicops

and:

readelf -d ocserverbasicops

to get some idea what's going on. The latter should indicate a library
rpath already pointing to where the library is, something like this:

 0x000f (RPATH)  Library rpath:
[/home/mats/iotivity.work/out/linux/x86_64/release/]