Closed Bug 1846362 Opened 2 years ago Closed 2 years ago

mozilla-fakespot organization create request

Categories

(mozilla.org :: Github: Administration, task)

Product:
mozilla.org
Component:
Github: Administration
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rvasilyev, Assigned: cknowles)

Details

We want to move at least one our repository from our gitlab server to github please help us with creation

So, the big questions:

  1. Public or private? - Which will inform what level of assistance we need to offer. Public is much easier.
  2. What's the destination org. that you're aiming for? I see that you're currently a member of mozilla, mozilla-it, and mozilla-sre-deploy - mozilla's probably the default target.
  3. I'm not familiar with gitlab - is there anything like apps/actions from the github universe? or is this really just a source code repository?
  4. Besides yourself, is there a list of people that would be accessing it, and are they in other Mozilla GHE orgs?

Let me know and we can start asking more directed questions.

Flags: needinfo?(rvasilyev)

Thank you for quick reply.
Let me answer.

  1. Private
  2. Not clearly understand meaning "destination". We want to put some of our repos into this "org".
  3. I thought to use it for code storage and optionally run CI/CD pipelines.
  4. List of the people is the whole Fakespot developers.

Oh! I'm sorry - This is a request for the creation of a whole new org. It was unclear between the title and the description. Apologies.

Let me re-ask the questions with that focus in mind.

Normally by default our orgs are pretty well controlled.
Some things are not optional - like the ability to transfer out repos/delete repos (which are the same as far as GitHub is concerned) - Legal really wants oversight on any repos being transferred out of our control. So bugs have to be filed to do this.
Application approvals - install github applications needs owner level access - so you'll need to file bugs so secops can approve any apps.

But other defaults can be negotiated - like creating private repos - Normally we like to be involved as private repos have a tendency to get orphaned quickly. But if ALL your repos are private, then that's going to hamper you - so you just have to ask for that ability.
And Actions - normally we lock down actions to the org to Github provided, and a few known good ones - https://github.com/MoCo-GHE-Admin/Approved-GHE-add-ons/blob/main/New_Org_Default_settings.md

And now to the updated list of questions:
Creating an org has some large logistics around it - how many repos roughly are we talking about? We're not charged for them - but if we're talking 1-2 - then it might be better to find you a home in an existing org.
What name would you be thinking of for the org?
Would you want the ability to create private repos?
Can you give us the complete list of developers you'd want to invite (so we have an idea of licensing/etc.)?

And we need Secops to sign off on all of the above - Hal, Austin - what'd I miss, thoughts, etc?

Flags: needinfo?(hwine)
Flags: needinfo?(asargent)

Answering:

  1. How many repos roughly are we talking about? - currently we have about 100 repos, we want to start with one
  2. What name would you be thinking of for the org? - mozilla-fakespot
  3. Would you want the ability to create private repos? - yes
  4. Can you give us the complete list of developers you'd want to invite (so we have an idea of licensing/etc.)? - it will be whole Fakespot (about 20 people) for beginning we can put there:
    Saoud Khalifah
    Joe McBride
    Vladimir Stepanov
    Roman Vasilyev
    Sen Tian
    Jian Iwu
    Zijun Ucheng
Flags: needinfo?(rvasilyev)

Alright - we'll be discussing internally - and I'll get back to you. Final question for this round, as you hadn't mentioned yet - is there a time concern here?

Notes for Hal/Austin - I'm inclined to go forward with this - with the private repo exemption, as it's single product focused, there's enough users/repos that bringing them in anywhere else would be awkward. Only concerns would be licensing and getting the org setup.

Ok, we started github discussion because we stuck with huge files which is not in our repo now, so I thought to speed up a process by moving our repo into mozilla github but seems like org creation is time consuming we should looks for other solutions.

If speed is an issue we can move fast, once we have all the concerns hammered out, which is still ongoing.

GitHub isn't an awesome place for huge files (or binaries) in general - so can you speak more about what's going on there? (if a meeting is preferred, I'd be happy to set one up. Just let me know who to invite.). GitHub's actually in the process of upping the charging for their large-file-storage product. So we'd probably prefer that that not be a path we follow.

Understood, we have 2 models for machine learning 2 and 6 gigs what will be the best place to put this files?

Per the documentation here, even with our enterprise account - you can't put the 6 GB file in GitHub anyway - but the 2G one probably shouldn't go into the repos either. Let me see if I can find a resource for you on what to do with them.

Thank you for clarification, sounds like downloading models is the only option for now :(

other option is use GCP mounted volume

Apparently you aren't limited to using GitHub's LFS ... you can have a pointer to some other LFS ... Jonathan Moss (@Jonathan on slack) has offered to advise if you'd like to discuss that option set with him.

I'm not sure if this is a stopper for you going into a github org - I'll proceed with the pre-work, but if things still look like you want to go forward, let me know.

+1 from the risk team

Flags: needinfo?(hwine)
Flags: needinfo?(asargent)

for now we just went with kubernetes persistent volume, but I think we still need mozilla-firefox github org

Yup, As long as we're not storing huge files in the repos without excellent github related reasons - I think we're good to go.

I'm working through the security process (their +1 above indicates no objections to the private repo creation permission) in getting the org setup.

And then our IAM folk will need to setup for SAML on the org - but once that's all done we can start sending out invites.

As I work on getting the space ready - there some things you can give us if desired -
Is there a contact email (perhaps to a google group) for the contact for the org?
Is there an image (preferably 500x500 Jpeg) that you'd like to use for the org?
Is there a description sentence for the org?
And finally - is there a URL you'd like to provide for the org?

And for the people listed in comment 4, Most look like they're setup correctly to be included. Saoud Khalifah, Sen Tian, and Jun Cheng (which I think is "Wijun" - there's no profile in phonebook with that name.) don't have GitHub ID's linked, I'll email them directions on getting themselves setup.

And finally - Based on recent experience with setting up new orgs - it would be super helpful if the initial influx of ~20 users were listed out in this bug so we don't end up processing things piecemeal.

And status - I have the initial org created, the default secops posture applied (with the exception of allowing members to create their own private repos) and I have the Jira case (IAM-1182) filed with to get the Auth0 setup allowing for SAML integration. Once that happens, we'll be ready to start sending out invites. (Just checked, Saoud and Jun haven't updated their people.m.o profiles yet, until they do, they won't be able to join the org.)

If there's any way you can get me the details from comment 15, that'd help in getting the org ready to go. If you have any questions, please let me know.

Flags: needinfo?(rvasilyev)

question in comment 15 means list of the users who have to be added to this group?

Flags: needinfo?(rvasilyev)

Yes, if possible - The idea is to prevent the 20ish people coming in in dribs and drabs, and just get them setup all at once. Also, I'd wager more than a few don't have linkages setup, and so we can help them navigate that, and it's just easier to do it in bulk.

But if that doesn't work out - we can do it piecemeal. Just takes longer.

Alright - the org is just about ready for users from the administration standpoint. Just want the questions from comment 15 for any customization, and any user list you can provide, and we can start inviting people.

Thank you just passed this ticket to Joe McBride to get exact list of the people, sorry for delayed answer.

Alright, I see that most people in that list have linked up - the only two remaining are:
https://people.mozilla.org/p/cmkoehler and
https://people.mozilla.org/p/saoud

So, I'll send out some invites for the org to the linked folk, along with an email.

Note that the org still doesn't have the usual contact/description info in to per comment 15 - but that IS optional, so I'm not blocking on it.

Good morning, hopefully All hands was excellent.

Most people have joined the org, the two unlinked in comment 22 haven't linked yet, and Yubin, Jun, and Ajmol didn't process their invites in time (I've refreshed the invite and emailed them.)

Did you want to do any of the setup in comment 15? If not, then I think this bug is likely complete. We can process any further adds as normal user adds.

Flags: needinfo?(rvasilyev)

Sorry for long reply, just doublechecked with my team
Jun, Yubin and Ajmol can't see invitations in their github profiles auddin@mozilla.com, jucheng@mozilla.com and yjamora@mozilla.com
also we can see "Jian Iwu" spelled wrong should be "Jian Wu" jiwu@mozilla.com

Flags: needinfo?(rvasilyev)

So, Jun has accepted the github invite and signed in - so they're working. I do show that Yubin and Ajmol haven't accepted their invites yet - if they're having trouble with email, they can go here and accept the invite from the GitHub side. (and I've re-emailed them those directions.)

And as to Jian - if you're referring to your spelling in comment 4 - That appears to be only there - people.m.o and github both appear to be JIan Wu and linked properly. And they're signed into the org. If I'm not understanding, please let me know.

And SKhalifah and CMKoehler still haven't linked GH ID's to their people.m.o accounts, so I can't process invites yet.

And if you have any descriptions/links/emails/logos you'd like to associate with the org per comment 15, that would be handy.

Flags: needinfo?(rvasilyev)

And I see that Yubin has accepted the invites, will poke Ajmol one more time.

Please update if there's more work you'd like done here, or if we can close out this ticket.

Please also add me https://people.mozilla.org/p/roman-vasilyev

Flags: needinfo?(rvasilyev)

I have no idea how THAT got missed. (actually I do, looks like I went off of the list in comment 21, not the earlier list in comment 4) Invites sent, Please accept the people.m.o one first, then the github invite.

Resetting the needinfo - as I'm still waiting on the info for comment 15, or clearance that it's not desired to customize the org at this time.

Flags: needinfo?(rvasilyev)

Alright - based on no response to the optional comment 15 items, and having gotten invitations out to people (and finally ALL of them, apologies), I'm marking this as resolved.

The org is created, you have access to create and use public and private repositories in it, and can also transfer in repositories. So I think you're set.

If you ever decide you need some of the customization as mentioned in comment 15, please open a new bug with specifics, and we can get things going.

If you have questions or concerns, please let me know.

Assignee: nobody → cknowles
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(rvasilyev)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.