On Fri, Aug 29, 2014 at 02:59:48PM +0300, Simos Xenitellis wrote: > > It has been said already that there are two main options: > > 1. Start working at once with the AW engineers to send upstream any code > that is missing (Linux kernel drivers, make upstream u-boot work with all > AW SoCs, etc). As a resource, those two Linux kernel engineers from AW are > available to help now. The access to the AW kernel engineers is the most > important resource. > Then, the GPL issues would be gradually resolved. > > 2. Get AW to spend resources to go through and vet tarballs of source code. > I suppose it would take a lot of resources from AW, the result would be old > versions of the source code and we would not have started yet to talk to > the engineers. > This option is a painful option, and should only be the last option. > > In both options, the end result would probably be the same, however Option > 1 will get results faster and is the most beneficial for the future of the > community. > > As a community, it makes sense to try Option 1 and see where it gets us in, > let's say, three months. If we do not get any results, then many more may > choose to go for Option 2. > > It worries me however that for Option 1, Luc will make this list a living > hell. He will sabotage any effort in order not to be proved "wrong". > In this sense, it would be silly for an AW engineer to join the list and > attempt to discuss here. I can already predict endless questions about > licensing towards the engineers (these are not for the engineers to > discuss). > > We have the opportunity to draw a line and move forward. > Which one is the smartest option? > > Simos
So let me translate your email so everyone knows what you are hinting at here: a Fork. You're actually quite predictable. Luc Verhaegen. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
