Re: Call to NOT move to github or gitlab

[Ricardo Bánffy]

> 
> Trouble ticket systems are where problems go to die. Priority: Minor.
> WONTFIX.

Not necessarily. I maintain a couple projects that don’t get much traffic and I 
use to be somewhat responsive. Not as much as I’d like, but nobody forked them 
because of my laziness. 

> Every trouble ticket system works a little differently. I heavily use
> about 30 Open Source programs. I don't have the time to learn and
> remember 30 trouble ticket systems.

We know that. This is even a good reason to pick something like GitHub, or 
Launchpad, or anything else like them. If the common solution fits the workflow 
the contributors want, I’m ok. I even use Jira for work and EVERYONE HATES IT, 
including me. 

> I had this problem with the Bluefish editor, so after a few months of
> them making lack of zen-coding *my* problem, I switched to VSCode. I've
> had this problem on the LyX list, and am continuing to try to create a
> LyX alternative.

This is why open source is so great. There are abundant solutions for most of 
our problems. I’ve faced the “the problem is you” answer more times than I 
remember and it’s fine. Most of the time, open source is someone else’s 
software and, if it doesn’t work for me, I can always try to make it mine (by 
means of a fork) or use something else. This is a feature, not a bug. It’s 
likely VTE will never smooth scroll text or do DECWDL/DECDHL and it’s OK. I 
don’t care enough to do it myself. Otoh, I volunteered to eventually add 
Tektronix graphics to it (some day). I’m trying to get a good reference machine 
(most likely a VT 200 or 300 series terminal - a real DVST terminal belongs in 
a museum) for helping with that. Maybe with luck I can add ReGIS as well. 

> One more thing. In the past Troubleshooters.Com had a "Symptom
> Description Wizard" that asked several questions and spit out a symptom
> description ready for copy and paste into anything, or for printing. No
> required fields, completely obvious how to use. It went away when Java
> Applets stopped being supported. If this is something that could be an
> asset to the world, I can recreate it with a modern web application.
> Any opinions on this?

If you choose to do it in Python, you can count me in. I’m less thrilled about 
JavaScript, but it may be a better choice for it.