Development GPL Compliance

Originally Posted by dontpanic

Hi,

I want to drop in and let you know that we did find that we did not release the complete source code package last Friday. The engineering team is putting together the package again now. We want to do it right, though, so give us a little time to check things out and push the code out again. We apologize for the mistake.

DP

It is good to see you can admit a mistake... but:

Please define "a little time"

I think this item CAN have an ETA!

Community is waiting.

Patience guys............

enTourage have admitted the oversight......please don't let this escalate again into a full blown slagging match.

The code is on it's way.

Thanks to jcase, MichaelV, robot, shinkamui (and any I've missed) for their persistence in bringing this about but let's avoid cheapshots at integrity etc which cause these things to escalate into stupid and time-wasting fights.

Originally Posted by drsteve

Patience guys............

enTourage have admitted the oversight......please don't let this escalate again into a full blown slagging match.

The code is on it's way.

Thanks to jcase, MichaelV, robot, shinkamui (and any I've missed) for their persistence in bringing this about but let's avoid cheapshots at integrity etc which cause these things to escalate into stupid and time-wasting fights.

Now worries drsteve,

Absolute not intended to start things over!
Just trying to put things clear and building up relations again.

Sorry if you interpreted different,

Jos.

Okay, we've taken another shot at posting our source code. You can find it in our knowledge base here:

https://www.entourageedge.com/suppor...barticleid=159

DP

Originally Posted by dontpanic

Okay, we've taken another shot at posting our source code. You can find it in our knowledge base here:

https://www.entourageedge.com/suppor...barticleid=159

DP

Thank you!

Jos.

After spending six hours trying to compile the kernel (under widows using cygwin+arm-elf, and under ubuntu using CodeSourcery arm crosscompiler)...

dontpanic, I don't want to start flame and assume that the source code is complete, but it would be nice, if you also publish the ".config" file used to compile the latest version of the kernel and if you tell us which compiler you're using.

Thanks.

p.s. also didn't see gstreamer source code (it's used as part of video player).

Originally Posted by robot

After spending six hours trying to compile the kernel (under widows using cygwin+arm-elf, and under ubuntu using CodeSourcery arm crosscompiler)...

dontpanic, I don't want to start flame and assume that the source code is complete, but it would be nice, if you also publish the ".config" file used to compile the latest version of the kernel and if you tell us which compiler you're using.

Thanks.

p.s. also didn't see gstreamer source code (it's used as part of video player).

Robot,

Hey, I sincerely appreciate your understanding and constructive attitude. We do know that we need to provide better documentation. Unfortunately we are just a little more than a week away from a major software release. We can check into your requests and try to sort these things out, but it may be a few days before we can get back to you on this issue. Just a crazy time.

DP

Originally Posted by dontpanic

.....Unfortunately we are just a little more than a week away from a major software release....
DP

And I say YAY!

Good going Entourage...

Now I'm going to be sitting on pins and needles waiting for the update! And I second that "YAY!" and "Good going, enTourage!"

Me too!!! How am I going to get to sleep tonight???? With pictures of updated Edge floating in my head.

dontpanic, there's no need for documentation (it does not help those who are not familiar with compiling kernels, and those who compiled allready know how to do it). What I asked for is ".config" file which automaticly created when compiling kernel and contain exact settings used for compilation. It's greatly improove the speed of developing (so many companies like nook and samsung include it in kernel source code). I can compile without it, but it'll take few days, but with this file it will take a few hours (even taken in account some problems with source code published, which can be fixed).
On the other hand.., hope that you'll published updated source code right at release time, and at this time it'll contain all necessary things.

p.s. any details about upcoming update? Android 2.2? Improoved power management?

Details on the next release, AKA "Dingo" will be coming early next week. There are a lot of good things in it, but sadly Froyo upgrade is not one. We have some third party dependencies for that and for Flash upgrades (Adobe only works directly with processor vendors for all Flash certifications) and power management improvements, so it will be another couple of months for those. I can spill the beans on a few items, I guess...support for USB to VGA adapter...major UI overhaul...other stuff.

DP

dontpanic,

Robots request is legit for the config, you are required to provide the config and source used to build the kernel, under the GPL.

Justin

Oh, and I can say that there will likely be some lag between our releases and release of the source code. We know that it is supposed to work differently, and really do not mean it as any kind of affront to the GPL copyright holders or the developer community. It is just a matter of resources and things are usually very crazy in the last weeks running up to a release and then the few weeks after the release because of the increase in support needed. We will try to keep the delay as short as possible from this point on. Like I keep saying, we understand we have an issue and are working on improving.

DP

Originally Posted by jcase

dontpanic,

Robots request is legit for the config, you are required to provide the config and source used to build the kernel, under the GPL.

Justin

Justin,

I agree. Let me see what I can do Monday.

DP