Regain access to the original repo (rmagick/rmagick)

[vassilevsky]

Looks like GitHub made their move. https://github.com/rmagick is now an organization. It has no repositories yet. @wurde and I are owners.

The old https://github.com/rmagick has been renamed to https://github.com/rmagick-temp . It has the old repository.

I'm not sure how to proceed from here.

Ideally we need to move the original repo (https://github.com/rmagick-temp/rmagick) to the new https://github.com/rmagick organization, merge this repo (https://github.com/gemhome/rmagick) onto it, and continue working on it. But I don't think we have permissions to do that.

@bf4 how is your conversation with Moncef going?

@ioquatix @u338steven @mockdeep @linduxed bringing you here to let you know about this development

[linduxed]

I don't see any reason for the previous repo to exist. This repository is a straight up continuation of the work, it didn't "branch away" from upstream at any point.

While I'm not sure how @mmaiza would feel about it (or you guys for that matter) but to minimize confusion for the end-users of this gem, I think we should just add a tag indicating the point at which the fork was created and move on. I see no reason why any work should be done on the pre-fork-rmagick or how anyone would benefit from having two projects which both are in some sense "the official version".

This project has moved far beyond what it was late July last year (when the fork happened) and continues to improve with the help of both the people mentioned in this issue, but also various sporadic contributors.

In short:

1. Move this repository to rmagick/rmagick.
2. Either delete or forget the old repository. I don't think the end users benefit in any way from having the old project around. If @mmaiza doesn't want to delete it, fine, it'll stay as one of the many forks of the project, but I don't see the reason why it should.

[vassilevsky]

git-wise, this repo is indeed just a continuation of the old one. It has all the history and tags.

What bothers me are issues and pull requests open at the old repo. It would be nice to properly close them. They are the originals and this repo's issues are mostly copies.

[linduxed]

With that said, all of the creators of the original issues were pinged when the issues were imported by @bf4. It would be nice to just move the old issues here and merge them manually into a nice cohesive whole, but that's something I think neither will nor can happen.

I don't think this is a problem.

[bf4]

We could just move gemhome/rmagick to rmagick/rmagick and leave the original repo alone as a reference :)

[vassilevsky]

As you say.

[vassilevsky]

I have moved the repository and updated all links in the code.

[bf4]

wee!!!

[bf4]

@vassilevsky dunno if you want to re-add me as owner/collaborator to the rmagick org.

Unrelated, let's fork https://github.com/minimagick/minimagick to rmagick and invite them to move here?

Congratulations guys 👍 this is well deserved.

[vassilevsky]

@bf4 check your email for an invitation.

@wurde thank YOU for your super-effective help!!!

Everyone, feel free to email me your postal address and I will send you postcards!

[vassilevsky]

Not sure about minimagick. What are potential benefits?

[vassilevsky]

@linduxed this seems to be a good time to post another writeup :) Your first one was very helpful. It made it to Ruby Weekly! I saw it there and joined the project because of it :)

[mockdeep]

I wish we could get rid of that " forked from rmagick-temp/rmagick" message...

[bf4]

the only way for mortals to do it is the delete the repo and repush.. might need to ask github to help so we don't lose the issues

[bf4]

@vassilevsky great idea re: writeup!

btw, if anyone wants to help set up an rmagick github page I'd be happy to help migrate it from the current site

re: minimagick just because they're related projects. nothing more