[windup-dev] Screenshot of feedback form for feedback
Brad Davis
bdavis at redhat.com
Sat Jul 11 10:07:13 EDT 2015
I will run with taking a first crack at the Analytics piece. WINDUP-690
Thanks,
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Jess Sightler" <jsightle at redhat.com>
To: windup-dev at lists.jboss.org
Sent: Friday, July 10, 2015 6:47:25 PM
Subject: Re: [windup-dev] Screenshot of feedback form for feedback
Yes, I think we can pull in the application name and file path
information by default.
I agree that it would be nice to put in a clickable link for feedback on
hints. I think we can do this regardless of whether the hint is a
fallback hint or not, as this could be used for general.
The backend is currently still being decided and designed. This is just
the frontend component.
Should we go ahead with development with the feedback from Rodney and
Brad incorporated?
Thanks,
Jess
On 07/09/2015 10:52 PM, Brad Davis wrote:
> 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 at redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Rodney Russ" <rruss at redhat.com>
> To: "Windup-dev List" <windup-dev at lists.jboss.org>
> 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:
>
>> Attached... let me know what you think, please.
>>
>> [Screenshot from 2015-07-09 19-15-37.png]
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
--
Calendar Free/Busy: https://www.google.com/calendar/embed?src=jsightle%40redhat.com&ctz=America/New_York
_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
More information about the windup-dev
mailing list