protonscr

Organization: Move whitelist request and game-specific issues to separate repos

protonclosed
ValveSoftware/Proton#76 · opened 2018-08-22 by akien-mga · updated 2018-08-23 · 3 comments · github
Aakien-mga 2018-08-22 github

First of all congrats for a great release and for the work you've done here, it's an incredible milestone for Linux gaming.

I see that after 12 hours the issue repo is already filling up pretty fast, which is great, but being familiar with managing open source projects, I wonder if that's the best workflow for the development of Proton on one hand, and for improving SteamPlay compatibility on the other hand.

I would suggest to create new repositories/issue trackers for:

  • Whitelist requests; all issues should have the same form, following a configured ISSUE_TEMPLATE.md, which would make it clear what game was tested (including its Steam ID for disambiguation), on what platform, etc.
  • Game-specific bug reports; same thing, there should be a specific issue template for those.

This tracker (ValveSoftware/Proton) would be for actual software issues in Proton, buildsystem stuff, enhancement and feature requests, etc. It should be kept primarily for Proton developers and contributors.

WDYT?

Kkisak-valve maintainer 2018-08-23 github

Hello @akien-mga, since I'm labeling the issues during initial review, there's not much of an issue with mixing these issue reports.

Some convenience links:

Whitelist requests only

Games needing workarounds

Whitelist requests and unofficially supported games excluded

Mmirh 2018-08-23 github

Mhh, I dunno.. It starts to become confusing when geniuses start to mass report everything and the kitchen sink.
Already half of the first page is wishlists - let alone half of the reminder being bugs in unofficial games.

Nothing extracted yet.