In order to propagate your local changes to the community you must do the following:

join #linuxmce-devel on Freenode irc, and stay connected

create a ticket in svn, remember the ticket #.

update your local database with changes from the central repository, using sqlCVS.

update the central repository with changes from your local database, using sqlCVS, you must refer to the svn ticket # you created in the description you provide.

get the sqlCVS batch numbers from irc as you submit with sqlCVS

update the svn ticket you created with the sqlCVS batch number(s) you saw in irc.

ask a dev in #linuxmce-devel to check and approve your submission.

stay in #linuxmce-devel and monitor your ticket on svn for any questions/issues which may arise.

once complete a dev will close the ticket and the template will be available to all LinuxMCE users.

Detailed:

You must join #linuxmce-devel irc channel on Freenode and stay connected while you submit your template. This will allow you do get the sqlCVS batch numbers for your device template submission for properly documenting, and requesting approval of, your device template.

Go to svn.linuxmce.org and create a new ticket indicating the name of the device template you are submitting. Record and remember the ticket number (XXXXX) as you will need to return to it later.

Go to Advanced > sqlCVS > Diff

Select the repositories and the tables you want to check for changes. If you don't know what tables were changed, you can select all of them, but be advised this will take a long time to complete.

If you only added a device template for example, you can select only dce repository, which will also select all tables in that repository. If you know what tables were changed, you can narrow the selection in order to run faster.

If you added a new manufacturer, or infrared codes, you must also include the ir repository.

After you have made your selection, click "Next".

The page will call /usr/pluto/bin/sqlCVS with the parameters selected on page, which will run an integrity check first, then display the changes in the selected repository(s) and tables (new/changed/deleted records).

Each record added/changed/deleted will have a checkbox next to it, so you will be able to select which changes you will checkin or revert.

In the description you must refer to the svn ticket (XXXXX) you created above, you should create it similar to this:

Refers to #XXXXX, device template for My New Device

Once your selection is done, you can click "Checkin" at the very bottom of the page. Be careful, "Revert" will remove the selected changes from your local system instead of submitting them.

Important note: BEFORE you click "Checkin", or "Revert", you MUST disable all popup blockers in your browser or this will not work.

Depending of the button you clicked, the operations you selected will be reverted or committed to thesqlCVS main database (central repository). This may take a while, depending on the amount of records/tables used.

Return to the ticket you created in svn and reply to it, put the sqlCVS batch number(s) you saw on the #linuxmce-devel irc channel in your reply.

Request a dev approve your sqlCVS batches.

Stay connected in #linuxmce-devel, and monitor your ticket in svn. The devs have questions or there may be issues to resolve.

Upon successful submission/approval of your device template the devs will close the ticket you created and the device will be available to all linuxmce users. Thank you for contributing!

Submitting Device Templates

The process of submitting your device template is similar to the process described above. However, there are some special considerations to take into account.

Always submit your templates one at a time. Follow the procedure for each one individually. It can be cumbersome but it prevents problems down the road.

Always submit your templates when doing a clean installation. Dont do it 6 months later, do it when installing. Taking the time to do it properly saves you and other LinuxMCE users time down the road.

With those considerations being said, the procedure is as follows.

Complete new LinuxMCE install to the point of being done with the initial setup wizard. This is neccesary because it would be difficult to login to web admin with no users.