[PLEASE READ] Moving repo to the main tenstorrent org soon

[tt-rkim]

Please read this in its entirety, and please comment below with any questions you have.

What's happening?

We are moving the tt-metal repository from the tenstorrent-metal organization to the main tenstorrent organization. The new link to the repo will now be https://github.com/tenstorrent/tt-metal

We are doing this to:

• de-duplicate work
• simplify our onboarding and maintenance processes
• have a centralized feel to how we present our software to the outside world

When will this happen?

Because of the prioritized nature of this request from Tenstorrent leadership, we are moving with P0 urgency. As with all P0s, a hard deadline will be difficult to pin down, as the ask is "as soon as convenient". The deadlines of such plans are always pending setbacks.

As of the morning on Thursday, April 11th, the current plan is to aim to move during PDT morning time on Monday, April 15th.

What will change from a developer's perspective?

In terms of developer flow, you will need access to the main org and start accessing the metal repo and related CI on the main org from now on, rather than accessing the tenstorrent-metal organization. The eventual goal is to close tenstorrent-metal to only those absolutely necessary (ie. infra team).

We have tested with a fork and have some automation to handle things like transferring CI, but this is one of those things where it's difficult to have a complete picture of everything needed in a synchronous manner. GitHub does have documentation on it, but we suspect that even GitHub itself would have difficulty mapping out everything that would change without investing significant time into researching their own systems.

You should still be able to:

• access the GitHub repo website and clone
• push and open pull requests
• run CI and view logs and artifacts
• open issues

We do expect other small hiccups here and there. Infra team will be monitoring the repo and its normal flows such as CI and developer pull requests for the next couple of days after the move.

However, going forward, anything to do with repo permissions must go through IT. Metal infra team will no longer be handling write permissions. This includes both Tenstorrent developers and contractors. For the short period during and after the move, please direct any questions to #tt-metal-infra or the infra team members directly if you need help.

What will not change from a developer's perspective?

Projects (for now) will stay on the tenstorrent-metal organization. We will be updating everyone, especially project owners, on what to do with existing projects. For now, please continue using the project boards as normal.

What about my current issues and pull requests?

GitHub says they will be transferred, so we should be covered.

Is there anything I need to do to get ready by end of day tomorrow?

Please do the following as soon as possible:

• Ensure your full name is on your GitHub account.
• Request main org access through IT's TTDesk as a TT-Metalium developer under a GitHub Access ticket. We will try our best to import full-time employees automatically, but we cannot guarantee that you will be. Escalate to your reporting manager to help expedite such requests. TTDesk: https://ttdesk.atlassian.net/servicedesk/customer/portals?q=
  • If you are a contractor or external developer, please discuss submitting a ticket with your representative at Tenstorrent.
• Do a sanity check for your main org access.
  • If you are a Tenstorrent employee: check if you are part of the main org by checking if your name is listed here: https://github.com/orgs/tenstorrent/teams/metalium-developers.
    • If you see a 404, then you do not have access and need to submit an IT ticket under GitHub Access.
    • If you see the page, but not your name, please submit an IT ticket under GitHub access.
  • If you are a contractor: please reach out to your contact at Tenstorrent for more information.
• If you are a Tenstorrent contact for a contractors, we will directly contact you about next steps and sanity checks for your contractors.

Is there anything I need to do after the move?

Please do the following after the move is completed and announced:

• Delete any local copies of tt-metal you have and re-clone using the main org.
• Write any docs and links pointing to the main org's remote link, rather than the old org.
• Ensure your issues and their relevant assignees are transferred.
• Send any problems / requests about access to IT, rather than metal infra team.

GitHub handles a lot of the redirecting needed to accommodate a repository transfer. This means any bookmarks, links etc. should automatically redirect to the main org. However, going forward, we need to ensure that we point to the main org. This includes sending links and writing docs.

What about the other repos, such as UMD, SFPI, lfs etc?

The other repos will stay on the tenstorrent-metal org for now, but we will also plan to move them. This means that those developing on these repos will still be accessing them through the metal org. Because all these other repos are public, there is no need to worry about permissions or anything like that.

Separate annoucements for moving them will occur. These moves should be relatively simpler than the tt-metal move, as there's less CI and settings to transfer.

In the case of SFPI, we will be working with the SFPI team directly to help move it in a convenient and non-disruptive manner.

Thank you for reading and your patience.

cc: @tenstorrent-metal/developers @tenstorrent-metal/external-developers

[tt-rkim]

@pgkeller Brought up what happens if you can see the https://github.com/orgs/tenstorrent/teams/metalium-developers page but not your username. Good question - and the answer is please submit an IT ticket.

I have edited the post.

[tt-rkim]

@ttmtrajkovic also brought up which category should you use for the ticket: Please use github access and put metal repo move in the body

[tt-rkim]

As of Sat, Apr 13: We have sent out automated invites to the main org and the metalium team. Please check your email. You may not have received an invite if you're already part of the main org.

If you have not gotten an invite and cannot view this page: https://github.com/orgs/tenstorrent/teams/metalium, please send in an IT request. You will be able to view this page if you received an invite and click it.

If you can view this page, but cannot your name on it: https://github.com/orgs/tenstorrent/teams/metalium, please send in an IT request.

If you can view this page, and see your name on it: https://github.com/orgs/tenstorrent/teams/metalium, please sit tight.

We will now be slowly adding people to the metalium-developers team.

[tt-rkim]

We are still on track to move the repo today to the main org. Please ensure you will maintain your write access to the repo, or let us know if there are problems. Re-read the announcement and let us know if there's something we should clarify.
We will update everyone with a more exact time with at least an hour warning so that you don't accidentally push when the move is happening.

[tt-rkim]

This is now complete. Thank you for your patience.