Contributors mailing list archives
Re: Welcoming new contributions, Favoring innovation Let's enhance our community !by
Thanks for your feedback.
I see this is a very promising move. I hope everyone at the board is open to consider it just the *first* move.
However a road map for continuous improvement is not entirely clear from the given announcement, so I felt compelled to raise this issue again:
Just to make sure it's clear that there are still a lot of topics to tackle before OCA can be a viable home for all Odoo contributors.
El mié., 26 sept. 2018 a las 12:32, Daniel Reis (<firstname.lastname@example.org>) escribió:
Citando David Arnold <email@example.com>:> Good move towards making OCA a more attractive / vivid place for > contributors, but there is still way to go: Biggest constraint so > far for casual contribution has been that there is no shared > history, when I use a OCA module as a library. > > Therefore the following situation: > > - I copy the OCA module > - I fix it in my working tree > - I go for a swim instead of replicating the fix and contributing > upstream, because the whole setup is just too cumbersome.I'm sorry to disappoint you David, but the new workflow won't fix that use case. If your local fix is not proposed to the OCA branch, it won't land there and your tree will still diverge from the upstream OCA. -- Daniel
+57 (315) 304 13 68
|Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.|
|Environmental Consideration: Please avoid printing this email on paper, unless really necessary.|
Camptocamp SA, Joël Grand Guillaume