Re: [windup-dev] Screenshot of feedback form for feedback

Hi Brad! Getting feedback from the customer is great. Currently I do not know a single customer looking forward to allowing an upload of its usage statistics. (Maybe the German/Austrians/French are a little bit too sensitive about this ...) If such a feature is included, I strongly recommend to explicitly communicate it to the user and provide an easy way to disable it. I like the feedback pop-up. What about adding a check-box to also allow the user to upload the statistics of his reports if he likes to do so? It would be also great to add 1-2 sentences explaining what is happening to the feedback and that we are grateful for it. best regards, Marc ----- Ursprüngliche Mail ----- Von: "Brad Davis" <bdavis(a)redhat.com&gt; An: "Windup-dev List" <windup-dev(a)lists.jboss.org&gt; Gesendet: Freitag, 10. Juli 2015 04:55:36 Betreff: Re: [windup-dev] Screenshot of feedback form for feedback * For the anonymous analytics, my plan was to leverage Google Analytics. The JBoss Developers Studio team (Max specicifically) already does some of this, so we could leverage his knowledge for API and regulations. Brad Davis Senior Manager, Red Hat Consulting Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com ----- Original Message ----- From: "Brad Davis" <bdavis(a)redhat.com&gt; To: "Windup-dev List" <windup-dev(a)lists.jboss.org&gt; Sent: Thursday, July 9, 2015 10:52:38 PM Subject: Re: [windup-dev] Screenshot of feedback form for feedback Definitely a great start, Jess! Where does the data push to on the backend? To Rodney's point of detailed info on a migration, we could add in Meta Information on the source code report's highlighted lines that don't have hints, and then put a button to Submit Hint. (Like when we highlight a line that we know uses Websphere classes, but we don't have information on its migration path.) In that case, we could take the Meta Information around the highlighted line, maybe the line itself, the fully resolved classes on the line, etc. One thing I considered in the past as well was adding the ability to submit anonymous analytics to assist the Windup team. That could include: what vendor classes are used in the application? If we had that information along with a SHA256 of the archive it came from, we could much better plan for things that customers are seeing in the field that we haven't yet gotten rules in place for. It would have to be an opt in type of thing due to the European regulations and requirements around "offline" functionality for high security customers. Getting more feedback and allowing people to contribute without contributing code is absolutely key. Good job Jess! Brad Davis Senior Manager, Red Hat Consulting Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com ----- Original Message ----- From: "Rodney Russ" <rruss(a)redhat.com&gt; To: "Windup-dev List" <windup-dev(a)lists.jboss.org&gt; Sent: Thursday, July 9, 2015 7:22:22 PM Subject: Re: [windup-dev] Screenshot of feedback form for feedback Would you need to know where it's used, both file/class and perhaps application? On 9 Jul 2015, at 17:16, Jess Sightler wrote: _______________________________________________ windup-dev mailing list windup-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev _______________________________________________ windup-dev mailing list windup-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/windup-dev