6:22 p.m.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
9:52 p.m.
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>
To: "Windup-dev List" <windup-dev(a)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(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
9:55 p.m.
* 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>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
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>
To: "Windup-dev List" <windup-dev(a)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(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
12:20 a.m.
On 9 Jul 2015, at 20:55, Brad Davis wrote:
* 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.
I know from a legal perspective, we needed to ensure that the default
was opt-out and the user would have to explicitly opt-in to allow
feedback. There are also some limitations as well. It would be good to
start a conversation with Max once analytics begins to bubble to the top
of the backlog.
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>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
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>
To: "Windup-dev List" <windup-dev(a)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(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
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
1:50 a.m.
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>
An: "Windup-dev List" <windup-dev(a)lists.jboss.org>
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>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
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>
To: "Windup-dev List" <windup-dev(a)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(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
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
7:48 a.m.
Hey Marc;
I know the services team in the states would be easily open to running the analytics
during our engagements. All of our customers have an NDA in place with Red Hat so as long
as we aren't exposing those analytics or providing any identifying information, not
sure why they'd care. They upload archives to the support portal and logs all the
time.
I'd imagine with analytics, we could just add a flag that can be set during execution
so that it's opt in. It's invaluable info to the cause and planning.
Brad
Sent from my iPhone
On Jul 10, 2015, at 2:50 AM, Marc Zottner <mzottner(a)redhat.com>
wrote:
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
Von: "Brad Davis" <bdavis(a)redhat.com>
An: "Windup-dev List" <windup-dev(a)lists.jboss.org>
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>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
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>
To: "Windup-dev List" <windup-dev(a)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(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
_______________________________________________
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
5:47 p.m.
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(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Rodney Russ" <rruss(a)redhat.com>
To: "Windup-dev List" <windup-dev(a)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(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
_______________________________________________
windup-dev mailing list
windup-dev(a)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=A...
9:07 a.m.
I will run with taking a first crack at the Analytics piece. WINDUP-690
Thanks,
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Jess Sightler" <jsightle(a)redhat.com>
To: windup-dev(a)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(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Rodney Russ" <rruss(a)redhat.com>
To: "Windup-dev List" <windup-dev(a)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(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
_______________________________________________
windup-dev mailing list
windup-dev(a)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=A...
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
3456
days inactive
3458
days old
8 comments
4 participants
participants (4)
-
Brad Davis -
Jess Sightler -
Marc Zottner -
Rodney Russ