openerp-community team mailing list archive

[Wouter Tebbens <wouter@xxxxxxxxxxxxxxxx>]

Hi Maxime, all,

On 09/07/2013 04:56 PM, Maxime Chambreuil wrote:
> If contributor decides where its contribution is going, it might not be
> the best investment and you leave no room for the OCA board to manage
> the OCA and reach his objectives.

I think the Board should indeed set the objectives, but it could work
for example like this:

**********begin example**********

The Board selects a few priority projects that it considers would need
funded resources. The Board then provides the donors the following
options to donate for:
1) general mission of the OCA;
2) for specific project A*;
3) for specific project B*;
4) for specific project C*;

(*) The OCA Board will keep the ultimate responsibility in deciding how
to allocate resources according to the OCA's mission. It will do so as
much as possible according to the wishes of the donors.

**********end example**********

The advantage is that potential donors have a choice to dedicate their
contribution to a specific concrete project. Experience with
crowdfunding shows that this can be very effective if done right. People
would like to have a (sense of) influence when making their contribution.

This is of course just an example and can be done in a million ways.

best regards,

Wouter

> 
> When I donate, the organization I am donating to is the best to know
> where it is needed and useful. We want our donation to be the most
> effective.
> 
> If you want to decide where donations are going, you'd better join the
> board.
> -- 
> Maxime Chambreuil
> +1 (514) 276-5468 #126
> 
> ------------------------------------------------------------------------
> Dear Eric, Stefan and all,
> 
> I agree with your ideas to making quality signals more clear with more
> explicit criteria and sets of compatible modules.
> 
> Maybe OCA can have a donations policy where people can contribute to
> specific projects/modules/features. This might be in combination with
> offering bounties for some concrete work to be done. If we'd like
> something like that, we could implement some open idea/task tracking
> system, ideally with votes for members to set priorities.
> 
> That's some first thoughts but I find this an important discussion to
> continue exploring.
> 
> Best,
> Wouter Tebbens
> 
> Eric Caudal <eric.caudal@xxxxxxxxxxxxxx> escribió:
> 
> Hi Ana,
> Thanks for your input.
> I like the idea of fund raising  per community (basically what has been
> done for Magento).
> 
> Nevertheless, I think there are already available many open tools (lp,
> apps.openerp.com etc) where people can already freely contribute. I dont
> think we need to add another one that will add few value to the existing
> tools.
> 
> I would rather have a clear recognition of the difference made by the
> community reviewer projects and get them more visible on the OpenERP
> universe.
> 
> Unrated list of modules are welcome and necessary but end-users will
> best remember a few sets of useful and workable modules rather than
> thousands of modules of uneven quality that they cannot test one by one.
> 
> This is why we need to maintain quality modules and set of modules and
> advertise them to improve current OpenERP image and visibility.
> 
> Eric CAUDAL
> 
> Eric Caudal
> /CEO/
> --
> *Elico Corporation, Shanghai branch
> /OpenERP Premium Certified Training Partner/ *
> Cell: + 86 186 2136 1670
> Office: + 86 21 6211 8017/27/37
> Skype: elico.corp
> eric.caudal@xxxxxxxxxxxxxx <mailto:eric.caudal@xxxxxxxxxxxxxx>
> http://www.elico-corp.com
> 
> Elico Corp
> On 07/09/2013 20:29, Ana Juaristi wrote:
> 
>     HI everybody:
> 
>     My opinion is that fundraising should be made for each community
>     project.
>     It can be very complicated founding something that people is
>     contributing. Maybe a little contribution could be needed to mantain
>     the website or any administrative tasks but it would be like paying
>     a marketing site more than contributing on modules.
>     I think that community should be totally open and noone can fix if
>     something have got enough quality to be included or not. For any
>     administrative validation task you include on ecosystem more
>     difficult will be mantaining it, more complex would be people to
>     contribute and that's not the objetive of community modules.
>     I would prefere having a totally open site where people can download
>     any module, even if it's not documented, even if it's not certified,
>     even if it has not quality and... let people using it including it's
>     value with their comments, votes and so on like hotel reserving
>     websites or any other people mantained site.
>     As much valued is a module more people will use it, so more services
>     will sell the contributor so more visibility will obtain with modules.
>     On technical side, as much documented, much clear code, much used
>     module more visibility will obtain, so more people will use it, so
>     it will be more tested, so more valuation will obtain.
>     On the other side, if someone has got a very good idea about a new
>     blueprint / functionality a new foundrising project could be created
>     to obtain founds to realize that project.
> 
>     I don't think so community modules should be fiscalized very much.
>     We need focusing about a place where community can download,
>     comment, report bugs, contribute and value other people
>     contributions. I will agree on contributing in a crowdfunding
>     project to realize this but I don't see very clear contributing to
>     something to cover costs that are not clear yet.
> 
>     Thank you very much:
>     Ana
> 
> 
>     2013/9/7 Stefan <stefan@xxxxxxxx <mailto:stefan@xxxxxxxx>>
> 
>         On 09/07/2013 12:23 PM, Eric Caudal wrote:
> 
> 
>             I would see the certification less as a technical quality
>             control and more as an operation of marketing and visibility
>             of the current community work.
> 
> 
>         Hi Eric,
> 
>         It seems to me that the criteria mainly have technical
>         implications. Of course, the concerns you mention are all valid.
>         So what do you think of assigning this seal of approval simply
>         based on whether a module comes from a project which falls under
>         the community review, while making the requirements that you
>         expressed explicit in the reviewing guidelines (maybe after
>         reviewing some existing code for older modules)?
> 
>         Cheers,
>         Stefan.
> 
> 
>         -- 
>         Therp - Maatwerk in open ontwikkeling
> 
>         Stefan Rijnhart - Ontwerp en implementatie
> 
>         mail: stefan@xxxxxxxx <mailto:stefan@xxxxxxxx>
>         tel: +31 (0) 614478606 <tel:%2B31%20%280%29%20614478606>
>         web: http://therp.nl
> 
> 
>         _______________________________________________
>         Mailing list: https://launchpad.net/~openerp-community
>         <https://launchpad.net/%7Eopenerp-community>
>         Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>         <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>         Unsubscribe : https://launchpad.net/~openerp-community
>         <https://launchpad.net/%7Eopenerp-community>
>         More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
>     -- 
>     CEO Avanzosc, S.L <http://www.avanzosc.es> : Office phone / Tfono
>     oficina: (+34) 943 02 69 02
>     Ana Juaristi Olalde <http://www.anajuaristi.com/>: Personal phone:
>     677 93 42 59. User/usuario skype: Avanzosc
>     www.openerpsite.com <http://www.openerpsite.com/>
> 
> 
>     /El contenido de esta comunicación y de toda su documentación anexa
>     es confidencial y se dirige exclusivamente a su destinatario. El uso
>     no autorizado de esta información está prohibido por la legislación
>     vigente. Si usted no es el destinatario le rogamos nos lo indique,
>     no comunique su contenido a terceros y proceda a su destrucción.
>     Disculpe las molestias que le haya ocasionado la recepción indebida
>     de este e-mail. Sus datos figuran en un fichero cuyo titular es
>     Avanzosc, S.L., a quien usted puede dirigirse para ejercer sus
>     derechos de acceso, rectificación, cancelación y oposición en Julio
>     Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 -
>     _administracion@xxxxxxxxxxxx <mailto:soporte@xxxxxxxxxxxx>_/
> 
>     //
> 
>     /Komunikazio honen edukia eta dokumentazio erantsia konfidentziala
>     da eta hartzaileak bakarrik jaso beharko luke. Indarrean dagoen
>     legeriak debekatu egiten du bertan eskainitako informazioa baimenik
>     gabe erabiltzea. Komunikazioa zuri iritsi bazaizu, baina zu ez
>     bazara hartzailea, mesedez, guri jakinarazi, eta jasotako
>     informazioa ez inori jakinarazi eta suntsitu. Barkatu okerreko email
>     hau jasotzeak eragindako eragozpenak. Zure datuak Avanzosc, S.L.
>     enpresaren fitxategietan sartuta daude. Zure datuak atzitzea eska
>     dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari
>     aurka egitea ere. Horretarako, enpresara jo dezakezu, helbide
>     honetan: Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa:
>     943 02 69 02 - //_administracion@xxxxxxxxxxxx
>     <mailto:soporte@xxxxxxxxxxxx>_/
> 
>     /*This message and all documents attached to it are confidential and
>     intended only for the person or entity to which it is addressed. Any
>     use of this information by unauthorised persons is prohibited under
>     current legislation. If you received this message by error, please
>     advise us, destroy it and refrain from communicating its contents to
>     third parties. We apologise for any inconvenience receiving this
>     email improperly may cause to you. *Your personal data are included
>     in a file owned by Avanzosc, S.L. If you want to exercise your
>     rights of access, correction, erasure and objection you can contact
>     the Controller at Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), T:
>     943 02 69 02 – _administracion@xxxxxxxxxxxx
>     <mailto:soporte@xxxxxxxxxxxx>_/
> 
> 
>     _______________________________________________
>     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
>