-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue tracking: PS! edition #2297
Comments
Do we currently support popup forms? I'd guess no. Imagine a popup form asking for someone's password... such phishing... |
Command-based just isn't a very good system... |
Mandatory xkcd: https://imgs.xkcd.com/comics/standards.png The proposal doesn't feel like the universal standard |
tbh, we do need some sort of issue tracker... the biggest issue with existing ones is probably that most of them cost money, and I don't trust the ones that don't not to have glaring vulnerabilities. |
Is it possible that this kind of form could only work client-sided? That way, other servers cannot try to do another kind of popup form server-side? |
We could, but at that point we might want to write it entirely separate from PS or something. One idea would be to host it outside of the main server, so vulnerabilities are less of an issue. My only issue with that is that moderation/trolls could be an issue if it's disconnected from the PS login system. |
This is semi off topic, but did PS's old forums use PS login credentials? I'm wondering if those could be optimized for bug reports... Did those have a 'liking' or 'staring' feature by chance? (I don't remember) |
(I want to reemphasize how useful sorting reports by categories could also be very helpful) |
Yes, PS's old forums did. PS's old forums were also hacked. That's kind of why I said I don't really trust most third-party software these days. |
bugzilla works fine for mozilla. No idea how well it works from a end-user perspective though. |
Now that we have #2367, we can just put approved mechanics bugs there. I'm fine with the current system for everything else. |
I am working with Nineage to start thinking about creating an issue tracking system for PS! that would allow the average user to easily and effectively report bugs pertaining to relevant parts of PS!. Here's the basics of what I was thinking along the lines of for the architecture:
>user does /reportbug
The client sends the user a popup with a form asking for information pertaining to the bug, such as...
After the user fills that information out, it will send this to the server, where the database of issues are stored. (TSV database like the existing local ladder system...?)
>user does /viewbugs
And of course, there will be a certain rank that is able to delete reports based on the report number with
/deletereport [report number]
This is just a rough sketch on my idea of a issue tracking system, what does everyone else think?
The text was updated successfully, but these errors were encountered: