[C-safe-secure-studygroup] Agenda - 14 November 2018

Laurence Urhegyi Laurence.Urhegyi at codethink.co.uk
Tue Nov 13 18:03:05 GMT 2018


Let's use the below agenda for tomorrow's call.

On 31/10/18 11:40, Laurence Urhegyi wrote:
> Since we don't have an ISO zoom account yet we'll need to use the following 
> conferencing service:
> 
> Freephone Access Phone Number: 0800 496 0694 (UK)
> UK toll: 020 7023 9790 / +44 20 7023 9790
> Toll Free Access Phone Number: 1.866.305.1460 (USA and Canada)
> Direct Dial Access Phone Number: +1.416.620.1296
> Other International Toll Free Access Phone Numbers - 
> http://www.onconference.com/g800
> 7-Digit Access Code: 9245414 (public)
> If you are the chairperson, press the * key, and enter 6712#.
> 
> On 31/10/18 09:54, Laurence Urhegyi 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
> 

-- 
Laurence Urhegyi
Codethink Ltd
http://www.codethink.co.uk/
We respect your privacy.   See https://www.codethink.co.uk/privacy.html



More information about the C-safe-secure-studygroup mailing list