Discussions with the FLEx team
Perspectives on Service
After filing an error report to the correct address for reporting errors about FLEx I had this conversation with the person answering that inbox.
Hi Hugh,
I guess you mean you pressed the Send/Receive button from within WeSay. There are a lot of random errors like this. I do have an issue open about this that I hope some Linux developer will look at. In the meantime, I suggest running the process again as you did. What version of FLEx do you have installed?
Thanks
No, I was sending to We Say for the first time from FLEx. Not the other way round. I have the latest 8.3 beta FLEx version installed.
- Hugh
Okay, at thanks for clarifying this. The other person having this problem is using 8.2.9. I guess it doesn’t make any difference. Both are flaky.
Just check to see if that was me as well. I updated about a month ago [really it was two weeks ago and I also reported the problem then too].
No, it’s Kent Rasmussen. There are other Linux users, but they don’t much report the errors anymore since it doesn’t usually make a difference.
As in the errors don't get fixed by LSDev? or what difference was expected [by the reportees]?
We have a very small team of developers working on FLEx (4?). We have hundreds (thousands?) of open issues. Most developers like working on new stuff rather than fixing bugs so it’s really hard to prioritize things that work at all. Even issues that block people from doing their work may take months to get fixed. It’s not that we don’t want to fix the bugs, it’s just the reality of the beast. I hate telling people the bug reported 6 years ago finally got fixed.
I'm sure that celebrating bug fixes from bug reports for 6 years ago is hard. I'm still waiting on a solution for entering word paradigms with fusional morphology... So I moved on to a noun-class language...
Sounds like a good idea!
