Archives
Contributors
-
Re: Select recipients on chatter widget
Hi Timon,what do you mean by "free recipient selection"? Do you mean something like a litte search and add widget right above the message box?Best RegardsChristianVon: "Timon Tschanz" <timon.tschanz@camptocamp.com>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Montag, 25. November 2019 14:52:01
Betreff: Select recipients on chatter widgetHello I'm looking for an add-on to allow free recipient selection on the inline chatter form. Has something like this been done before? Target version is a V10 Kind Regards Timon Tschanz
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Christian Zöllner
E-Mail: c.zoellner@intero-technologies.de
Intero Technologies GmbH
Heinrich-Heine-Ring 76
D - 18435 Stralsund
Tel: +49 (0) 3831 – 44 55 7 - 0
Fax: +49 (0) 3831 – 44 55 7 - 79
Internet: www.intero-technologies.de
Intero Technologies GmbH • Firmensitz: Heinrich-Heine-Ring 76, 18435 Stralsund , Deutschland • Registergericht: Amtsgericht Stralsund, HRB 7076 • Geschäftsführer: Frank Löffler, Lars Lifson • USt-Ident.Nr. DE 251251697
This eMail and its content is dedicated to the intended recipient only. If you have received it in error please contact the sender immediately by fax or return eMail. Please then delete the eMail and any copies of it.
by Christian Zöllner - 03:10 - 25 Nov 2019 -
Re: Proposing myself as connector-lira PSC member
1. Make Alexey PSC of that entire group, as he has also contributed to some project things (project_role and others).2. Create a separate PSC for connector-jira.I'm OK with 1.Me too
by Lorenzo Battistini. - 02:20 - 25 Nov 2019 -
Re: Proposing myself as connector-lira PSC member
I'm ok with both.On Mon, Nov 25, 2019 at 11:22 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:There's no specific connector-jira PSC, but associated to "Project & Service PSC", so maybe that's too broad. Options:1. Make Alexey PSC of that entire group, as he has also contributed to some project things (project_role and others).2. Create a separate PSC for connector-jira.I'm OK with 1.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Simone Orsi - 11:30 - 25 Nov 2019 -
Re: Proposing myself as connector-lira PSC member
There's no specific connector-jira PSC, but associated to "Project & Service PSC", so maybe that's too broad. Options:1. Make Alexey PSC of that entire group, as he has also contributed to some project things (project_role and others).2. Create a separate PSC for connector-jira.I'm OK with 1.Regards.
by Pedro M. Baeza - 11:20 - 25 Nov 2019 -
Re: Proposing myself as connector-lira PSC member
+1 here. Thanks for your contribs! :)On Sun, Nov 24, 2019 at 9:27 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:Dear contributors,What I’ve done so far:
- v12 migration
- [IMP] connector_jira: worklog/timesheet date timezone
- [FIX] connector_jira: issues can be moved between projects
- [IMP] connector_jira: restrict linked AAL modification
- [ADD] connector_jira_tempo_project_role
- [IMP] connector_jira: search by Jira keys
- [IMP] connector_jira: import estimation and status for tasks
- [IMP] connector_jira: view JIRA keys on project and task views
- [IMP] connector_jira: restrict linked tasks alteration
- [IMP] connector_jira: do not track sync updates
- [IMP] connector_jira: improved user binding
Kind regards,Alexey_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Simone Orsi - 09:01 - 25 Nov 2019 -
Re: Proposing myself as connector-lira PSC member
+1--Yves Goldberg - איב גולדברגodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500
------- Original message -----From: "Joël Grand-Guillaume" <joel.grandguillaume@camptocamp.com>To: Contributors <contributors@odoo-community.org>Subject: Re: Proposing myself as connector-lira PSC memberDate: Monday, November 25, 2019 09:47+1 for me. Thanks for your participationOn Sun, Nov 24, 2019 at 9:27 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:Dear contributors,What I’ve done so far:- v12 migration
- [IMP] connector_jira: worklog/timesheet date timezone
- [FIX] connector_jira: issues can be moved between projects
- [IMP] connector_jira: restrict linked AAL modification
- [ADD] connector_jira_tempo_project_role
- [IMP] connector_jira: search by Jira keys
- [IMP] connector_jira: import estimation and status for tasks
- [IMP] connector_jira: view JIRA keys on project and task views
- [IMP] connector_jira: restrict linked tasks alteration
- [IMP] connector_jira: do not track sync updates
- [IMP] connector_jira: improved user binding
Kind regards,Alexey_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
by Yves Goldberg - 08:51 - 25 Nov 2019 - v12 migration
-
Re: Proposing myself as connector-lira PSC member
+1 for me. Thanks for your participationOn Sun, Nov 24, 2019 at 9:27 AM Alexey Pelykh <alexey.pelykh@gmail.com> wrote:Dear contributors,What I’ve done so far:- v12 migration
- [IMP] connector_jira: worklog/timesheet date timezone
- [FIX] connector_jira: issues can be moved between projects
- [IMP] connector_jira: restrict linked AAL modification
- [ADD] connector_jira_tempo_project_role
- [IMP] connector_jira: search by Jira keys
- [IMP] connector_jira: import estimation and status for tasks
- [IMP] connector_jira: view JIRA keys on project and task views
- [IMP] connector_jira: restrict linked tasks alteration
- [IMP] connector_jira: do not track sync updates
- [IMP] connector_jira: improved user binding
Kind regards,Alexey_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions
by Joël Grand Guillaume - 08:45 - 25 Nov 2019 -
Re: automatic bank statements import
Thanks Alexey,Will review!El dom., 24 nov. 2019 9:02, Alexey Pelykh <alexey.pelykh@gmail.com> escribió:Dear community,There’s a set of PRs that add base for automatic bank statements import and some implementations:- PayPal
- TransferWise
Some more implementations are to arrive within couple of months timeframe:- LHV bank (Estonia)
- PrivatBank InterPay (Ukraine)
- Braintree
- Payoneer
Regarding the EU PSD2 directive, currently it requires too much paperwork and license cost is huge, so until there’s some enhancements to TPP definition we’re a bit blocked there, yet there’s no technical difficulties.And I’d like to kindly request for a review of those PRs from interested parties.Kind regards,Alexey_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jordi Ballester Alomar - 09:40 - 24 Nov 2019 -
Re: Place to share knowledge/tools on deployment
Hope anyone might be interested to join the effort:dodoois a CLI or library entrypoint to the dodoo server middleware for Odoo.KF 1:it hot-reloads config for DB, SMTP and the admin password.KF 2:it supports libpg dsn. (ej. for db server multiplexing)KF 3:set max connection per database.KF 4:dbfilter on odoo version and client project version.KF := Killer Feature
On Tue, Nov 19, 2019 at 9:10 PM David Arnold <dar@xoe.solutions> wrote:@Georg speccing for kops backend taskers startedAn opportunity for cleaning the python middleware.Also to slice off the essentially broken odoo built in scheduler/server :D (maybe)On Tue, Nov 19, 2019 at 5:42 PM David Arnold <dar@xoe.solutions> wrote:Planned refactoring to this regard from our side:- Modularize- Swap subcommands easily ("make your own `odooup`")On Mon, Nov 18, 2019 at 3:42 PM Georg Notter <georg.notter@agenterp.com> wrote:Haha sorry wrong targetMit freundlichen Grüßen
We look forward to see you. Best Regards
Dipl. Ing. (Fh) Georg Notter
Agent ERP GmbH
www.agenterp.comAm 18.11.2019 um 21:07 schrieb Georg Notter <georg.notter@agenterp.com>:
Moin david ruf mal wieder durch!Mit freundlichen Grüßen
We look forward to see you. Best Regards
Dipl. Ing. (Fh) Georg Notter
Agent ERP GmbH
www.agenterp.comAm 16.11.2019 um 02:38 schrieb David Arnold <dar@xoe.solutions>:
And beaten again: https://github.com/OdooOps/awesome-odoo-ops#readmeOn Fri, Nov 15, 2019 at 8:28 PM David Arnold <dar@xoe.solutions> wrote:Sorry, I've beaten myself, the reference should always be:https://github.com/OdooOps/awesome#readme(with the same document reference to the readme at the end)On Fri, Nov 15, 2019 at 8:27 PM David Arnold <dar@xoe.solutions> wrote:For now, there is a skeleton carefully ripped from: https://github.com/sindresorhus/awesomeFirst couple of PRs should come soon from myself, but please feel free to submit your own PRs abiding by the contributing rules. (those are relatively simple for once ;-)On Fri, Nov 15, 2019 at 5:33 PM David Arnold <dar@xoe.solutions> wrote:Now, for the first time in a row... :DOn Fri, Nov 15, 2019 at 5:06 PM Jordi Riera <jordi.riera@numigi.com> wrote:Hello David,Did you have the time to move forward with the awesome repo/list ?Best,JordiLe jeu. 31 oct. 2019 à 10:37, David Arnold <dar@xoe.solutions> a écrit :True, Russell has put together some compelling user stories. I plan to process them somehow to that end.El jue., 31 oct. 2019, 7:47 a.m., Jordi Riera <jordi.riera@numigi.com> escribió:Great,And we can create traffic to the ODEPs through the awesome-list.We need to find the good catch phrases to inspire people to contribute on doc.Thank you David,JordiLe jeu. 31 oct. 2019 à 00:27, David Arnold <dar@xoe.solutions> a écrit :Ok. I like, lots of communities do those awesome-x listing ;-)A good mix catering to different levels of abstraction should gain enough traction over time, you're right, we need to create practical value, too.But I think, especially for the more involved people to let loose of their deer siloes, the foundation's need to be talked true with time and effort (hence ODEPs).Only through excellent community governance will we have a chance to eventually agree.This week, I intent to create that awesome-deployment-odoo-repo.BR,David A.El mié., 30 oct. 2019, 3:12 p.m., Jordi Riera <jordi.riera@numigi.com> escribió:Hello everyone,sorry for my silence in the previous days. Busy days as we all know.I think we should start small to grow slowly but surely.I like your enthusiasm, David, and feel free to lead the effort on the subject. While ODEPs seem great, I have the feeling that might scare a lot of contributors due to the mass of reading to do.In parallel to it, I would like to see something more practical, like an awesome-odoo-deploy, where we would see a list of all the tool to deploy odoo.I see that you have already a good list with:* doodba* odoo cloud platform...What do you think?OdooOps seems a good place to start. Could you create a new repo for the listing?Cheers,JordiLe mer. 30 oct. 2019 à 12:27, David Arnold <dar@xoe.solutions> a écrit :Yeah, OCA might probably endorse it later on when OCA wishes to. Absolutely!From a constituency point of view, OCA does not seem to be able to add shared legitimacy. This needs to be provided by the involved actors themselves.Namely, to my knowledge, those are:- Tecnativa (doodba)- Camptocamp (Odoo cloud platform, and other tooling, anthem, marabunta)- Acsone (odoo-bedrock, click-odoo, Bob templates, and other tooling)- Akretion (docky and other tooling)- XOE ( DockeryOdoo & OdooOperator and a couple of forks / mix&match from Acsone and Camptocamp)Can we pass the point where PRoC > PRoSP (Perceived Return on Collaboration > Persived Return on Siloed Project) for those actors?El mié., 30 oct. 2019, 1:27 a.m., Russell Briggs <russ@paraflyer.net> escribió:Great stuff David!Yeah it feels like this should eventually become an OCA project once it gets some traction, since it is potentially quite a fundamental community component?I will have a read and make some comments in a bit :)RussOn Wed, 30 Oct 2019, 9:57 AM David Arnold, <dar@xoe.solutions> wrote:By the way I commit by all means NOT to retain unique ownership on the OdooOps GitHub organization. Any meritable community, abiding by the self constituing decision making processes (e.g. ODEPs) is eligible to share the burdon. ;-)El mar., 29 oct. 2019, 3:50 p.m., David Arnold <dar@xoe.solutions> escribió:Hi all,I redacted a first ODEP 0002 in Order to propose the constituency of a docker base runtime repository.I stepped over some steps and wrote down everything I had in mind.For legitimacy building, please comment on the PR and indicate your level of approval:Approve: Section 1, Section 2, etc.Disaprove: Section 4Ideally we would get unanimous approval of the "Motivation" section, so this section could be merged quickly.According to the eminent approval levels I'll outfactor parts into separate PRs / Discussions.Please leave your opinion / approval level, even if you are only a user and no active committer of the Odoo docker community.BR,David A.El dom., 27 oct. 2019, 11:36 p.m., David Arnold <dar@xoe.solutions> escribió:I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").My 2 cents.El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:The interest will grow if the few involve here make it work...El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:What is the next step for this to move on?- Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?- Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?It would be nice to know who is interested by this topic.tnx--Yves Goldberg------- Original message -----From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>To: Contributors <contributors@odoo-community.org>Subject: Re: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:52Hi Jordi,I think we could start with:- one repository to store a base/minimal docker image + documented extensions.
- one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
My 2 cents.On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:Hello list,During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)How would you see it ?What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.Let me know what you thinkJordi--
Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by dar - 10:41 - 22 Nov 2019 -
Re: New library to migrate Odoo module code "odoo-migrate"
Hi all,Sorry I'm late to the party, this is a very interesting idea! Has it evolved since the last message? Is it already under OCA? Can somebody point me where the source code is now?Best regards,El lun., 14 oct. 2019 a las 19:02, Sylvain LE GAL (<sylvain.legal@grap.coop>) escribió:Hi all,First thanks all for your enthusiasm !About the name, OK to rename it. I'm not sure that if you want to rename the lib, or the command. For exemple, for git aggregator feature. The lib is named git-aggregator, and the command is gitaggregate. Can we continue the discussion here ?About the repository, if I understand correctly, it should be great to be under OCA umbrella, and in a stand-alone repository as proposed by Pedro and Stephane bidoul. Let's go renaming first, and moving owner of the lib after.The last week-end, I worked to integrate tests. Now, it includes tests that checks that initial V8 module are correctly migrated in V13. So I guess that it allows people to contribute avoiding regression.I also added tools to log (warning, error) if the migrated module depends on obsolete module based on the OpenUpgrade documentation.About the evolution, david Arnold, I did not feel the need to use pybowler for the time being, but feel free to make a Pull request using pybowler, if you want.Kind regards.Le lun. 14 oct. 2019 à 17:37, David Arnold <dar@xoe.solutions> a écrit :PS: As long as the tool strictly works on the workdir and does not attempt to interfere with database migration, the scope is clear, and the need is there :)On Mon, Oct 14, 2019 at 10:25 AM David Arnold <dar@xoe.solutions> wrote:Hi Silvain,there was coming something to my mind, I'd like to share.Some time ago, I worked with pybowler, which is a code transformar on the python grammar level.Like regex without the "regular" in it.It is super convenient to write certain transform scripts, And I'd suggest to use it for your library, as it is very easy to extend and very powerful.It would also be easy to make contributions and once community grows familiar with python grammar expressions, then it might unleash unprecedented productivity for OCA maintenance tasks and beyond.Here are some example transform script: https://gist.github.com/blaggacao/13cf79fad489bca962e4a43eb580e9ee#file-logging-not-lazy-pyBased on facebook's excellent pybowler library.Best Regards,David A.On Fri, Oct 11, 2019 at 5:39 PM David Arnold <dar@xoe.solutions> wrote:+1 stephane comment about standalone+1 about resist feature creepHasn't there been some proposal going around to have OCA-libs as a Github orga for those standalone projects to be hosted / promoted?There is python-xmlsig and python-xades from Eric and many others too.El vie., 11 oct. 2019, 9:16 a.m., Simone Orsi <simahawk@gmail.com> escribió:Nice! Thanks Sylvain.+1 for standalone project as well :)On Fri, Oct 11, 2019 at 2:57 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:+1 to keep it a standalone project. I'd rather see the good parts of OCA/maintainer-tools become standalone projects too.Regarding growing features, be strong Sylvain, resist scope creep :) Do one thing and do it well!-sbiOn Fri, Oct 11, 2019 at 2:47 PM David Arnold <dar@xoe.solutions> wrote:Re: Do you plan to grow features or is it limited to make those repetitive tasks more scriptable?On Fri, Oct 11, 2019 at 3:12 AM David Beal <david.beal@akretion.com> wrote:génialLe jeu. 10 oct. 2019 à 18:12, Sylvain LE GAL <sylvain.legal@grap.coop> a écrit :Dear OCA Contributors,I am working on a migration from 8.0 to 12.0.For that purpose, I had to migrate a lot a modules. (about 50 OCA modules, and >100 custom modules)A lot of changes are very recurrent, and automatable. (removing python2 header, renaming __openerp__.py into __manifest__.py, changing import).I began to make some scripts, and finally began to create a new python3 library, to make that work. The name is "odoo-migrate" and the description is available here https://pypi.org/project/odoo-migrate/. and can be installed with the commandpip3 install odoo-migrateOnce installed, you can run the following command (other options are available)odoo-migrate -m my_module_name -i 8.0 -t 12.0It is based on the OCA recommendations available on this wiki.In addition to performing recurring operations,- it displays some warning if some patterns are found. (for example, if "ir.values" is found in a module 11+)- it calls black for recent version- it realize commits1) If you're interested by such tool, you can review or test this project.2) If you want to contribute, feel free, especially if you love regular expressions. It is still WIP, and there is a lot of work to do, like making change in xml file. (replacing openerp + data by odoo tag). Also adding test and plug with travis could be great.3) if some OCA members are OK, I can transfer this project under OCA umbrella.thank you for your feedback.kind regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Twitter: lreficent_erp(+34) 679052448 | lois.rilo@eficent.com | http://www.eficent.comLois Rilo AnteloEficent Business and IT Consulting Services, S.L.
by Lois Rilo Antelo - 04:56 - 21 Nov 2019 -
OCA 2020 RFQs - close Thursday 29th November
Dear OCA Contributors,Just a reminder that the OCA 2020 RFQs close on Thursday 29th November.
You can see more details here:Register your interest by sending an email or if you have any questions please get in touch.Warm regards,
Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 01:16 - 21 Nov 2019 -
Re: "Adopt a Module" campaign?
Great Idea Alexey :)
Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, CanadaLe mar. 19 nov. 2019 à 04:42, Alexey Pelykh <alexey.pelykh@gmail.com> a écrit :I agree to volunteer, as long as we agree on approach and steps. In my mind, every repository should have a “Adopt Me” issue with “help” wanted, where bot will maintain a list of modules that are not adopted. And periodic "call for maintainers” on events?As for lint: have no idea how to approach this, “if commit has a new file __manifest__.py then do something"On 19 Nov 2019, at 11:27, Sylvain LE GAL <sylvain.legal@grap.coop> wrote:Le mar. 19 nov. 2019 à 10:17, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Well, OK for both, but resources are needed to perform that, so if you volunteer for performing them, +1 for me.Regards.El mar., 19 nov. 2019 a las 10:12, Alexey Pelykh (<alexey.pelykh@gmail.com>) escribió:How to perform that?Ask them, very-very politelyTecnnically,- In a first step, it's quite easy to add maintainers keys in the odoo modules that fetch github code. (https://github.com/OCA/interface-github)- In a second step a nice bot can create PR adding maintainers for some (all modules). (a little more complex, but not so hard) Can be an objective of a code sprint.regard.Are you suggesting Travis to fail if no maintainer is declared?For new modules, yes. For current ones - give warning. It makes no sense of adding module and not becoming a maintainer for it (unfortunately, I did the same for some time because lack of knowledge)
On 19 Nov 2019, at 11:02, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:> 1) “noone”’s modules should be adopted either by their original author(s) or by volunteerHow to perform that?> 2) add a lint to ensure when module is added, it has a declared maintainerAre you suggesting Travis to fail if no maintainer is declared?Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Bruno Joliveau - 08:01 - 20 Nov 2019 -
Re: Translate OCA website to Portuguese Brazil
Please point to the proper translation URL (in https://translation.odoo-community.org/ site) for checking.Regards.
by Pedro M. Baeza - 05:46 - 20 Nov 2019 -
Re: "Adopt a Module" campaign?
Great idea!On Wed, Nov 20, 2019 at 4:07 PM Lorenzo Battistini <elbaddy@gmail.com> wrote:I think this is a good idea.ThanksOn Tue, 19 Nov 2019 at 09:56, Alexey Pelykh <alexey.pelykh@gmail.com> wrote:Idea is quite simple: lots and lots of modules have no declared maintainers, even when they are added by a specific author. Steps suggested are:1) “noone”’s modules should be adopted either by their original author(s) or by volunteer2) add a lint to ensure when module is added, it has a declared maintainerHopefully, this would allow more "self-management” on a module level by original holders of leadership of respective module
On 19 Nov 2019, at 10:52, Sylvain LE GAL <sylvain.legal@grap.coop> wrote:Hi Alexey,I find the idea quite funny. (And interesting for the OCA to have more maintainers).If community agree with such an idea, I think that we should first target the most used modules, (if they don't havemaintainers already).Candidate list : https://www.odoo.com/apps/modules/browse?author=Odoo+Community+Association+%28OCA%29&order=DownloadsLe mar. 19 nov. 2019 à 09:47, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Please detail a bit more what are the steps of that campaign.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel : +352 20 21 10 20 19
Fax : +352 20 21 10 21
Gsm : +352 691 50 60 88Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu
by Denis Roussel - 05:41 - 20 Nov 2019 -
Re: Translate OCA website to Portuguese Brazil
Hi,There may have been a misunderstanding...My integration is translated on the community site: www.odoo-community.org to Portuguese, not the project: github.com/oca/websiteIs this possible?Luis Felipe Miléo
phone: +55 11 3090-9303
mobile: +55 35 988 763 663
www.kmee.com.br
From: "Pedro M. Baeza (Tecnativa)" <pedro.baeza@tecnativa.com>
To: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Sent: Thursday, November 14, 2019 10:12:51 PM
Subject: Re: Translate OCA website to Portuguese BrazilHi, Luis,You were already member of the PT-BR team. Is there any problem you are facing?Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Luis F Miléo - 05:41 - 20 Nov 2019 -
Re: "Adopt a Module" campaign?
I think this is a good idea.ThanksOn Tue, 19 Nov 2019 at 09:56, Alexey Pelykh <alexey.pelykh@gmail.com> wrote:Idea is quite simple: lots and lots of modules have no declared maintainers, even when they are added by a specific author. Steps suggested are:1) “noone”’s modules should be adopted either by their original author(s) or by volunteer2) add a lint to ensure when module is added, it has a declared maintainerHopefully, this would allow more "self-management” on a module level by original holders of leadership of respective module
On 19 Nov 2019, at 10:52, Sylvain LE GAL <sylvain.legal@grap.coop> wrote:Hi Alexey,I find the idea quite funny. (And interesting for the OCA to have more maintainers).If community agree with such an idea, I think that we should first target the most used modules, (if they don't havemaintainers already).Candidate list : https://www.odoo.com/apps/modules/browse?author=Odoo+Community+Association+%28OCA%29&order=DownloadsLe mar. 19 nov. 2019 à 09:47, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Please detail a bit more what are the steps of that campaign.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lorenzo Battistini
https://github.com/eLBati
by Lorenzo Battistini. - 04:06 - 20 Nov 2019
