andychase
commented
2 years ago It has been a few weeks since we announced the impending migration from our current GitHub Legacy account into an EPA Enterprise system and we wanted to remind everyone of our form submission request.
Before this Friday, January 28th, 2022, EPA staff should complete the User Profile Form and indicate whether you prefer to migrate to the GH Enterprise system as a licensed user or as an external collaborator. Contractors should discuss the status of their accounts with their contracting officer before completing the User Profile Form. Please note:
-
Any user account that has been approved for a license will be migrated over and have access to all the Enterprise features.
-
Any user account that requests to be migrated over as an External Collaborator within the new system will have a limited ability to work within the Enterprise system but can still contribute to their assigned public repositories.
-
Beginning February 1st inactive accounts will be deleted from the GH Legacy account. An account will be considered inactive if no migration election has been submitted through the User Profile Form.
We would also like to announce that the system migration date has changed from April 1st, 2022 to May 1st, 2022. This change was made to align the period of performance for the licenses with other EPA renewal schedules.
Please let us know your preference regarding your account rollover to avoid losing access to your repositories and teams. If you have any questions not covered in those resources, please reach out to your Region's or Program's GitHub Organization Owner or you can contact EPA GitHub administrators through github@epa.gov.
@ackuan @adamtheising @adavis10 @adichter @aergul @agdeer @agrappold @ahallEPA @ahanfk @aignatius @ajasonbrown @ajmacpherson @alexbijak @alfoster3 @alikamalepa @AliScott20 @allenbrookes @alspringsteen @altennant2 @amarkari @amkhan5 @amypiscopo @AndreaBassi @andreasmaier-abt @andrewphutchens @andrewshannoncsra @anjiayiepa @AnneKuhn @annvega @aparks-rti @aparks123 @aprematta @aptorres1 @areff @arelkhattabi @ARMurray @arunacs @arunvarghese-icf @ArvanaghiAli @aviellp @awalrath @AWolvert @awsgisp @axtseng @azarehar @babakkamrani @banderson735 @BAPEPA @bcryan @bdyson12
GitHub Enterprise Licensing Announcement
EPA GitHub Users,
EPA is upgrading our GitHub account to a new product, GitHub Enterprise Cloud. GitHub Enterprise will offer more features and functionality for our users including unlimited private repositories, increased access to GitHub Actions, and better security. The GitHub Council has been diligently working to institute a migration plan, establish procedures and processes for account functions, and upgrade user resources and documentation.
In the process of upgrading to GitHub Enterprise, the migration team will be working to make the transition as smooth as possible. This includes transferring all repositories and user accounts directly into the Enterprise system. However, one of the requirements of the upgrade to Enterprise functionality is the inclusion of user licenses.
Before January 28th, 2022, EPA staff should complete the User Profile Form and indicate whether you prefer to migrate to the GH Enterprise system as a licensed user or as an external collaborator. Contractors should discuss the status of their accounts with their contracting officer before completing the User Profile Form. Please note:
Why Do You Need a GitHub Enterprise License
GitHub Enterprise licenses (i.e., what GitHub defines as per-user pricing) are needed for using products not provided in the free version of GitHub (see GitHub's products). You should consider purchasing a GitHub Enterprise license if you:
The GitHub Enterprise Account will launch on April 1st, 2022. All purchased licenses should have a period of performance beginning on April 1st, 2022.
The GitHub Enterprise Council is excited to be guiding this process to help consolidate and improve open-source development across the Agency. We look forward to sharing the advancements and new resource materials with the GitHub user community. As we progress, please watch for additional communications related to any changes you will see in the login process, user roles, and new features. In the interim, please consult these resources for additional information:
If you have any questions not covered in those resources, please reach out to your Region's or Program's GitHub Organization Owner or you can contact EPA GitHub administrators through github\@epa.gov.
@ackuan @adamtheising @adavis10 @adichter @aergul @agdeer @agrappold @ahallepa @ahanfk @aignatius @ajasonbrown @ajmacpherson @alexbijak @alfoster3 @alikamalepa @aliscott20 @allenbrookes @alspringsteen @altennant2 @amarkari @amkhan5 @amypiscopo @andreabassi @andreasmaier-abt @andrewphutchens @andrewshannoncsra @anjiayiepa @annekuhn @annvega @aparks-rti @aparks123 @aprematta @aptorres1 @areff @arelkhattabi @armurray @arunacs @arunvarghese-icf @arvanaghiali @aviellp @awalrath @awolvert @awsgisp @axtseng @azarehar @babakkamrani @banderson735 @bapepa @bcryan @bdyson12