octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Octave on Android


From: Corbin Champion
Subject: Re: Octave on Android
Date: Tue, 5 Nov 2013 10:15:01 -0800

On Fri, Nov 1, 2013 at 9:02 AM, Thomas Treichl <address@hidden> wrote:
Am 01.11.13 00:25, schrieb Corbin Champion:

I agree with the fact that the DMCA complaint was filed before the facts were known, but I really don't know why that was the choice made.  I mainly posted, because I want people to understand (anyone who reads this now or in the future) that there is a better way to go about this.  Just talk to the developer.  Just ask for what you want.

About amends, I have filed a rebuttal to the app being delisted.  I am not sure what the timeline is for processing it, or whether they will or will not contact Thomas again in that process, or whether they will or will not find things in my favor.  Never been in this rodeo.  I have provided a link to this thread and my source code and other information.

Appreciate the support.  I am not feeling burned by this specifically, but by a generic behavior.  I forgive Thomas and I hope he forgives me.

Anyway, that is enough drama for this list.

Corbin
Dear Corbin,

  forgiveness to both of us, agreed.

  From my point of view there are some tips I'd like to share with you at the end here, you maybe should check that once again before exactly the same package is listed once again at Play Store. Take the following situation as a basis, where on my and other peoples' tablet OdePkg is still installed and is not listed on Play Store any more. I've searched all of my tablet for at least your contact informations, but could not find any, people cannot get into contact with you any more about OdePkg.

  Next, you deliver dldsolver.oct in form of lib__file0.so as a binary file within the package. Therefore at least §3 of the underlying GPL V2 should be taken under account where you can still choose between 2 of 3 options (I think you can't choose option 3.3 any more because you require money to make it working). 3.1 says you can deliver the binary file together with the source files and 3.2 gives you the option to deliver a written offer...

  Further, dldsolver.oct is build of various *cc files that I've written with an underlying GPL V2 but also uses some Fortran files that I've not written and come with other licenses like e.g. a 3 clause BSD license with the daskr solver and even some other licence with the radau* solvers. They clearly want the copyright notice to be shared - which isn't. All licence files are included in the source package of OdePkg, please make sure that you can still deliver your package that way you do without even breaking other's people licences - which again is meant as a tip for your next release.

Ok, now, enough from my side. Keep on coding!

  Thomas

This is a good point.  I already submitted the counter to your complaint and I think, if granted, they will put it back up in the Play Store as is.  I have a big update coming to both the main app and the add-on packages/apps which will fix this, but it will not roll out for a little bit.  Specifically, the packages will include all the normal files provided by the similar Debian packages (instead of a subset), which I believe contain the correct and sufficient copyright information. In addition, I will add a written offer (hadn't thought of that, but it is not a big deal), per your suggestion.  Hopefully, no one minds the problem persisting for a few more weeks.

Thanks,
Corbin


reply via email to

[Prev in Thread] Current Thread [Next in Thread]