Coder Social home page Coder Social logo

lutris-dashboard's Issues

Add an action between Accept and Reject

While some installers should be rejected outright (piracy, shady sources, etc), more often I want to follow up with the submitter and and questions or request changes.

For example, recently someone submitted an installer for GOG's Windows version of Another World. There is already an installer for GOG's native version, so our policy is not to accept the Windows version in that scenario… unless it has features that the native one lacks. So in this case, rather than reject outright, I'd like to ask the submitter why they wanted the Windows version when the native one already exists. Otherwise I have to choose between accepting an unnecessary installer, rejecting a useful installer, or doing the work of researching why the Windows installer may be needed (In this case I chose to do nothing, and someone else accepted the installer later, so the submission is no longer available).

It would be nice to have a third option, something like "Reject with reason" or "Request information/changes", that allows moderators to send a message to submitters and preserves the installer. The message could be sent through email or appear on the submitter's dashboard; the submission could either be included in the message or set back to draft status.

Don't exit when accepting/removing submissions/drafts if there are still some available

Once a submission/draft is accepted/deleted the page exits back to the submissions page. Instead, it should load another draft/submission if there are any available.

With the way it is now you have to review the installer, accept/delete installer, go back to game page, reload to refresh review button, and review the remaining edits. Repeat that process until there aren't any left.

It's tedious.

Add pagination

I would like to be able to see how many pages of unmoderated installers I have to deal with and browse through them.

After validated a submitted script, you have to reject all older submitted script versions

Hello,
when I validate a submitted script modification, I have to reject all older submitted script modifications.
Sometimes there are more than 20 modifications to reject, it takes a lot of time and it is useless as we have already validated a script.
What about to automatically reject all all older submitted script versions when a modo validated one of them?

Diffs are kinda fucked

The installer: line is not actually there in the submission at the bottom, but it's shown like it's added there
image

Sorting preference is not remembered

If I switch sorting preference to "oldest", this sorting rule will reset if I review an installer, close the page or switch to another tab (like new installers). This requires pressing the button after each review which is very inconvenient.

Dashboard: diffs are broken for some installers

List of duplicates

Allow to edit installers that are under review

Very often the installers that we review can be alright but may contain a tiny mistake or an awful name, which can be easily fixed. But currently, there's no way to do that from the dashboard, you have to look for the game on the website yourself and edit the installer manually which after a few of them makes you go insane.

Field for editing the script is too small

When reviewing an installer, if you first edit the "notes" field or any other field but "script", and then edit the "script" field, the "script' field will be very small. This hinders the reviewing process.
Observe:
Peek 2021-12-10 04-31

Sort new installer submissions by submission date

Currently, installer updates are sorted by submission date (most recent first, to form a LIFO queue). However, new installers are sorted alphabetically. Most of the current first page of submissions has something that makes them hard to approve for one reason or another (and I do not want to reject them; see #26), so this view is basically useless at the moment :(

Add Oldest/Newest sorting

I would to be able to view installers that were the oldest to be submitted instead of newest, and be able to choose between 2 options.

Merge installers

This happens a lot:

  1. Installer version X doesn't work
  2. Someone forks installer X and submits it as version X (fixed)

Current workaround:

  • Accept and publish installer X (fixed)
  • Delete installer X
  • Rename X (fixed) back to X

This is extra work and means that the history for installer X is lost.

It would be better if I could instead accept the X (fixed) version and then merge it into X. The merging implementation would take these actions:

  • Adds the most recent revision of X (fixed) as a revision of X.
  • Deletes X (fixed)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.