Hi Piwigo community,
We have recently moved the Subversion (SVN) repository to piwigo.org directly (I mean that we manage the Subversion repository now).
edit by plg, on June 27th, 2009: I have added [wiki] Host your extension on piwigo.org Subversion repository with updated information concerning this topic. Some information in the first post are now obsolete as we have made things much simpler for extension contributors
The extension manager http://piwigo.org/ext let you publish your extensions, but you still have to manage the source code by yourself. Recently, P@t has added the "multiple author" feature for a single extension. If you want several developers to work on the same extension, you need a code manager like Subversion. Even if you work alone on your extension, Subversion helps you to work with cleaner methods.
I propose you to host your extension code on the same repository, in the "extensions" directory http://piwigo.org/dev/browser/extensions
The advantages are:
* your coding activity is more visible (that's good for you as a developer, and for Piwigo as a project because it generates technical
activity)
* you can work in team
* you work in a cleaner way
If you are interested, please send me an email (use the forum email form) with the following informations:
* your htpasswd string generated on http://aspirine.org/htpasswd_en.html (keep the same username as the one you use in the extension manager and forum) choose the "MD5" algorithm.
* the technical name of your extensions. For plugins, use the same name as the directory in "piwigo/plugins", for templates the same name as in "piwigo/template" directory, etc.
I'll create a directory for each of your extension. Only you will have write access on it (and Piwigo core team, which has write access
everywhere in the repository). If you want several developers to work on the same extension, tell me so and I'll configure it the way you ask.
Bye
Offline
Excellent! Perfect! I will push my plugins code there.
Offline
very good idea !!
Offline
I can't log in the "extensions" directory :-(
Here is the message when i do a click on "login" link :
"Authentication information not available. Please refer to the installation documentation."
Offline
Eric wrote:
I can't log in the "extensions" directory :-(
What do you exactely mean? (you log into Subversion repository, not into a specific directory)
Eric wrote:
Here is the message when i do a click on "login" link :
Which "login" link?
[wiki] Install and use SubVersion on Windows XP/Vista
Offline
Sorry, i've mistaken. :-/
Of course with my TortoiseSVN, it works much better... ;-)
Offline
VDigital wrote:
Excellent! Perfect! I will push my plugins code there.
Charlies' content with strange difficulties to add some php modules from getId3.
and Whois Online with no difficulties at all.
What shall I do for STC (Swift Theme Creator available in trunk)? Could / Would you transfer it?
Offline
It's perhaps preferable to sub-divise extensions on different directories (plugins, ) like categories of PEM.
So, with that it's easy to check-out only all the plugins on trunk work area.
svn co http://piwigo.org/svn/extensions/plugins trunk\plugins
And also for themes, template...
Actually, for my plugins and other, I launch individually command lines.
svn co http://piwigo.org/svn/extensions/wsstats trunk\plugins\wsstats
I can do
svn co http://piwigo.org/svn/extensionstrunk\plugins
but themes, plugins, tools will go to plugins directories.
Offline
Splitting Plugins, themes, ...
+1
Offline
Is it possible to have branches for plugins in svn ?
Offline
rvelices wrote:
Is it possible to have branches for plugins in svn ?
You can create branches locally to each extension. I'm quite sure it doesn't answer your question, so please give me an example of what you would like to do.
Offline
plg wrote:
rvelices wrote:
Is it possible to have branches for plugins in svn ?
You can create branches locally to each extension. I'm quite sure it doesn't answer your question, so please give me an example of what you would like to do.
Just have 2 versions of my extension. One that works with current piwigo trunk and one with the current piwigo release branch.
So for example I suppose thqt the working solution would be
http://piwigo.org/svn/extensions/rv_sitemap/trunk
http://piwigo.org/svn/extensions/rv_sit … anches/2.0
Offline
rvelices wrote:
So for example I suppose thqt the working solution would be
http://piwigo.org/svn/extensions/rv_sitemap/trunk
http://piwigo.org/svn/extensions/rv_sit … anches/2.0
(sorry for the long waiting answer).
Yes, absolutely rvelices. I would also do it this way.
Offline
One svn question - can I checkout something without the creation of .svn directories? It is for posting on the extension manager.
Offline
rvelices wrote:
One svn question - can I checkout something without the creation of .svn directories? It is for posting on the extension manager.
Instead of performing a "checkout", you need to perform an "export". Is this action available with TortoiseSVN?
Personally I use SVK above SVN, and I have no ".svn" metadata directories in my checkouts (and I really appreciate that). But running SVK on Windows doesn't seem to be "the easy way to do it".
Offline