Archives
Contributors
-
Re: Procedure to create 16.0 branches
I already apply this policy on the repositories I manage.So +1.On Wed, Jul 20, 2022 at 2:07 PM Jesús Alan Ramos Rodríguez <notifications@odoo-community.org> wrote:+1El mié, 20 de jul. de 2022 6:57 a. m., Maxime Chambreuil <notifications@odoo-community.org> escribió:+1El mié, 20 de jul. de 2022 06:07, Roussel, Denis <notifications@odoo-community.org> escribió:As I'm in favor of that change for so long, you definitely convinced me with the arguments you exposed.So, +1On Wed, Jul 20, 2022 at 12:46 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:Dear contributors,I'm starting to think about the process to create the 16.0 branches. And the more I think about it, the more I'm convinced we should do it by adding "installable": False in the module manifests, instead of creating empty branches.This would have several benefits:- Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
- Avoid CLA bot issues: currently, the CLA bot is flagging old commits that were ok at the time they were created, but may not be valid today as contributors may have changed email, or revoked their CLA.
- Reduce oca-github-bot complexity:
work has to be done to make the bot aware of other branches in
migration PRs (notably to look-up maintainers). This would be unnecessary
if a migration PR is a normal PR to an existing addon directory. On the
contrary, the bot could even detect migration PRs automatically by
noticing the change to the installable flag, so this could simplify some
processes.
- Slow git repo growth: by avoiding the recreation of identical commits in several branches we would slow down the git repo size increase.
About the possible drawbacks, I am under the impression that all the reasons we had back then to create empty branches have faded away:- Today, Odoo and all the OCA tooling work perfectly well when there are addons marked as uninstallable. They are correctly ignored by linters, tests, and Odoo does not attempt to import the code.
- Regarding discoverability, the addons table in the README shows a clear view of what is not migrated.
All we'd need maybe is to agree on a process to remove modules that have not been migrated for several versions. But in a first approach, regular PRs to remove now useless modules would probably be sufficient.Are there any other arguments (pro or con) that I would have missed ?Looking forward to reading your feedback on this proposal.-Stéphane_______________________________________________
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 Laurent Mignon - 02:45 - 20 Jul 2022 - Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
-
Re: Procedure to create 16.0 branches
+1El mié, 20 de jul. de 2022 6:57 a. m., Maxime Chambreuil <notifications@odoo-community.org> escribió:+1El mié, 20 de jul. de 2022 06:07, Roussel, Denis <notifications@odoo-community.org> escribió:As I'm in favor of that change for so long, you definitely convinced me with the arguments you exposed.So, +1On Wed, Jul 20, 2022 at 12:46 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:Dear contributors,I'm starting to think about the process to create the 16.0 branches. And the more I think about it, the more I'm convinced we should do it by adding "installable": False in the module manifests, instead of creating empty branches.This would have several benefits:- Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
- Avoid CLA bot issues: currently, the CLA bot is flagging old commits that were ok at the time they were created, but may not be valid today as contributors may have changed email, or revoked their CLA.
- Reduce oca-github-bot complexity:
work has to be done to make the bot aware of other branches in
migration PRs (notably to look-up maintainers). This would be unnecessary
if a migration PR is a normal PR to an existing addon directory. On the
contrary, the bot could even detect migration PRs automatically by
noticing the change to the installable flag, so this could simplify some
processes.
- Slow git repo growth: by avoiding the recreation of identical commits in several branches we would slow down the git repo size increase.
About the possible drawbacks, I am under the impression that all the reasons we had back then to create empty branches have faded away:- Today, Odoo and all the OCA tooling work perfectly well when there are addons marked as uninstallable. They are correctly ignored by linters, tests, and Odoo does not attempt to import the code.
- Regarding discoverability, the addons table in the README shows a clear view of what is not migrated.
All we'd need maybe is to agree on a process to remove modules that have not been migrated for several versions. But in a first approach, regular PRs to remove now useless modules would probably be sufficient.Are there any other arguments (pro or con) that I would have missed ?Looking forward to reading your feedback on this proposal.-Stéphane_______________________________________________
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 "Jesús Alan Ramos Rodríguez" <alan.ramos@jarsa.com> - 02:06 - 20 Jul 2022 - Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
-
Re: Procedure to create 16.0 branches
+1El mié, 20 de jul. de 2022 06:07, Roussel, Denis <notifications@odoo-community.org> escribió:As I'm in favor of that change for so long, you definitely convinced me with the arguments you exposed.So, +1On Wed, Jul 20, 2022 at 12:46 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:Dear contributors,I'm starting to think about the process to create the 16.0 branches. And the more I think about it, the more I'm convinced we should do it by adding "installable": False in the module manifests, instead of creating empty branches.This would have several benefits:- Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
- Avoid CLA bot issues: currently, the CLA bot is flagging old commits that were ok at the time they were created, but may not be valid today as contributors may have changed email, or revoked their CLA.
- Reduce oca-github-bot complexity:
work has to be done to make the bot aware of other branches in
migration PRs (notably to look-up maintainers). This would be unnecessary
if a migration PR is a normal PR to an existing addon directory. On the
contrary, the bot could even detect migration PRs automatically by
noticing the change to the installable flag, so this could simplify some
processes.
- Slow git repo growth: by avoiding the recreation of identical commits in several branches we would slow down the git repo size increase.
About the possible drawbacks, I am under the impression that all the reasons we had back then to create empty branches have faded away:- Today, Odoo and all the OCA tooling work perfectly well when there are addons marked as uninstallable. They are correctly ignored by linters, tests, and Odoo does not attempt to import the code.
- Regarding discoverability, the addons table in the README shows a clear view of what is not migrated.
All we'd need maybe is to agree on a process to remove modules that have not been migrated for several versions. But in a first approach, regular PRs to remove now useless modules would probably be sufficient.Are there any other arguments (pro or con) that I would have missed ?Looking forward to reading your feedback on this proposal.-Stéphane_______________________________________________
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 Maxime Chambreuil - 01:56 - 20 Jul 2022 - Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
-
Re: Procedure to create 16.0 branches
As I'm in favor of that change for so long, you definitely convinced me with the arguments you exposed.So, +1On Wed, Jul 20, 2022 at 12:46 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:Dear contributors,I'm starting to think about the process to create the 16.0 branches. And the more I think about it, the more I'm convinced we should do it by adding "installable": False in the module manifests, instead of creating empty branches.This would have several benefits:- Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
- Avoid CLA bot issues: currently, the CLA bot is flagging old commits that were ok at the time they were created, but may not be valid today as contributors may have changed email, or revoked their CLA.
- Reduce oca-github-bot complexity:
work has to be done to make the bot aware of other branches in
migration PRs (notably to look-up maintainers). This would be unnecessary
if a migration PR is a normal PR to an existing addon directory. On the
contrary, the bot could even detect migration PRs automatically by
noticing the change to the installable flag, so this could simplify some
processes.
- Slow git repo growth: by avoiding the recreation of identical commits in several branches we would slow down the git repo size increase.
About the possible drawbacks, I am under the impression that all the reasons we had back then to create empty branches have faded away:- Today, Odoo and all the OCA tooling work perfectly well when there are addons marked as uninstallable. They are correctly ignored by linters, tests, and Odoo does not attempt to import the code.
- Regarding discoverability, the addons table in the README shows a clear view of what is not migrated.
All we'd need maybe is to agree on a process to remove modules that have not been migrated for several versions. But in a first approach, regular PRs to remove now useless modules would probably be sufficient.Are there any other arguments (pro or con) that I would have missed ?Looking forward to reading your feedback on this proposal.-Stéphane_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Denis Roussel - 01:05 - 20 Jul 2022 - Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
-
Procedure to create 16.0 branches
Dear contributors,I'm starting to think about the process to create the 16.0 branches. And the more I think about it, the more I'm convinced we should do it by adding "installable": False in the module manifests, instead of creating empty branches.This would have several benefits:- Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
- Avoid CLA bot issues: currently, the CLA bot is flagging old commits that were ok at the time they were created, but may not be valid today as contributors may have changed email, or revoked their CLA.
- Reduce oca-github-bot complexity:
work has to be done to make the bot aware of other branches in
migration PRs (notably to look-up maintainers). This would be unnecessary
if a migration PR is a normal PR to an existing addon directory. On the
contrary, the bot could even detect migration PRs automatically by
noticing the change to the installable flag, so this could simplify some
processes.
- Slow git repo growth: by avoiding the recreation of identical commits in several branches we would slow down the git repo size increase.
About the possible drawbacks, I am under the impression that all the reasons we had back then to create empty branches have faded away:- Today, Odoo and all the OCA tooling work perfectly well when there are addons marked as uninstallable. They are correctly ignored by linters, tests, and Odoo does not attempt to import the code.
- Regarding discoverability, the addons table in the README shows a clear view of what is not migrated.
All we'd need maybe is to agree on a process to remove modules that have not been migrated for several versions. But in a first approach, regular PRs to remove now useless modules would probably be sufficient.Are there any other arguments (pro or con) that I would have missed ?Looking forward to reading your feedback on this proposal.-Stéphane
by Stéphane Bidoul - 12:45 - 20 Jul 2022 - Improve security.
Indeed, currently migration PRs have a lot of commits and reviewers
only look at the last 2 commits. By accident or malice, it would be easy
for a contributor to sneak bad code in older commits, that would go
unnoticed. As the community grows, I think this a very important topic.
-
RE: Proposing myself as l10n-spain PSC
Hello Ignacio,
> “I need more information. Why this change?”
I was on holidays in the beach, someone wrote me by WhatsApp asking if I know something about all the proposal PSC in that day, I didn’t know anything. The sea, the beach and 30º magic degrees was enough for me with my family. But I’m human and I was so curious, so I check my email.
I realize that in my PSC proposal was a few answers, all positive except one, why now there was too many answers?
I remembered the important Issue that odoo-community.org Odoo had with SPAM and that Jairo fixed with Stephan Bidoul couples weeks ago (you can check it in discord). So, I thought, hey! Maybe my proposal was saw for a few contributors as all the emails went to spam!
The prove is that you didn’t receive the answer of Omar while it is there! à https://odoo-community.org/groups/contributors-15/contributors-243662?mode=&date_begin=&date_end=
The email from Omar was rejected by your mail server.
I just wanted to know the opinion of more contributors; (and that day looked like everyone would read it). In my first proposal I didn’t want to argument more after a decade in Odoo. I'm pretty tired of endless discussions with Pedro, I didn't want to argue anymore. But seeing so much movement, I thought, let's see what more people think, Pedro is a great contributor, but he is not the community nor is the location his, he is from everyone to everyone.
Right now, honestly, I am very happy to see how great contributors and accounting experts like Vicent or Omar are PSC for a stronger, more united, more plural and higher quality localization.
I am so happy that if you consider that the community will be better with me from PSC, great and if not, great too!
For a more plural, more united, and more participatory community. With quality yes, but with kindness and empathy.
Best regards for everyone and happy holidays!
Rafael
De: Ignacio Ibeas (Acysos S.L.) <notifications@odoo-community.org>
Enviado el: jueves, 14 de julio de 2022 17:52
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Proposing myself as l10n-spain PSCHello,
I'm the oldest PSC, but I know that now I'm less active.
I don't understand. You request a several weeks ago, but you withdraw the request. Now I see you get the approve from the new PSC.
Now you has this votes from PSC:
-1 Pedro M. Baeza (PSC)
+1 Harald Panten (PSC)For the moment I don't make a vote. The last time I went to study the request and you tell me that is not necessary.
Now you add the positive vote of Omar Castiñeira, but I don't see the mail form him.
I need more information. Why this change?
Greetings,
IgnacioEl 14/7/22 a las 13:27, Jairo Llopis escribió:
El jue, 14 de jul de 2022 a las 11:21:53 AM, Rafael Blasco <notifications@odoo-community.org> escribió:
Due the issue in OCA about mailing list and Spam which was solved by Jairo and Stefan surely my proposition wasn’t received by the Spanish community, and today looks like the best day to refresh
Of course +1
_______________________________________________
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._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rafael Blasco (Moduon) - 10:16 - 18 Jul 2022 -
One stop shop (OSS) Tax with foreign fixed establishment
Hi all,Has anymore already faced or/and solved the case where you need to apply the tax based on your fixed establishment providing the goods.My company is in country C only (no multi-company) and I have a warehouse in country C and D. So accounting is declared in country C, taxes are declared in country C and D according to their respective shipments.When the SO is placed, the shipping country is not known yet.If country D is shipping goods to a customer address in country D, this is a national delivery with the VAT of the delivery address country.If country D is shipping goods to a B2B EU customer address not in country D, this is an intracom delivery without VAT.Worst use case is if for one SO line of 10 units, you ship 4 from country C to country C (national delivery) and 6 from country D to country C (intracom delivery). You need an invoice for each delivering country and apply different tax while it's related to the same SO line.For B2C, the tax rate is always the one based on the customer delivery address but the declaration is done to the tax department of the delivering country.The 2 possible approaches I see are:- change the SO line at delivery to put the correct tax. But this could lead to SO line splitting and the SO does not reflect the original SO confirmation anymore. This can cause issues in the connections to e-commerce platforms. So I'm not in favor of it- change the tax set on the invoice at invoice generation. This will need to know what tax to apply, meaning we need to refine the qty_to_invoice to have one qty_to_invoice per delivering country.Of course, this should also work with returns and credit notes and the goods can be returned to a different country than the one that initially shipped the goods.Any input is welcome. I created this discussion here:Kind regards,Jacques-Etienne Baudoux
by Jacques-Etienne Baudoux - 11:56 - 18 Jul 2022 -
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 SoroaEl 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 SoroaEl 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=aBest 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.
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.40Astreinte Informatique : (+33) 06.81.85.61.43Member of the OCA (Odoo Community Association)
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 OleaLANDOO - 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 SoroaEl 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=aBest 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.
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.40Astreinte Informatique : (+33) 06.81.85.61.43Member of the OCA (Odoo Community Association)
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 OleaLANDOO - 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 SoroaEl 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=aBest 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.
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.40Astreinte Informatique : (+33) 06.81.85.61.43Member of the OCA (Odoo Community Association)
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 OleaLANDOO - 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 all.I don't want to be polemic, I just would like to have a decision based in good information and following answer of Pablo, I think he can help us with some more info.Pablo, I know you're the leader of a very skilled team.To clarify this point to the rest of contributors, could you share with us github accounts of your developers and the sum of all their PRs in state closed?I mean the metric proposed by Pedro withIn a quick review I can share this, with all of you.PRs closed and authored by:
1) Actual PSCs in descending order
Pedro, 216
https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Apedrobaeza+is%3Aclosed+
Acysos, 51
https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Aacysos+is%3Aclosed+
Omar, 42
https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Aomar7r+is%3Aclosed+
Cubells, 42
https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Acubells+is%3Aclosed+
Harald, 12
https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3AHaraldPanten+is%3Aclosed+
2) Other involved contributors
Aritz, 132
https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Aao-landoo+is%3Aclosed+
Etobella, 76
https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Aetobella+is%3Aclosed+
3) Studio73, ???
https://github.com/OCA/l10n-spain/pulls?q=is%3Apr+author%3Afuentes73+is%3Aclosed
6 + other members of this companyThanks.-----------------------------------------------------------Josean SoroaEl jue, 14 jul 2022 a las 18:12, Pablo Fuentes (<notifications@odoo-community.org>) escribió:Hello everyone,
Thank you all for your kind words. Just for the record.
Although you might think that I do not have enough experience in l10n-spain, technically I do, and functionally I am well advised by my colleagues who have enough experience (1 lawyer and 3 tax advisors).
So my proposal was on behalf of the Studio73 team because I am the one with the most availability.
About very few contributions it's not compleatly fair. I'm behind most of my colleagues contributions during the analysis and internal review and this is dificult to measure but it's ok.
Regardless, there is no problem by my side not to promote as a PSC.
Thanks for your consideration.
Best Regards,Pablo Fuentes
Gerente - Ing. Informático
pablo@studio73.esConsultoría Informática Studio 73 S.L.
C/ Camí vell de l'estació, 6 Bajo Izquierda
46870 - Ontinyent (Valencia)
www.studio73.es - 96 191 12 79El jue, 14 jul 2022 a las 15:07, Enric Tobella Alomar (<notifications@odoo-community.org>) escribió:IMO, It is too soon for Pablo being a PSC member. You can check how many PRS he has done on OCA and it is not so much:Most of them are from long time ago and only 6 in l10n-spain.It is allways interesting to have PSCs, but I would prefer to see him more on action before.Kind regards,From: Urtzi Pérez <notifications@odoo-community.org>
To: "Contributors" <contributors@odoo-community.org>
Date: Thu, 14 Jul 2022 11:56:57 -0000
Subject: Re: Proposing myself as l10n-spain PSC
Hi,In my opinion Pablo is a +1 too.I agree with every point Josean has explained, and as the responsible of the spanish localization and member of the board of Aeodoo, I'd like to reinforce Josean's words saying that the projects we are facing this year will result in a large amount of contributions in short periods of time, so we'd need some efficiency in the deepest technical reviews most contributors can't do (mostly because of lack of experience).Pedro, I think the most important concept is to give the Spanish localization the push it needs. I'm sure that working with skilled people like Pablo could help you (and the other actual PSCs) to improve the repository's health.Regards.¿Nos dejas una reseña en Google My Business? Haz Clic AquíUrtzi PérezPol. Ind. Torrelarragoiti Parcela 8A- Pab. 1048170 ZamudioAviso legal: Este mensaje electrónico está dirigido únicamente a la(s) dirección(es) indicadas anteriormente; el carácter confidencial, personal e intransferible del mismo está protegido legalmente. Cualquier revelación, uso o reenvío no autorizado, completo o en parte, está prohibido. Si ha recibido este mensaje por equivocación, notifíquelo inmediatamente a la persona que lo ha enviado y borre el mensaje original junto con sus ficheros anexos sin leerlo ni grabarlo, total o parcialmenteEl jue, 14 jul 2022 a las 13:07, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:They can contribute the same reviewing and proposing pull requests. The only difference is the right to trigger the merge command. What can't be done is someone that hasn't contributed a lot yet to the localization to have the same merits that someone that has done a lot along the years.This proposal can be reviewed in some time when the number of contributions will be significant.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
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
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:26 - 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=aBest 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.
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.40Astreinte Informatique : (+33) 06.81.85.61.43Member of the OCA (Odoo Community Association)
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 OleaLANDOO - 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.
Greetings,
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.
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.
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.40Astreinte Informatique : (+33) 06.81.85.61.43Member of the OCA (Odoo Community Association)
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 OleaLANDOO - 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 -
Re: Proposing myself as l10n-spain PSC
Hello everyone,
Thank you all for your kind words. Just for the record.
Although you might think that I do not have enough experience in l10n-spain, technically I do, and functionally I am well advised by my colleagues who have enough experience (1 lawyer and 3 tax advisors).
So my proposal was on behalf of the Studio73 team because I am the one with the most availability.
About very few contributions it's not compleatly fair. I'm behind most of my colleagues contributions during the analysis and internal review and this is dificult to measure but it's ok.
Regardless, there is no problem by my side not to promote as a PSC.
Thanks for your consideration.
Best Regards,Pablo Fuentes
Gerente - Ing. Informático
pablo@studio73.esConsultoría Informática Studio 73 S.L.
C/ Camí vell de l'estació, 6 Bajo Izquierda
46870 - Ontinyent (Valencia)
www.studio73.es - 96 191 12 79El jue, 14 jul 2022 a las 15:07, Enric Tobella Alomar (<notifications@odoo-community.org>) escribió:IMO, It is too soon for Pablo being a PSC member. You can check how many PRS he has done on OCA and it is not so much:Most of them are from long time ago and only 6 in l10n-spain.It is allways interesting to have PSCs, but I would prefer to see him more on action before.Kind regards,From: Urtzi Pérez <notifications@odoo-community.org>
To: "Contributors" <contributors@odoo-community.org>
Date: Thu, 14 Jul 2022 11:56:57 -0000
Subject: Re: Proposing myself as l10n-spain PSC
Hi,In my opinion Pablo is a +1 too.I agree with every point Josean has explained, and as the responsible of the spanish localization and member of the board of Aeodoo, I'd like to reinforce Josean's words saying that the projects we are facing this year will result in a large amount of contributions in short periods of time, so we'd need some efficiency in the deepest technical reviews most contributors can't do (mostly because of lack of experience).Pedro, I think the most important concept is to give the Spanish localization the push it needs. I'm sure that working with skilled people like Pablo could help you (and the other actual PSCs) to improve the repository's health.Regards.¿Nos dejas una reseña en Google My Business? Haz Clic AquíUrtzi PérezPol. Ind. Torrelarragoiti Parcela 8A- Pab. 1048170 ZamudioAviso legal: Este mensaje electrónico está dirigido únicamente a la(s) dirección(es) indicadas anteriormente; el carácter confidencial, personal e intransferible del mismo está protegido legalmente. Cualquier revelación, uso o reenvío no autorizado, completo o en parte, está prohibido. Si ha recibido este mensaje por equivocación, notifíquelo inmediatamente a la persona que lo ha enviado y borre el mensaje original junto con sus ficheros anexos sin leerlo ni grabarlo, total o parcialmenteEl jue, 14 jul 2022 a las 13:07, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:They can contribute the same reviewing and proposing pull requests. The only difference is the right to trigger the merge command. What can't be done is someone that hasn't contributed a lot yet to the localization to have the same merits that someone that has done a lot along the years.This proposal can be reviewed in some time when the number of contributions will be significant.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
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
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:06 - 14 Jul 2022 -
Re: Proposing myself as l10n-spain PSC
Helo,
I'm agree with the Enric reply. For the moment nevative vote.
Greetings
El 14/7/22 a las 15:07, Enric Tobella Alomar escribió:
IMO, It is too soon for Pablo being a PSC member. You can check how many PRS he has done on OCA and it is not so much:Most of them are from long time ago and only 6 in l10n-spain.It is allways interesting to have PSCs, but I would prefer to see him more on action before.Kind regards,From: Urtzi Pérez <notifications@odoo-community.org>
To: "Contributors" <contributors@odoo-community.org>
Date: Thu, 14 Jul 2022 11:56:57 -0000
Subject: Re: Proposing myself as l10n-spain PSC
Hi,In my opinion Pablo is a +1 too.I agree with every point Josean has explained, and as the responsible of the spanish localization and member of the board of Aeodoo, I'd like to reinforce Josean's words saying that the projects we are facing this year will result in a large amount of contributions in short periods of time, so we'd need some efficiency in the deepest technical reviews most contributors can't do (mostly because of lack of experience).Pedro, I think the most important concept is to give the Spanish localization the push it needs. I'm sure that working with skilled people like Pablo could help you (and the other actual PSCs) to improve the repository's health.Regards.¿Nos dejas una reseña en Google My Business? Haz Clic AquíUrtzi PérezPol. Ind. Torrelarragoiti Parcela 8A- Pab. 1048170 ZamudioAviso legal: Este mensaje electrónico está dirigido únicamente a la(s) dirección(es) indicadas anteriormente; el carácter confidencial, personal e intransferible del mismo está protegido legalmente. Cualquier revelación, uso o reenvío no autorizado, completo o en parte, está prohibido. Si ha recibido este mensaje por equivocación, notifíquelo inmediatamente a la persona que lo ha enviado y borre el mensaje original junto con sus ficheros anexos sin leerlo ni grabarlo, total o parcialmenteEl jue, 14 jul 2022 a las 13:07, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:They can contribute the same reviewing and proposing pull requests. The only difference is the right to trigger the merge command. What can't be done is someone that hasn't contributed a lot yet to the localization to have the same merits that someone that has done a lot along the years.This proposal can be reviewed in some time when the number of contributions will be significant.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
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
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:06 - 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.
I don't understand. You request a several weeks ago, but you withdraw the request. Now I see you get the approve from the new PSC.
Now you has this votes from PSC:
-1 Pedro M. Baeza (PSC)
+1 Harald Panten (PSC)For the moment I don't make a vote. The last time I went to study the request and you tell me that is not neccesary.
Now you add the positve vote of Omar Castiñeira, but I don't see the mail form him.
I need more information. Why this change?
Greetings,
Ignacio
El 14/7/22 a las 13:27, Jairo Llopis escribió:
El jue, 14 de jul de 2022 a las 11:21:53 AM, Rafael Blasco <notifications@odoo-community.org> escribió:
Due the issue in OCA about mailing list and Spam which was solved by Jairo and Stefan surely my proposition wasn’t received by the Spanish community, and today looks like the best day to refresh
Of course +1_______________________________________________
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 - 05:50 - 14 Jul 2022 -
Re: Proposing myself as l10n-spain PSC
Hello,
I also agree.
Greetings
El 13/7/22 a las 16:46, Enric Tobella Alomar escribió:
I added you as member of the PSC team. GitHub invite should follow in the next 24h.Best regardsFrom: Omar Castiñeira <notifications@odoo-community.org>
To: "Contributors" <contributors@odoo-community.org>
Date: Wed, 13 Jul 2022 12:12:16 -0000
Subject: Re: Proposing myself as l10n-spain PSC
Thanks Pedro, nowadays I'm not a member of core contributors, in the early years yes.El mié, 13 jul 2022 a las 11:32, Pedro M. Baeza (Tecnativa) (<notifications@odoo-community.org>) escribió:OK, Omar is an experienced contributor and also in the localization repository. He doesn't need this PSC title, as he already has merge rights as core contributor, but there's no problem in have him on board.+1Regards._______________________________________________
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
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
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 - 05:50 - 14 Jul 2022 -
Re: Proposing myself as l10n-spain PSC
Hello,
I also agree.
Greetings
El 13/7/22 a las 16:46, Enric Tobella Alomar escribió:
I added you as member of the PSC team. GitHub invite should follow in the next 24h.Best regardsFrom: "cubells" <notifications@odoo-community.org>
To: "Contributors" <contributors@odoo-community.org>
Date: Wed, 13 Jul 2022 07:02:10 -0000
Subject: Proposing myself as l10n-spain PSC
Hi all, I would like to apply as PSC for https://github.com/OCA/l10n-spain Main reason is the big development we are doing from last year to cover Basque Country requirements (Fiscal Ticketbai and Batuz project). This task is not fully finished and we need a big push in next weeks. Also in next months we have a team working in localization for Canary Islands, with also specific fiscal rules. And in near future we expect to have important changes in rest of spanish fiscal rules. I have contributed in this repository for last years and I have a developer and functional profile. My github account is https://github.com/cubells Thanks for considering my request and regards. Vicent Cubells Trey, kilobytes de soluciones -- Atentament, cubells. --
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
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 - 05:50 - 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.
I don't understand. You request a several weeks ago, but you withdraw the request. Now I see you get the approve from the new PSC.
Now you has this votes from PSC:
-1 Pedro M. Baeza (PSC)
+1 Harald Panten (PSC)For the moment I don't make a vote. The last time I went to study the request and you tell me that is not neccesary.
Now you add the positve vote of Omar Castiñeira, but I don't see the mail form him.
I need more information. Why this change?
Greetings,
Ignacio
El 14/7/22 a las 13:27, Jairo Llopis escribió:
El jue, 14 de jul de 2022 a las 11:21:53 AM, Rafael Blasco <notifications@odoo-community.org> escribió:
Due the issue in OCA about mailing list and Spam which was solved by Jairo and Stefan surely my proposition wasn’t received by the Spanish community, and today looks like the best day to refresh
Of course +1_______________________________________________
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 - 05:46 - 14 Jul 2022
