We still have to do https://freenode.net/groupreg .
That is because channels starting with a single # are reserved on freenode. Whereas channels with ## are public. We want official status though, so we need to groupreg.

I had originally planned to do this already, but I'm very busy maintaining a handful of projects (in Xbox ecosystem and otherwise). I also have regressions in XQEMU to fix.

So I'd be grateful if someone else of @XboxDev could do this.

When this is complete, we need a new issue about bridging XboxDev IRC and XboxDev Discord (unless done immediately).

@OpenXDK only has 2 public repositories:

• cxbe. Which is also hosted on XboxDev (not as a seperate repo yet).
• xbiso. Whereas XboxDev currently maintains extract-xiso. However, I believe most of us are open to just replacing extract-xiso with something else.

@OpenXDK only has 1 public member:

• @thrimbor. Who has also engaged in nxdk discussions and development (when it was still on the @xqemu organization).

The goals of both organizations seem to align nicely [1]. Getting rid of the OpenXDK organization would help to focus and direct traffic to XboxDev. XboxDev has more momentum right now.

I'd love to hear what the @OpenXDK members (and also @XboxDev members) think about this.

[1] Except that we wouldn't use the Xbox shield logo by Microsoft; to avoid possible legal issues in the future.

This issue is about the XboxDev Discord

I wonder if the Discord server should have roles for expertise.. like GPU, APU, PCB, Python, QEMU, .. so we can always highlight those people who are important (as all members of a role can be highlighted using @role).

Ideally people could add themselves to these list using a bot or something - so you could basically subscripe to topics.

Just so if something important happens, they get a highlight, such as with the logo decision - we could have said: "new XQEMU logo in the works, please vote @xqemu", so even people who don't always read #xqemu, see those important issues.

We could also have a role for people interested in helping with beginner tasks (for all projects currently listed on XboxDev discord; because beginners often suck at finding them on github on their own).
So whenever a new task is available, we could highlight them with @easy.
Also when people ask "what can I work on?!" we'd just direct them to search for @easy in the Discord search - and they'd find all past tasks immediately (or the bot could list them, so IRC bridgers can also see them).

I thought of this when I needed people with python expertise because I know a handful of people with python skills but I'm unable to highlight them easily.

Thoughts?

We get a lot of off-topic talks in Discord channels.

With 300 users, and many end-users (instead of developers) joining we are slowly running into trouble keeping discussions organized.

I think we should add pinned messages to every channel which explain the rules.
Each channel description could just say "Read Pinned messages before posting!"

In particular:

• We currently have XQEMU discussions on all channels which are not clearly marked as being XQEMU (contextless questions like: "Did you try game XYZ?").
• #user-support is often used to share experiences, not to request support. So when a user actually needs help we might miss it because we are desensitized. This actually happened on Citra Discord in the past and lead to users leaving without response after half an hour, later bad-mouthing Citra on 4chan etc. Ideally we should move user-support to project specific forums.
• Research is being discussed in emulation channels.
• nxdk development is included in #development despite having its own channel.

We could have a logo for XboxDev. I believe we have had an issue for this before, or did discuss this in the past, but I can't seem to find it. So this is a new place to discuss it.

I had shown a logo idea on Discord earlier today:

See the discussion with more similar logos and the SVG in XboxDev Discord log: https://discord.com/channels/428359196719972353/428359408204906497/738387930103414826

༼ つ ◕_◕ ༽つ

This issue is about XboxDev Discord

We should probably have a role for @XboxDev on Discord so users can reach maintainers quickly, as those maintainers have the ability to decide if a repo should be moved under the XboxDev GitHub org, or review Wiki articles.

In contrast to roles listed in #1 , this role should probably be closed, so users can't pretend to be someone they are not.
Also as the overall topic is "XboxDev" anyway, there is no point in highlighting @XboxDev unless you want a maintainer (which is also the highlight for XboxDev maintainers on GitHub)

nxdk was originally an idea to attract CTF players to XQEMU; hence it was hosted on XQEMU.
XQEMU developers then started XboxDevWiki to be able to work closer with Cxbx-Reloaded developers (maintain and develop the shared ecosystem together).
So eventually nxdk moved to XboxDev to split responsibility.
The Wiki also quickly attracted new projects and people almost entirely unrelated to emulation (Xbox-Linux, people working on XID hardware, people who just like to document Xbox history, ..).

As a result, XboxDev grew and has become more independent (> 350 Discord users).

However, at this point emulation is getting more popular.
Especially XQEMU infrastructure (developer IRC) is still linked to XboxDev Discord through #xqemu. There's also #user-support which is for both projects (although it's primarily based for XQEMU, as Cxbx-R has their own infrastructure, hence #cxbx-r is slow).
The few mentions of XQEMU and Cxbx-R on the Wiki and GitHub are not as problematic.

These emulation channels draw in end-users (non-developers) who distract from actual goals.

I think we are approaching the point where we should split XQEMU and Cxbx-R from XboxDev.

Nothing would really change, except that we wouldn't be highlighting them from XboxDev projects anymore. Each project would use their own communication infrastructure, but use XboxDev communication infrastructure for XboxDev projects.

The major benefit is that we can focus on attracting developers, improve response times for user-support and we can avoid treating non-XQEMU projects "unfairly" (as XQEMU is omnipresent in all XboxDev channels, possibly driving others away; also slightly related #12 ).

XboxDev would still recommend developers to test their tools in XQEMU (and possibly Cxbx-R if HLE works for it) so these projects would also still benefit directly.

Hi,

I think it would be nice to have a CONTRIBUTING.md in order to welcome newcomers and introducing them to the git/community standards.

Related:
@JayFoxRox wrote:

Please adopt the repos standard convention for commit titles (sentence starting with uppercase letter, that describes the change with a verb).
Ideally split independent changes (pipfile / code improvements / readme changes) into separate commits.

Some of our users might be using an official Debug Xbox (XDK) with a Microsoft kernel. Those kernels will still do XBE checks which prevents running retail games or unsigned homebrew binaries.

We should have an open-source tool like nkpatcher for debug kernels, which removes signature checks so users can load unsigned binaries. We can use a DXT to inject these changes on an unmodified debug Xbox.

Some checks which have to be removed / modified (list is probably incomplete):

Kernel

• RSA signature check
• Region check
• Media check
• Flip bits for entry-point and kernel thunk

Game

• DVD-2X check (Hook NtDeviceIoControlFile, or remove X2 media flag)