https://www.drupal.org/docs/develop/git/setting-up-git-for-drupal/obtain...

All materials that are stored in a Drupal.org Git repository must be created by the individual that pushed it to the repository. We do not allow organizations to have a Git account at Drupal.org. It is inappropriate to use an organizational account to commit to a project in a Drupal.org Git repository.

Is this the right queue to report projects where all the commits are from a shared company account? The above documentation doesn't say.

Comments

TR created an issue. See original summary.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Component: Policy » Other
Assigned: Unassigned » avpaderno

Ordinary site moderators (like myself) don't have access to user profiles and cannot remove git access from a organizational account. I think apaderno (also a site moderator) has more access. For now, I assign this to him and hope is able to sort it out sort out. If apaderno cannot help, it need to be escalated to the Infrastructure team.

(The "Policy" component is for discussing policy, not for enforcing an established policy.)

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Assigned: avpaderno » Unassigned
Status: Active » Fixed

Except in the case the user explicitly stated in a publicly visible comment on drupal.org the account is shared, the action to take in those cases is sending an email to help@drupal.org.

Only user administrators can see the edit account form (and see the information entered in that form), but it's not their task to reinforce the Drupal.org Terms of Service, given that they don't have access to all the information necessary to understand if the account is really used from different people. If the user explicitly said the account is shared, the user administrators can set the account as shared, though.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.