-
-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move sale_automatic_workflow and sale_payment_method to sale-workflow project #47
Comments
I'm 👍 on this in principle, but let's not rush things. I'll raise attention on the contributors mailing list. |
👍 |
2 similar comments
👍 |
👍 |
👍 I wonder if it's possible to let somehow a message to let users know where to find the new repo host |
I also think that e-commerce repository overlaps a lot of others repositories, and more over, e-commerce is only one channel more, not an isolated flow itself, so I prefer to remove this repo and split its contents in the corresponding areas repos. |
I'm 👍 on the concept but I do not want to break any existing setup. One of the role of OCA is to provide some stability. We were angry enought with Odoo coboy release let's try to do better. |
👍 to move it |
Sounds good as I use them outside of e-commerce connectors too (for sort of a prepayment workflow), but please handle some of the mentioned unported modules too then, and any of their issues or PRs as good as github allows (I have ongoing PR for porting one of them) |
I discussed about that with @bguillot and agree. The modules are not only related to e-commerce and overlap with other repositories, mainly sale-workflow. 👍 |
I agree also to remove this repository and move it outside. 👍 |
👍 |
Thanks for your answers, It seems that everyone agree with that. @nbessi I think most of people that use e-commerce modules will also use sale-workflow so it should not be too dangerous for existing deployments. I will make a PR to move sale_payment_method (because it has no current PR). But what is the process to move the PR's from e-commerce to sale-workflow ? |
@bguillot ok but at least we should have a mail on community mailing list before/when proceeding |
What's the status of this? Now that Odoo has its own e-commerce module I think it's important to "clean" this. |
I can merge as this has enough thumbs up. |
But I don't see PR for the move in sale-workflow. Can you do it? |
@pedrobaeza who are you talking to? |
Well, actually it can be anyone, but I refer to one of the involved in this conversation. |
Hello, I started to make PRs here : |
I'm thinking we should probably add a ChangeLog file at the root of the project for modules which get moved from one project to another. At least this will give the people a hint about where to look. |
👍 for moving |
So here is a checklist:
And all the open pull requests that involve those modules. I am migrating: |
This PR is also needed too #88, because OCA/sale-workflow#172 is already merged |
Thanks @antespi, I updated the list above. |
This has been done, so I close. |
Hello,
I am here to discuss about moving the modules sale_automatic_workflow (and derived) and sale_payment_method (and derived) to the project sale-workflow.
First of all those modules are very linked with other sale-workflow modules, it leads to loop dependencies for travis for instance (modules in e-commerce depends on modules in sale-workflow).
That's why @gurneyalex and @sebastienbeau suggested to move at least sale_payment_method in my PR OCA/sale-workflow#121
Moreover, thoses modules can be used even in a non e-commerce company (you may want to automate the validation of sale_orders or invoices without having an e-commerce shop).
So after discussing with @guewen it appears that maybe sale_automatic_workflow, sale_payment_method and sale_payment_method_automatic_workflow would be better in sale-workflow project (product_links is still relevant in e-commerce).
That makes also sense for the unpported modules : sale_quick_payment, sale_automatic_workflow_exceptions and sale_payment_method_transaction_id (thoses are glues modules).
Before extracting the branches I would like to have your opinions about that and what will be the best procedure to do it (indeed thoses modules are concerned by some PR's).
I can first do it with sale_payment_method (no PR in 7 or 8).
Thanks for your feedbacks
The text was updated successfully, but these errors were encountered: