From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Nash, George
Sent: Thursday, March 23, 2017 1:41 PM
To: Christian Gran ; iotivity-dev at
lists.iotivity.org
Subject: Re: [dev] Jira cleanup
Christian,
I took the time to work through
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/0e6e4a57/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not availab
at gmail.com
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/627ec443/attachment.html>
First of all,
resource/c_common/include for all headers under the resource/c_common is
acceptable idea?
Any issue from here or good technic?
BR, Uze Choi
-Original Message-
From: Daniel Mihai [mailto:daniel.mi...@microsoft.com]
Sent: Friday, March 24, 2017 12:02 AM
To: ??? (Uze Choi);
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/3daf792a/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: ?? ?? .
Type: image/gif
Size: 13402 byte
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/b2fe293c/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: ?? ?? .
Type: image/gif
Size: 13402 byte
/attachments/20170324/f6be6eb0/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13402 bytes
Desc: ?? ?? .
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/f6be6eb0/attachment.gif>
Hi,
thanks Dave and George, this is very good input.
In my oinion the minimal thing we should do with tickets we want to keep is:
1) agree on someone who owns the ticket (assign)
2) check in 3 month if the ticket has been worked on (may be split into other
tickets, resolved as outdated, ?)
For
__
iotivity-dev mailing list
iotivity-dev at lists.iotivity.org<mailto: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/20170324/26eb33d6/attachment.html>
cool - thanks :-)
On 23 Mar 2017, at 21:52, Heldt-Sheller, Nathan mailto:nathan.heldt-sheller at intel.com>> wrote:
Hi folks,
FYI I also scrubbed the entire open JIRA tickets list and:
1. Applied a ?security? label to anything security-related that I found.
2. Marked as Resolved
e/IOT-347
maybe this could be built by CI too ? Waiting for feedback on tracker too
Regards
--
mailto:philippe.coval at osg.samsung.com gpg:0x467094BC
https://blogs.s-osg.org/author/pcoval/
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/7485e0ac/attachment.html>
Hi Bt.jo,
In Mynewt we use BLE GATT, and we leverage the underlying BLE security
(4.2 secure connections) and bind that as a security context for OIC.
If you wanted to run DTLS, I?d recommend also putting IPv6 over BLE,
and then running DTLS on top of that. IP is yet more overhead, but then
Could someone who has the appropriate rights (I presume that's "admin":
Habib, Rick or Dan) push the button to update the Coverity scan? The
last one is a bit long in the tooth, dating back to Sept. 18, quite a
bit has changed.
om<mailto:binh01t2 at gmail.com>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/4264df68/attachment.html>
I am not sure I like the practice of closing a bug just because it is old or
has not been worked on.
I think it is very good to review the old tickets to check it they are still
valid. (I don?t think a single open ticket below the 100 in the list was worth
keeping open.)
Currently Jira is
HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/2ad223ba/attachment.html>
On 03/24/2017 11:31 AM, Nash, George wrote:
> Prathamesh Ranade,
> Scons is not finding the Visual Studio community version. I personally don?t
> have the same setup so there are just things to try I don?t know if they will
> work. They range in the order of what I think is the easy to hardest.
On 03/24/2017 01:02 PM, Mats Wichmann wrote:
>
> I've done the following, and an
> (a) constructed a python virtual environment using 2.7 (my default
> python is 3.6 on this machine, but that won't work for scons)
> (b) launch the visual studio-aware version of a command shell ("VS2015
> x86 x64
On 03/24/2017 01:17 PM, Mats Wichmann wrote:
> On 03/24/2017 01:02 PM, Mats Wichmann wrote:
>
>>
>> I've done the following, and an
>> (a) constructed a python virtual environment using 2.7 (my default
>> python is 3.6 on this machine, but that won't work for scons)
>> (b) launch the visual
This is not a big deal but my opinion is that having a single header file for
each directory under c_common is an inefficient use of directories.
I look at c_common as similar to "the IoTivity CRT". I believe that a typical
CRT has malloc.h and stdlib.h in a single directory. There is no:
ivity.org/mailman/listinfo/iotivity-dev
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/217b3ab8/attachment.html>
ubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/0f408799/attachment.html>
_
> 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/20170324/a946460b/attachment.html>
y-dev mailing list
iotivity-dev at lists.iotivity.org<mailto: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/20170324/a0b49a39/attachment.html>
le to make if you are in
charge of everything. jira tix should *never* be closed, only resolved.
g
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/ab2ab196/attachment.html>
currently 141 issues in Jira, that are in open state and have
> not been updated for more then 6 month now.
>
> The plan is to clean up Jira and close outdated tickets by end of March.
>
> If you see a ticket, that you still want to keep - please just add a
> comment to it.
>
> This will update the ?updated date? field and it will no longer be part of
> the filtered tickets.
>
>
>
> For the list of tickets, please use this Jira filter:
>
> status in (Open, "In Progress", Reopened, Assigned, "To Do", "In Review")
> AND updated <= -180d
>
>
>
> or just this link
>
> https://jira.iotivity.org/issues/?jql=status%20in%20(
> Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Assigned%
> 2C%20%22To%20Do%22%2C%20%22In%20Review%22)%20AND%20updated%
> 20%3C%3D%20-180d
> <https://jira.iotivity.org/issues/?jql=status%20in%20(Open,%20%22In%20Progress%22,%20Reopened,%20Assigned,%20%22To%20Do%22,%20%22In%20Review%22)%20AND%20updated%20%3C=%20-180d>
>
>
>
> Please feel free to comment, or if you have some more input how we can
> make sure that we only keep issues in Jira we are actually working on?.
>
>
>
> thanks
>
> Christian
>
>
>
> ___
> 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/20170324/89e14bfd/attachment.html>
tivity.org/pipermail/iotivity-dev/attachments/20170324/bf4a64d6/attachment.html>
27 matches
Mail list logo
