From now, piwigo.org extension manager can generate the archive from a Git URL (and just like SVN, with automatic replacement of version number and extension url). I'm going to notify some Git users.

xbgmsharp wrote:

Would be nice if we could have a beta channel from master latest available and production channel from a specific tag as a release.

yes but that concernes also svn and maybe also piwigo itself so... good idea but not really planed for now ^^

Lexiglot is ready to accept Github repository (we wait a few days to identify possible bugs).

--

I wrote a tutorial to explain how to migrate a plugin from piwigo.org Subversion to Github, currently reviewed by Tadjio and soon added in the Wiki (the migration is not mandatory, people will be free to stay on Subversion, and even request new repositories)

--

Things to do on the forum:

- svn:xxxx (old hotlink support) will have to redirect to github after creating the svn revisions/git hashs map
- git:xxxx redirect to github
- issue:xxxx redirect to github

no change for "bug/feature:xxxx" links, Mantis will become readonly but will be kept running for a while
OR we can migrate closed bugs to Github and redirect "bug/feature:xxxx" to Github as well

Problem
How to get the title of an issue (and optionally the message of a git commit) ?

Github has an API, but is limited 5000 requests par hour, if we want to inject issues name in the forum we will certainly have to manage a cache on our server.... or we can just drop that and display only "issue #45"

mistic100 wrote:

Problem
How to get the title of an issue (and optionally the message of a git commit) ?

Github has an API, but is limited 5000 requests par hour, if we want to inject issues name in the forum we will certainly have to manage a cache on our server.... or we can just drop that and display only "issue #45"

I can implement the cache mecanism. In case of name change on Github, we have to force refresh. Maybe we should say that cache expires after X hours or days.

but we totally lost the interest of the switch : forks, pull-requests and wide visibility on a social coding network

for me it's "keep our SVN" or "move to Github"

nicolas wrote:

plg wrote:

In the meantime, Git has arrived and Github has become "the place to be" for open source projects. Nowadays, each time I say Piwigo is using SVN I get replies such as "you're a dinosaur, switch to Github: it's a whole new world" ! I don't like the idea to lose control on Piwigo source code repository, but I like even less that Piwigo is not where it should be to attract contributors the easiest way. This is why, after discussions and several months of thinking, I strongly think we have to switch to Git and to Github for source code and for bugtracker.

To keep control on sources, I think a good idea is to install the main repository on piwigo servers and push to github commits with a hook. The official repository is for example git.piwigo.org and backup is github.com/piwigo/piwigo

This way has an another advantage : no problem of cache for internal links !

There is both samples available for open source project.
For example the kernel main GIT repository is git.kernel.org , and they do have a mirror on Github.
On the other end, a few smaller Open Source project, I know moved it all to Github.

If you want to have full control, you will need something like GitLab and mirror to github to get the social of it.
As usual it the classic fight of internal vs external.

The question is irrelevant for git :)

But in github, no you can't

--

It has never been planned to move every plugin in Piwigo organization, only the core, the main plugins (maintained by the team), Lexiglot and PEM.

Developpers move their plugins to their own Github account if they want