Reply to thread

Message

Agree with Piranha. You've done some great work dukus, but it needs more exposure. Further, I think both the website hosting the plugins and the plugin installer itself need to be integrated into MP better.

- Require (force) plugin developers adding plugins to the official MP site to make an extension package available (as well as a standard zip if desired).

This would mean any plugin added to the MP site is automatically available for install/update via the extension installer and the onus is on the plugin developers, not yourself to keep plugins up-to-date in extension package installer format.

- Liase with the MP developers to integrate the extension installer into the MP Configuration app. If it were integrated into the config app, it'd get a whole lot more exposure in an instant and would probably get developers more interested in releasing plugins in the package format right from the start.

See http://addons.mozilla.org/ for an example of the model that I think should be adopted.

Basically for an extension installer to work, the community needs to move from the adhoc plugin release system as it stands today, to a more structured release system with a standard package download that the extension installer can use from within MP Config.

<blockquote data-quote="scythelt" data-source="post: 160880" data-attributes="member: 27879">Agree with Piranha. You've done some great work dukus, but it needs more exposure. Further, I think both the website hosting the plugins and the plugin installer itself need to be integrated into MP better.- Require (force) plugin developers adding plugins to the official MP site to make an extension package available (as well as a standard zip if desired). This would mean any plugin added to the MP site is automatically available for install/update via the extension installer and the onus is on the plugin developers, not yourself to keep plugins up-to-date in extension package installer format.- Liase with the MP developers to integrate the extension installer into the MP Configuration app. If it were integrated into the config app, it'd get a whole lot more exposure in an instant and would probably get developers more interested in releasing plugins in the package format right from the start.See <a href="http://addons.mozilla.org/" target="_blank">http://addons.mozilla.org/</a> for an example of the model that I think should be adopted. Basically for an extension installer to work, the community needs to move from the adhoc plugin release system as it stands today, to a more structured release system with a standard package download that the extension installer can use from within MP Config.</blockquote>

[QUOTE="scythelt, post: 160880, member: 27879"] Agree with Piranha. You've done some great work dukus, but it needs more exposure. Further, I think both the website hosting the plugins and the plugin installer itself need to be integrated into MP better. - Require (force) plugin developers adding plugins to the official MP site to make an extension package available (as well as a standard zip if desired). This would mean any plugin added to the MP site is automatically available for install/update via the extension installer and the onus is on the plugin developers, not yourself to keep plugins up-to-date in extension package installer format. - Liase with the MP developers to integrate the extension installer into the MP Configuration app. If it were integrated into the config app, it'd get a whole lot more exposure in an instant and would probably get developers more interested in releasing plugins in the package format right from the start. See [url]http://addons.mozilla.org/[/url] for an example of the model that I think should be adopted. Basically for an extension installer to work, the community needs to move from the adhoc plugin release system as it stands today, to a more structured release system with a standard package download that the extension installer can use from within MP Config. [/QUOTE]