New organization of the VDR Plugins on github

  • Hi,


    Some members of this VDR forum are trying to set up a new organization for the vdr-plugins in the hope that over time, people will have a central location they can turn to, to get information about the various vdr-plugins without having to hunt for it on various pages and sites on the internet.


    The project started few days ago with creating a mirror of various vdr plugins.


    You can learn more about this new organization on the projects page .


    Here are the vdr plugins of the project that have already been mirrored.


    Contributors, especially the owners of mirrored plugins that want to get more privileges or want the ownership of their plugins should file a request here:
    https://github.com/vdr-project…projects.github.io/issues


    Ludi

  • We already have projects.vdr-developer.org so what would be the point of another archive? Just a mirror?

    As far as I could understand, it was among others to lower the bar for new contributions as github has more features and is easier to use. Moreover, I think that the hope is also to increase the international distribution of the vdr.


    You can find more information on the following page.
    https://vdr-projects.github.io/


    Please, be aware that the new organization has just started and things are still in movement.

  • As far as I could understand, it was among others to lower the bar for new contributions as github has more features and is easier to use.


    IMO, you're just raising the bar by introducing some extra layers. There haven't been any problems forking projects from vdr-developer.org into github beforehand and I've been doing that for ages. How should one publish changes to the upstream, if they are forking from your mirrors? Are you really going to act as a man in the middle by reviewing pull request and then submitting the same changes forward to the original master? Have you really though the process through as it seems to me, that you're going to kill the VDR community by making the plugin scene just messier?


    BR,
    Rofa

  • I don't belong to the people organizing this new infrastructure. There is a discussion going on about it in this german thread . One of the topics is also how to handle packages, whose developer has not touched his package for a long time.


    But as far as I could understand from the german thread, one of the points in the medium term is also to have a place where developers can turn to in order to find patches available for their packages instead of hunting them down in threads of the VDR forum and more generally on the internet.


    In fact, my aim by creating this thread was not to explain the ins and outs of the new infrastructure; I simply don't have the knowledge to do it correctly. I opened this thread for the non-german speaker of the forum to let them know about this new development.


    Maybe that somebody with more knowledge can reply to specific questions like those from rofafor. On the other hand, I suppose that the english github page about the project will also get updated when more things have been settled.


    Cheers,


    Ludi

  • Maybe that somebody with more knowledge can reply to specific questions like those from rofafor.


    I'll try.


    How should one publish changes to the upstream, if they are forking from your mirrors?

    Well actually it's not really planned to publish back upstream. We'd like the remaining developers to join us.


    Are you really going to act as a man in the middle by reviewing pull request and then submitting the same changes forward to the original master?

    Pull requests could be merged into a newly created "community" branch. But that's just one suggestion we're discussing right now.


    Have you really though the process through as it seems to me, that you're going to kill the VDR community by making the plugin scene just messier?

    Well, we try to do the exact opposite. We want to give more control to the community without taking too much control from the original developer. It's just about finding the right balance.

  • Hello,


    As a 'newbee' with VDR and with the limitation of the language (French or +/- English), it's difficult to play with VDR. GoogleTranslate could help sometimes, but some other ... it's better to forget it. If something could improve the internationalization of VDR, I think it is a good thing. I know that VDR is available from many years in Debian, but there is not enough documentation in French or English to be autonomous and ask many questions in a forum, only because I need the translation is an obstacle.


    About the internationalization, It gave me the link on MiniDVBLinux (https://www.minidvblinux.de/) because I want use a Raspberry Pi3 with a Sundtek MediaPro III tuner. All interfaces are in German, it's normal but I'm not able to test this solution :-(


    I don't know if the technical solution is good or not, but I'm sure that to improve the visibility and coherence of the VDR project is a good thing for everyone, primarily for me ;-)

  • If something could improve the internationalization of VDR, I think it is a good thing. I know that VDR is available from many years in Debian, but there is not enough documentation in French or English to be autonomous and ask many questions in a forum, only because I need the translation is an obstacle.

    This might be somewhat hard to fix - being able to read german does not seem to stop anyone to ask questions in this forum, which might have already been answered somewhere...


    The VDR itself is reasonably well documented and offers translations for several languages:

    https://projects.vdr-developer.org/git/vdr.git/tree/INSTALL

    https://projects.vdr-developer.org/git/vdr.git/tree/MANUAL

    man 1 vdr

    man 5 vdr


    On top of that you need an output plugin (like rpihddevice) and a source for your channels.conf - you could use an extra program like w_scan, an online source like the channelpedia or the wirbelscan vdr plugin.


    Then there are distribution specific details - patches for the vdr source, extra configuration files - for Debian you should read the README.Debian (which is also part of the vdr package, using the local version is the better option to prevent confusion based on version differences).


    Up to this point nearly everything is available in english - documentation, C(++) code, scripts and configuration files.


    The hard part is putting the pieces together (and sadly the remains of the old french version of the vdr wiki are only available using the internet archive: https://web.archive.org/web/20…80/wiki/index.php/Accueil )


    If you are using a VDR distribution like MLD, you get a lot of additional scripts, configuration mechanisms and User Interfaces which might be not internationalized, but the sources are available and tend to use more english than the resulting distribution ;)

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • :D OK, there is some documentations !

    Thank you to share this, seriously. After look at the Wiki page during few minutes, I found the links "In anderen Sprachen" ... I am ashamed of not be able to find this before, and it's not the first time that I go on this page ;(


    Thanks for the others links and the advice for MLD. As you wrote it, it's not easy to put all things together.