run_9ee08fcb8c10cf84

input

{
  "request": "Triage Jira ticket MZCLD-3779: Announce internal repositories for everyone",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3779"
  ],
  "sourceContext": {
    "issue": "MZCLD-3779"
  }
}

summary

MZCLD-3779 is a Backlog task requesting a broader announcement that internal GitHub repositories are now available for most Mozilla orgs, plus a request to provide an easy path for teams to convert existing private repos to internal repos. There are no comments yet and no linked runbook/design doc was referenced in the ticket to pull additional context from Confluence.

findings

• Ticket is in Backlog status with zero comments, indicating no triage or progress has occurred yet.
• The core ask has two parts: (1) a wider communications/announcement effort about internal repos being enabled for most orgs, and (2) a self-service or documented mechanism for converting private repos to internal repos.
• No runbook or Confluence design doc is linked in the ticket description or comments, so no additional technical/process context could be retrieved beyond the ticket text itself.

proposed actions

Thanks for filing this. To move this forward, could we split it into two trackable pieces of work?

1) **Wider announcement**: Draft a short comms message (e.g., for #moz-messaging/discourse/all-hands or the relevant internal channels) explaining that internal repositories are now available for most Mozilla GitHub orgs, who to contact for orgs not yet enabled, and any caveats/limitations. Happy to help draft this if someone points to the original enablement announcement/ticket for reference.

2) **Self-service conversion path**: Investigate whether GitHub's API/UI supports converting a private repo to internal directly, or whether this needs to be done by org admins/Cloud Ops on request. If it can be self-service, document the steps (or build a small script/workflow) and link it in the announcement. If it requires admin action, define the request process (e.g., a Jira Service Desk request type) and document it in our internal repos runbook.

Could you confirm which orgs still don't have internal repos enabled, and whether there's an existing runbook/doc for the internal-repos rollout we should link here? That will help scope both the announcement and the conversion workflow. Given no urgency indicated, suggesting we keep this in Backlog until scoped, then move to the current sprint once the two sub-tasks are clarified.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3779"
    },
    "result": {
      "key": "MZCLD-3779",
      "summary": "Announce internal repositories for everyone",
      "status": "Backlog",
      "description_text": "We\u2019ve turned on internal repositories for most Mozilla orgs, but a few people have told me we should announce it more widely. We should also offer an easy way for folks to convert their private repositories to internal repositories.",
      "comment_count": 0,
      "comments": []
    }
  }
]

log