openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #06713
Re: odoo vertical-medical
Is naming it "Odoo Medical" an option at all? Can anyone create a piece of
software and call it "Odoo Something"? Even if SA agrees to calling it
"Odoo Medical", does anyone understands the good/bad implications of using
their trademark in the naming of a community module?
AFAIK Odoo is a trademark that belongs to a private company. I do not
want to start a thread of conspiracy theories, etc but to me it feels like
someone writing a new piece of software/module on top of Odoo should not
even want to call it "Odoo Something", because it is not Odoo, it is
something else that runs on top of Odoo and this "something else" by the
way was not even developed by Odoo (the company) itself so how come naming
it "Odoo Something" could make any sense?
What you are trying to accomplish (make it clear that the software is
designed to run on Odoo) maybe should be accomplished in a different way.
And maybe the community should start thinking about it now and decide what
is the best way forward for the naming of such software so we can have some
kind of best practice.
if we think about iphone apps, android apps, etc, such necessity to
link the software to the platform the software runs on is unnecessary
because there is a specific marketplace for the platform. If likewise
Medical is advertised on the Odoo marketplace and it is hosted on OCA or
some other repository specific to Odoo then I would say naming it "Medical"
would be sufficient (and the logo could have a phrase like "built for Odoo"
to create the link you want when the app is viewed outside a Odoo context).
My 2 cts.
On Tue, Aug 5, 2014 at 4:26 PM, Luis Panozzo <luis.panozzo@xxxxxxxxxxxx>
wrote:
> Unfortunatelly OCA is not a recognized brand .... Only the ant may help
>
>
> Luis Panozzo (Lp)
> Technology Manager
> Elmatica AS
> luis.panozzo@xxxxxxxxxxxx
> Skype: luispanozzo
>
>
> On 5 August 2014 19:48, Mario Arias <the.clone.master@xxxxxxxxx> wrote:
>
>> Like this one...
>>
>>
>>
>> On Tue, Aug 5, 2014 at 10:34 AM, Mario Arias <the.clone.master@xxxxxxxxx>
>> wrote:
>>
>>> Good question Luis... Now we just need to wait for a good answer...
>>>
>>>
>>> If there are problems, we could swap odoo with oca logo.... ant
>>> included... ;-)
>>>
>>>
>>> Regards,
>>> -Mario
>>>
>>>
>>> On Tue, Aug 5, 2014 at 10:22 AM, Luis Panozzo <luis.panozzo@xxxxxxxxxxxx
>>> > wrote:
>>>
>>>> Is there an approval from Odoo to mess up with their logo?
>>>> I am sure that is a registered element and regardless of how the
>>>> community votes we would still need their approval and sanction.
>>>> Lp
>>>>
>>>>
>>>> Luis Panozzo (Lp)
>>>> Technology Manager
>>>> Elmatica AS
>>>> luis.panozzo@xxxxxxxxxxxx
>>>> Skype: luispanozzo
>>>>
>>>>
>>>> On 5 August 2014 17:41, Mario Arias <the.clone.master@xxxxxxxxx> wrote:
>>>>
>>>>> +1 A lot cleaner. Thanks Pedro !!
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Any opinions from OCA board ? The idea is to get a logo for this
>>>>> vertical and include it on the website...
>>>>>
>>>>>
>>>>> There are also proposals to use differentiated color schemas on logos
>>>>> for OCA / community projects... How should we proceed, voting ?
>>>>>
>>>>>
>>>>>
>>>>> As soon as we make the code change proposals on git, we would like
>>>>> to help improve content on the site... We first need a working project
>>>>> before marketing... ;-)
>>>>>
>>>>>
>>>>> Regards,
>>>>> -Mario
>>>>>
>>>>>
>>>>> On Tue, Aug 5, 2014 at 3:14 AM, Pedro Manuel Baeza Romero <
>>>>> pedro.baeza@xxxxxxxxx> wrote:
>>>>>
>>>>>> I like this one.
>>>>>>
>>>>>> Regards.
>>>>>>
>>>>>>
>>>>>> 2014-08-05 11:11 GMT+02:00 Mario Arias <the.clone.master@xxxxxxxxx>:
>>>>>>
>>>>>> About fonts... on "medical" I am using the font that S.A. is using
>>>>>>> for the official apps logos...
>>>>>>> Same goes for colors, I am using the ones blessed by S.A.
>>>>>>>
>>>>>>> You can check https://www.odoo.com/page/brand-assets
>>>>>>>
>>>>>>>
>>>>>>> Not sure if that is good or not, but at least will avoid a "fonts
>>>>>>> and colors war" were each one likes a different one... ;-)
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> -Mario
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Aug 5, 2014 at 3:02 AM, Kitsikpui Elliot Elikplim <
>>>>>>> ekitsikpui5@xxxxxxxxx> wrote:
>>>>>>>
>>>>>>>> The logo loos good, just a few suggestions from my end.
>>>>>>>> 1. The Font of the med should be same as that of the Odoo
>>>>>>>> 2. The space between the Odoo and Med should be closed up a little
>>>>>>>> more.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks and look forward to seeing your module come out in time.
>>>>>>>>
>>>>>>>> Warm Regards & Stay Creative!
>>>>>>>> Elikplim Elliot Kitsikpui
>>>>>>>> +233 27 193 1935 | +233288312658
>>>>>>>>
>>>>>>>> This email and any files transmitted with it are confidential and
>>>>>>>> intended solely for the use of the individual or entity to whom they are
>>>>>>>> addressed. If you have received this email in error please notify the
>>>>>>>> sender. This message contains confidential information and is intended only
>>>>>>>> for the individual named.
>>>>>>>> If you are not the named addressee you should not disseminate,
>>>>>>>> distribute or copy this email. Please notify the sender immediately by
>>>>>>>> email if you have received this email by mistake and delete this email from
>>>>>>>> your system. If you are not the intended recipient you are notified that
>>>>>>>> disclosing, copying, distributing or taking any action in reliance on the
>>>>>>>> contents of this information is strictly prohibited.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> > On 5 Aug 2014, at 06:51, Mario Arias <the.clone.master@xxxxxxxxx>
>>>>>>>> wrote:
>>>>>>>> >
>>>>>>>> > Hi,
>>>>>>>> >
>>>>>>>> > We have been working on the medical vertical for some time now,
>>>>>>>> and will be loading soon a proposal to github that adds several features
>>>>>>>> like:
>>>>>>>> > • SMS/email templates for appointment
>>>>>>>> creation/modification/cancellation
>>>>>>>> > • Multi medical center, allowing a physician to work in
>>>>>>>> more than one center and controlling the agendas consolidated per physician
>>>>>>>> and per medical center.
>>>>>>>> > • Weekly agenda template, so physicians and assistants only
>>>>>>>> need to select an empy slot and fill some fields...
>>>>>>>> > • Multi level access: physician, assistants, call center
>>>>>>>> operators...
>>>>>>>> > • Updated Invoicing
>>>>>>>> >
>>>>>>>> > And after that...
>>>>>>>> > • Rename from oemedical to OdooMed
>>>>>>>> > • QR barcodes
>>>>>>>> > • Updated to new 8.0 features (qweb reports, new API, ...)
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > In the mean time, what do you think of this logo...
>>>>>>>> >
>>>>>>>> > <odoo_med_cmyk.png>
>>>>>>>>
>>>>>>>> >
>>>>>>>> > If you like it for the OCA page / project, let me know and I will
>>>>>>>> provide the .svg file...
>>>>>>>> >
>>>>>>>> > Regards,
>>>>>>>> > -Mario
>>>>>>>> > _______________________________________________
>>>>>>>> > Mailing list: https://launchpad.net/~openerp-community
>>>>>>>> > Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>>>>>> > Unsubscribe : https://launchpad.net/~openerp-community
>>>>>>>> > More help : https://help.launchpad.net/ListHelp
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Mailing list: https://launchpad.net/~openerp-community
>>>>>>> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>>>>> Unsubscribe : https://launchpad.net/~openerp-community
>>>>>>> More help : https://help.launchpad.net/ListHelp
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~openerp-community
>>>>> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~openerp-community
>>>>> More help : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help : https://help.launchpad.net/ListHelp
>
>
Follow ups
References