90s design (please lets move to 21st century)
I want to modernizer the "Ruby Issue Tracker because every time I access that site, I want to throw up 🤮¹
Here my different proposals to solve this MAJOR issue:
b) Move fully in to Github Discussions & Github Issues. (I'm sure if we contact Github they will be pleased to help us migrate bugs.ruby-lang.org in to Github Discussions/Issues).
c) (Propose yours, in the comments below.)
If we decide to choose the option A, I will be please to help.
Let's do a Cons and Pros about each proposal.
OPTION "don't change anything"
- No work.
- Less contributions. (Are we in the 90s?).
- Search is broken.
OPTION "Update the design using modern CSS framework"
- A fresh look, that gives life to the community.
- Work to do.
- Search is broken.
OPTION "Migrate to Github Discussions/Issues"
- More accessible for new Devs (because most devs they have an account in Github).
- 1 place for issues, discusions and code!
- A non broken search.
- Migration to do.
- Depending to much from Github? (I know that Microsoft bought Github, and MS has a very bad reputation, but Github seams that they are not letting that bad behavior corrupt Github).
ANALOGY: Do you know when you are Code Reviewing,
but you see something super ugly in the code that you are reviewing,
and then this super ugly thing doesn't allow you to see anything else,
you only that ugly thing.
Then this is what it happens to me evey time I access bugs.ruby-lang.org
If you go to my profile you can see that I was Registered on 04/02/2015,
and I have 0 issues and 0 comments, because the first thing that I do when I arrive to that bugs.ruby-lang.org, is to close it. (NO JOKE)
Updated by WaKeMaTTa (Mohamed Ziata) 2 months ago
xtkoba (Tee KOBAYASHI) wrote in #note-3:
I do not understand what "search is broken" means. Could you explain what you tried to do? Searching in Ruby Issue Tracking System seems to just work for me.
You can see it in the screenshot -> https://media.discordapp.net/attachments/766466740069859349/848985772920668180/unknown.png
But I just tried again, and this time I didn't have any error.
Maybe it was only a temporal issue. :)