COLLECTED BY

Organization: Archive Team

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.

Collection: Archive Team: The Github Hitrub

This collection is a set of Github repository archives from two major sets: A panic grab upon the acquisition by Microsoft, and a larger, ongoing set of Pretty Much Everything.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20201112030801/https://github.com/HeroTransitions/Hero/pull/594

HeroTransitions / Hero

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WIP] Update for swift 5 #594

Open

barrault01 wants to merge 2 commits into HeroTransitions:develop from barrault01:master

barrault01 commented Mar 27, 2019

Hello I run the xcode migration, I run the tests and they are passing.


          update for swift 5

daniel-beard commented Apr 3, 2019

Any chance of someone merging this one soon and getting a new cocoapods release?

pauloec commented Apr 11, 2019

Unlikely. The owner has left indefinitely.

iosdevben commented Apr 25, 2019

Thanks for doing the PR @barrault01. I've switched my Cartfile to point to your repo instead.

mikehobi mentioned this pull request

update version for swift 5 #603

Closed


          Create FUNDING.yml

0206df1

JoeMatt requested changes

Collaborator

JoeMatt left a comment •

edited

Do we also need to add,

s.swift_version = '5.0'

to the Podspec?

.github/FUNDING.yml

  
      @@ -0,0 +1,12 @@
    
        # These are supported funding model platforms

JoeMatt Oct 7, 2019
Collaborator

Can we remove this from the PR and open another with it if it's wanted

JoeMatt mentioned this pull request

Removed all warnings for Swift 5 #611

Open

JoeMatt changed the base branch from master to develop

Collaborator

JoeMatt commented Oct 8, 2019

.swift-version should be updated to 5.0 also.

Member

kuyazee commented Oct 8, 2019

.swift-version should be updated to 5.0 also.

Shouldn’t we remove the .swift-version file because of the specification in the Podspec?

Collaborator

JoeMatt commented Oct 8, 2019

.swift-version should be updated to 5.0 also.

Shouldn’t we remove the .swift-version file because of the specification in the Podspec?

I agree, .swift-version is considered deprecated by Cocoapods. Other tools may use it but it was never a standard for swift. Package.swift or the XCode project already reflect their compatible version.s

kuyazee self-requested a review

Member

kuyazee commented Oct 8, 2019

.swift-version should be updated to 5.0 also.

Shouldn’t we remove the .swift-version file because of the specification in the Podspec?

I agree, .swift-version is considered deprecated by Cocoapods. Other tools may use it but it was never a standard for swift. Package.swift or the XCode project already reflect their compatible version.s

Ok then, once the .swift-version file is removed we can merge this PR. Thanks guys

JoeMatt added the Merge Conflicts label

barrault01 requested a review from JoeMatt

Author

barrault01 commented Oct 12, 2019

Guys going to close this pull request I just run the xcode migration, and now with Xcode 11 it is not building the tests anymore... I will let my repository available until someone migrate the lib to xcode 11 + Swift 5.

barrault01 closed this

Collaborator

JoeMatt commented Oct 21, 2019

Reopening so we can build on this work

JoeMatt reopened this

JoeMatt changed the title ~~update for swift 5~~ [WIP] Update for swift 5

JoeMatt added this to the 1.6.0 milestone

jdisho commented Nov 12, 2019 •

edited

What is the status of this PR? Is somebody working on?
If not, I would prefer taking it over.

Collaborator

JoeMatt commented Nov 17, 2019 •

edited

What is the status of this PR? Is somebody working on?
If not, I would prefer taking it over.
@jdisho

You're welcome to copy this branch and make a new PR and reference this issue number #594. Looks like it just needs a rebase and conflict resolution.

nick-potts mentioned this pull request

Swift 5 Migration #645

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

You can’t perform that action at this time.