Give a bug a hug

Fri Oct 11 13:02:20 EDT 2019

For what its worth, I think this is the way to go. A totally community run initiative, with a bounty on bug fixes. Someone or several someones outside of the LiveCode team would need to take responsibility for setting up a structure. We'd love to see bugs being fixed, by members of the community. It's kind of the reason behind Open Source. There are plenty of bugs that would be suitable, which don't require deep dives into the engine. Pull requests arrive in the usual manner and get approved or fed back on in the normal scheme of things by our team. If this could be encouraged by a bounty on fixes, funded by the community, run by the community and entirely outside of LiveCode Ltd.'s scope, what's not to like? Our overstretched resources would be augmented by a community team, and the dual nature of the licensing would bear fruit in a new and productive manner. I like it. 

Over to you. 

Best Regards,

Heather

Heather Laine
Customer Services Manager
LiveCode Ltd
www.livecode.com

> On 10 Oct 2019, at 22:17, Mike Kerner via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> wow, i managed to mute this conversation.  fail.
> @paul, that's exactly why we ponied up, too, as an insurance policy.  we
> have been burned by numerous organizations either abandoning their software
> work product or disappearing.  thankfully, for most of our mission-critical
> stuff, we have, own, and maintain the source.
> @Sean, I'm not generally thinking of the underlying engine for the bounty
> program, I'm thinking of pieces in LCS/LCB.  In those cases, the PR doesn't
> get submitted to the LC repo until whatever step it was further down.
> There isn't any reason why private repos can't be used to manage this
> process, especially with submodules.  The patrons would have access to the
> repo, no one else would.
> As for the conversation about the unfinished projects that all of us ponied
> up for on a promise, I 100% agree, which is why the funds are escrowed.
> The developer proposing a solution doesn't get paid until the patch is
> tested and approved by the patrons of the patch.
> 
> On Wed, Oct 9, 2019 at 11:02 AM Bob Sneidar via use-livecode <
> use-livecode at lists.runrev.com> wrote:
> 
>> +1 Richard. I got onboard with what user to be Runtime Revolution (I think
>> it was version 2!) Where livecode is today is orders of magnitude more than
>> it was when it first started. There was no datagrid. No way to display
>> tabular data apart from a very simple table field. No arrays. Difficult and
>> confusing database APIs. No mobile support. The list goes on.
>> 
>> LC is like a really good girlfriend. She isn't everything I ever wanted,
>> but she's good enough for me. :-)
>> 
>> Bob S
>> 
>> 
>>> On Oct 8, 2019, at 19:49 , Richard Gaskin via use-livecode <
>> use-livecode at lists.runrev.com> wrote:
>>> 
>>> Pi Digital wrote:
>>> 
>>>>> On 8 Oct 2019, at 21:42, Richard Gaskin wrote:
>>>>> 
>>>>> And here is a May 2016 update:
>>>>> 
>>>>> 
>> https://livecode.com/trevor-devore-interviews-kevin-mark-on-infinite-livecode/
>>>>> 
>>>>> 
>>>>> A small number of people keep going round and round on this a large
>>>>> number of times.
>>>>> 
>>>>> How many times will the same conversation happen before more recent
>>>>> information is absorbed?
>>>> 
>>>> An excellent article. Which part was you pointing to in reference to
>>>> Lagi’s question about older campaigns funded that have still not met
>>>> the core?
>>> 
>>> There's a section in the middle listing off the accomplishments since
>> the Kickstarter, and some of the discussion goes into how much of that was
>> paid for out-of-pocket.
>>> 
>>> 
>>>> And which part do you refer to when asserting that absorption of info
>>>> is needed to reduce the same conversations recursion rate?
>>> 
>>> The portion of Lagi's post I had originally quoted in my reply:
>>> 
>>>   This is what I was talking about being treated like mushrooms
>>>   - no communication as to what the future holds.- rough timescales
>>>   as to when new or reassigned resources will be implemented - what
>>>   is the intention with sqlite, 2d physics, Audio ....
>>> 
>>> He's one of about three people who keep going back to the Kickstarter
>> list as some form of eternal damnation against the team, and he knows that
>> I know that he's read comments here and in the forums from Kevin and other
>> team members that have discussed all of that over and over and over and
>> over again.
>>> 
>>> How many times does Kevin need to post a mea culpa about being among the
>> 80% of software project leaders that underestimated cost?  Apparently half
>> a dozen isn't enough.
>>> 
>>> In summary: Most of the list was delivered, most of the remainder is in
>> the DB as feature requests to be completed as resources permit.
>>> 
>>> 
>>> Kevin, Heather, Mark and others have been very forthcoming here about
>> what the company is working on, at least to the degree that this community
>> allows.  But there's not much allowance granted:
>>> 
>>> As they've explained many times, they've joined the majority of
>> companies less willing to offer loose projections about delivery times
>> precisely because of things like this.  If they give a projected deadline
>> and circumstances change, it will become a dominant and repeated theme
>> among a very small but very vocal minority.  This isn't unique to LC; their
>> previous candor was a distinction.  Now they operate like everyone else,
>> because the moment they dare to discuss anything not already in the can
>> they expose themselves to a continuation of this same tediousness that
>> every other company figured out how to avoid by keeping cards close.
>>> 
>>> Wanna know what Apple's working on for 2020? Good luck.
>>> 
>>> --
>>> Richard Gaskin
>>> Fourth World Systems
>>> Software Design and Development for the Desktop, Mobile, and the Web
>>> ____________________________________________________________________
>>> Ambassador at FourthWorld.com                http://www.FourthWorld.com
>>> 
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
> 
> 
> -- 
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>   and did a little diving.
> And God said, "This is good."
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode