I'm all for discussion, though I don't promise instant gratification - ultimately, I'll choose whatever I think's best for reViSiT. As Maarten will testify, many suggestions find their way into reViSiT, but I'm not afraid to veto others (usually giving my reasons). I'm only one person - and not always in the best position to decide what would work best in all scenarios - that's when a consensus is useful. And I could easily be overlooking more elegant ways to do things, or whole new directions I've never thought of. Bottomline: there's really no risk to voicing ideas - I'll only pick the ones I think are innovative myself!

Program interchange, for example, is something I'm already looking to improve, but there are obstacles. For example, I really wanted to do drag and drop of MIDI data between reViSiT and hosts, but most hosts have internal/proprietary clipboards. Still, my experiments suggest copying/dragging from reViSiT to some hosts might be possible, just not the other way round. Interchange of tracker data itself is even harder - there is no standard format or OLE type even for dumping into other trackers. However, it is already on my list to support clipboard and dragging selections as text, MIDI, and someday audio - for dragging into explorer or other programs. Each format, however, has it's own limitations:

text: do I export the text the user sees (e.g. volume XOR panning column) or everything (volume AND panning column)? 
MIDI: how do I manage the loss of information when converting from trackers to MIDI?
audio: the process of mixing-down more-or-less makes this a one-way process, limiting the musical editing opportunities in other programs.

File formats are similar - reViSiT's extended feature set makes it less useful to export to the golden oldies (MOD, IT, XM), and no universal tracker file format has yet been developed (it's something I've been meaning to chat about with TakTik - one of Renoise's developer). Promisingly, reViSiT appears to have set a bit of a trend with its use of zipped XML files, which is similar to how Renoise now does it, and means a Renoise<>reViSiT converter should be relatively simple (though there are still notable differences in the formats). The structure of each format is extensible and fairly open, so there's no reason why someone out there can't cobble one together themselves - and getting the Module.xml file out of reViSiT's .zip file is just a drag and drop operation on Windows XP or higher.

Anyway, I think we've highlighted an area where more discussion is needed  and where its useful to know, for example: What other programs/technologies/processes are being used? What interchange do they support? What formats/methods are needed?