Hi again, I've uploaded my draft proposal and the link is https://docs.google.com/document/d/1vRlm5vFJXcCJ7bkMPY6JRzdk90jelnsPNGtrCs8TkSE/edit?usp=sharing .
Please provide some feedback on what I have missed, what more I can include and such. I am extremely sorry that this comes so late. Best regards On 24 March 2016 at 18:29, Awanthika Senarath <[email protected]> wrote: > Hello Chanuka, > > please find my comments inline, > > I went through the DevStudio kernel and have a few questions. I'd be ever > so grateful for your answers. > > 1. The DeveloperStudioLog class doesn't include any control scheme to > limit reporting multiple cases of the same error in short time periods. > Reporting all cases seems like a nuisance, especially if it's an intended > error. > Would limiting such successive reports cause any harm? One way would be to > pause/ stop reporting the same error after, say, 10 close occurrences. > > you can include your suggestions in your proposal. > > 2. Should the error report be fully automated and not interact with the > developer at all? > It seems better to allow the developer to attach a message along with the > report. That way the internal devs can get contextual info as well. > > the error report should contact the developer as it should ask for his > consent which is the normal procedure. > > You can decide on how best to implement it. > > 3. Developers would be interested in getting feedback for what they > report and want to track the progress on issues. This could be implemented > as an opt-in feature, along with anonymization. > > Yes, it would be a nice to have feature. > > Feel free to prioritize and include your ideas in the proposal. If you > need any information on the current implementation or more information on > anything drop us a mail. > > Regards > Awanthika > > Awanthika Senarath > Software Engineer, WSO2 Inc. > Mobile: +94717681791 > > > > On Thu, Mar 24, 2016 at 12:11 PM, Chanuka Wijayakoon < > [email protected]> wrote: > >> Hello everyone, >> >> I went through the DevStudio kernel and have a few questions. I'd be ever >> so grateful for your answers. >> >> 1. The DeveloperStudioLog class doesn't include any control scheme to >> limit reporting multiple cases of the same error in short time periods. >> Reporting all cases seems like a nuisance, especially if it's an intended >> error. >> Would limiting such successive reports cause any harm? One way would be >> to pause/ stop reporting the same error after, say, 10 close occurrences. >> >> 2. Should the error report be fully automated and not interact with the >> developer at all? >> It seems better to allow the developer to attach a message along with the >> report. That way the internal devs can get contextual info as well. >> >> 3. Developers would be interested in getting feedback for what they >> report and want to track the progress on issues. This could be implemented >> as an opt-in feature, along with anonymization. >> Thoughts? >> >> Best regards >> >> On 24 March 2016 at 09:11, Chanuka Wijayakoon <[email protected]> >> wrote: >> >>> Great, I'll get back to you with a draft proposal today. >>> >>> Thank you. >>> >>> On 24 March 2016 at 08:12, Awanthika Senarath <[email protected]> >>> wrote: >>> >>>> Hello Chanuka, >>>> >>>> What we expect is something similar to eclipse mars implementation. >>>> >>>> The latest released developer studio is on Eclipse Luna, and the next >>>> release would be on Eclipse Mars which would be release within this >>>> quarter.You can checkout the Developer Studio kernel code and get a basic >>>> understanding on the code level. >>>> >>>> You can go ahead and start creating your proposal. >>>> >>>> Regards >>>> Awanthika >>>> >>>> Awanthika Senarath >>>> Software Engineer, WSO2 Inc. >>>> Mobile: +94717681791 >>>> >>>> >>>> >>>> On Tue, Mar 22, 2016 at 8:01 PM, Chanuka Wijayakoon < >>>> [email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> I am Chanuka Wijayakoon, a 2nd year undergraduate at the Department of >>>>> Computer Science & Engineering in University of Moratuwa. I'm interested >>>>> in >>>>> building a semi-automated error reporting extension for DevStudio as a >>>>> GSoC >>>>> 2016 intern. >>>>> >>>>> I have selected this proposal after carefully considering my skills >>>>> and past experience in working with Java and related technologies. I have >>>>> a >>>>> special interest towards building Eclipse plugins. >>>>> >>>>> So far I have researched on existing solutions for automated error >>>>> reporting and came across the AERI of Eclipse Mars as a model solution. It >>>>> provides developers with a rich set of features to report errors in >>>>> Eclipse >>>>> to a central server with relevant metadata. It integrates with the Eclipse >>>>> RCP as part of the EPP. >>>>> >>>>> As I understand, a viable solution for proposal 16 would be of similar >>>>> design tailored for DevStudio users. Currently I'm studying how DevStudio >>>>> (based on Eclipse Luna 4.4) differs from Eclipse Mars 4.5, implementation >>>>> details of EPP & JIRA usage. >>>>> >>>>> I'd be grateful if you could tell me whether I'm headed in the right >>>>> direction and suggest anything to further read or work on to familiarize >>>>> with your system. >>>>> >>>>> Best regards, >>>>> >>>>> >>>>> Chanuka Wijayakoon >>>>> Mobile: +94 779 089 737 >>>>> <https://lk.linkedin.com/in/chanukawijayakoon> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>> >>> >>> -- >>> Chanuka Wijayakoon >>> Mobile: +94 779 089 737 >>> <https://lk.linkedin.com/in/chanukawijayakoon> >>> >> >> >> >> -- >> Chanuka Wijayakoon >> Mobile: +94 779 089 737 >> <https://lk.linkedin.com/in/chanukawijayakoon> >> > > -- Chanuka Wijayakoon Mobile: +94 779 089 737 <https://lk.linkedin.com/in/chanukawijayakoon>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
