Contributors

• Re: Proposing myself as l10n-spain PSC

  Just another precision. 

  I agree now we have no delays with merges in Basque localization, but that's because:

  - Pedro, you are helping a lot. Many thanks for your constant effort and compromise with community.

  -  development has nearly stoped after Logroño OCA days.

  Next weeks things are going to change and we want to be prepared.
  
  Thanks and regards 
  

  -----------------------------------------------------------
  Josean Soroa
  

  
  

  El vie., 15 jul. 2022 14:52, Pedro M. Baeza (Tecnativa) <notifications@odoo-community.org> escribió:
  

  Just one precision: it's not going to speed up anything, as the speed right now is immediate.

  
  

  El vie., 15 jul. 2022 14:41, Josean Soroa - Landoo <notifications@odoo-community.org> escribió:
  

  Hi.

  
  

  In this case I think we have a good solution using maintainers rights, so we are not going to follow with this discussion.

  In the mentoring project for v15, Aritz has mentored some modules not included in Basque localization and in the future he will continue this way, so we will talk about that in some months.

  
  

  For now, as mentioned by Pedro, establishing Aritz as maintainer will be enough to speed up the migrations to v14 and 15, we are planning for this month.

  Just for better comprehension of all, some light over very important details:

  - we were told by Pedro and Tobella (or thats what we understood) about the right of maintainers to merge their modules, but restricted to same branch. This is not a solution for us, because we need to merge migration of modules and this in different branch.

  - from Sylvain answer yesterday, we realized that 3 months there has been a new change in OCA rules, to allow maintainers do the same but also in different branches.

  That's perfect for us and I want to thank Sylvain for this key contribution.

  And for the rest of maintainers, take note of this new rule. Will be very useful.

  
  

  Regards.
  

  -----------------------------------------------------------
  

  Josean Soroa

  
  

  
  
  
  
  

  
  

  
  

  El jue, 14 jul 2022 a las 18:32, Pablo Fuentes (<notifications@odoo-community.org>) escribió:
  

  Hi, 

  
  

  I compleatly agree with Jairo's message and I don't agree with create a new repo just for the basque country just because of don't want to promote Aritz.

  If we talk about merits and meritocracy, Aritz has some... he is:

  - Top 7 contributor by commits https://github.com/OCA/l10n-spain/graphs/contributors

  - Top 13 contributor by additions https://github.com/OCA/l10n-spain/graphs/contributors?type=a

  
  

  Best Regards,

  
  

  El jue, 14 jul 2022 a las 18:02, Soporte Acysos (<notifications@odoo-community.org>) escribió:
  

  Hello,

  I'm the oldest PSC, but I know that now I'm less active.

  Negative vote.
  

  I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
  Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
  If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.
  

  Greetings,
  Ignacio
  

  El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
  

  Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

  
  

  Regards.

  
  

  El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
  

  Hi all,

  
  

  Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

  
  

  Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

  
  

  Regards.

  
  

  El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
  

  Hi Graeme,

  
  

  some precision inline.

  
  

  regards.
  

  Sylvain LE GAL - Twitter
  

  GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)

  Site Web | FramaSphere | Facebook
  3 Grande rue des Feuillants, 69001 Lyon
  Standard : (+33) 09.72.32.33.17
  

  Service Informatique : (+33) 09.73.79.64.40

  Astreinte Informatique : (+33) 06.81.85.61.43

  Member of the OCA (Odoo Community Association)
  

  Web Site | Twitter
  

  
  

  
  

  Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
  

  Hi Josean,

  
  

  You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

  
  

  FYI,

  - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)

  - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)
  

  
  

   

  Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

  
  

  But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

  
  

  On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
  

  Hi all.
  Excuse me for this long answer but the question is very important for us.
   
  My vote is +1 for Aritz.
  
  My reasons are very similar to the case of Pablo:
  - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
  - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
  - Aritz is one of the few developers who knows deeply Basque Country localization

  
  In are more deep explanation, I'm involved in this question by 3 different rules.
  - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
  From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
  - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
  This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
  - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.
  
  I hope other members of the community will agree with this point of view and will send a +1 to this applicant.
  
  Thanks.
  -----------------------------------------------------------
  Josean Soroa
  LANDOO SL - www.landoo.es
  -----------------------------------------------------------
  

  
  

  
  

  El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
  

  Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -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
  

  _______________________________________________
  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
  

  
  

  
  

  --
  

  Aritz Olea

  LANDOO - Sistemas de Información con Odoo

  _______________________________________________
  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
  

  --
  Acysos S.L. (www.acysos.com)
  Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
  Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
  Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
  Github (http://www.github.com/acysos)
  Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
  C/ Miguel Astrain 18, 1º Oficina A
  31006 Pamplona, Navarra.
  soporte@acysos.com
  Tel. 948238905
  ---------------------- // -------------------
  La información contenida en este mensaje de correo electrónico es
  confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
  acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
  persona a la que va dirigido, cualquier divulgación, copia o distribución de
  la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
  tomada o dejada de tomar basada en la información contenida en este mensaje
  queda prohibida y puede ser ilegal.
  The information in this e-mail is confidential and may be legally privileged.
  It is intended solely for the addressee. Access to this e-mail by anyone is
  unauthorised. If you are not the intended recipient, any disclousure,
  copying, distribuition or any action taken or omited to be taken in reliance
  on it, is prohibited and may be unlawful.
  

  _______________________________________________
  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 Josean Soroa - 04:01 - 15 Jul 2022

• Re: Proposing myself as l10n-spain PSC

  Just one precision: it's not going to speed up anything, as the speed right now is immediate.

  
  

  El vie., 15 jul. 2022 14:41, Josean Soroa - Landoo <notifications@odoo-community.org> escribió:
  

  Hi.

  
  

  In this case I think we have a good solution using maintainers rights, so we are not going to follow with this discussion.

  In the mentoring project for v15, Aritz has mentored some modules not included in Basque localization and in the future he will continue this way, so we will talk about that in some months.

  
  

  For now, as mentioned by Pedro, establishing Aritz as maintainer will be enough to speed up the migrations to v14 and 15, we are planning for this month.

  Just for better comprehension of all, some light over very important details:

  - we were told by Pedro and Tobella (or thats what we understood) about the right of maintainers to merge their modules, but restricted to same branch. This is not a solution for us, because we need to merge migration of modules and this in different branch.

  - from Sylvain answer yesterday, we realized that 3 months there has been a new change in OCA rules, to allow maintainers do the same but also in different branches.

  That's perfect for us and I want to thank Sylvain for this key contribution.

  And for the rest of maintainers, take note of this new rule. Will be very useful.

  
  

  Regards.
  

  -----------------------------------------------------------
  

  Josean Soroa

  
  

  
  
  
  
  

  
  

  
  

  El jue, 14 jul 2022 a las 18:32, Pablo Fuentes (<notifications@odoo-community.org>) escribió:
  

  Hi, 

  
  

  I compleatly agree with Jairo's message and I don't agree with create a new repo just for the basque country just because of don't want to promote Aritz.

  If we talk about merits and meritocracy, Aritz has some... he is:

  - Top 7 contributor by commits https://github.com/OCA/l10n-spain/graphs/contributors

  - Top 13 contributor by additions https://github.com/OCA/l10n-spain/graphs/contributors?type=a

  
  

  Best Regards,

  
  

  El jue, 14 jul 2022 a las 18:02, Soporte Acysos (<notifications@odoo-community.org>) escribió:
  

  Hello,

  I'm the oldest PSC, but I know that now I'm less active.

  Negative vote.
  

  I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
  Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
  If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.
  

  Greetings,
  Ignacio
  

  El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
  

  Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

  
  

  Regards.

  
  

  El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
  

  Hi all,

  
  

  Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

  
  

  Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

  
  

  Regards.

  
  

  El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
  

  Hi Graeme,

  
  

  some precision inline.

  
  

  regards.
  

  Sylvain LE GAL - Twitter
  

  GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)

  Site Web | FramaSphere | Facebook
  3 Grande rue des Feuillants, 69001 Lyon
  Standard : (+33) 09.72.32.33.17
  

  Service Informatique : (+33) 09.73.79.64.40

  Astreinte Informatique : (+33) 06.81.85.61.43

  Member of the OCA (Odoo Community Association)
  

  Web Site | Twitter
  

  
  

  
  

  Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
  

  Hi Josean,

  
  

  You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

  
  

  FYI,

  - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)

  - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)
  

  
  

   

  Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

  
  

  But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

  
  

  On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
  

  Hi all.
  Excuse me for this long answer but the question is very important for us.
   
  My vote is +1 for Aritz.
  
  My reasons are very similar to the case of Pablo:
  - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
  - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
  - Aritz is one of the few developers who knows deeply Basque Country localization

  
  In are more deep explanation, I'm involved in this question by 3 different rules.
  - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
  From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
  - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
  This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
  - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.
  
  I hope other members of the community will agree with this point of view and will send a +1 to this applicant.
  
  Thanks.
  -----------------------------------------------------------
  Josean Soroa
  LANDOO SL - www.landoo.es
  -----------------------------------------------------------
  

  
  

  
  

  El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
  

  Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -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
  

  _______________________________________________
  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
  

  
  

  
  

  --
  

  Aritz Olea

  LANDOO - Sistemas de Información con Odoo

  _______________________________________________
  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
  

  --
  Acysos S.L. (www.acysos.com)
  Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
  Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
  Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
  Github (http://www.github.com/acysos)
  Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
  C/ Miguel Astrain 18, 1º Oficina A
  31006 Pamplona, Navarra.
  soporte@acysos.com
  Tel. 948238905
  ---------------------- // -------------------
  La información contenida en este mensaje de correo electrónico es
  confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
  acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
  persona a la que va dirigido, cualquier divulgación, copia o distribución de
  la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
  tomada o dejada de tomar basada en la información contenida en este mensaje
  queda prohibida y puede ser ilegal.
  The information in this e-mail is confidential and may be legally privileged.
  It is intended solely for the addressee. Access to this e-mail by anyone is
  unauthorised. If you are not the intended recipient, any disclousure,
  copying, distribuition or any action taken or omited to be taken in reliance
  on it, is prohibited and may be unlawful.
  

  _______________________________________________
  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 Pedro M. Baeza - 02:51 - 15 Jul 2022

• Re: Proposing myself as l10n-spain PSC

  Hi.

  
  

  In this case I think we have a good solution using maintainers rights, so we are not going to follow with this discussion.

  In the mentoring project for v15, Aritz has mentored some modules not included in Basque localization and in the future he will continue this way, so we will talk about that in some months.

  
  

  For now, as mentioned by Pedro, establishing Aritz as maintainer will be enough to speed up the migrations to v14 and 15, we are planning for this month.

  Just for better comprehension of all, some light over very important details:

  - we were told by Pedro and Tobella (or thats what we understood) about the right of maintainers to merge their modules, but restricted to same branch. This is not a solution for us, because we need to merge migration of modules and this in different branch.

  - from Sylvain answer yesterday, we realized that 3 months there has been a new change in OCA rules, to allow maintainers do the same but also in different branches.

  That's perfect for us and I want to thank Sylvain for this key contribution.

  And for the rest of maintainers, take note of this new rule. Will be very useful.

  
  

  Regards.
  

  -----------------------------------------------------------
  

  Josean Soroa

  
  

  
  
  
  
  

  
  

  
  

  El jue, 14 jul 2022 a las 18:32, Pablo Fuentes (<notifications@odoo-community.org>) escribió:
  

  Hi, 

  
  

  I compleatly agree with Jairo's message and I don't agree with create a new repo just for the basque country just because of don't want to promote Aritz.

  If we talk about merits and meritocracy, Aritz has some... he is:

  - Top 7 contributor by commits https://github.com/OCA/l10n-spain/graphs/contributors

  - Top 13 contributor by additions https://github.com/OCA/l10n-spain/graphs/contributors?type=a

  
  

  Best Regards,

  
  

  El jue, 14 jul 2022 a las 18:02, Soporte Acysos (<notifications@odoo-community.org>) escribió:
  

  Hello,

  I'm the oldest PSC, but I know that now I'm less active.

  Negative vote.
  

  I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
  Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
  If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.
  

  Greetings,
  Ignacio
  

  El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
  

  Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

  
  

  Regards.

  
  

  El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
  

  Hi all,

  
  

  Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

  
  

  Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

  
  

  Regards.

  
  

  El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
  

  Hi Graeme,

  
  

  some precision inline.

  
  

  regards.
  

  Sylvain LE GAL - Twitter
  

  GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)

  Site Web | FramaSphere | Facebook
  3 Grande rue des Feuillants, 69001 Lyon
  Standard : (+33) 09.72.32.33.17
  

  Service Informatique : (+33) 09.73.79.64.40

  Astreinte Informatique : (+33) 06.81.85.61.43

  Member of the OCA (Odoo Community Association)
  

  Web Site | Twitter
  

  
  

  
  

  Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
  

  Hi Josean,

  
  

  You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

  
  

  FYI,

  - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)

  - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)
  

  
  

   

  Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

  
  

  But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

  
  

  On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
  

  Hi all.
  Excuse me for this long answer but the question is very important for us.
   
  My vote is +1 for Aritz.
  
  My reasons are very similar to the case of Pablo:
  - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
  - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
  - Aritz is one of the few developers who knows deeply Basque Country localization

  
  In are more deep explanation, I'm involved in this question by 3 different rules.
  - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
  From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
  - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
  This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
  - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.
  
  I hope other members of the community will agree with this point of view and will send a +1 to this applicant.
  
  Thanks.
  -----------------------------------------------------------
  Josean Soroa
  LANDOO SL - www.landoo.es
  -----------------------------------------------------------
  

  
  

  
  

  El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
  

  Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -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
  

  _______________________________________________
  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
  

  
  

  
  

  --
  

  Aritz Olea

  LANDOO - Sistemas de Información con Odoo

  _______________________________________________
  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
  

  --
  Acysos S.L. (www.acysos.com)
  Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
  Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
  Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
  Github (http://www.github.com/acysos)
  Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
  C/ Miguel Astrain 18, 1º Oficina A
  31006 Pamplona, Navarra.
  soporte@acysos.com
  Tel. 948238905
  ---------------------- // -------------------
  La información contenida en este mensaje de correo electrónico es
  confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
  acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
  persona a la que va dirigido, cualquier divulgación, copia o distribución de
  la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
  tomada o dejada de tomar basada en la información contenida en este mensaje
  queda prohibida y puede ser ilegal.
  The information in this e-mail is confidential and may be legally privileged.
  It is intended solely for the addressee. Access to this e-mail by anyone is
  unauthorised. If you are not the intended recipient, any disclousure,
  copying, distribuition or any action taken or omited to be taken in reliance
  on it, is prohibited and may be unlawful.
  

  _______________________________________________
  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 Josean Soroa - 02:41 - 15 Jul 2022

• Re: Proposing myself as l10n-spain PSC

  Hi, 

  
  

  I compleatly agree with Jairo's message and I don't agree with create a new repo just for the basque country just because of don't want to promote Aritz.

  If we talk about merits and meritocracy, Aritz has some... he is:

  - Top 7 contributor by commits https://github.com/OCA/l10n-spain/graphs/contributors

  - Top 13 contributor by additions https://github.com/OCA/l10n-spain/graphs/contributors?type=a

  
  

  Best Regards,

  
  

  El jue, 14 jul 2022 a las 18:02, Soporte Acysos (<notifications@odoo-community.org>) escribió:
  

  Hello,

  I'm the oldest PSC, but I know that now I'm less active.

  Negative vote.
  

  I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
  Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
  If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.
  

  Greetings,
  Ignacio
  

  El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
  

  Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

  
  

  Regards.

  
  

  El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
  

  Hi all,

  
  

  Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

  
  

  Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

  
  

  Regards.

  
  

  El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
  

  Hi Graeme,

  
  

  some precision inline.

  
  

  regards.
  

  Sylvain LE GAL - Twitter
  

  GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)

  Site Web | FramaSphere | Facebook
  3 Grande rue des Feuillants, 69001 Lyon
  Standard : (+33) 09.72.32.33.17
  

  Service Informatique : (+33) 09.73.79.64.40

  Astreinte Informatique : (+33) 06.81.85.61.43

  Member of the OCA (Odoo Community Association)
  

  Web Site | Twitter
  

  
  

  
  

  Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
  

  Hi Josean,

  
  

  You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

  
  

  FYI,

  - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)

  - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)
  

  
  

   

  Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

  
  

  But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

  
  

  On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
  

  Hi all.
  Excuse me for this long answer but the question is very important for us.
   
  My vote is +1 for Aritz.
  
  My reasons are very similar to the case of Pablo:
  - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
  - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
  - Aritz is one of the few developers who knows deeply Basque Country localization

  
  In are more deep explanation, I'm involved in this question by 3 different rules.
  - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
  From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
  - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
  This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
  - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.
  
  I hope other members of the community will agree with this point of view and will send a +1 to this applicant.
  
  Thanks.
  -----------------------------------------------------------
  Josean Soroa
  LANDOO SL - www.landoo.es
  -----------------------------------------------------------
  

  
  

  
  

  El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
  

  Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -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
  

  _______________________________________________
  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
  

  
  

  
  

  --
  

  Aritz Olea

  LANDOO - Sistemas de Información con Odoo

  _______________________________________________
  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
  

  --
  Acysos S.L. (www.acysos.com)
  Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
  Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
  Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
  Github (http://www.github.com/acysos)
  Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
  C/ Miguel Astrain 18, 1º Oficina A
  31006 Pamplona, Navarra.
  soporte@acysos.com
  Tel. 948238905
  ---------------------- // -------------------
  La información contenida en este mensaje de correo electrónico es
  confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
  acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
  persona a la que va dirigido, cualquier divulgación, copia o distribución de
  la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
  tomada o dejada de tomar basada en la información contenida en este mensaje
  queda prohibida y puede ser ilegal.
  The information in this e-mail is confidential and may be legally privileged.
  It is intended solely for the addressee. Access to this e-mail by anyone is
  unauthorised. If you are not the intended recipient, any disclousure,
  copying, distribuition or any action taken or omited to be taken in reliance
  on it, is prohibited and may be unlawful.
  

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

  ---

  by Pablo Fuentes Rodríguez - 06:30 - 14 Jul 2022

• Re: Proposing myself as l10n-spain PSC

  Hello,

  I'm the oldest PSC, but I know that now I'm less active.

  Negative vote.
  

  I always tell the things directly, I see there is a political movement, no meritocracy. Too much PSC in two days.
  Aritz have experience only Basque Country localization. He only contribute in this localization. I don't think that need to be PSC for the moment.
  If there is a separated project for Basque Country Localization, i think that will be a good PSC. But have separated repository for this localization is not necessary now.
  

  Greetings,
  

  Ignacio

  
  

  El 14/7/22 a las 15:27, Pedro M. Baeza (Tecnativa) escribió:
  

  Yeah, Aritz, it's the solution for that modules: to become a maintainer. I already told you about that in some occasion and to remove the current inactive maintainer.

  
  

  Regards.

  
  

  El jue., 14 jul. 2022 15:16, Aritz Olea <notifications@odoo-community.org> escribió:
  

  Hi all,

  
  

  Pedro, even if I were PSC I would not merge PRs of modules I don't know enough. I think it's more efficient having more PSCs specialized and motivated in some modules than trying to have someone specialized in all of them.

  
  

  Thanks Graeme and Sylvain for your feedback. Sylvain, I didn't know the information you sent about the merge right of the module maintainers. This can be really helpful for us. If I don't get Pedro's approval, this can be a good solution for the Basque modules.

  
  

  Regards.

  
  

  El jue, 14 jul 2022 a las 14:56, Sylvain LE GAL (<notifications@odoo-community.org>) escribió:
  

  Hi Graeme,

  
  

  some precision inline.

  
  

  regards.
  

  Sylvain LE GAL - Twitter
  

  GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)

  Site Web | FramaSphere | Facebook
  3 Grande rue des Feuillants, 69001 Lyon
  Standard : (+33) 09.72.32.33.17
  

  Service Informatique : (+33) 09.73.79.64.40

  Astreinte Informatique : (+33) 06.81.85.61.43

  Member of the OCA (Odoo Community Association)
  

  Web Site | Twitter
  

  
  

  
  

  Le jeu. 14 juil. 2022 à 14:36, Graeme Gellatly <notifications@odoo-community.org> a écrit :
  

  Hi Josean,

  
  

  You raise an interesting point and part of this is how different repos evolved. We are starting to see a kind of natural split between a PSC with I suppose a high level view of a repository's purpose, strategy, inclusions exclusions etc and maintainers with specific module knowledge as repositories get larger. However, there is a tension that maintainers cannot merge even the code they maintain, but PSC's can. For me, long term the solution is merge rights for maintainers for the modules they maintain.

  
  

  FYI,

  - a developer has merge right on github for a PR if declared maintainers in the manifest of the modified module(s) for the current branch. That feature has been enabled since 3 years. (Ref.)

  - a developper has also merge right on github for a PR if declared maintainer in the manifest of the modified module(s) for any branch. (past or future). That feature has been enabled since 3 monthes. (Ref)
  

  
  

   

  Indeed, this is how almost all other opensource works. I know people with much more knowledge than me are working on this. But in this case, it may make more sense for a separate repository anyway. In fact maybe it makes sense for a lot of repos.

  
  

  But also there are very many workarounds to a short term merge problem, and in a code sprint it often makes more sense to work separately anyway just for CI time, although maybe this no longer applies. I don't know the Spanish localisation at all, but FWIW the idea that fiscal specific code is going to be merged inside of two days into what is a very long lived and presumably stable repo is the opposite of a good reason.  In fact, I thought the policy was 5 days after 2 approved reviews to allow any objections unless some good reason to override. Maybe I'm wrong, those principles have changed over time.

  
  

  On Thu, Jul 14, 2022 at 10:52 PM Josean Soroa - Landoo <notifications@odoo-community.org> wrote:
  

  Hi all.
  Excuse me for this long answer but the question is very important for us.
   
  My vote is +1 for Aritz.
  
  My reasons are very similar to the case of Pablo:
  - I believe in our l10n-spain repo, we shoudn't restrict PSCs to those with deep knowledge of all 39 modules. Selected PSCs should be professionals with enough experience on OCA contribution rules and aware of its limitations. They have to review and merge only modules within their area of expertise.
  - I know him as a serious and responsible professional. I'm sure he is not going to merge PRs outside his expertise.
  - Aritz is one of the few developers who knows deeply Basque Country localization

  
  In are more deep explanation, I'm involved in this question by 3 different rules.
  - As President of Aeodoo I'm trying to boost spanish localization and I believe that one of the mistakes in spanish community is the very small number of PSCs
  From last year Urtzi (from Coninpe) is the member of the board of Aeodoo leading with spanish localization and results are very hopeful. Just see "Mentoring project". Hi has a very good vision on this point and is asking for more PSCs.
  - As member of "Basque Country localization team", I'm actively working to add specific Basque fiscal requirements (basically Ticketbai). Leader of this team is Victor (from Kernet) and this days is in holidays, so I speak in his name. We are planning to proceed with two code sprints on this july and we need enough PSCs to not stop the development of this window. In this team we are 10 companies with a compromise of at least 2 resources dedicated to this activities, each one (so 20 people). Objective is to have all our needed developments from v13 to v15 at the end of July. This is not possible if we have to wait to much for merge. Take note that we are speaking about 5 modules x 2 versions (14 and 15) = 10 PRs with their approvals and merges.
  This is too much work in a windows of 2 days for only one or two PSCs and they need good knowledge about Basque fiscality. None of actual PSCs is involved directly in this developments.
  - As contributor I see other questions. For example, in Italy they have 9 PSCs (as explained by Sergio Corato in this mailing list). All of them are fully skilled in their 54 modules? I'm sure they're not. But I'm sure each one of them only merges modules that they know enough.
  
  I hope other members of the community will agree with this point of view and will send a +1 to this applicant.
  
  Thanks.
  -----------------------------------------------------------
  Josean Soroa
  LANDOO SL - www.landoo.es
  -----------------------------------------------------------
  

  
  

  
  

  El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:
  

  Sorry, Aritz, your experience in the localization is totally limited to TicketBAI, so for me as PSC representative of l10n-spain is a -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
  

  _______________________________________________
  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
  

  
  

  
  

  --
  

  Aritz Olea

  LANDOO - Sistemas de Información con Odoo

  _______________________________________________
  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
  

  --
  Ignacio Ibeas
  Acysos S.L. (www.acysos.com)
  Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
  Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
  Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
  Github (http://www.github.com/acysos)
  Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
  C/ Miguel Astrain 18, 1º Oficina A
  31006 Pamplona, Navarra.
  ignacio@acysos.com
  Tel. 948238905
  ---------------------- // -------------------
  La información contenida en este mensaje de correo electrónico es
  confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
  acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
  persona a la que va dirigido, cualquier divulgación, copia o distribución de
  la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
  tomada o dejada de tomar basada en la información contenida en este mensaje
  queda prohibida y puede ser ilegal.
  The information in this e-mail is confidential and may be legally privileged.
  It is intended solely for the addressee. Access to this e-mail by anyone is
  unauthorised. If you are not the intended recipient, any disclousure,
  copying, distribuition or any action taken or omited to be taken in reliance
  on it, is prohibited and may be unlawful.
  

  ---

  by Ignacio Ibeas - 06:10 - 14 Jul 2022

15 more replies