timja / jenkins-gh-issues-poc-06-18

0 stars 0 forks source link

[JENKINS-64903] Rename jenkinsci organization in GitHub to jenkins #1409

Open timja opened 3 years ago

timja commented 3 years ago

Now we use `jenkins` as the Docker Hub user name, and `jenkins` as the Helm Chart repository name suggestion. It would be very good if `jenkins` could also be used in GitHub organization name rather than `jenkinsci`.

GitHub has a process for such cases, all that is needed to do is to contact the GitHub support.

I saw a successful case in the past while an inactive user account was taking the organization name, and claimed later by the organization owner (https://github.com/chezmoi), so we got to try at least.


Originally reported by felipecassiors, imported from: Rename jenkinsci organization in GitHub to jenkins
  • assignee: oleg_nenashev
  • status: Open
  • priority: Minor
  • resolution: Unresolved
  • imported: 2022/01/10
timja commented 3 years ago

oleg_nenashev:

I tried contacting https://github.com/Jenkins several years ago, but did not get a response.

Contacting GitHub support is doable, but only if we have a consensus about renaming in the community

timja commented 3 years ago

felipecassiors:

I couldn't find any contact address to https://github.com/Jenkins. In fact, I tried to contact GitHub support for this issue and their response is attached.

As per their response, it seems that the "Jenkins" user could have some private activities still (not showing publicly). So, could you try to open an Issue on one of his repositories? We can reach out him there.

In the worst case, we could use their "trademark claim" as said in the response.

timja commented 3 years ago

oleg_nenashev:

Hi felipecassiors. Thanks for attaching this answer. I will bring up this topic at the Jenkins Governance Meeting on Wednesday. Will check with others whether we want to proceed and make a trademark claim. Not sure it will be effective though, because "Jenkins" is a pretty common surname.

Mar 10 meeting agenda: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.1gtco63t6ztr

 

timja commented 3 years ago

oleg_nenashev:

We discussed it at the yesterday's Jenkins Governance meeting and agreed that we would not like to invest time in renaming the org. The main reason is a big number of connected automation tools and apps which are likely to be impacted. We discussed an option of having a redirect from /jenkins to /jenkinsci if the account is acquired, but we are not ready to trigger the trademark infringement policy just due to that. Name Squatting policy does not apply there taking the response from GitHub support

timja commented 3 years ago

felipecassiors:

That's right.

Just one clarification: as per GitHub, all the old references to the repositories will redirect to their new ones.

Take as example my dotfiles repo: https://github.com/felipecassiors/dotfiles -> https://github.com/felipecrs/dotfiles. Even though there is a user registered with my old username, the redirections did not break.

timja commented 3 years ago

oleg_nenashev:

There are many other things in addition to redirects. READT APIs, Connected GitHub Apps, tooling, plugin metadata and so on. Without testing it is hard to say what may break, but there is a non-zero probability that something breaks after renaming

timja commented 3 years ago

felipecassiors:

That's right.