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.
The Wayback Machine - https://web.archive.org/web/20220602191154/https://github.blog/changelog/2022-06-02-github-enterprise-cloud-customers-can-access-ip-addresses-for-audit-log-entries-for-enterprise-owned-assets/
GitHub Enterprise Cloud customers can access IP addresses for audit log entries for enterprise owned assets
GitHub Enterprise Cloud owners now have the ability to opt-in to display enterprise members’ IP addresses for all
events involving enterprise-owned private repositories and enterprise-owned assets, such as issues and projects, in your audit log.
This additional information can be used to improve threat analyses and
further secure your software.
Note, IP addresses will continue to not be displayed for activity related to public repositories.
Dependabot version updates help you keep your dependencies up-to-date by opening pull requests automatically when new versions are available.
With this release, you can now more easily enable and configure Dependabot version updates from your repository’s settings page. Within the "Dependabot" section of the "Code security and analysis" tab, you can choose to enable Dependabot version updates, which will prompt you to create a dependabot.yml config file. If a dependabot.yml file exists, you can access that from the repository settings page.
Note: you still need to configure Dependabot version updates with a dependabot.yml file to enable it.
Today's Changelog brings you the release of project webhooks, a first exploration into templates and a host of improvements to GitHub Issues.
☁️🪝 Automate more with project webhooks
The first release of webhooks for projects (beta) is now available for Organizations and GitHub Apps. 🤩
Once configured and enabled, webhooks will transmit events for any action taken on project items within your organization. This includes changes made (via projects) to status, assignee, labels, and even draft issue titles and descriptions!
You can find webhooks for projects (beta) in the "Webhooks" section of your organization settings page under the title Projects v2 Items. For more information, including technical specifications, check out the docs.
🦻 We're still developing webhooks, and we'd love to hear your feedback; drop us a line in our Feedback Discussion.
🎨 Get started with templates
When you create a new project, you now have the option of multiple templates to choose from. Start with either the default table or board, or explore one we've created for you with our team backlog or feature templates.
Stay tuned for more with templates in the future. 💖
🧭 Improved navigation via project header
Quickly understand which organization or user a project belongs to and easily navigate via the breadcrumbs in the project header. We've got more to do here, so please let us know what you think.
✨ Bug fixes & improvements
Other changes include:
Bug fix so projects (beta) insights retain URL parameters when switching to custom date ranges.
The emoji menu on milestone creation now loads in the correct place.
Users trying to upload large files now receive the correct 'file too large' error, not a 'file type not supported' error.
Bug fix when converting a task list item to an issue, the ` character is now correctly formatted.
When transferring an issue between repositories, if no search results are found there is new UI to help you understand why some repositories are excluded.
Using the assignee filter menu on the issues index page, you now have the option to filter by the current user instantly, without having to wait for all possible assignees to load.
See how to use GitHub for project planning with GitHub Issues, check out what's on the roadmap, and learn more in the docs.