openerp-community team mailing list archive

[Bertrand Hanot <bertrand.hanot@xxxxxx>]

Hi all,

I don't have a magic answer to these questions, but just my personal feedback/feeling.

By default, most development of the community should be open-source and hence published (that's the basic philosophy on which OpenERP model is based).
Now if a partner have invested a lot in developing a specific module, it's not really fair to just took what he did without notifying him and making a lot of money out of it.
Best practice according to me is to communicate with the original developer, and enhance together the current module. Buy a few hours/days of consultancy from the original author, it'll help him to finance all its R&D costs and it'll help you to gain time (and hence money) and acquire more experience on the specific fonctionnality domain you'll have to implement for your customer.
It's really a WIN-WIN approach... and the reason why OpenERP is what it is today.

But it's just my feeling/idea (i hope shared by a lot of partners), not at all a strict rule.

Kind regards.

Bertrand Hanot
BHC IT Services
________________________________
From: partners-bounces@xxxxxxxxxxx [partners-bounces@xxxxxxxxxxx] On Behalf Of Nabil Majoul [nabil.majoul@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, January 30, 2013 11:51
To: Serpent Consulting Services
Cc: Partners@xxxxxxxxxxx; openerp-community@xxxxxxxxxxxxxxxxxxx
Subject: Re: OpenERP: [Openerp-community] Partners Collaboration Model

Hello,
Thank you all for your answers.
It does clarify  things.
i understand that it's everyone choice to share or not share with the community but my question was also about how we can leverage and also remunerate each other developments:
Partner A develops an Insurance Module that he is not willing to share
Partner B would like to use that Module for one of his customers.

My understanding is that this will lead to a one to one negociation between A and B...But is there practices established ? is there an interest to establish some rules or a framework for this kind of collaboration?
Best Regards,

PbuSent from my iPad

On Jan 30, 2013, at 11:11 AM, Serpent Consulting Services <serpentcs.lp@xxxxxxxxx<mailto:serpentcs.lp@xxxxxxxxx>> wrote:

Hello,

Lionel Sausin said it quite right and each line of the email says a lot and gives a bunch of information.

However, I would Like to add apps.openerp.com<http://apps.openerp.com> which is also a good way for specially those who are integrators , but not purely technical (who don't use bzr).

It is kind of difficult for all community members to push/share/distribute the work done to a common framework where all the community can see.

Even though this is difficult, the new community organization well led by C2C, Akretion, Vauxooo, Therp, Agaplan, Domsense(Agile) and some more(Apologies if I miss some names) is doing well. You can see HERE<http://www.serpentcs.com/serpentcs-new-community-organization-for-openerp> to know more on this. (We used the blog from OpenERP and information from C2C. Thank them.)

Its always better to ask in Community channel, so you can get several opinions, suggestions and accurate help from all the experienced Community members.

Launchpad and Forums are again useful ones !

Thanks.

P.S. : Not to Forget, Competition brings Quality!


On Wednesday 30 January 2013 02:48 PM, "Lionel Sausin, de la part de l'équipe informatique Numérigraphe" wrote:
Dear Nabil Majoul,

Thanks for asking, it's not a naive question at all: it's important everyone understands that contributing is *not* a "partner" topic.

OpenERP being newer that other ERPs, OpenERP Partners need to share their success stories. I think that's about all they share on this list - they are competitors after all.
Some partners don't share anything at all (and it's OK).
There is a bigger picture however : the community is now big enough to sustain shared development of advanced features beyond the roadmap of OpenERP SA - check out https://launchpad.net/~openerp-community-reviewer/+participation<https://launchpad.net/%7Eopenerp-community-reviewer/+participation>
The community is *not only* the partners.
The community is partners + business experts + power users + independent IT firms  + translators + OpenERP SA themselves + every other contributor. The community book has more details : http://doc.openerp.com/v6.1/contribute/index.html#how-to-contribute-link
You can ask the mailing-list openerp-community@xxxxxxxxxxxxxxxxxxx<mailto:openerp-community@xxxxxxxxxxxxxxxxxxx> for further advice (I'm CCing them).

Lionel Sausin.

Le 29/01/2013 10:41, Nabil Majoul a écrit :
Dear Partners,

Please forgive my naive question.
I see a lot of emails back and forth asking if any body worked in such or such subject.
And I was wondering if there Is a defined framework for collaboration between partners.

For example, If I’m looking for Insurance related module and one partner developed such module
Is there a model or expected practice ?
Or is it on a case by case negociation?

Thank you for your insights.
Best Regards,

Nabil Majoul
Head of Professional Services / Partner
Targa Consult<http://www.targa-consult.com/>
<mime-attachment.png><http://ch.linkedin.com/in/nmajoul>

Work: 41 79 8151435
Email: mailto:nabil.majoul@xxxxxxxxxxxxxxxxx

<mime-attachment.png><http://www.targa-consult.com/>











_______________________________________________
Mailing-List: OpenERP Partners
Post to: partners@xxxxxxxxxxx<mailto:partners@xxxxxxxxxxx>
Unsubscribe: mailto:partners-request@xxxxxxxxxxx?subject=unsubscribe
Options: https://mailman.openerp.com/mailman/options/partners






_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx<mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



--

Thanks,
Regards,
<Serpent3-e1320864501636.jpg>
Serpent Consulting Services.
Web : http://www.serpentcs.com
Twitter: jaynvora, husendaudi
Skype: jaynvora, husen.daudi
Blog : http://www.serpentcs.com/blog