<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font face="Ubuntu">Hi Martin,</font><br>
</p>
<br>
<div class="moz-cite-prefix">Le 15/12/2016 à 10:04, Martin Winter a
écrit :<br>
</div>
<blockquote
cite="mid:718864A3-076E-4B02-9863-124CE22F73A3@opensourcerouting.org"
type="cite">Donald,
<br>
(and everyone else working on it)
<br>
<br>
Thanks for setting up Slack. We (NetDEF) can get a free upgrade to
the standard edition
<br>
as part of bing a 501c3 non-profit.
<br>
<br>
See <a class="moz-txt-link-freetext" href="https://freerangerouting.slack.com/pricing">https://freerangerouting.slack.com/pricing</a> for difference
between Free and Standard
<br>
model.
<br>
<br>
Happy to do this if this community thinks Slack is useful. Please
be aware that it’s
<br>
free “only” up to 250 users - and 85% discount above it.
<br>
<br>
We can only do this for one Slack - so we may want to wait until
everyone confirms
<br>
the new selected name (i.e. no legal issues)
<br>
</blockquote>
A simple google search on "Free Range Routing" gives some published
articles<br>
e.g. IEEEXplore <a
href="http://ieeexplore.ieee.org/document/1673164/"><a class="moz-txt-link-freetext" href="http://ieeexplore.ieee.org/document/1673164/">http://ieeexplore.ieee.org/document/1673164/</a></a><br>
related to automated guided vehicles studies. I don't know if using
the same name <br>
will make confusion or not (it is not the same scope, so not the
same research area).<br>
From the legal issue, I ask my legal department in charge of the
opensource contribution<br>
at Orange to check if there is a potential problem or not.<br>
<br>
I would not re-open the debate, but why just using Open Source
Routing ? I think you could<br>
publish a code with the name of your entity or is there some legal
issue that prohibit this ?<br>
<br>
Regards<br>
<br>
Olivier<br>
<blockquote
cite="mid:718864A3-076E-4B02-9863-124CE22F73A3@opensourcerouting.org"
type="cite">
<br>
- Martin
<br>
<br>
_______________________________________________
<br>
cmaster-next mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:cmaster-next@lists.nox.tf">cmaster-next@lists.nox.tf</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.nox.tf/listinfo/cmaster-next">https://lists.nox.tf/listinfo/cmaster-next</a>
<br>
</blockquote>
<br>
<PRE>_________________________________________________________________________________________________________________________
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.
</PRE></body>
</html>