Folks, The donations to fix specific bugs is a notable idea. But what comes to mind is where the programming effort to fix the funded bug will come from. Presumably, you are thinking it will come from mothership staff programmers. I don’t know, but suspect the staff programmers are already busily working on tasks supporting existing efforts. Suppose bugfix A, funded by donations, takes 40hrs to fix. This 40 hrs will take 40 hrs from somewhere else.
So, my basic question is: can the time management strategies of the mothership accommodate these special bugfix jobs? Also, if staff already allot significant time to bugfix efforts, perhaps community votes for highest priority bugs would be effective. On the other hand, if a high priority bugfix can be funded by a client with a special need and the capability of funding it fully (I think that already happens), that’s also to the good. I guess what I’m saying is that, if you want the mothership to do the fixing, they should be giving input on what might also work for them. Alternatively, maybe there are programmers in the LC community who have the skills to tackle some of the bugs and will, if they are supported financially. In that vein, perhaps a system of bidding for bug fixes on the “auction block” could be developed. Payment would be made after tests confirmed the solution, and it could be incorporated into future LC versions. Those are just some thoughts, maybe useful, maybe not. Best to all, Bill William Prothero http://es.earthednet.org > On Oct 5, 2019, at 9:56 AM, Curry Kenworthy via use-livecode > <use-livecode@lists.runrev.com> wrote: > > > I have a very humble proposal to move things forward in more positive manner, > and entirely eliminate ALL negativity. > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
