[news.eclipse.technology.epf] Routing Feedback

["Rob Robason" <rob.robason@xxxxxxxxxxxxx>]

I'm starting to think about how we'll handle improvements and other feedback 
we get from users of our published process. The Feedback button would be the 
natural way for the user to make requests. I've started experimenting with 
providing a "mailto:"; URL for feedback, which produces a message with a very 
long URL subject line. Connecting that URL to its originating plugin is 
problematic.

It seems applying some sort of hidden fingerprint to a webpage pointing to 
its source in the method library, then passing that to the Feedback URL as a 
parameter would be handy.

What's the recommended practice for managing feedback?

-- 
Rob Robason
Software Process Manager
Wind River Systems