Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 971780" data-attributes="member: 10858">We won't be allowing MPEI's (or any other installers) in official MediaPortal download portal that are modifying any core MediaPortal files:&nbsp;<ol>
<li data-xf-list-type="ol">We cannot give support on MediaPortal versions that we didn't build</li>
<li data-xf-list-type="ol">3rd party modifications can cause unstable MediaPortal - not good for the public image</li>
<li data-xf-list-type="ol">3rd party modifications can cause logical conflicts between other plugins</li>
</ol>When distributing any content (plugins, extensions, core modifications) MPEI or non-MPEI based following needs to be made sure:&nbsp;<ol>
<li data-xf-list-type="ol">MediaPortal.log (or any other relevant log(s)) is/are modified to clearly state the core components being modified so team members can identify such builds without any hasle</li>
<li data-xf-list-type="ol">Users are clearly notified that they are using a custom MP build and team is not able to give any support if any issues arise (no matter if it is core MP feature, 3rd party plugin or the modified part of core feature)</li>
</ol>What comes to getting modifications to MediaPortal itself, we are more than willing to receive development (and testing as well!) contributions. Every proposed change will be evaluated before they can be accepted (code quality, feature importance, willingness to give support for users etc.). Best way to get some new / modified functionality included in MediaPortal code base is to provide a feature that is widely wanted and is implemented in non-plugin specific way.&nbsp;ps. it would be really good to receive a list of the MPEIs (or other installers) that are in the official extension library so we can remove those to increase the quality MediaPortal users are seeing and to reduce the extra effort that is caused by some extra bug hunting.</blockquote>

[QUOTE="tourettes, post: 971780, member: 10858"] We won't be allowing MPEI's (or any other installers) in official MediaPortal download portal that are modifying any core MediaPortal files: [LIST=1] [*]We cannot give support on MediaPortal versions that we didn't build [*]3rd party modifications can cause unstable MediaPortal - not good for the public image [*]3rd party modifications can cause logical conflicts between other plugins [/LIST] When distributing any content (plugins, extensions, core modifications) MPEI or non-MPEI based following needs to be made sure: [LIST=1] [*]MediaPortal.log (or any other relevant log(s)) is/are modified to clearly state the core components being modified so team members can identify such builds without any hasle [*]Users are clearly notified that they are using a custom MP build and team is not able to give any support if any issues arise (no matter if it is core MP feature, 3rd party plugin or the modified part of core feature) [/LIST] What comes to getting modifications to MediaPortal itself, we are more than willing to receive development (and testing as well!) contributions. Every proposed change will be evaluated before they can be accepted (code quality, feature importance, willingness to give support for users etc.). Best way to get some new / modified functionality included in MediaPortal code base is to provide a feature that is widely wanted and is implemented in non-plugin specific way. ps. it would be really good to receive a list of the MPEIs (or other installers) that are in the official extension library so we can remove those to increase the quality MediaPortal users are seeing and to reduce the extra effort that is caused by some extra bug hunting. [/QUOTE]

Verification