[C-safe-secure-studygroup] Agenda for meeting - Weds 31 Oct
Aaron Ballman
aaron at aaronballman.com
Wed Oct 31 18:35:37 GMT 2018
On Wed, Oct 31, 2018 at 2:15 PM Andrew Banks <andrew at andrewbanks.com> wrote:
>
> >> Clive will reach out to MISRA for a statement expressing what MISRA
> >> finds to be acceptable use of their IP within an ISO standard.
>
> To save Clive the effort, I will take over this action :-)
>
> There is a MISRA Technical Board meeting on Thursday next week (the 8th), and I will ask the question...
Thank you for the offer, Andrew! Clive and I will contact you off-list
to make sure we're all on the same page regarding what we're asking
after.
~Aaron
>
> Kind regards
> Andrew
> Chairman, MISRA C Working Group
>
>
> -----Original Message-----
> From: C-safe-secure-studygroup [mailto:c-safe-secure-studygroup-bounces at lists.trustable.io] On Behalf Of c-safe-secure-studygroup-request at lists.trustable.io
> Sent: 31 October 2018 17:44
> To: c-safe-secure-studygroup at lists.trustable.io
> Subject: C-safe-secure-studygroup Digest, Vol 23, Issue 18
>
> Send C-safe-secure-studygroup mailing list submissions to
> c-safe-secure-studygroup at lists.trustable.io
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup
>
> or, via email, send a message with subject or body 'help' to
> c-safe-secure-studygroup-request at lists.trustable.io
>
> You can reach the person managing the list at
> c-safe-secure-studygroup-owner at lists.trustable.io
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of C-safe-secure-studygroup digest..."
>
>
> Today's Topics:
>
> 1. Re: Agenda for meeting - Weds 31 Oct (Aaron Ballman)
> 2. Re: Agenda for meeting - Weds 31 Oct (Michael Wong)
> 3. Re: Agenda for meeting - Weds 31 Oct (Michael Wong)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 31 Oct 2018 13:07:54 -0400
> From: Aaron Ballman <aaron at aaronballman.com>
> To: C Safety and Security Study Group Discussion
> <c-safe-secure-studygroup at lists.trustable.io>
> Cc: aj.guillon at gmail.com
> Subject: Re: [C-safe-secure-studygroup] Agenda for meeting - Weds 31
> Oct
> Message-ID:
> <CAAt6xTvxSfZZoVGt=0eyxABioLQ5FqmONdK8S_a8ezoPS5uqsQ at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> We did not meet quorum for today's call, so we did not make progress
> on existing homework items. Attendees included: me, Clive Pygott,
> Michael Wong, and Charles Wilson.
>
> We had an informal discussion about the direction of the group,
> without reaching any binding decisions. The discussion centered around
> ways to resolve the issues the group is currently facing with IP
> challenges, quorum, and finding a permanent chair. The action items
> from the discussion were:
>
> Clive will reach out to MISRA for a statement expressing what MISRA
> finds to be acceptable use of their IP within an ISO standard.
> Charles is going to explore the possibility of stepping up as chair.
> Michael is going to email the study group reflector with information
> about other, related organizations working in the same space as we
> are. We may be able to liaise with these groups to entice some more
> domain experts to join the study group.
>
> We will reconvene on Nov 14th at 12pm ET to continue the discussion
> about the future of the group and hopefully we will have sufficient
> attendance to make binding decisions on how we want the study group to
> proceed.
>
> ~Aaron
> On Wed, Oct 31, 2018 at 5:54 AM Laurence Urhegyi
> <Laurence.Urhegyi at codethink.co.uk> wrote:
> >
> > Hi,
> >
> > Meeting today at 16:00 UTC, see here for local time:
> >
> > https://www.timeanddate.com/worldclock/fixedtime.html?msg=C+Safe+and+Secure+Study+Group&iso=20181031T16&p1=1440&ah=1&am=30
> >
> >
> > Outstanding actions
> > ~~~~~~~~~~~~~~~~~~~
> > * Clive to send out the revised update for ISO and ask for final review. [done]
> > * Laurence to push on ISO to sort out the Zoom account. [done - but need to
> > carry over]
> > * Laurence to begin chasing down the status of the homework. [done but also to
> > carry on]
> > * In the context of discussing Rule 11.6 - Martin to furnish proposal [0] with
> > another example. [done]
> >
> >
> > Agenda
> > ~~~~~~
> > Aaron's mail [0] from Pittsburgh. Quoting that:
> >
> > * Do you think we should continue to attempt to produce a standard
> > combing both safety and security rules for static analyzers?
> > * If the consensus is to continue forward,
> > * What is the best way for us to resolve the IP concerns before
> > April and are you willing to take on any or all of that effort?
> > * If you are a member of the ISO global directory, are you willing
> > to step up as chair? If you're not, are you willing to join ISO to
> > step up as chair?
> > * Are you able to help find more participants in either domain so
> > that we can address our quorum and expertise concerns?
> >
> > Fair warning: I plan to poll the question of whether we want to
> > disband the study group. It would be useful for me to know if you're a
> > regular attendee that is unable to attend the teleconference on Oct 31
> > but have a strong opinion.
> >
> >
> > Homework
> > ~~~~~~~~
> > Thanks to those who were able to respond to homework requests on the list. We
> > have three items we can cover.
> >
> >
> > Rules discussed on list:
> > ~~~~~~~~~~~~~~~~~~~~~~~~
> > * 11.6 - in progress, Martin [done] [0]
> > * 11.7 - Fulvio (in the context of Martin's additional example) [done] [1]
> > * 12.4 - Fulvio [done] [2]
> > * 13.1 - Clive [done] [3]
> >
> >
> > Not discussed on list:
> > ~~~~~~~~~~~~~~~~~~~~~~
> > * 12.1 - Aaron, please follow up on gitlab info with a post to list
> > * 12.2 - Clive (revive old post)
> > * 12.3 - Martin (revive old post)
> > * 13.2 - Aaron - tough one, no consensus last time
> > * 13.3 - Martin
> >
> > Thanks,
> > Laurence
> >
> > [0]
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000649.html
> > [1]
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000634.html
> > [2]
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000642.html
> > [3]
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000648.html
> > [4]
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000651.html
> >
> > _______________________________________________
> > C-safe-secure-studygroup mailing list
> > C-safe-secure-studygroup at lists.trustable.io
> > https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 31 Oct 2018 13:14:52 -0400
> From: Michael Wong <fraggamuffin at gmail.com>
> To: C Safety and Security Study Group Discussion
> <c-safe-secure-studygroup at lists.trustable.io>
> Cc: AJ Guillon <aj.guillon at gmail.com>, Illya Rudkin
> <codeplayillya at gmail.com>
> Subject: Re: [C-safe-secure-studygroup] Agenda for meeting - Weds 31
> Oct
> Message-ID:
> <CAAUWkG_uSzBR--99K1J_xLFkOj-v-G0YbAr1usn3rjyUcf310w at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all, you asked during the call for a link on the Khronos Safety and
> secure effort. Here they are OpenCL
> KSCAF
> https://www.khronos.org/blog/khronos-safety-critical-advisory-forum-details-and-why-you-should-join
> OpenCL SC
> https://www.khronos.org/openglsc/
> SYCL SC
> Its in our intention, but we are like OpenCL SC but for C++
> https://www.khronos.org/sycl/
> I am the chair of SYCL, but I have also linked in the other 2 chairs who
> can answer questions about this more clearly. Thanks.
>
> On Wed, Oct 31, 2018 at 1:08 PM Aaron Ballman <aaron at aaronballman.com>
> wrote:
>
> > We did not meet quorum for today's call, so we did not make progress
> > on existing homework items. Attendees included: me, Clive Pygott,
> > Michael Wong, and Charles Wilson.
> >
> > We had an informal discussion about the direction of the group,
> > without reaching any binding decisions. The discussion centered around
> > ways to resolve the issues the group is currently facing with IP
> > challenges, quorum, and finding a permanent chair. The action items
> > from the discussion were:
> >
> > Clive will reach out to MISRA for a statement expressing what MISRA
> > finds to be acceptable use of their IP within an ISO standard.
> > Charles is going to explore the possibility of stepping up as chair.
> > Michael is going to email the study group reflector with information
> > about other, related organizations working in the same space as we
> > are. We may be able to liaise with these groups to entice some more
> > domain experts to join the study group.
> >
> > We will reconvene on Nov 14th at 12pm ET to continue the discussion
> > about the future of the group and hopefully we will have sufficient
> > attendance to make binding decisions on how we want the study group to
> > proceed.
> >
> > ~Aaron
> > On Wed, Oct 31, 2018 at 5:54 AM Laurence Urhegyi
> > <Laurence.Urhegyi at codethink.co.uk> wrote:
> > >
> > > Hi,
> > >
> > > Meeting today at 16:00 UTC, see here for local time:
> > >
> > >
> > https://www.timeanddate.com/worldclock/fixedtime.html?msg=C+Safe+and+Secure+Study+Group&iso=20181031T16&p1=1440&ah=1&am=30
> > >
> > >
> > > Outstanding actions
> > > ~~~~~~~~~~~~~~~~~~~
> > > * Clive to send out the revised update for ISO and ask for final review.
> > [done]
> > > * Laurence to push on ISO to sort out the Zoom account. [done - but need
> > to
> > > carry over]
> > > * Laurence to begin chasing down the status of the homework. [done but
> > also to
> > > carry on]
> > > * In the context of discussing Rule 11.6 - Martin to furnish proposal
> > [0] with
> > > another example. [done]
> > >
> > >
> > > Agenda
> > > ~~~~~~
> > > Aaron's mail [0] from Pittsburgh. Quoting that:
> > >
> > > * Do you think we should continue to attempt to produce a standard
> > > combing both safety and security rules for static analyzers?
> > > * If the consensus is to continue forward,
> > > * What is the best way for us to resolve the IP concerns before
> > > April and are you willing to take on any or all of that effort?
> > > * If you are a member of the ISO global directory, are you willing
> > > to step up as chair? If you're not, are you willing to join ISO to
> > > step up as chair?
> > > * Are you able to help find more participants in either domain so
> > > that we can address our quorum and expertise concerns?
> > >
> > > Fair warning: I plan to poll the question of whether we want to
> > > disband the study group. It would be useful for me to know if you're a
> > > regular attendee that is unable to attend the teleconference on Oct 31
> > > but have a strong opinion.
> > >
> > >
> > > Homework
> > > ~~~~~~~~
> > > Thanks to those who were able to respond to homework requests on the
> > list. We
> > > have three items we can cover.
> > >
> > >
> > > Rules discussed on list:
> > > ~~~~~~~~~~~~~~~~~~~~~~~~
> > > * 11.6 - in progress, Martin [done] [0]
> > > * 11.7 - Fulvio (in the context of Martin's additional example) [done]
> > [1]
> > > * 12.4 - Fulvio [done] [2]
> > > * 13.1 - Clive [done] [3]
> > >
> > >
> > > Not discussed on list:
> > > ~~~~~~~~~~~~~~~~~~~~~~
> > > * 12.1 - Aaron, please follow up on gitlab info with a post to list
> > > * 12.2 - Clive (revive old post)
> > > * 12.3 - Martin (revive old post)
> > > * 13.2 - Aaron - tough one, no consensus last time
> > > * 13.3 - Martin
> > >
> > > Thanks,
> > > Laurence
> > >
> > > [0]
> > >
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000649.html
> > > [1]
> > >
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000634.html
> > > [2]
> > >
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000642.html
> > > [3]
> > >
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000648.html
> > > [4]
> > >
> > https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000651.html
> > >
> > > _______________________________________________
> > > C-safe-secure-studygroup mailing list
> > > C-safe-secure-studygroup at lists.trustable.io
> > >
> > https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup
> >
> > _______________________________________________
> > C-safe-secure-studygroup mailing list
> > C-safe-secure-studygroup at lists.trustable.io
> >
> > https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://lists.trustable.io/pipermail/c-safe-secure-studygroup/attachments/20181031/a90141ef/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 31 Oct 2018 13:44:15 -0400
> From: Michael Wong <fraggamuffin at gmail.com>
> To: C Safety and Security Study Group Discussion
> <c-safe-secure-studygroup at lists.trustable.io>
> Cc: AJ Guillon <aj.guillon at gmail.com>, Illya Rudkin
> <codeplayillya at gmail.com>
> Subject: Re: [C-safe-secure-studygroup] Agenda for meeting - Weds 31
> Oct
> Message-ID:
> <CAAUWkG_xFiEngscZ-R0Ro875_xa45dVmCiM4qL=bm_XAOFwbyQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all, I sent the wrong opencl SC link. I am going to ask AJ, the chair on
> copy to send the write link. Thanks.
>
> On Wed, Oct 31, 2018 at 1:14 PM Michael Wong <fraggamuffin at gmail.com> wrote:
>
> > Hi all, you asked during the call for a link on the Khronos Safety and
> > secure effort. Here they are OpenCL
> > KSCAF
> >
> > https://www.khronos.org/blog/khronos-safety-critical-advisory-forum-details-and-why-you-should-join
> > OpenCL SC
> > https://www.khronos.org/openglsc/
> > SYCL SC
> > Its in our intention, but we are like OpenCL SC but for C++
> > https://www.khronos.org/sycl/
> > I am the chair of SYCL, but I have also linked in the other 2 chairs who
> > can answer questions about this more clearly. Thanks.
> >
> > On Wed, Oct 31, 2018 at 1:08 PM Aaron Ballman <aaron at aaronballman.com>
> > wrote:
> >
> >> We did not meet quorum for today's call, so we did not make progress
> >> on existing homework items. Attendees included: me, Clive Pygott,
> >> Michael Wong, and Charles Wilson.
> >>
> >> We had an informal discussion about the direction of the group,
> >> without reaching any binding decisions. The discussion centered around
> >> ways to resolve the issues the group is currently facing with IP
> >> challenges, quorum, and finding a permanent chair. The action items
> >> from the discussion were:
> >>
> >> Clive will reach out to MISRA for a statement expressing what MISRA
> >> finds to be acceptable use of their IP within an ISO standard.
> >> Charles is going to explore the possibility of stepping up as chair.
> >> Michael is going to email the study group reflector with information
> >> about other, related organizations working in the same space as we
> >> are. We may be able to liaise with these groups to entice some more
> >> domain experts to join the study group.
> >>
> >> We will reconvene on Nov 14th at 12pm ET to continue the discussion
> >> about the future of the group and hopefully we will have sufficient
> >> attendance to make binding decisions on how we want the study group to
> >> proceed.
> >>
> >> ~Aaron
> >> On Wed, Oct 31, 2018 at 5:54 AM Laurence Urhegyi
> >> <Laurence.Urhegyi at codethink.co.uk> wrote:
> >> >
> >> > Hi,
> >> >
> >> > Meeting today at 16:00 UTC, see here for local time:
> >> >
> >> >
> >> https://www.timeanddate.com/worldclock/fixedtime.html?msg=C+Safe+and+Secure+Study+Group&iso=20181031T16&p1=1440&ah=1&am=30
> >> >
> >> >
> >> > Outstanding actions
> >> > ~~~~~~~~~~~~~~~~~~~
> >> > * Clive to send out the revised update for ISO and ask for final
> >> review. [done]
> >> > * Laurence to push on ISO to sort out the Zoom account. [done - but
> >> need to
> >> > carry over]
> >> > * Laurence to begin chasing down the status of the homework. [done but
> >> also to
> >> > carry on]
> >> > * In the context of discussing Rule 11.6 - Martin to furnish proposal
> >> [0] with
> >> > another example. [done]
> >> >
> >> >
> >> > Agenda
> >> > ~~~~~~
> >> > Aaron's mail [0] from Pittsburgh. Quoting that:
> >> >
> >> > * Do you think we should continue to attempt to produce a standard
> >> > combing both safety and security rules for static analyzers?
> >> > * If the consensus is to continue forward,
> >> > * What is the best way for us to resolve the IP concerns before
> >> > April and are you willing to take on any or all of that effort?
> >> > * If you are a member of the ISO global directory, are you willing
> >> > to step up as chair? If you're not, are you willing to join ISO to
> >> > step up as chair?
> >> > * Are you able to help find more participants in either domain so
> >> > that we can address our quorum and expertise concerns?
> >> >
> >> > Fair warning: I plan to poll the question of whether we want to
> >> > disband the study group. It would be useful for me to know if you're a
> >> > regular attendee that is unable to attend the teleconference on Oct 31
> >> > but have a strong opinion.
> >> >
> >> >
> >> > Homework
> >> > ~~~~~~~~
> >> > Thanks to those who were able to respond to homework requests on the
> >> list. We
> >> > have three items we can cover.
> >> >
> >> >
> >> > Rules discussed on list:
> >> > ~~~~~~~~~~~~~~~~~~~~~~~~
> >> > * 11.6 - in progress, Martin [done] [0]
> >> > * 11.7 - Fulvio (in the context of Martin's additional example) [done]
> >> [1]
> >> > * 12.4 - Fulvio [done] [2]
> >> > * 13.1 - Clive [done] [3]
> >> >
> >> >
> >> > Not discussed on list:
> >> > ~~~~~~~~~~~~~~~~~~~~~~
> >> > * 12.1 - Aaron, please follow up on gitlab info with a post to list
> >> > * 12.2 - Clive (revive old post)
> >> > * 12.3 - Martin (revive old post)
> >> > * 13.2 - Aaron - tough one, no consensus last time
> >> > * 13.3 - Martin
> >> >
> >> > Thanks,
> >> > Laurence
> >> >
> >> > [0]
> >> >
> >> https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000649.html
> >> > [1]
> >> >
> >> https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000634.html
> >> > [2]
> >> >
> >> https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000642.html
> >> > [3]
> >> >
> >> https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000648.html
> >> > [4]
> >> >
> >> https://lists.trustable.io/pipermail/c-safe-secure-studygroup/2018-October/000651.html
> >> >
> >> > _______________________________________________
> >> > C-safe-secure-studygroup mailing list
> >> > C-safe-secure-studygroup at lists.trustable.io
> >> >
> >> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup
> >>
> >> _______________________________________________
> >> C-safe-secure-studygroup mailing list
> >> C-safe-secure-studygroup at lists.trustable.io
> >>
> >> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup
> >>
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://lists.trustable.io/pipermail/c-safe-secure-studygroup/attachments/20181031/3e3cd4fb/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> C-safe-secure-studygroup mailing list
> C-safe-secure-studygroup at lists.trustable.io
> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup
>
>
> ------------------------------
>
> End of C-safe-secure-studygroup Digest, Vol 23, Issue 18
> ********************************************************
>
>
> _______________________________________________
> C-safe-secure-studygroup mailing list
> C-safe-secure-studygroup at lists.trustable.io
> https://lists.trustable.io/cgi-bin/mailman/listinfo/c-safe-secure-studygroup
More information about the C-safe-secure-studygroup
mailing list