Developer Collaboration

[Carnage]

i'm taking inspiration from http://divmod.org/trac/wiki/DivmodCombinator a python tool for use with svn, it made my life so much easier with developing python modules I wanted something similar for vbulletin.

I'm probably going to mock something up in the next couple of hours, so I may have more details then.

--------------- Added [DATE]1255727698[/DATE] at [TIME]1255727698[/TIME] ---------------

Been playing around, found that there are very few (1) hooks in the plugins page which wasn't really of much use.

Copied some of the export code into a file and modfied it to export to the file system putting each plugin hook into its own file in ./products/plugins/hookname.php did the same for template and install code.

The idea is to use http://www.php.net/manual/en/book.svn.php the pecl svn module to create and update an svn repo for the code. Also there will need to be something to take it the other way and import from the file system into vbulletin.

Essentially a php file that provide the following functions:

• Export product to ./products/ directory (currently only templates, plugins and install code done)
• Manage svn repository pre product. (create, commit, rollback,checkout etc)
• Import from file system to vbulletin.
• Add a field in products table for additional files which will be copied to the products directory and included in import/export operations.
• Creates a Full product export; includeing additional files when a product is exported from vbulletin.
• Syncs product version and svn revision number (using branches or tags or something)

--------------- Added [DATE]1255733636[/DATE] at [TIME]1255733636[/TIME] ---------------

brainwave: If designed right, it wouldn't matter which backend version control system was used. The vbversion product could have plugins to use either svn git or cvs depending on personal preferance...