Create PRIVATE repository called `hubs-marketing-page`
Categories
(mozilla.org :: Github: Administration, task)
Tracking
(Not tracked)
People
(Reporter: rwilson, Unassigned, NeedInfo)
Details
Hello! I'm an engineer on the Mozilla Hubs Team. We are doing some well needed refactoring and need to pull our marketing page code off of our managed hubs product for organization sake.
Please make a PRIVATE repository:
Name:
hubs-marketing-page
Description:
For the marketing page on hubs.mozilla.com, first launched for the Managed Hubs product in November 2022
Please copy the Manage Access roles to the same ones in: https://github.com/mozilla/turkey-portal/settings/access
Thank you!
Robin
|
||
Comment 1•3 years ago
|
||
So I need some information for our records.
First, what organization are you looking to create this in - I assume, based on the example you gave, github.com/mozilla/hubs-marketing-page - but being hubs, it could be in mozillareality instead.
Second, from the template for these types of bugs, here, there are some fields I need.
Data Classification of data in repo: REQUIRED
Other business justification for private repo:
When can the repository be made public? REQUIRED
|
|
||
Comment 2•3 years ago
|
||
Pinged in slack to make sure the needinfo gets seen.
Hi! Thank you for the ping! Here's the information I have.
I've read all of the repository creation section, and want to request a private repository. I've filled in all the required fields.
Org for repo: mozillareality
Name of Repository: hubs-marketing-page
Link to your people.m.o entry with verified GitHub login: https://people.mozilla.org/p/robinkwilson
Data Classification of data in repo: landing page for hubs.mozilla.com - currently has low priority secrets hardcoded for our local, staging and production environments.
Other business justification for private repo: We don't expect anyone else to contribute to this repo. Has secrets hardcoded because of a strict deadline we had to cut corners.
When can the repository be made public? Once we remove the sensitive information -- but currently that is not prioritized.
|
|
||
Comment 4•3 years ago
|
||
Alright, that's excellent. But I ran into another snafu (apologies for not catching this earlier)
I notice a couple problems.
- you're not actually a member of the mozillareality org - over in bug 1804332 you were sent invites, but apparently the invites lapsed. We do ask that people requesting private repos be current members the org in question. I can resend the invites, but ...
- in comment 0 you ask for perms to be copied from a repo in the mozilla org - that's not really a thing in github - you can't port teams from org to org. There's 4 teams with 48 people in them, they'd need to ask for approvals, get access to the org, etc. I'm happy to apply any mozillareality teams to this, OR, we could create this repo in mozilla org, and we can faithfully recreate the perms fully.
Let me know.
|
|
||
Comment 5•3 years ago
|
||
Pinged a few times in Slack - Still need to figure out the org and desired permission structure.
Please respond so we can get this completed.
|
|
||
Comment 6•3 years ago
|
||
Re-pinged in slack - but also noticed an error in my comment 4
You are not a member of the mozillareality org - but that was because you hadn't logged in and SAML'd before the enforce date (around Oct 26th, 2022). If you go to https://github.com/orgs/mozillareality/sso you should get the access re-established.
However, there is still the question of "do you really want this repo in the mozillareality org, given your desire to use teams out of the mozilla org?"
Please let me know.
|
|
||
Comment 7•3 years ago
|
||
Re-pinging for location/access details so we can create this and you can start using it - please let me know.
|
|
||
Comment 8•3 years ago
|
||
Going to close this out as it's been open for over a month. If you find answers to the questions I had, I'm happy to create this repo, just reopen the bug with the info.
Always reachable on slack and matrix, happy to discuss if you have questions.
Description
•