Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Question about Module Structure
by
dar
Hello again,
I found out that I can fork the document with suggestions.
I spared out the module quality levels, as this seems to be of urgent concern and scheduled for asap implementation.
Therefore, please share your ideas on:
A little show-off (a picture says more than thousand word): https://asciinema.org/a/tUg6ND6VERFL4ZehSQgj0cRiL
You can check the result here: https://github.com/xoes-oca/sales_team_multicompany/pull/1
Best Regards,
David A.
El jue., 22 feb. 2018 a las 14:22, David Arnold (<dar@xoe.solutions>) escribió:
A little show-off (a picture says more than thousand word): https://asciinema.org/a/tUg6ND6VERFL4ZehSQgj0cRiLYou can check the result here: https://github.com/xoes-oca/sales_team_multicompany/pull/1--El jue., 22 feb. 2018 a las 13:23, David Arnold (<dar@xoe.solutions>) escribió:Hello,I've been thankfully pointed to the fact, that I missed the main discussion by two-three weeks.Now, I'm not sure if this proposal is counter-productive or if it would probably in it's clarity and conciseness have a real chance of being taken into account be the steering committee.I would really wish to see a simpler contributing workflow.I think everyone faces this problem at some point.And I also think a lot of beneficial impetus gets turned down silently because of those obstacles.It addresses the issues of the discussion at its best and most condensed expression.I hope this opportunity for change did not already pass by freezing the world for the next 3-4 years until further contributing statistics impose further reactions to the OCA ecosystem.Best Regards,David A.--El jue., 22 feb. 2018 a las 12:41, David Arnold (<dar@xoe.solutions>) escribió:Hello,I think I've found the right frame and initiative to place my thoughts: https://docs.google.com/document/d/1wwnu7oe5cDTyjZH3hdKkGLnF6fH4jPP3RLMPAhm3gjs/edit#heading=h.7w9he6vxmsocIt's a great document and initiative!Best Regards,David--El jue., 22 feb. 2018 a las 10:43, David Arnold (<dar@xoe.solutions>) escribió:Addendum:As an alternative solution to the organization problem could count to split out the one-module-one-repo into a oca-dev organization and then do tagged packages in oca which resembles the current structure (using precisely git subrepo approach). That way the impact of such a move is mitigated without leaving out the benefits.--El jue., 22 feb. 2018 a las 10:37, David Arnold (<dar@xoe.solutions>) escribió:Dear OCA Members,--Dear OCA Steering Commitee,Dear OCA Board,I've tried on several occasions to work with OCA repos, but it somehow doesn't fit any simple, easy to remember development and upstream-commit workflow I've been able to come up with.In despair, I tried to do a PoC of a one-module-one-repo structure https://github.com/xoes-ocaThere is a extremely useful tool called git subrepo (combinable with git subhistory) I've found to be the perfect solution for the problem to incorporate upstream modules in own code, do improvements with close to 0 changes to your normal workflow and just git subrepo push to upstream those chages transparently and cleanly.Problem is that doesn't work out of the box with topic repositories, so it basically breaks my ideally perfect workflow and then again going the extra mile is often too cumbersome in the heat of the battle.If we would have one-module-one-repo the contributing workflow becomes as simple as that:...Using hub by github (https://hub.github.com/)hub fork git@github.com:oca/foogit subrepo clone git@github.com:myuser/foo foo# do some commits touching module foo within my current working dirgit subrepo pushhub pull-request> Pull request created: https://github.com/oca/foo/pulls/208Wouldn't that be something that's worth evaluating to boost contribution and ease of adaption?
I'm principally very in favor of the OCA iniciative, but honestly contributing has those (solvable) hurdles and gets rather cumbersome (for the new generation of iphone-ux-socialized programmers).Let me know what you think about, I'd be happy to more closely integrate our development efforts with OCA one's.And if there are concerns about code organization, I guess since github allowed for topics this can be easily replicated with using topic filters: https://github.com/search?q=topic%3Aproduct+org%3Axoes-oca&type=Repositories
Best Regards,David A.
DAVID ARNOLD
Gerente Generalxoe.solutions
dar@xoe.solutions
+57 (315) 304 13 68Confidentiality 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.
DAVID ARNOLD
Gerente Generalxoe.solutions
dar@xoe.solutions
+57 (315) 304 13 68Confidentiality 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.
DAVID ARNOLD
Gerente Generalxoe.solutions
dar@xoe.solutions
+57 (315) 304 13 68Confidentiality 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.
DAVID ARNOLD
Gerente Generalxoe.solutions
dar@xoe.solutions
+57 (315) 304 13 68Confidentiality 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.
DAVID ARNOLD
Gerente Generalxoe.solutions
dar@xoe.solutions
+57 (315) 304 13 68Confidentiality 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.
DAVID ARNOLD Gerente General | |
xoe.solutions dar@xoe.solutions +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. |
Reference
-
Question about Module Structure
bydar-
Re: Question about Module Structure
byDatenbetrieb Technologie UGh, Peter Niederlag