[frr] Lightening talk at Apricot - can I name some/all of your companies?

[olivier.dugeon at orange.com]

Hi Martin,

Your proposal is fine for me; I'll try to understand what it is possible to communicate.

Regards

Olivier


Le 28/02/2017 à 15:54, Martin Winter a écrit :
> Olivier,
>
> On 28 Feb 2017, at 20:19, olivier.dugeon at orange.com wrote:
>
>> Hello Martin,
>>
>> This is a bit complicated regarding Orange. I have no power to decide a such communication and involving our communication department will take too much time.
>
> Understood. Might be good to raise that question internally for the next time (i.e. I expect latest in May at the RIPE meeting to have more presentation about it). So any chance to have this clarified would be highly appreciated.
>
>> So, I prefer you not mention Orange as company. What you could do eventually, is to mention that there is individual contributions from Orange employee.
>
> I think in this case I rather don’t mention Orange for now. I’ll plan to mention “other contributors” without specifying company names as well. Is this ok?
>
> Regards,
>    Martin Winter
>
>> Le 27/02/2017 à 09:43, Martin Winter a écrit :
>>> So I’m planning to present a lightening talk this thursday at Apricot
>>>
>>> (I won’t know until Wed late if I get a slot, so no guarantee)
>>>
>>> Part of the talk I wanted to list who is behind FRR and wanted to check if
>>> you all are ok or if I should not mention any of your companies.
>>>
>>> So please clarify either in private or public reply if you are ok or not
>>>
>>> Thinking about mentioning:
>>>     - NetDEF / OpenSourceRouting
>>>     - Cumulus
>>>     - LabN
>>>     - Orange
>>>     - 6Wind
>>> (happy to add more - just shoot me an email and let me know who else to add)
>>>
>>> Regards,
>>>   Martin Winter
>>>
>>> _______________________________________________
>>> frr mailing list
>>> frr at lists.nox.tf
>>> https://lists.nox.tf/listinfo/frr
>>
>>
>> _________________________________________________________________________________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>
>
>


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20170228/20eaac20/attachment.html>