Proposing myself as oca-custom repo maintainer

[petrus-v]

As member of the OCA Internal tools workgroup I'd like to propose myself as oca-custom repo maintainer.

We could imagine a dedicated team and let such team manage some repositories, but probably a bit earlier to generalise something so I just requesting this for the time being !

[etobella]

This will not work, we don't have the maintainer part. We should need to define a new group just for that maybe 🤔

[petrus-v]

This will not work, we don't have the maintainer part. We should need to define a new group just for that maybe 🤔

This seems to be an un-documented features as pointed mentioned #55 (comment):

https://github.com/OCA/repo-maintainer/blob/master/oca_repo_maintainer/tools/manager.py#L166

[etobella]

It seems so, but I am not sure if the functionality disables this collaborators if we remove them later 🤔

[petrus-v]

Indeed, probably not handle, so what's the proper way ?
Does a repository can be maintain by two PSC ?

I suppose I've to create a new PSC that represent the OCA Internal Tool Working and could be called oca-internal-tool-working-group with at least me inside and the oca-custom repo, or should I be part of community-maintainers and add this team as oca-custom maintainer ? but I don't really feel very legitimate to maintain some of related repositories.

Or maybe I don't have to be oca-custom' maintainer as you proved today that you are very reactive while you are notified !

[etobella]

well, you could do a new team and leave the representative as the board

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[simahawk]

@petrus-v ping :)

[petrus-v]

This depends on OCA/repo-maintainer#25 (just created)

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.