Register plugin in official plugin registry of Wordpress.org

[luflow]

Hi everyone!

I just wanted to suggest that the plugin should be registered on wordpress.org.

That would also lead to free access to the translation management in https://translate.wordpress.org/ which should be used for translations instead of shipping them in the repository.

AND it would create higher visibility for new woocommerce shop owners that want / consider to use BSPAYONE as PSP.

[fjbender]

Thanks for the suggestion! Currently, we haven't considered this option since Wordpress' Plugin Repo is on a SVN basis, which will create a headache of it's own. Do you have any best-practice guides at hand on how to maintain Git and the SVN-Plugin-Repo at the same time?

[luflow]

Maybe something like https://github.com/rayrutjes/wp-plugin-git-svn-sync ?

But I also asked in the woocommerce and wordpress slack about this problem - maybe there is even a better solution for that.

[luflow]

@fjbender just got an answer in the woocommerce Slack. The best thing to use is: https://github.com/mikejolley/github-to-wordpress-deploy-script

[luflow]

@fjbender Other inspirations from other wordpress developers:

You can check my workflow at https://github.com/ignicoapp/ignico-wordpress (edited) Most important are build and deploy:wp command from build.xml file and bin/sync.sh file.

thanking Piotr Kierzniewski for that suggestion

I've built/implement something similar, using TravisCI :slightly_smiling_face: Here it is, if you want to see it: https://github.com/cristianraiber/travis-deployment && https://github.com/MachoThemes/simple-author-box/blob/master/.travis.yml You're going to want to take a look at L59-61 in travis.yml and make sure you encode your SVN repo username/password

thanking cristianraiber for that suggestion

[fjbender]

Thanks for asking in the apropriate channels, @luflow! We'd probably go with Christian's approach. However, due to vacations it's going to take a couple of weeks.

[luflow]

Yeah christians approach is great but has some implications to think about like:

• Does every merge into the master create a new version? Maybe travis has some posibilities to only fire a new deployment when a version tag is added manually by you or something like that...
• Is it good to have a automatically working remote system to trigger updates (that in most cases will lead to auto updates of all installed plugins in the world because of the wordpress auto update feature)

So maybe a non-automated version deployment like mentioned in the second comment is the best way to go.

The best thing to use is: https://github.com/mikejolley/github-to-wordpress-deploy-script

But at the end its totally up to you ;)

[fjbender]

My plan was to make use of Travis' "Deploy on tagged commit only" feature (we're doing this for our Shopware repository, for instance).

Mike's shell script looks great for an initial release, too :)

[luflow]

@fjbender Awesome! sounds like a plan :)

[fjbender]

Added an initial version at https://wordpress.org/plugins/bs-payone-woocommerce/ manually.

Travis CI Integration will follow.

[hreinberger]

as @fjbender wrote, we're in the wordpress store already and already tested a Travis config. We'll implement this in the coming days (hopefully), so that every tagged release gets pushed to wordpress.org automatically. Closing this for now.