Re: Regarding Mentors for GNOME-Continuous Project



Hey Colin, Sri,

So, since we haven't been able to find a mentor yet, we are instead thinking of working on the Coala project [1] (as a part of QA this time), which so far has Lasse Schuirmann as one of the mentors. Basically this project is about getting continuous static code analysis to the developers. So it will consist out of two parts:


1. HTML output for coala - Which Lasse will me mentoring,

2. Integrating the output into GNOME Continuous - Continuous would need to execute coala for all projects providing a simple configuration. - This is the part which needs another mentor. (This essentially reduces the burden of having one person solely mentoring our continuous projects, unlike last year). [2]


I'd be happy to know what you guys think about it. And it would also be good to inculcate coala as a part of QA as and when its ready!



Regards,

Shivani


[1] https://github.com/coala-analyzer/coala

[2] https://wiki.gnome.org/Outreach/SummerOfCode/2015/Ideas


On Fri, Mar 6, 2015 at 11:15 PM, Sriram Ramkrishna <sri ramkrishna me> wrote:
On Fri, Mar 6, 2015 at 5:46 AM, Colin Walters <walters verbum org> wrote:
> Hi Shivani,
>
> Unfortunately I haven't found an available mentor for Continuous yet.  I'd
> like to do it myself but unfortunately this is a 5-10% time project for me
> now that the underlying ostree component became more important for my
> employer.
>
> Is anyone else able to mentor?
>

I would love to see this happen. I'd mentor if I had the technical depth.

sri

> On Tue, Mar 3, 2015, at 02:02 PM, Shivani Poddar wrote:
>
> Hello!
>
> This mail is in regard to a project that I was a part of last year, and also
> helped in starting with the GNOME-QA. The focus of the project as listed
> earlier on was to "Enable GNOME to detect bugs early and improve the overall
> quality of applications. Several projects have started using dogtail scripts
> for tests, this idea will help new projects to adopt tests, improve them and
> make use of CI in GNOME".
>
> As a part of the project me and my co-intern worked to write tests for few
> of the GNOME Components, documenting the same in the QA Wiki [1]. I had also
> written a series of blogs about the same, because of which we saw
> significant applicants in the subsequent OPW rounds who were interested in
> taking up the project with ease.
>
> I would like to take this project further this year too (As a part of the
> Google Summer of code 2015 programme ) , and hope to exhaust the list of the
> components we need to cover as soon as possible. This would not only enable
> us to achieve automated testing, but also ensure a foundational testing
> framework in place for the developers to take forward on.
>
> Given, that the mentors for the project last year may not be able to mentor
> the same this time, I'd request for anyone interested to please suggest me
> about how this can be taken forward.
>
>
> Thank You,
> Shivani Poddar.
>
> [1] https://wiki.gnome.org/MartinSimon/AppsPriorityList
>
>
>
> _______________________________________________
> gnome-continuous-list mailing list
> gnome-continuous-list gnome org
> https://mail.gnome.org/mailman/listinfo/gnome-continuous-list
>
>
>
> _______________________________________________
> gnome-continuous-list mailing list
> gnome-continuous-list gnome org
> https://mail.gnome.org/mailman/listinfo/gnome-continuous-list
>
_______________________________________________
gnome-continuous-list mailing list
gnome-continuous-list gnome org
https://mail.gnome.org/mailman/listinfo/gnome-continuous-list



--
Shivani Poddar.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]