31 replies to this topic

[kocus37]

What is OE-Alliance?

See this site, maybe OpenPli could join and all toghether we could do better, and all open source.

http://www.world-of-...nce-and-openVix

[Persian Prince]

did you bother yourself to read thread title and the first post ?

every enigma2 developer knows about OE Alliance

[WanWizard]

We have decided not to.

The basic principles we already apply for years, so for us there is nothing new.

We do have an issue with the philosophy behind it, we don't like hack and patch work. We are absolutely focused on a clean and stable OE core, which is impossible with everyone having write access to the repo. If not very stricktly managed it will become a mess. And as far as I can see it isn't. Try to imagine all linux develops having write access to the kernel repo...

[littlesat]

And even we can't merge.... as they are violating licences...

[kocus37]

Thanks for the answer, and i like openpli and you are right in that, i like that you are stick with all the your rules. Its nice to see that in our days. Great work and good path and values.

[andyblac]

We do not add functionality that it will only work on DMM boxes... The devs on schwerkraft are doing this as they want that their plugin will only work on DMM boxes. So we leave the orriginal check in there since a bit more then a year ( I know it was on the request by schwerkraft devs - but we do respect licenses).

At least I see that OE-alliance shamelessly violate at least the mytube license.. Everything from the etpm is patched out (search on etpm)
https://github.com/o...e/src/plugin.py

that is an oversight, i did not know about, it will be fixed, it anyway, it should not be being built for non dmm boxes.

https://github.com/o...ced/Makefile.am

look at line 116

EDIT:

done, https://github.com/o...892ac05f7e8214e

Edited by andyblac, 30 August 2012 - 10:14.

[andyblac]

And even we can't merge.... as they are violating licences...

one mistake, we DO respect licenses, please stop spreading accusations.

[andyblac]

We have decided not to.

The basic principles we already apply for years, so for us there is nothing new.

We do have an issue with the philosophy behind it, we don't like hack and patch work. We are absolutely focused on a clean and stable OE core, which is impossible with everyone having write access to the repo. If not very stricktly managed it will become a mess. And as far as I can see it isn't. Try to imagine all linux develops having write access to the kernel repo...

you do not patch work ehh, really ?, you like everyone else have .bbapends in your gits to suite your needs ( i thought that was patching , hmm maybe i learn something new ), and have you even tried an oe-alliance image ?. and as you do not understand how we control the oe please do not try to guess, if you want to join and participate just ask, as i have said to you guy's before your welcome, just like any other team / manufacture, we are in talks with manufactures to get them to join so the drivers/linux kernels can be optimised for the OE, and they seem very interested in the basics of what OE-ALLIANCE is trying to do. one stable OE for teams/manufactures to use.

[Alias1]

Why every time this guy shows up on here he has nothing positive to say.
Stick to your own forum mate where your admins have free reign.

[andyblac]

Why every time this guy shows up on here he has nothing positive to say.
Stick to your own forum mate where your admins have free reign.

because i do not like people sayings that is not true, and try to spend untruths

[jemneppt]

Why every time this guy shows up on here he has nothing positive to say.
Stick to your own forum mate where your admins have free reign.

second that! all this guys do is complain how bad the openPLi gits is so i wonder why they use it at all if such a big bother
with these kind of comments he is only contributing to the special title of copy&paste-master, merge-master or code-borrow-forgot-to-thank-the-person-who-wrote-it-master
and the more he merge, take, copy, the more he complain
fortunately he is becoming the laughing stock of the community with all these strange remarks.

!! big thanks to the PLi team for keeping up with these kind of guys, respect !!

[Carl]

We have decided not to.

The basic principles we already apply for years, so for us there is nothing new.

We do have an issue with the philosophy behind it, we don't like hack and patch work. We are absolutely focused on a clean and stable OE core, which is impossible with everyone having write access to the repo. If not very stricktly managed it will become a mess. And as far as I can see it isn't. Try to imagine all linux develops having write access to the kernel repo...

you do not patch work ehh, really ?, you like everyone else have .bbapends in your gits to suite your needs ( i thought that was patching , hmm maybe i learn something new ), and have you even tried an oe-alliance image ?. and as you do not understand how we control the oe please do not try to guess, if you want to join and participate just ask, as i have said to you guy's before your welcome, just like any other team / manufacture, we are in talks with manufactures to get them to join so the drivers/linux kernels can be optimised for the OE, and they seem very interested in the basics of what OE-ALLIANCE is trying to do. one stable OE for teams/manufactures to use.

I wonder which manufactures this are probably non which openpli support.