Differences

This shows you the differences between two versions of the page.

Link to this comparison view

dev:extensions:use_scm [2014/11/07 10:19]
plg updated for SVN + Github and details about Lexiglot
dev:extensions:use_scm [2014/11/07 10:50] (current)
mistic100
Line 1: Line 1:
 ====== Use a source code manager (SCM) ====== ====== Use a source code manager (SCM) ======
  
-It is highly recommended to use an SCM when you create and maintain a plugin. Piwigo.org extension manager and translation manager are both compatible with Subversion (SVN) and Github. Piwigo.org provides an SVN repository where your extension is welcomed.+It is highly recommended to use SCM when you create and maintain a plugin. Piwigo.org extensions manager and translation manager are both compatible with Subversion (SVN) and Github. Piwigo.org also provides an SVN repository where your extension is welcomed.
  
-=== PEM (plugins repository) ===+===== PEM (plugins repository) =====
  
-== Configure your Git or SVN repository ==+=== Configure your Git or SVN repository ===
  
-Go to [[http://piwigo.org/ext/my.php|your page]] and select the migrated plugin, then click on the SCM icon {{http://piwigo.org/ext/template/images/scm.png}}.+Go to [[http://piwigo.org/ext/my.php|your page]] and select your plugin, then click on the SCM icon {{http://piwigo.org/ext/template/images/scm.png}}.
  
 Select Git or SVN and change the URL, don't change the other fields. You must give the root URL of your repo: Select Git or SVN and change the URL, don't change the other fields. You must give the root URL of your repo:
Line 16: Line 16:
 Validate. You should see the correct Github/SVN information in the bottom block, if not, double check the form. Validate. You should see the correct Github/SVN information in the bottom block, if not, double check the form.
  
-== Release a new revision from your SCM ==+=== Release a new revision from your SCM ===
  
-Now when you release a new revision of your extension, you can let PEM do it directly from your SCM. PEM will automatically extract files, add release info, replace the version number in your source code. PEM can also detect the new languages!+When you release a new revision of your extension, you can let PEM do it directly from your SCM. PEM will automatically extract files, add release info, replace the version number in your source code. PEM can also detect the new languages!
  
-If you Git, you will be able to choose a specific branch. If you use SVN, you will be able to choose a specific SVN revision.+If you use Git, you will be able to choose a specific branch. If you use SVN, you will be able to choose a specific SVN revision.
  
-=== Lexiglot (translation platform) ===+===== Lexiglot (translation platform) =====
  
 If you want to benefit from the work of the active Piwigo translation team, your plugin can be added in [[http://piwigo.org/translate|Piwigo Translate]]. You can simply ask us on [[http://piwigo.org/contact|Contact page]] or we may directly contact you about your plugin! If you want to benefit from the work of the active Piwigo translation team, your plugin can be added in [[http://piwigo.org/translate|Piwigo Translate]]. You can simply ask us on [[http://piwigo.org/contact|Contact page]] or we may directly contact you about your plugin!
  
-If your plugin is using Piwigo.org SVN, we manage the commit access. If you're on Github, here is whad you have to do:+If your plugin is using Piwigo.org SVN, we manage the commit access. If you're on Github, here is what you have to do:
  
-== Authorize user ==+=== Authorize user ===
  
 As on SVN we use a single user to push translations to all plugins, this user is [[https://github.com/Piwigo-TranslationTeam|Piwigo-TranslationTeam]]. You must give push access to the user on your repo. As on SVN we use a single user to push translations to all plugins, this user is [[https://github.com/Piwigo-TranslationTeam|Piwigo-TranslationTeam]]. You must give push access to the user on your repo.
Line 34: Line 34:
 To do so, on your repository page, go to **Settings / Collaborators** and add **Piwigo-TranslationTeam**. To do so, on your repository page, go to **Settings / Collaborators** and add **Piwigo-TranslationTeam**.
  
-== Notify us ==+=== Notify us ===
  
-We need to configure Lexiglot to use your Github repository. Contact one of the team members on the forum or send an email to **translate-github [at] piwigo [dotorg** to tell us what is the new location of your plugin.+We need to configure Lexiglot to use your Github repository. Contact us on [[http://piwigo.org/contact|Contact page]] to tell us what is the location of your plugin.
  
-By default all commits are pushed to the master branch, you can tell us if you want translations to be pushed to any other branch (the branch must already exists).+By default all commits are pushed to the ''master'' branch, you can tell us if you want translations to be pushed to any other branch (the branch must already exists).
  
 We decided to not use pull-requests because it's a bit more complicated to implement and we don't want to spam you with a bunch of PR every week (the translation team is very active !). We decided to not use pull-requests because it's a bit more complicated to implement and we don't want to spam you with a bunch of PR every week (the translation team is very active !).
 
Back to top
dev/extensions/use_scm.txt · Last modified: 2014/11/07 10:50 by mistic100
 
 
github twitter newsletter Donate Piwigo.org © 2002-2020 · Contact