Merge OpenXDK organization into XboxDev about xboxdev HOT 5 CLOSED

Seems like a good idea to me.

I created the OpenXDK organization on GitHub back when I intended to create a "new OpenXDK" by myself, which obviously didn't happen like that.
My suggestion would be that I transfer both repositories to @XboxDev and delete the OpenXDK organization. Even if my versions of cxbe and xbiso don't end up getting used, it would probably be a better place to archive these repositories. Let me know if/when you want this to happen (apparently repository transfers have to get accepted within 24h).

from xboxdev.

As explained by @thrimbor on Discord:

The org is gone, xbiso lives in thrimbor/xbiso now (I consider it archived atm).

The cxbe fork has been removed altogether.

Thanks for cooperation! Closed.

from xboxdev.

Cxbx-Reloaded also contains an import of OpenXDK, with many additions to the original code. These additions might be beneficial to either OpenXDK or nxdk too...

from xboxdev.

That's be appreciated @PatrickvL. However, that's a separate issue for https://github.com/XboxDev/nxdk (or rather: for your fork, to remind people to "upstream").
There's also https://github.com/XboxDev/openxdk, but we should turn into a read-only archive repository because our intention to supersede it by nxdk.

This isssue was strictly about merging the OpenXDK GitHub organization (a political / social thing; not so much a technical decision). There wasn't even a copy of OpenXDK code hosted on the organization.

from xboxdev.

XboxDev/OpenXDK has no issue-tracker enabled, so I decided to write this suggestion here instead.

I'll create an issue in nxdk too, although I'm not sure how that compares against OpenXDK (any fork)...

from xboxdev.