Support for storing in the official svn repository

[tokkonopapa]

I think this topic is a little beyond the scope of this project. But everyone who wants to store his or her plugin in the official svn repository will face the issue how to check in svn repo. So in the future, I expect this boilerplate to support to bridge between github repo and svn repo.

It's not a new topic around github and svn repo. Here are some posts using git-svn:

• Developing on WordPress using Git
• Revisiting Git, Github, and the wordpress.org plugin repository
• Publishing WordPress Plug-Ins With Git
• Using Git (and GitHub) with Subversion Mirroring for WordPress Plugin Development

Sometimes, those methods will cause some conflicts which are completely unnecessary things.

Here are differnt ways:

• Deploy a wordress plugin from within GIT to Wordpress.org's SVN repository
• Github to WordPress Plugin Directory Deployment Script, Git-Flow Version

And discussions in the official blog.

• Create Git Repositories for Plugins and Themes

Any ideas?

[tommcfarlin]

Thanks for bringing this up.

I don't know if a future version of the Boilerplate will support this or not primarily because we're trying to keep the Boilerplate targeted at those who need help getting started with WordPress plugin development.

The Git-To-Svn syncing is something that more advanced users can do.

In the next couple of weeks, I'm working with a small team of contributors to help reorganize and plan 2.7.0 of the Boilerplate, so we can still make sure this a topic of conversation.

[tokkonopapa]

Since this project is very active, I can't stop to hope wisdom of many experts about this topic. On the other hand, I can understand the basic role of Boilerplate. I've watched this repo since the very begining, and I think this project gradually begin to involve some kind of framework of WordPress plugin development. But indeed, there may be several ways of syncing git-to-svn to fit the individual project. So I can agree that this project should always focus at the plugin development itself.

Thank you for your thinking.