| *** paulsher1ood has joined #trustable | 00:42 | |
| *** paulsherwood has quit IRC | 00:43 | |
| *** paulsherwood has joined #trustable | 00:50 | |
| *** paulsher1ood has quit IRC | 00:53 | |
| *** dabukalam has quit IRC | 01:32 | |
| *** dabukalam has joined #trustable | 01:32 | |
| *** ctbruce has joined #trustable | 08:04 | |
| *** laurenceurhegyi has joined #trustable | 08:16 | |
| *** ctbruce has quit IRC | 08:48 | |
| *** tiagogomes has joined #trustable | 09:12 | |
| *** ctbruce has joined #trustable | 09:32 | |
| *** jmacs_ has joined #trustable | 12:40 | |
| *** paulsher1ood has joined #trustable | 12:40 | |
| *** paulsherwood has quit IRC | 12:45 | |
| *** ChrisPolin has quit IRC | 12:45 | |
| *** jmacs has quit IRC | 12:45 | |
| *** ChrisPolin has joined #trustable | 12:51 | |
| *** ctbruce has quit IRC | 13:37 | |
| *** ctbruce has joined #trustable | 13:37 | |
| ChrisPolin | Hi all, we have been granted permission from SEI to make a derivative version of CERT-C. This is good news as it means OpenControl can be expanded to include this standard in its 'repertoire'. | 13:46 |
|---|---|---|
| ChrisPolin | However, the letter of agreement for permission states: | 13:46 |
| ChrisPolin | Naming of Derivative Works. Codethink shall not name the Derivative Work in such a manner as to create a likelihood of confusion as to the origination of such Derivative Work. Without limiting the generality of the foregoing, the Derivative Work shall not be named [“Introduction to CMMI” or any translation thereof] [with the same name as any of the Materials]. Additionally, Codethink must name the Derivative Work | 13:46 |
| ChrisPolin | to include "Codethink" in | 13:46 |
| ChrisPolin | the title (for example, you may call your derivative work "Codethink's Training on Implementing the CMMI® Model.” | 13:46 |
| ChrisPolin | That might be a potential issue, as while we have created the yaml, it isn't a 'Codethink' version. | 13:49 |
| ChrisPolin | I'm going to ask if this requirement can be removed in the circumstances, but perhaps someone with a little more experience in legalese might be able to advise? | 13:49 |
| paulsher1ood | well, let's consider what we would *like* to call this work... and then ask for that | 13:51 |
| paulsher1ood | but what's CERT got to do with CMMI? | 13:52 |
| ChrisPolin | Ideally we'd like to call it 'CERT-C Coding Standard', as anyone who wishes to use OpenControl for that purpose will only be looking for the standard name. | 13:52 |
| ChrisPolin | I think CMMI was used as an exampe. | 13:52 |
| ChrisPolin | example* | 13:52 |
| ChrisPolin | Either that or it was a poorly-proofed cut-and-paste. | 13:53 |
| paulsher1ood | so, what about 'OpenControl CERT-C Coding Standard', 'OpenControl CERT-C' | 13:53 |
| ChrisPolin | That could work, although it's not in keeping with the titles of the other standards on there. | 13:54 |
| ChrisPolin | And might lead the user to think that it's a standard produced by or with some affiliation to OpenControl. | 13:54 |
| ChrisPolin | The other two on there are named 'NIST-800-53-Standards' and 'PCI-DSS-Certifications', which is unambiguous. | 13:55 |
| ChrisPolin | I can forward you the agreement letter paulsherlood, if you'd like to read it. | 13:57 |
| paulsher1ood | yes please | 13:57 |
| paulsher1ood | i guess the key point to query with them is that we're aiming to do the work in the open as a community effort, not affiliated to Codethink. in any case, whatever we call it, others could fork and rename | 13:58 |
| ChrisPolin | This is true. I'll put it to them like that. | 13:58 |
| ChrisPolin | OpenControl have invited me to join their github, they're happy for me to create a new repo on there for it, so it's just a case of making sure we're ok with SEI. | 14:00 |
| paulsher1ood | cool! | 14:01 |
| paulsher1ood | we should update robert on this | 14:01 |
| ChrisPolin | Mm, he would be interested to hear about it. It might also move things forward with Misra. | 14:02 |
| paulsher1ood | yup... but probably best to get the naming+repo sorted first | 14:03 |
| ChrisPolin | Will keep you updated. | 14:03 |
| paulsher1ood | i guess we could even try calling it 'Trustable-C-Standard' if they are concerned about it being misconstrued as CERT | 14:04 |
| paulsher1ood | this could be considered to be more inflamatory in other senses though :) | 14:05 |
| ChrisPolin | Was just about to say that lol. | 14:05 |
| *** laurenceurhegyi has quit IRC | 16:55 | |
| *** ctbruce has quit IRC | 17:45 | |
| *** ChrisPolin has quit IRC | 23:43 | |
| *** paulsher1ood has quit IRC | 23:43 | |
| *** ChrisPolin has joined #trustable | 23:44 | |
| *** paulsher1ood has joined #trustable | 23:44 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!