Official repository should be on XQEMU organization account

[JayFoxRox]

The repository should be transferred to the XQEMU organization.

Reasons:

• We currently don't have too many links to this repository. Transitioning in the future will just be harder as more links point to this repository
• The official repo always gains most attention, if it's owned by a single person and that person disappears - for whatever reasons - it takes a long time to get back on track
• Having a username in front of the repository makes people wonder if this is the official / latest version. Additionally this repo is already a fork, so this is even more confusing
• As we transition to the fork based model (which GitHub is designed for), each developer, including espes, should send PRs = work on branches. However, if espes works on a branch and the repo is forked, these branches are also copied
• As we grow we'll probably use some more external tools such as Travis CI etc. It might be hard for one maintainer alone to keep up with the progress once the project gains traction. As these tools are usually controlled through the repo owner account, all of this would have to be handled by espes.
• It's pretty dumb to have an organization for an emulator project which does not even host the emulator on it's own repo (I bet there are people checking the orga, then failing to find a repo)
• Having it on an organization profile shows that this is a team or even community effort and might encourage people to contribute

This is just from the top of my head. There's probably more.

---

I believe me and @espes spoke about this in the past. I believe he was against this for reasons I don't remember. If these were of technical nature, we should probably contact GitHub support about this, to make the transfer easier / possible.

[JayFoxRox]

Reminder @espes

Also we should add topics after the move to gain more visibility of the repo.

[JayFoxRox]

Update:

• There is https://github.com/xqemu/xqemu/ now.
• @espes said "i want the stars lol". Personally, that's fine with me, but I'd prefer them on the orga account. If we could move the "follows" around, that'd be sweet though (if espes is fine with that, it's probably something we should contact the GitHub support about)
• The upstream of xqemu/xqemu is pointing to espes repo, this is kind of stupid imo. it should be the other way around (espes/xqemu should be a fork of xqemu/xqemu)
• Neither espes/xqemu or xqemu/xqemu can be found using the GitHub search because they are considered forks. I think we should have QEMU as upstream for xqemu/xqemu, but still be searchable (we should contact support about this). If that's not possible, I'm fine with removing the QEMU upstream reference entirely so we are searchable. We don't intend to PR back to QEMU anytime soon anyway.
• The issues are still listed on espes/xqemu (we should contact support about this, I don't think we can migrate them ourselves)
• xqemu/xqemu still contains all branches (including experimental / wip stuff). We should remove unnecessary branches.
• I believe the website is still using espes/xqemu? That's fine with me because he also owns the domain. However, it is not ideal either in my opinion - we should always have at least 2 people sharing responsibility so nothing bad happens if one of them disappears. Eitherway, the unused website branch should be deleted and we should document where the website is stored / who owns the domain, so new contributors don't get lost

[mborgerson]

Good to see the repo migrated! For migrating the issues, a quick Google search revealed this possible tool (apparently developed by Google) github-issue-mover.

[JayFoxRox]

In that case, I should probably run it as most of the posts are by me anyway (note how the information who posted it is moved into the post)

[JayFoxRox]

@xqemu I'll leave this here for 3 days (minimum).
If there is no veto or comment saying otherwise, I'll send this message to the GitHub support.
(Until then I'll also manually migrate the issues from espes/xqemu to xqemu/xqemu)

//Edit (5th August 2017): Still busy making up my mind about this. I think this is ridiculus and too much avoidable work / stress for me. I'm not sending this message / migrating issues for now.

Hi,

I'm writing on behalf of the XQEMU project, a fork of QEMU.

We are transitioning our development repository from https://github.com/espes/xqemu to https://github.com/xqemu/xqemu .
espes, the projects initiator, wants to keep the "Stars" on his repo, so we did not use the "Transfer Ownership" function.

Therefore, espes forked espes/xqemu to xqemu/xqemu.
This lead to the upstream fork of xqemu/xqemu being espes/xqemu.

**Please change the fork source / upstream of xqemu/xqemu to https://github.com/qemu/qemu , respecting the following:**
We noticed that forks can not be found using the github search.
So if we still couldn't be found with the new fork source, we don't want our main repo (xqemu/xqemu) to be a fork at all anymore = turn it into a stand-alone project.
We don't intend to contribute back to qemu/qemu in the next years and would prefer the exposure from the github search function.

**Please also change the upstream of https://github.com/JayFoxRox/xqemu to xqemu/xqemu.**

Greetings,
JayFoxRox

I think most people can just delete their current xqemu repo and refork.
I ask for my fork upstream to be changed because I use issues and PRs on my development repo.
I'd prefer to keep all of that.

@espes: Shall I also ask them to change the upstream of espes/xqemu to xqemu/xqemu, too?
(If they even allow that, as I don't have any permissions for your repo)

---

The current situation is ridiculous and very un-open-source. I'm very frustrated with this to be honest.

Personally I still think it would be far easier to just transfer ownership and espes could re-fork.
I think it would do all of this (changing upstreams, migrating issues, ..) automatically.
(For the very same reason I also wouldn't be surprised if they reject the request)

[mborgerson]

My $0.02. I'm in favor of forgoing the upstream and letting XQEMU be independent (that is, not "forked from ..."). This gives us three things:

• XQEMU is visible in searches on github.com (forks are not for some reason)
• XQEMU source code is searchable on github.com (forks are not for some reason)
• espes retains his rightful recognition

I think this makes the most sense because we are not really interested in sending pull requests to QEMU right now or in the foreseeable future. We can cherry pick or merge updates from QEMU proper offline and push them into our repo without issue. I think this would simplify things greatly.

[rlabrecque]

I just want to chime in as someone who is closer to espes' position on this, as someone that has a github project with a (relatively) lot of stars. Having it attached directly to my name has been great and I'd hate to lose that. But there are ways of doing this and still giving proper attribution.

Ultimately It would be nice to see xqemu/xqemu, non forked, espes/xqemu staying around as a fork. Give espes more attribution in the readme, on the xqemu site, what ever. The code is what 85% his, 14% JayFoxRox, 1% others?

Edit: I'm leaning even more in favor towards xqemu/xqemu now as time has passed!