1. Mailing Lists
  2. Contributors
  3. Re: Request for new project oca/queue

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Request for new project oca/queue

Re: Request for new project oca/queue

Avatar

Re: Request for new project oca/queue

by
Akretion France., David BEAL
- 10/10/2016 20:26:27

+1


Le 10 oct. 2016 18:08, "Pedro M. Baeza (Tecnativa)" <pedro.baeza@tecnativa.com> a écrit :
OK, let's go for that way then!

Regards.

2016-10-10 17:38 GMT+02:00 Guewen Baconnier <guewen.baconnier@camptocamp.com>:
Fully agree, perhaps it's easier to feel responsible of a small
repository with a very well known code base for a team of maintainers
than for many addons in a repository, most of them unknown.
Pedro, I was speaking about 'base_import_async' because it has no
functional dependencies and I bet other addons like this will arise.


On Mon, Oct 10, 2016 at 5:23 PM, Stéphane Bidoul
<stephane.bidoul@acsone.eu> wrote:
> +1 for a new small repo with the job queue only. Modules exploiting the
> queue in different functional domains can remain in their respective repos.
>
> I'm not afraid of having more smaller repositories with more focused groups
> of maintainers each. I'm convinced it will make the community more
> efficient.
>
> Best regards,
>
> -sbi
>
>
> On Mon, Oct 10, 2016 at 5:08 PM Pedro M. Baeza (Tecnativa)
> <pedro.baeza@tecnativa.com> wrote:
>>
>> I have 2 fears with this:
>>
>> - We still continue adding more and more repos.
>> - Concepts get very transversal now. For example, we have
>> https://github.com/OCA/bank-payment/tree/8.0/account_payment_transfer_reconcile_batch
>> that uses "queue" for reconciling payment order lines, but having this new
>> repo and moving to it makes to hardly follow the existence of this
>> batch/queue option.
>>
>> Thus, I still prefer to have one repository for both, and hosts possible
>> parallel implementations suffixed with _queue on each of the corresponding
>> repositories of the functional area.
>>
>> What do you think about this?
>>
>> Regards.
>>
>> 2016-10-10 15:38 GMT+02:00 Guewen Baconnier
>> <guewen.baconnier@camptocamp.com>:
>>>
>>> On Mon, Oct 10, 2016 at 3:23 PM, Yannick Vaucher
>>> <yannick.vaucher@camptocamp.com
> wrote:
>>> ...
>>> >
>>> > However, what could be done is that OCA connector team should still be
>>> > in
>>> > charge of both repository as for now I don't think there would be
>>> > enough
>>> > people for 2 teams, maybe I'm wrong.
>>> >
>>>
>>> Yes! That's indeed the idea.
>>>
>>>
>>> _______________________________________________
>>>                        Mailing-List:
>>> http://odoo-community.org/groups/contributors-15
>>>                        Post to: mailto:contributors@odoo-community.org
>>>                        Unsubscribe:
>>> http://odoo-community.org/groups?unsubscribe
>>>
>>>
>>
>> _______________________________________________
>>                        Mailing-List:
>> http://odoo-community.org/groups/contributors-15
>>                        Post to: mailto:contributors@odoo-community.org
>>                        Unsubscribe:
>> http://odoo-community.org/groups?unsubscribe
>>
>>
>>
> _______________________________________________
> Mailing-List: http://odoo-community.org/groups/contributors-15
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: http://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

Reference