Revenue and the Open Source edition

Mike Kerner MikeKerner at roadrunner.com
Wed May 4 14:38:18 CEST 2016


Exactly, Kevin, Monte,

The "priority bug fixes" is nothing more than a way for all of us to say
"me, first", and that is totally sensible and reasonable.  How important is
that bug that you reported, vs. all the other bugs that are in the DB?  Do
you really think that LC is going to hold some bug hostage until someone
ponies up to fix it?  Of course not.  That would kill the "recurring
subscription" model, that they and so many other software and development
tool firms have gone to, because all of us would just pay for the bugs we
want fixed, instead of paying an annual subscription.  I also completely
disagree that LC has tried to keep people from writing their own
externals.  Monte wasn't a member of the LC team until recently.  Before
that, he was a prolific writer of externals and a prolific adapter of C
libraries to LC externals.  How to do it is documented.  When I had
something I wanted, I just chose to pay Monte to do it, rather than do it
myself.  I get it if you can't afford to, but you can learn to do it.

LCB is in its absolute infancy, but it is a first attempt to push the LC
inyards up toward LCS, so that more of us will work on it and add features
to it.

It also bears repeating that I have told Kevin, and others, that I think
there is not enough bang for the buck for the Business edition, so we don't
buy it.

LCC is FOSS.  Take it, fork it, run with it.  Hell, there is nothing
stopping me from fixing the things in the SE that I want fixed, or added.
We paid whatever it was into the KS because we wanted the security of
knowing that in the event that LC ever dies, the code will still be there,
should we, or someone else, choose to pick it up and go with it, without
having to go through all the hogwash of Administration to get it.

On Wed, May 4, 2016 at 7:57 AM, Kevin Miller <kevin at livecode.com> wrote:

> We can either prioritize bug fixes for the good of the user base as a
> whole, or we can prioritize a bug that affects your project today. The
> former we do automatically, the latter has a cost for us and a benefit for
> you, thus the service. We¹ve had great feedback from our commercial
> customers who have chosen to use that service periodically.
>
> I do appreciate the input on licensing. It is never possible to please
> everyone. We will do what works for the majority and provides sufficient
> resource for us to continue to work on this platform we all rely on. Lets
> move on.
>
> Kind regards,
>
> Kevin
>
> Kevin Miller ~ kevin at livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
>
>
>
>
> On 04/05/2016, 11:12, "use-livecode on behalf of Kaveh Bazargan"
> <use-livecode-bounces at lists.runrev.com on behalf of
> kaveh at rivervalleytechnologies.com> wrote:
>
> >It's all getting too complicated...
> >
> >On 4 May 2016 at 10:39, RM <richmondmathewson at gmail.com> wrote:
> >
> >> To this I would just like to point out that in my "other" email I have
> >>been
> >> offered the chance to PAY Livecode to fix THEIR bugs:
> >>
> >> https://livecode.com/services/priority-bug-fixes/
> >>
> >> That seems a bit odd.
> >>
> >> Richmond.
> >>
> >>
> >> On 4.05.2016 09:53, Terence Heaford wrote:
> >>
> >>> It seems to me as a ³community² user that there is no community.
> >>>
> >>> There only appears to be those that want to pay, those that can¹t
> >>>afford
> >>> to pay and those that don¹t want to pay for ideological reasons.
> >>>
> >>> I, personally do not feel part of a community.
> >>>
> >>> When I read the discussions (not just this thread) the majority seem to
> >>> revolve around how to monetise the ³community² for the benefit of LC
> >>>and
> >>> how can we convert a ³community² user to a paid user.
> >>>
> >>> It seems to me that there are a number of people who subscribe to this
> >>> mailing list who want to own the product (rather than rent) and that is
> >>> understandable (I am probably one of those).
> >>>
> >>> But, to put it quite simply, I cannot afford it, it is to expensive for
> >>> me ( a loss for me and a loss for live code).
> >>>
> >>> If I were to produce a fantastic product that I thought would be useful
> >>> to a great many people, I may want to give it away for free but under
> >>>the
> >>> present arrangement I would not
> >>>
> >>> bother because I would not want to give away my coding effort.
> >>>
> >>> Could probably go on forever but I think that¹s enough.
> >>>
> >>> The end of my 2 pence worth.
> >>>
> >>>
> >>> All the best
> >>>
> >>> Terry
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> 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
> >>
> >
> >
> >
> >--
> >Kaveh Bazargan
> >Director
> >River Valley Technologies
> >@kaveh1000
> >+44 7771 824 111
> >www.rivervalleytechnologies.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."


More information about the use-livecode mailing list