On Thu, Jan 9, 2020 at 6:21 PM Nathan Hartman <hartman.nat...@gmail.com> wrote: > > On Thu, Jan 9, 2020 at 4:01 PM Gregory Nutt <spudan...@gmail.com> wrote: > > > For now, is this particular issue easy to fix? I didn't look at the code > > > yet. If it's a quick fix, we should just fix it right away. > > > > It is not. You could have to create and FTP client configuration and > > bring and FTP server on some test network. I have never done that kind > > of thing for user-reported bugs. My belief is that we are here to help > > people, not to solve their bugs. If they want to work through the fix > > for the bug, then we should help. > > Ok so it is not a trivial "check for NULL before dereferencing and > return error" five-minute-fix type situation. > > More below: > > > If they want us to do the work, we should be talking about contract > > labor. You really have to draw a line somewhere. We are giving away > > software and we help as much as we can, but we don't give personal > > services labor away for free unless we have a particular interest. > > > > At that least that is were I draw the line personally. If you don't > > draw a line somewhere, you will be used and abused for the profit of > > other people. > > > > I doubt that anyone is that interested in FTP since it really does work > > already. > > I agree with you there 100%. Open Source can be whatever someone wants > it to be, if they're willing to put in the effort. > > We have to get the issue tracker question resolved. I forget now, was > there a thread for discussing this? Or were the discussions scattered > / hidden in other subjects (like this one)? We need an explicit > "[DISCUSS] How Do We Track Issues" thread. Do you mind if I start one?
Nevermind that last part. There is an "Issue Reporting" thread.
