openmw.org

Speaking of which....

@Zini: What are you thoughts on this? We're all ready and the current status is that I just pull your branches, tags and all to make things "official". We could stay this course because it doesn't do anything disruptive.

It would eventually be nice to see people cloning from the OpenMW repo and you doing your magic there as well. *push push* hehehe

I assume you are referring to those github redirections you mentioned before. So that would basically mean we tell github to use the org repository instead of mine and when ever someone requests zinnschlag/openmw via git, he gets OpenMW/openmw instead? I am okay with that.

We can do that, or at least ask for that to happen. That would mean that you would need do you magic/code-review/pull-request on the OpenMW repo instead of your own... though, if I think about it, if the redirect holds true, then you shouldn't see a difference in anyway.

We'll see first what is possible and I'll ask github, you may also get an email since it is your repo that will get changed. PM your github email address please.

Zini, I did a bit of reading and github pushes another train of thought:

In addition to redirecting web traffic, all git clone, git fetch, or git push operations targeting the previous location will continue to function as if made on the new location. However, this can be somewhat confusing, so we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using git remote on the command line:

Code: Select all

git remote set-url origin new_url

More info here:
https://help.github.com/articles/how-to ... it-remotes

Here is a more thorough guide:
https://help.github.com/articles/changi ... mote-s-url

If you really want to have that redirect, have you tried 'transferring' your repo to OpenMW? If that doesn't work, for whatever reason, we can then contact github again.

The transfer button on my openmw repository does nothing. Not sure what is going on there.

At this point we have already wasted enough time on this issue that it would have been easier to just use OpenMW/openmw instead of zinnschlag/openmw. How about we do that anyway? From what I see only the following 3 changes need to be made:

1. I change my origin remote to OpenMW/openmw.
2. Everyone else changes their upstream remote (or whatever they use to push to my repository) to OpenMW/openmw.
3. We replace all mentioning of zinnschlag/openmw with OpenMW/openmw in the documentation (mostly the wiki, I think).

Is that acceptable?

People can still push again your repo, but then you would need to accept and push to OpenMW/openmw but yeah, we should really advertise (and cleanup all mentions to) the fact that zini/openmw is not longer the official "upstream".

Can put a note in your branches readme to tell people to go to the new one

When do we start this new process? Will there be an announcement? (I've got a couple of updates I'd like to make pull request)

You can continue to work as before. Pull requests aren't really much anyway. While you should request toward the org repo after the change, requests towards my old repo won't get lost.

That being said, I plan to move over tomorrow. And yes, I there will be an announcement.

Idk if this has been mentioned. But the github banner on the top right needs to be changed to link to the right repo.

Also maybe change "me" to "us"