1748 replies to this topic

[Taapat]

But our OE will never be open again, nobody should be able to create OV images without our permission and this won't change.

 

Ok you can do it.

However, as mentioned here, your OE recipe for fulan comes from MastaG which is a copy of my no longer supported OE repo for fulan: https://github.com/T...openpli-oe-core

Therefore, please make sure that everything related to fulan is available as open source.

You may not like this, but you use exactly the same license in OE as in enigma: https://github.com/T.../master/LICENSE

Edited by Taapat, 1 February 2021 - 10:19.

[Persian Prince]

 

But our OE will never be open again, nobody should be able to create OV images without our permission and this won't change.

 

Ok you can do it.

However, as mentioned here, your OE recipe for fulan comes from MastaG which is a copy of my no longer supported OE repo for fulan: https://github.com/T...openpli-oe-core

Therefore, please make sure that everything related to fulan is available as open source.

You may not like this, but you use exactly the same license in OE as in enigma: https://github.com/T.../master/LICENSE

 

 

meta-sh4 isn't meta-fulan like OE-A and you can find old versions of it if you search for it but even if I open some more repos it won't bring you any good as I want to use local patches which won't be available on git.

 

meta-sh4 is like 100% rework and almost done by me to support all SH4 brands/models.

 

OE license or anything else isn't a matter related to PLi so won't be open.

 

Believe me it's just 2 clicks for me to delete a repo and use local sources, something that even happens in some OE-A teams and nobody speaks about it.

[Taapat]

meta-sh4 is like 100% rework and almost done by me to support all SH4 brands/models.

This is no reason not to follow the license. And it has nothing to do with OpenPli.
You can change the code completely, but you have changed the code that contains the license, which you do not have the right to change.
As I wrote I have stopped fulan support and I am not interested in your changes, but I am interested that open source remains open source including all changes in it.

 

But of course your choice is to follow it, or join them who doesn't follow.

[WanWizard]

By way of explanation, my understanding is that Persian Prince has made the changes he made due to users taking code from OpenVision without crediting the source of that code.  Even more disturbing is that some of the code has apparently been used for commercial profit!  Obviously such profit is not being distributed to those who created the code.

 

Then I'm afraid PP hasn't understood the license.

 

The GPL v2 license explicitly allows code re-use, and explicitly allows commercial use of the code.

 

It only says that:

• if you modify a piece of GPLv2 licenced code, you have to clearly mark that code, with a description and date
• if you publish a piece of softwate that contaiins GPLv2 licenced code, you are required to publish the source code to (this may be on request)

Enforcing this is an entirely different matter, but the fact that someone doesn't obey by the rules doesn't mean you shouldn't do that either.

[babsy98]

OV clone many from oe-a and use my private ftp download server without ask for permission, and now make open source close

 

this is going in the wrong direction, better for user don't use OV image anymore and use only open source image like openpli and oe-a team Images

[IanSav]

Hi Babsy98,

 

Are you sure that the OpenVision Enigma2 repository is closed?  It was closed for a very short time and was reopened for access by everyone.

 

As a regular contributor to OpenVision I expect all code I contribute to be open to all.

 

Regards,

Ian.

[zeros]

OpenVision Enigma2 repository it's totally useless until one bitt is closed.

From OV statement:

 

Lots of our git repositories are now private and no self builing is possible thanks to source steallers.

And I'm not offended to PP, that he banned me from OV board. He knows better what he's doing and who he builds it for.

[Dimitrij]

https://github.com/O...gma2-openvision

[zeros]

Dimitrij, no, you misunderstood. I said it's not good enough, if even one other part is closed and there are so many, also at the core side.

[Persian Prince]

OV clone many from oe-a and use my private ftp download server without ask for permission, and now make open source close

 

this is going in the wrong direction, better for user don't use OV image anymore and use only open source image like openpli and oe-a team Images

 

What's your private FTP download server that we're using?

 

If it's private then how we have access to it?

 

Let me know please.

 

The wrong direction is already in OE-A, from https://openvision.tech/?p=192 :

 

• Some people/teams are showing fake git repos and their real enigma2 sources are closed or they’re using local patches and some of those public git repos are just for show (Can you believe a team updated enigma2 sources after 6 months with one file change? Yep a bad joke).

 

Regards,

Persian Prince

[Persian Prince]

OpenVision Enigma2 repository it's totally useless until one bitt is closed.

From OV statement:

 

Lots of our git repositories are now private and no self builing is possible thanks to source steallers.

And I'm not offended to PP, that he banned me from OV board. He knows better what he's doing and who he builds it for.

 

From https://openvision.tech/?p=192 :

 

The core of each enigma2 image is enigma2 itself and that’s open on our git and we update it for real not a fake repo so if you want to lecture us just keep it.

 

So the rest "none of your concern".

 

P.S. I didn't ban your account, you just don't have any account to log in (anymore). I prefer to spend my time on developing not answering to chaotic posts which won't bring any good, sorry.

[rantanplan]

and why are you still taking part in the discussion here ...
You continue to advertise completely outrageously by means of a direct link to 'Your' property and closed source project.
I would like it if this is no longer tolerated.
That you continue to play here and continue to discredit users who have supported you for a long time is also a cheek.

Please talk to yourself in 'your' forum and be glad that nobody contradicts you there.
If so, then you delete everything anyway you like.
Everyone should be happy that they are no longer present in your forum.

[zeros]

My point was just to warn you about the future use of OV. It's something similar that happening with Chinese company Huawey. I have no proof that it's mean, but you're warned.

It's not easy to keep it up and wear it all on your shoulders, but such progress is not acceptable in my opinion.
Good luck and I hope you're changing your position in one day.

[babsy98]

mynonpublic.com i use it in many oe-a bb files and you clone this to your close build git

 

i dont speak from e2 git, i spend more as 5 years to maintain the build git and OV copy many from oe-a work

 

you kick my work with your feet

[Persian Prince]

mynonpublic.com i use it in many oe-a bb files and you clone this to your close build git

 

i dont speak from e2 git, i spend more as 5 years to maintain the build git and OV copy many from oe-a work

 

you kick my work with your feet

First I didn't even know that URL is yours, second we never clone any git repo from that URL only fetch some tar.gz and zip drivers as a mirror.

 

I can upload all drivers ... on github (public) and make that mirror availble to all if you prefer, not hard to do.

 

If you search OE-A and PLi bb files they're fetching some git repos from us too which is ok as those are public git repos and we fetch some from them as they have public git too so I don't get your point but if you prefer I can set a new mirror for drivers on github and make it available to all and never use mynonpublic again.

 

Let me know.

 

Regads,

Persian Prince

[Abu Baniaz]

Is there an issue with this pull request?

https://github.com/O...igma2/pull/2880

[WanWizard]

No, sometimes I miss a notification, or don't have time. Merged it.

[Persian Prince]

Just to remind:

 

https://github.com/O...igma2/pull/2921

 

https://github.com/O...plugins/pull/12

 

https://github.com/O...i/tuxtxt/pull/7

 

https://github.com/O...-quadpip/pull/8

 

https://github.com/O...vicemp3/pull/18

 

https://github.com/O...lugins/pull/656

 

https://github.com/O...gimport/pull/52

 

https://github.com/O...e-core/pull/951

[littlesat]

As all images agree merged...

 

@PP

 

Does this copyright still exists? - If so I prefer it should be removed! All is already covered within the GPL license....

 

When this will not be removed it might be considered to remove it...

 

I made a lot of code for the community I never add additional stuff to put my name in the code itself.... You still can see on 'github' where it is coming from...!

echo "PEP8 double aggressive safe cleanup by Persian Prince" 
# Script by Persian Prince for https://github.com/OpenVisionE2
# You're not allowed to remove my copyright or reuse this script without putting this header.

Edited by littlesat, 16 April 2021 - 11:56.

[Persian Prince]

 

As all images agree merged...

 

@PP

 

Does this copyright still exists? - If so I prefer it should be removed! All is already covered within the GPL license....

 

When this will not be removed it might be considered to remove it...

 

I made a lot of code for the community I never add additional stuff to put my name in the code itself.... You still can see on 'github' where it is coming from...!

echo "PEP8 double aggressive safe cleanup by Persian Prince" 
# Script by Persian Prince for https://github.com/OpenVisionE2
# You're not allowed to remove my copyright or reuse this script without putting this header.

That's it in my PEP8.sh script which is not available in any of PLi repos, if you want to have it without copyright line in enigma2 repo let me know to send a new PR without that line.

 

Should I send the PR for any other branch of your enigma2? As some teams required it for python3 branches ...

 

Also thank you for merging them all, welcome to PEP8 era everyone