Outdated version of the documentation. Find the latest one here.


Once your plugin is ready and you think the plugin could be helpful for some people, do not hesitate to upload it to 公式のpythonプラグインリポジトリ. On that page you can find also packaging guidelines about how to prepare the plugin to work well with the plugin installer. Or in case you would like to set up your own plugin repository, create a simple XML file that will list the plugins and their metadata, for examples see other plugin repositories.


*公式の*pythonプラグインリポジトリは `<http://plugins.qgis.org/>`_で見つけることができます。

公式のリポジトリを使用するため、あなたは`OSGEO web portal <http://www.osgeo.org/osgeo_userid/>`_からOSGEO IDを入手しないといけません。



  • すべての登録ユーザは、新しいプラグインを追加することができます

  • *スタッフ*は全てのプラグインバージョンの承認と非承認を行うことができます。

  • users which have the special permission plugins.can_approve get the versions they upload automatically approved
  • users which have the special permission plugins.can_approve can approve versions uploaded by others as long as they are in the list of the plugin owners
  • a particular plugin can be deleted and edited only by staff users and plugin owners
  • if a user without plugins.can_approve permission uploads a new version, the plugin version is automatically unapproved.

Trust management

Staff members can grant trust to selected plugin creators setting plugins.can_approve permission through the front-end application.

The plugin details view offers direct links to grant trust to the plugin creator or the plugin owners.


Plugin’s metadata are automatically imported and validated from the compressed package when the plugin is uploaded.

Here are some validation rules that you should aware of when you want to upload a plugin on the official repository:

  1. the name of the main folder containing your plugin must contain only contains ASCII characters (A-Z and a-z), digits and the characters underscore (_) and minus (-), also it cannot start with a digit
  2. metadata.txt is required
  3. all required metadata listed in metadata table must be present
  4. the version metadata field must be unique