Allow rebranding / unbranding of Liferay sync tool.
One of the key advantages is "organizational ownership," not in the legal sense but in a user adoption sense. Many users do not know that "their" portal is Liferay, it is simple theirs. Adding a proprietary plugin with references to Liferay will disrupt the cohesive brand of the portal. It will also make supporting it a nightmare.
When a user has a problem with dropbox syncing a msft file, they call/email dropbox not msft. Users will be confused that for everything in the portal they contact "xyz help" but for sync they contact this "Liferay company." because it is in the About page and other references. If we could modify content areas in sync we could also add custom workflow directions (Sync this, not this...) for each org and have support go back to whatever the company uses now. It would allow "themes" an item I saw elsewhere in JIRA.
I do not mind having to pay for EE to sync to extra sites, I completely get that. You guys probably spent lots of time and $$ putting it together. ...But PLEASE do not not at the very least lockdown the plugins from customization.
I love you guys =)