Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Summary
GitHub Enterprise Managed Users (EMUs) are a new type of user account aimed for professional use on GitHub Enterprise Cloud (GHEC). EMUs are provisioned and managed via an enterprise's identity provider (IdP), providing companies with user lifecycle control and enhanced security.
Intended Outcome
Enterprises using EMUs can create user accounts for their employees via a linked IdP. Administrators are also able to manage user profile data (e.g. display name, email address, etc.) and membership to GitHub teams through their IdP.
How will it work?
After setting up a link between a GHEC account and a supported IdP, enterprises will be able to enable SAML (Security Assertion Markup Language) with SCIM (System for Cross-domain Identity Management) to manage the user provisioning lifecycle of EMUs. Once the EMU account is created, the user will get an invite email leading them to complete single sign-on (SSO) and gain access to their provisioned organization(s). In this release, EMU accounts will only be able to contribute (e.g. open issues, create pull requests) to repositories in organizations owned by their GitHub Enterprise Cloud account. EMUs will have read-only access to public repositories on GitHub.com, but will not be able to make contributions to public repos. We anticipate enabling policy for public contributions in a future release.
Membership to GitHub teams will also be managed through the enterprise's IdP. Administrators may add users to groups in their IdP and, via SCIM, those groups memberships will be reflected on teams in the enterprise's organizations. Administrators are then able to add those teams to repositories and assign roles on GitHub. In addition, enterprise owners will be able to audit the activity of EMUs in their enterprise account.
As part of the initiative we will be improving our authentication functionality to create a true SSO experience for customers using EMU-enabled Enterprises. Please find a screenshot of our in-progress development below:
Note: For the initial implementation of EMUs we will be optimizing for AzureAD and Okta as the IdP.
The text was updated successfully, but these errors were encountered: