Re: [Dev] GSoc 2016-Proposal 16

[nathieshamaddage]

Hi Awanthika and Jasintha,


I have added the additional feature as optional, in my proposal as you have 
suggested.

I submitted the draft proposal after filling up the implementation part of the 
document. And I also modified the architecture diagram a bit.

If you can, please have a look at the draft proposal and let me know whether 
any changes need to be done for it, or if I have missed anything. 


Thanks and regards


Nathiesha






Sent from Windows Mail





From: Awanthika Senarath
Sent: ‎Thursday‎, ‎March‎ ‎24‎, ‎2016 ‎8‎:‎04‎ ‎AM
To: Nathiesha Maddage
Cc: Jasintha Dasanayake, dev@wso2.org





Hi Nathiesha,



All you proposed ideas seems good. 




You can add all the ideas you have as optional features in your proposal. We 
can evaluate the applicability once the proposal is submitted.




As for the user side errors network availability and resource blocking it may 
not be required to be reported. 







Regards

Awanthika














Awanthika Senarath
Software Engineer, WSO2 Inc.

Mobile: +94717681791




On Tue, Mar 22, 2016 at 9:22 AM, Awanthika Senarath  wrote:


Hello Nathiesha,



This seems good. Let us know once you have completed the document. I will get 
back to you on the un-answered questions in your previous emails ASAP.




Regards

Awanthika





Awanthika Senarath
Software Engineer, WSO2 Inc.

Mobile: +94717681791






On Mon, Mar 21, 2016 at 11:20 PM,  wrote:




Hi all,




I will add the additional features to the project as you have suggested

I tried creating a draft high level architecture diagram for the project. And I 
also started with creating the draft proposal. The link is given below.




https://docs.google.com/document/d/12JqluYhlcWAN8kqxfTcwVrH_ylKaf3sNvevodOxwRho/edit?usp=sharing




The draft architecture diagram and its components are briefly described their. 
I didn't completed the implementation part and other latter parts completely 
yet. 




Regarding the architecture diagram, please let me know if that fits the purpose 
or any changes need to be done? For some use cases, I have denoted in the 
diagram as separate modules for easy visualization and scalability purposes. 
But certain modules can be integrated together into a single module if needed, 
during implementation.




And regarding the format of the proposal, have I missed anything? Do I need to 
include anything else? Please let me know your idea about that.




Thanks and regards




Nathiesha






Sent from Windows Mail





From: Awanthika Senarath
Sent: ‎Monday‎, ‎March‎ ‎21‎, ‎2016 ‎8‎:‎07‎ ‎AM
To: Nathiesha Maddage
Cc: dev@wso2.org, Jasintha Dasanayake







Hello Nathiesha ,



Please find my comments inline,






Regarding the Dev Studio, what  type of users are using it? Is it for the 
internal developers, external developers or for both? And when reporting the 
errors for the wso2 Jira, other than the information about the error, what 
information about users should be collected? I hope name and email would be 
sufficient enough.




It is for both. mainly it is for artifact development for WSO2 products and 
hence majority of the users are our customers, which would fall into external 
developers according to your categorization.




When considering the error reporting tool plugin found in Eclipse Mars, it 
provides a feature for the user to anonymize stack trace and anonymize messages 
if it contains sensitive data. Will that feature be useful for this proposed 
plugin as well?




Yes, +1. This would be a required feature since customers may have sensitive 
data they need to hide before reporting the error.




Other than the automatic error reporting to the wso2 Jira, an additional 
feature can be added to the plugin for the user to enter an email address, if 
he wishes to send the error report to some person/mailing list, only if that is 
useful. Furthermore should the plugin provide a way to contact the development 
team through the IDE? Like may be a menu item, that pops up a window that 
allows user to send a message/email to the development team? Or is it just the 
automated error reporting functionality expected?




We need to discuss this internally in the team. I'll provide you feedback later 
on this. 




Regarding the Jira wso2 online supporting system, I came through Jira Rest APIs 
that allows to access Jira services. Can those be used to access wso2 online 
supporting system as well? Or is there any other way or separate API for wso2 
online supporting system ?




You can use Jira rest APIs to access WSO2 support JIRA system.




And as additional features, would it be useful if reporter is provided on a 
feedback, where reporter can track the error and view the progress if he is 
interested? And also maybe to keep track of the errors sent previously and skip 
reporting the similar errors?




+1 these would be interesting features to have if you can integrate them with 
the task given. 







Regards

Re: [Dev] GSoc 2016-Proposal 16

[nathieshamaddage]

Hi all,




I will add the additional features to the project as you have suggested

I tried creating a draft high level architecture diagram for the project. And I 
also started with creating the draft proposal. The link is given below.




https://docs.google.com/document/d/12JqluYhlcWAN8kqxfTcwVrH_ylKaf3sNvevodOxwRho/edit?usp=sharing




The draft architecture diagram and its components are briefly described their. 
I didn't completed the implementation part and other latter parts completely 
yet. 




Regarding the architecture diagram, please let me know if that fits the purpose 
or any changes need to be done? For some use cases, I have denoted in the 
diagram as separate modules for easy visualization and scalability purposes. 
But certain modules can be integrated together into a single module if needed, 
during implementation.




And regarding the format of the proposal, have I missed anything? Do I need to 
include anything else? Please let me know your idea about that.




Thanks and regards




Nathiesha






Sent from Windows Mail





From: Awanthika Senarath
Sent: ‎Monday‎, ‎March‎ ‎21‎, ‎2016 ‎8‎:‎07‎ ‎AM
To: Nathiesha Maddage
Cc: dev@wso2.org, Jasintha Dasanayake





Hello Nathiesha ,



Please find my comments inline,






Regarding the Dev Studio, what  type of users are using it? Is it for the 
internal developers, external developers or for both? And when reporting the 
errors for the wso2 Jira, other than the information about the error, what 
information about users should be collected? I hope name and email would be 
sufficient enough.




It is for both. mainly it is for artifact development for WSO2 products and 
hence majority of the users are our customers, which would fall into external 
developers according to your categorization.




When considering the error reporting tool plugin found in Eclipse Mars, it 
provides a feature for the user to anonymize stack trace and anonymize messages 
if it contains sensitive data. Will that feature be useful for this proposed 
plugin as well?




Yes, +1. This would be a required feature since customers may have sensitive 
data they need to hide before reporting the error.




Other than the automatic error reporting to the wso2 Jira, an additional 
feature can be added to the plugin for the user to enter an email address, if 
he wishes to send the error report to some person/mailing list, only if that is 
useful. Furthermore should the plugin provide a way to contact the development 
team through the IDE? Like may be a menu item, that pops up a window that 
allows user to send a message/email to the development team? Or is it just the 
automated error reporting functionality expected?




We need to discuss this internally in the team. I'll provide you feedback later 
on this. 




Regarding the Jira wso2 online supporting system, I came through Jira Rest APIs 
that allows to access Jira services. Can those be used to access wso2 online 
supporting system as well? Or is there any other way or separate API for wso2 
online supporting system ?




You can use Jira rest APIs to access WSO2 support JIRA system.




And as additional features, would it be useful if reporter is provided on a 
feedback, where reporter can track the error and view the progress if he is 
interested? And also maybe to keep track of the errors sent previously and skip 
reporting the similar errors?




+1 these would be interesting features to have if you can integrate them with 
the task given. 







Regards

Awanthika











Awanthika Senarath
Software Engineer, WSO2 Inc.

Mobile: +94717681791




On Sun, Mar 20, 2016 at 8:15 PM,  wrote:




Hi ,




Thank you. I will look into the ‘IDeveloperStudioLog’ class to get an idea 
about the logging information.




I’ve got some more questions regarding the project and developer studio. 




Regarding the Dev Studio, what  type of users are using it? Is it for the 
internal developers, external developers or for both? And when reporting the 
errors for the wso2 Jira, other than the information about the error, what 
information about users should be collected? I hope name and email would be 
sufficient enough. 

When considering the error reporting tool plugin found in Eclipse Mars, it 
provides a feature for the user to anonymize stack trace and anonymize messages 
if it contains sensitive data. Will that feature be useful for this proposed 
plugin as well?




Other than the automatic error reporting to the wso2 Jira, an additional 
feature can be added to the plugin for the user to enter an email address, if 
he wishes to send the error report to some person/mailing list, only if that is 
useful. Furthermore should the plugin provide a way to contact the development 
team through the IDE? Like may be a menu item, that pops up a window that 
allows user to send a message/email to the development team? Or is it just the 
automated error reporting functionality expected? 

Re: [Dev] GSoc 2016-Proposal 16

[nathieshamaddage]

Hi ,




Thank you. I will look into the ‘IDeveloperStudioLog’ class to get an idea 
about the logging information.




I’ve got some more questions regarding the project and developer studio. 




Regarding the Dev Studio, what  type of users are using it? Is it for the 
internal developers, external developers or for both? And when reporting the 
errors for the wso2 Jira, other than the information about the error, what 
information about users should be collected? I hope name and email would be 
sufficient enough. 

When considering the error reporting tool plugin found in Eclipse Mars, it 
provides a feature for the user to anonymize stack trace and anonymize messages 
if it contains sensitive data. Will that feature be useful for this proposed 
plugin as well?




Other than the automatic error reporting to the wso2 Jira, an additional 
feature can be added to the plugin for the user to enter an email address, if 
he wishes to send the error report to some person/mailing list, only if that is 
useful. Furthermore should the plugin provide a way to contact the development 
team through the IDE? Like may be a menu item, that pops up a window that 
allows user to send a message/email to the development team? Or is it just the 
automated error reporting functionality expected? 


Regarding the Jira wso2 online supporting system, I came through Jira Rest APIs 
that allows to access Jira services. Can those be used to access wso2 online 
supporting system as well? Or is there any other way or separate API for wso2 
online supporting system ?


And as additional features, would it be useful if reporter is provided on a 
feedback, where reporter can track the error and view the progress if he is 
interested? And also maybe to keep track of the errors sent previously and skip 
reporting the similar errors?


Regards


Nathiesha










Sent from Windows Mail





From: Awanthika Senarath
Sent: ‎Sunday‎, ‎March‎ ‎20‎, ‎2016 ‎4‎:‎36‎ ‎PM
To: nathieshamadd...@gmail.com
Cc: Jasintha Dasanayake, dev@wso2.org





Hello Natheisha,



Please find my inline comments,





However I noticed the logging class  wso2 plugin has provided. Does it use any 
IStatus Objects or log any additional plugin specific information/error codes 
other than the normal error log info Eclipse provides? If so it would be useful 
to know about those in detail, when designing the error report format that need 
to be sent to the central server.




Please checkout the code and check the "IDeveloperStudioLog" class. this is the 
interface used to log information (warning, error etc) in developer studio. you 
can trace the implementation of this "DeveloperStudioLog" class and check how 
the logging is handled. If you need further information on this get back to us 
with specifics.




I studied about the error log file and how the error related information like 
meta Data, stack trace, system configuration info, java version, OS version and 
info about bundles, plugins involved, can be fetched into the proposed plugin, 
to create the error report to be sent. Is there any other information that I 
have missed and that should be included when sending the error report?




These information appears to be sufficient. Please check with the information 
that are being logged in Mars eclipse. 







And as you have replied to my previous email, it is clear that Eclipse platform 
errors as well as the devStudio plugin errors need to be reported. What about 
the expected errors where user expects, like exception to be thrown in 
particular situations like network not available, invalid license, resource 
blocked by another person etc. ? Should these be ignored or reported just like 
the internal unexpected errors?

 

I believe we need to report all errors irrespective of its nature. @ Jasintha : 
could you provide you opinion on this?






And when it comes to the development of the proposed plugin, what would be the 
most suitable target platform that would be compatible with Developer Studio? 
Is it eclipse version 3.5 or higher?




Currently you can test with the latest released developer studio 3.8.0 on top 
of Eclipse Luna. We are planning to release Developer studio on Mars in the 
near future. We will inform you once the release is ready so that you can do 
development on that.










Regards

Awanthika








Awanthika Senarath
Software Engineer, WSO2 Inc.

Mobile: +94717681791




On Sun, Mar 20, 2016 at 11:56 AM,  wrote:




Hi Jasintha,




I am currently working on making a high level architecture diagram for the 
proposed tool. I will send it to you asap along with the draft proposal, so you 
can give your suggestions about it, whether I am in the right track and if any 
improvements need to be done for that.




Meanwhile I encountered with certain issues, that I need a little clarification 
about.






I installed Developer Studio to get a basic idea about its plugins and overall 
structure. I guess 

[Dev] GSoc 2016-Proposal 16

[nathieshamaddage]

Hi Jasintha,




I am currently working on making a high level architecture diagram for the 
proposed tool. I will send it to you asap along with the draft proposal, so you 
can give your suggestions about it, whether I am in the right track and if any 
improvements need to be done for that.




Meanwhile I encountered with certain issues, that I need a little clarification 
about.






I installed Developer Studio to get a basic idea about its plugins and overall 
structure. I guess I need not have a detailed understanding about its 
functionality for this project, as the project mainly focuses on errors. 


However I noticed the logging class  wso2 plugin has provided. Does it use any 
IStatus Objects or log any additional plugin specific information/error codes 
other than the normal error log info Eclipse provides? If so it would be useful 
to know about those in detail, when designing the error report format that need 
to be sent to the central server.


I studied about the error log file and how the error related information like 
meta Data, stack trace, system configuration info, java version, OS version and 
info about bundles, plugins involved, can be fetched into the proposed plugin, 
to create the error report to be sent. Is there any other information that I 
have missed and that should be included when sending the error report?


And as you have replied to my previous email, it is clear that Eclipse platform 
errors as well as the devStudio plugin errors need to be reported. What about 
the expected errors where user expects, like exception to be thrown in 
particular situations like network not available, invalid license, resource 
blocked by another person etc. ? Should these be ignored or reported just like 
the internal unexpected errors?





And when it comes to the development of the proposed plugin, what would be the 
most suitable target platform that would be compatible with Developer Studio? 
Is it eclipse version 3.5 or higher?



Regards

Nathiesha




Sent from Windows Mail





From: Jasintha Dasanayake
Sent: ‎Friday‎, ‎March‎ ‎18‎, ‎2016 ‎6‎:‎56‎ ‎AM
To: Nathiesha Maddage, dev@wso2.org









On Thu, Mar 17, 2016 at 8:55 PM,  wrote:




Hi Jasintha,




Can I get an idea about the possible errors that might occur in the developer 
studio?? And should the error reporting plugin detect WSO2 plugin errors as 
well as Eclipse errors?




Basically  you should capture all type of errors happen while working with a 
Developer studio plugin ,




Thanks and Regards

/Jasintha

 









Regards




Nathiesha






Sent from Windows Mail








-- 


Jasintha Dasanayake
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware





mobile :- 0711368118___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] GSoc 2016-Proposal 16

[nathieshamaddage]

Hi Jasintha,


Can I get an idea about the possible errors that might occur in the developer 
studio?? And should the error reporting plugin detect WSO2 plugin errors as 
well as Eclipse errors? 


Regards


Nathiesha






Sent from Windows Mail___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev