MovieStacker v1.1.0 released
 

MovieStacker v1.1.0 is ready!


The full "release notes" is in the ZIP file.
I have to thanks Jorel for sending me icon of my avatar, it was really good, but I think that it just don't blend well... :?
I use a different (simple) icon for this release, but I still searching for the right one.

Well, I hope you all like it! :D

Hi muaddib!

Nice work!
Can you tell me, where to download the sources, according to the GPL, please? Thanks.

Best regards,
shh

Hi shh,

The source will be posted right here as soon as muaddib sends it to me. Probably soon, because we talked about that yesterday.
I agree 100% with you that the "modified" sources should be posted.. But be aware that the GPL license left a big loophole, and that is that they didn't specify WHEN the sources should be posted. So it's to the discression of the developer making the changes when HE decides to post them, within a reasonable time of course. If you look carefully at Lindows ( www.lindows.com ), you'll find that some of the sources are released months after GPL sources have been modified. They use that as a "propietary advantage". So if muaddib wants to retain the modifications for a while, he can :wink:
Also, I'm not sure if muaddib followed some suggestions that were talked some time ago, and that is regarding "hooks" from the sources to separate his sources to FitCD's sources. You see, I develop some commercial software for clients, and I do use some (minimal) GNU sources, as I prefer to use "BSD" license for commercial use. So what I do with GNU software is that I code my routines ( functions, procedures ) as "External" functions around the main GNU sources. This way, the only thing in the GNU source is a "call" to an external routine, which is my property, and I don't have to give that to anyone. So this way, I don't violate the GNU license, because I AM giving out the modified GNU sources, but not MY sources. And of course, this makes the modified GNU source "uncompilable" because it's missing my propietary source. Again, another unspecified "loop hole" in GNU license, which RS didn't think about. That's also how some commercial "modules" for Linux are being developed and sold. They "attach" to the kernel, but the kernel sources are not touched, again permitting a propietary advantage to a developer for commercial ( or whatever ) use.

Regards,
-kwag

Hi shh!!!

It's been some time you don't show up.
I was already missing you.
I'm glad you are here! :D

I will release the sources soon.
I just have to organize some code and make up some docs (I don't even have a “readme”! 8O )

When it's done, I'll post it here in kvcd.net.

Hi!

> It's been some time you don't show up.

Sadly, I'm *very* busy at the time. Extending FitCD/Fit2Disc and ReStream is eating up all my time.

> I will release the sources soon.
> When it's done, I'll post it here in kvcd.net.

Ok. I hope to see it soon. Although I know how long it could take to create a proper readme. ;)
(people still keep me bugging to create one for ReStream...)


...yet another GPL-discussion. ;)

> hooking to external, non GPL code

Yupp, I also think that this would be conform to the GPL. Of course this won't go the other way round (see the Vidomi-GPL discussions).
The problem is, that pre1.1.0 Versions of my FitCD are very dirty coded (to my understanding), so attaching external functions can be quite difficult.

> Lindows

I've followed the discussions around Lindows, transgaming and so on.
To my understanding, the conclusion was, that when a program is released, the sources should also be "available" in some kind of way. I think Lindows just held them back, because they haven't released the final OS, yet. After releasing their v3.0, they also published the sources.

Cheers,
shh

Simple solution: If you want to put out free software, release it into the public domain.