83 replies to this topic

[Rob van der Does]

And to elaborate a bit: on https://github.com/o...ultiQuickButton there is a well maintained version of MQB that is usefull for many, many brands; far more boxes then PLi will ever support. The only thing that needs to be done is to remove a few OE-a specific functions, that are not available in PLi.

So how difficult can it be to build form there, with a small patch over it to do that job?

Make that patch once, and enjoy forever!

[WanWizard]

I think that is pretty simple.

 

For generic fixes, send a pull request upstream. For specific code (supporting the reason the fork was made in the first place), that's a bit pointless, it won't be accepted upstream.

[delagroov]

Appearently not..

Specific fix has been done on request of Littlesat..but Pli does not use it.

Keep in mind  MQB version in feed is not usable for 8 months..and I think users are important

What worries even more is that i porposed to make you contrubutors in my MQB fok, so you can add your own Pli stuff, but appearently pli is not interst in getting MQB workin.

Edited by delagroov, 18 August 2013 - 17:56.

[delagroov]

What worries even more is that i proposed to make you contributors in my MQB fork, so you can add your own Pli stuff and do a pull request yourself, but apparently pli is not interested in getting MQB workin.

Edited by delagroov, 18 August 2013 - 17:59.

[littlesat]

So there must be commits done on a fork of a fork of a fork?...
Indeed i already told you i'm not a mqb user... And probable the not working dmm version nobody does use...
For what are you really using mqb? I suggest it is better to include something in e2...
But as always someone needs to put time in it.

[delagroov]

I did not set e2openplugins up...

So one needs to setup a fork, to push back commits by pull request in the fork.
 

So I did put time in it on your request of 8 months ago..and still no workin MQB for users..
And you even wont participate..so why complaining and ask 8 mnths ago," who commits back support of  hbbtv to e2openplugins/MQB-vu"

Where you waisting my time...???

You have the complete right not to support MQB on Pli, but you dont have the right to ask others to commit and then not usin it and waisting there time


 

 

 

Edited by delagroov, 18 August 2013 - 18:46.

[littlesat]

What are you arguing... Your commit is merged 2 days ago..
https://github.com/E.../commits/master
Can we remove the "the for vu" limitation? Because that was the reason why it was not that way in our feeds as far i understood.

Edited by littlesat, 18 August 2013 - 18:55.

[delagroov]

I am not arguing on the merge, but replying on your reply...but that speaks for itself when reading a thread in the right context

 

Are you waisting other peoples time???

Edited by delagroov, 18 August 2013 - 19:00.

[Robinson]

As a layman, I don't know much about github, sourceforge etc.

I don't, however, approve of the arguing and I don't like it when various E2 communities offend each other and so on.

As a normal user, I would like to see various plugins being adjusted to work on various images and various receivers. And the problem is not only with MQB. It is also about TranscodingSetup and possibly others.

Let's hope that some time soon all those arguments will be over. Or am I just a dreamer?

[Erik Slagter]

Are you waisting other peoples time???

About wasting time...

 

Every party here has different interest here. Every party will have to do some work. By forking a repo instead of pushing the changes to the original repo, it gets easier for the one wanting to have changes in the plugin and it gets more work for the one including the plugin (i.e. OpenPLi).

 

So, who's wasting who's time?

 

Many users (including you) don't seem to understand we have a responsibility for a complete image, not just the one nice looking plugin. Adding a new plugin is futile if it appears to break the whole image (now, or later). Also one plugin that requires extra maintenance is managable. But it's never one plugin. So that's why we often reject "specials".

[delagroov]

Its really becoming a joke, Erik Slagter,
 

 

I did not set e2openplugins up...

So one needs to setup a fork, to push back commits by pull request in the fork.
 

 

So you as Organization member have the total access and other can't push to it directly without forking it first.
Hence i forked it to supply you the needed patch

 

Funny that i have to explain to you how e2openplugins works....

But this is the last i write, because you indeed waisting time.

 

[WanWizard]

Everyone who is seriously motivated to work on E2OpenPlugins and is willing to obey the one simple rule (which is that these plugins are generic and should work on ALL platforms) can get access to a repo.

 

And a lot of people already have: https://github.com/E...ns?tab=members.

 

I can't recall seeing an access request from you (or anyone else in relation to this plugin), and I still haven't seen a reply from you on Erik's question to the VU+ specials in that fork (which violate that one simple rule), indicating that you don't really care about truly generic and open.

 

So what is it exactly that you complain about?

[Rob van der Does]

Well, maybe it would be handy and nice to answer http://openpli.org/f...ndpost&p=367239 elaborated in http://openpli.org/f...dpost&p=367242.

[delagroov]

Everyone who is seriously motivated to work on E2OpenPlugins and is willing to obey the one simple rule (which is that these plugins are generic and should work on ALL platforms) can get access to a repo.

 

And a lot of people already have: https://github.com/E...ns?tab=members.

 

I can't recall seeing an access request from you (or anyone else in relation to this plugin), and I still haven't seen a reply from you on Erik's question to the VU+ specials in that fork (which violate that one simple rule), indicating that you don't really care about truly generic and open.

 

So what is it exactly that you complain about?

Why should I

 

Littesat asked to do the way i did and thats enough for this small tweak..

http://openpli.org/f...on/#entry366755


So that what i did and all the rest of discussion is pointless..

You asked for it, i did it and plnick merged...

So now its there, nothing more to say about it..

 

So its up to you what you do with it.....and if it's still useless i can t help it.
 

Edited by delagroov, 19 August 2013 - 17:49.

[delagroov]

Everyone who is seriously motivated to work on E2OpenPlugins and is willing to obey the one simple rule (which is that these plugins are generic and should work on ALL platforms) can get access to a repo.

 

And a lot of people already have: https://github.com/E...ns?tab=members.

 

I can't recall seeing an access request from you (or anyone else in relation to this plugin), and I still haven't seen a reply from you on Erik's question to the VU+ specials in that fork (which violate that one simple rule), indicating that you don't really care about truly generic and open.

 

So what is it exactly that you complain about?

In addition to the rule.

Think you need to ask yourself, why you have  e2openplugin-MultiQuickButton-vu at all on e2openplugins and you can t make me responsable for that. Think you need to discuss this then with plnick, which was accepted up then.
I only did  a pull request on an existing repository on e2openplugins, and this on reqeust from a pli core member
 

[WanWizard]

I don't know who created that repo (could be one of 7 that have that right at the moment), if it was up to be it would be gone today. But it's there, so I can't.

 

If you want access to that, discuss it with plnick (who seems to maintain it), ask him to send me a PM, and I'll arrange it. As I said, all one has to do is ask.

[delagroov]

But thats not needed..for just one small minor tweak.

Think you need to consider and ask plnick yourself as your organizationmember, why you have it on e2openplugins and accepted it, according to your rule.

 

It's obvious you dont want to use MQB (which is fine), so it really makes no sense to have it then or an outdated version fronm IHAD on the feed.







 

[Rob van der Does]

Well, maybe it would be handy and nice to answer http://openpli.org/f...ndpost&p=367239 elaborated in http://openpli.org/f...dpost&p=367242.

Not having had a single answer/advise to a repeatedly asked simple question, I think I have a simple advise for PLi:
 

As the OE-A version of MQB suits thirteen different image-build teams (all together supporting approx 50 different boxes (maybe more; I didn't count them), it seems the most logical to use that version for the PLi feeds as well.

Once a simple task has been done (building for the PLi feeds from there) all the PLi users can enjoy a good working plugin, while the PLi-team doesn't need to maintain anything at all.

[gjstroom]

enigma2-plugin-extensions-multiquickbutton-vu is now removed from github.com/E2OpenPlugins.

I think it's also the cause almost all todays builds failed.

https://github.com/E...dee6ed6006cb136

 

delagroov commented on afbfae2

That's a clear statement..

Far much better then Pli accusing me, just because i did a pull request to your repository.

Thanks.

Edited by gjstroom, 21 August 2013 - 18:47.

[delagroov]

Before anybody misinterpret above context, I  think it should be more like this
 

Plnick committed:

remove recipe for multiquickbutton plugin, which breaks e2openplugin …

…rules ...

https://github.com/E...dee6ed6006cb136

 

 

delagroov commented on afbfae2

That's a clear statement..

Far much better then Pli accusing me, just because i did a pull request to your repository.

Thanks.

Edited by delagroov, 21 August 2013 - 20:33.