Contributors

• Re: oca/oca.recipe.odoo repository?

  > Could somebody with the appropriate permissions make the settings accessible
  
  > to the maintainers (StefanRijnhart+hbrunn at the moment)?
  
  > Currently permissions are managed via a GitHub team sync script, from the
  
  > PSC members database. The current policy is that only PSC representatives
  
  > and board have admin access to the repos. I'm not sure it still makes sense
  
  > for tooling repos such as this one, but it's the way it is now. I gave you
  
  > access, but it may only last until the team sync script kicks in again.
  
  thanks Stéphane, I changed the bits that need changing currently, so it won't 
  be super problematic if we lose access again.
  
  
  > Generally, who is the address to ask about OCA github permission stuff? I
  
  > try to avoid asking Alexandre about everything.
  
  > I guess it's support@odoo-community.org [3] , but it will mostly end up with
  
  > Alexandre and myself anyway ;) That's also something we'll need to work on,
  
  > i.e. manage the bus factor for the OCA infrastructure. Cheers,
  
  indeed, that's an important one.
  
  
  -- 
  Your partner for the hard Odoo problems
  https://hunki-enterprises.com

  ---

  by Holger Brunn - 11:30 - 22 Dec 2021

  1 attachments 1 attachments

  signature.asc

• Re: oca/oca.recipe.odoo repository?

  Hi Holger,

  
  

  On Wed, Dec 22, 2021 at 10:46 AM Holger Brunn <mail@hunki-enterprises.com> wrote:
  

  we're busy with this currently, but don't have access to the settings tab of 
  https://github.com/OCA/oca.recipe.odoo
  Could somebody with the appropriate permissions make the settings accessible 
  to the maintainers (StefanRijnhart+hbrunn at the moment)?

  
  

  Currently permissions are managed via a GitHub team sync script, from the PSC members database.

  The current policy is that only PSC representatives and board have admin access to the repos.

  I'm not sure it still makes sense for tooling repos such as this one, but it's the way it is now.

  
  

  I gave you access, but it may only last until the team sync script kicks in again.
  

   

  Generally, who is the address to ask about OCA github permission stuff? I try 
  to avoid asking Alexandre about everything.
  

  
  

  I guess it's support@odoo-community.org, but it will mostly end up with Alexandre and myself anyway ;)

  That's also something we'll need to work on, i.e. manage the bus factor for the OCA infrastructure.

  
  

  Cheers,
  

  
  

  -sbi
  

  ---

  by Stéphane Bidoul - 11:01 - 22 Dec 2021

• Re: oca/oca.recipe.odoo repository?

  Hi all,
  
  we're busy with this currently, but don't have access to the settings tab of 
  https://github.com/OCA/oca.recipe.odoo
  Could somebody with the appropriate permissions make the settings accessible 
  to the maintainers (StefanRijnhart+hbrunn at the moment)?
  
  Generally, who is the address to ask about OCA github permission stuff? I try 
  to avoid asking Alexandre about everything.
  
  Thanks in advance,
  Holger
  
  
  -- 
  Your partner for the hard Odoo problems
  https://hunki-enterprises.com

  ---

  by Holger Brunn - 10:45 - 22 Dec 2021

  1 attachments 1 attachments

  signature.asc

• Re: oca/oca.recipe.odoo repository?

  > I'll take care of this this week.
  
  yay thanks! We're busy closing PRs on
  https://github.com/anybox/anybox.recipe.odoo/pulls
  currently, the plan is to also add py3 tests there and then move the whole 
  thing to the OCA repo
  
  
  -- 
  Your partner for the hard Odoo problems
  https://hunki-enterprises.com

  ---

  by Holger Brunn - 08:55 - 3 Mar 2021

  1 attachments 1 attachments

  signature.asc

• Re: oca/oca.recipe.odoo repository?

  I'll take care of this this week.
  
  Alexandre
  
  On 04/02/2021 11:02, Holger Brunn wrote:
  
  > Hi all,
  
  > 
  
  > I'd like to fork https://github.com/anybox/anybox.recipe.odoo which has been
  
  > inactive/externally maintained (amongst others by Stefan Rijnhart and me) to a
  
  > repo under the OCA umbrella, namely oca/oca.recipe.odoo.
  
  > 
  
  > We had the discussion before in
  
  > https://odoo-community.org/groups/contributors-15/contributors-27171
  
  > where the issue of branding was raised, that's why I suggest the new name.
  
  > This way we also don't clash with the original on pypi etc.
  
  > 
  
  > Please don't let this devolve into a discussion about what to use for builds/
  
  > deployment, OCA can host various alternatives in my opinion.
  
  > 
  
  > The fork will probably happen anyways, but I prefer to have it under the OCA
  
  > organization rather than some specific one just for that.
  
  > 
  
  > Best regards,
  
  > Holger Brunn
  
  > 
  
  > -- Your partner for the hard Odoo problems https://hunki-enterprises.com
  
  > 
  
  > _______________________________________________
  
  > Mailing-List: https://odoo-community.org/groups/contributors-15 
  
  > <https://odoo-community.org/groups/contributors-15>
  
  > Post to: mailto:contributors@odoo-community.org
  
  > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
  
  > <https://odoo-community.org/groups?unsubscribe>
  
  > 
  
  
  
  -- 
  Alexandre Fayolle
  Senior Software Engineer
  Tel : +33 4 58 48 20 30
  
  Camptocamp France SAS
  18 rue du Lac Saint André
  73 370 Le Bourget-du-Lac
  France
  
  http://www.camptocamp.com
  

  ---

  by Alexandre Fayolle - 08:16 - 3 Mar 2021

9 more replies