Repo is dead -> official successor

[sebastianludwig]

This is a difficult phase for any OS project. Path has obviously abandoned any work on FastImageCache. @mallorypaine one of/the original developer announced in #152 that he'll continue maintaining FIC even though he's not associated with Path anymore - @mallorypaine please object, if you changed your mind, while I try to push more work your way :-)

To prevent any further fragmentation we should try to channel as many issues and PRs towards @mallorypaine's fork. Long term we should try to move the repository entirely.

The Plan

1. Upvote this issue to gain attention
2. If you're about to open an issue or PR, head over to @mallorypaine's fork to do so
3. Get in touch with GitHub and see if there's a way to transfer the repository
4. Find a way to update the podspec

[sebastianludwig]

Regarding 3.: I tried to reach out to Path and to see if there's a way for them to transfer the repos. Not much hope though...

[sebastianludwig]

Also just wrote GitHub support explaining the issue. Let's see what they'll have to say

[sebastianludwig]

GitHub got back to me

Hi Sebastian,

Sorry we didn't get back to you sooner!

[Option 1]

I'm afraid that only the owners of the repository are able to transfer ownership. The best way to resolve this would be to contact or have Mallory contact the organization owners directly to make this request.

[Option 2]

If that's no longer an option, we can pass along a message to the owners on your behalf. We do ask that you draft the message yourself, as we want to avoid any confusion as to who actually making the request, you or GitHub.

[Option 3]

We can also offer to detach Mallory's fork instead and make it the root of its own network. Though that doesn't resolve the underlying issue, it will stop showing the repository as a fork.

If Mallory is interested in that option, please have them contact us directly. Let me know if you have any questions about this — I'm happy to do what I can to help!

Best,
Robin

I don't see any value in detaching the fork (option 3), that'd only make it harder to find. @mallorypaine already mentioned that he doesn't know anybody who's still working at Path. That eliminates option 1 and we're left with option 2. I'd be happy to draft a message, but before I do, @mallorypaine could you give a quick 👍/👎 if you're cool with all this?

Edit: Ah, while you're at it, maybe activate issues in your fork? :-)

[mallorypaine]

would love to find a way to own the repo. thanks for checking!

[sebastianludwig]

Quick update: I just asked GitHub to pass a message on to Path.

[sebastianludwig]

Just got feedback from Robin: GitHub still hasn't heard back from the account owners. I'm running out of ideas for how to get in touch with "them" (not sure there's still anybody but an accountant keeping the company alive).

@mallorypaine how about you activate issues and PRs in your fork, we start manually redirecting new issues and PRs there and I'll try to find a way to update the podspec?

[mallorypaine]

Done

[sebastianludwig]

There's a blog post describing how to claim a pod. It's basically just filling out a very slim form. I've submitted the claim with the following details:

Mallory Paine
mpaine@g****.com
FastImageCache

Let's see what happens.

There has been an issue discussing a similar situation over at CocoaPods/CocoaPods#7431.

Edit: I should have clicked "Send" on the form before I post this comment ^^ Now I'm seeing a message that you have already claimed the pod @mallorypaine? In this case you should be able to push the updated podspec from your repo and also release a new version. Can you try?