Re: [commops] GSoC 2017 org applications open ( sourcing interest and ideas)

[Brian Exelbierd]

-All the original lists, now in BCC - with a new list in To.

Note: My webmail client is terrible and won't let me directly fix the
reply-to, so please mind it and lets move this traffic to the GSoC list.

I am replying to this everyone on the original thread as we need to work
together to make this deadline.

I have started an etherpad with the requirements for the Organizational
Application (due on Feb 9 - 2 days!):

http://etherpad.osuosl.org/TFx0SpB4S6

Please add anything you have and suggest text! It is easier to edit than
create, so even if you aren't confident, toss some ideas on the pad. 
English grammar and editing is easy - coming up with new text is not!

We also need to iterate ideas.  Radka has has been working on the
updated wiki pages and you will find them at:

Main page: https://fedoraproject.org/wiki/GSOC_2017
Student application:
https://fedoraproject.org/wiki/GSOC_2017/Student_Application_Process
Ideas: https://fedoraproject.org/wiki/Summer_coding_ideas_for_2017

Please add your project ideas and additional edits there.

You may find some source material in the wiki and here:
http://etherpad.osuosl.org/fedora-gsoc-welcome-2016

Corey Sheldon - thank you for kicking off this thread.

I think we can still make this deadline with our powerful community
effect.

Thinking forward to 2018, I intend to make this process easier by
committing our final answers to something durable, like a pagure repo so
they don't get lost.  This will help us not have to recreate all the
data next year.  I have also added a calendar reminder for myself to
remember to start the application earlier and to start us on project
generation earlier.  This snuck up on me this year.  I firmly believe
that things only get to do that once :).

regards,

bex

On Thu, Jan 19, 2017, at 11:15 PM, Corey W Sheldon wrote:
> As some of you may know, every year Google hosts the Google Summer of
> Code (GSoC), last year we participated with some decent results for a
> few projects.  I was just sending this heads up to those whom may be
> interested in partaking as a mentor or student (even if you are already
> a fedora contributor) for a project within Fedora.
>
> Basic requirements for students and ideas are below and find the full
> lowdown at [0].
>
> What are the eligibility requirements for participation?
> You must be at least 18 years of age
> You must currently be a full or part-time student (or have been
>
> accepted for the fall term) at an accredited university as of the
> student acceptance date
> You must be eligible to work in the country you will reside in during
>
> the program
> You have not already been accepted as a Student in GSoC more than once
> You must reside in a country that is not currently embargoed by the
>
> United States. See Program Rules for more information.
>
> Prospective students: read the Student Manual [1]
>
> Prospective Mentors: read the Mentors Manual [2]
>
> [0] https://developers.google.com/open-source/gsoc/faq
>
> [1]
> https://developers.google.com/open-source/gsoc/resources/manual#student_manu...
>
> [2]
> https://developers.google.com/open-source/gsoc/resources/manual#mentor_manua...
>
> Hopefully I will see some of you among the applications.
>
> -- 
> Corey W Sheldon
> M:703.839.6609:|:D:310.909.7672
> PGP:|:0x4B1616F5BDFCC807:|:0x151D53B9C62FA404:|
> |:0x418E43BCA33F2A72:|:|:0xA82F0594E76CB213:|:|:0x6B4FFDF3D89BCFA5:|
> |:https://keybase.io/linuxmodder:%7C:https://ameridea.github.io:%7C
> |:https://cs.danychtech.com
>
> A goal is not always meant to be reached, it often serves simply as
> something to aim at. --Bruce Lee
> Absorb what is useful, discard what is not, add what is uniquely your
> own. --Bruce Lee
> Any man willing to sacrifice security for convenience, is deserving of
> neither. -- Benjamin Franklin
>
> Disclaimer: All correspondence shall be deemed of a sensitive nature,
> and not re-distributed without good cause or  per-approval.
> All Emails shall be GPG signed or carry a attached vcf/asc blob, any
> email lacking this shall be treated with healthy skepticism.
> _______________________________________________
> Fedora Community Operations (CommOps) mailing list --
> [e-mail]
> To unsubscribe send an email to [e-mail]
> Email had 2 attachments:
> sheldon_corey.vcf
> 1k (text/x-vcard)
> signature.asc
> 1k (application/pgp-signature)

[commops] GSoC 2017 org applications open ( sourcing interest and ideas)

[Athos Ribeiro]

Hello,

I do have a proposal for GSoC, should I just include it in the ideas
page? It involves my masters degree research, which is in the static
analysis field.

I'd rather have someone from either the static analysis SIG or infra
mentoring me on it, but I would not be opposed to mentor a student on it
if I cannot find a mentor. I already sent an email to the guys in the
Static Analysis SIG (https://fedoraproject.org/wiki/StaticAnalysis) this
week.

I attached the message I sent to the SIG.
> For conducting my research, I need a database with static analysis
> reports from different analyzers in different software versions.  I
> ping'd Dave Malcolm in IRC a while ago about mock-with-analysis. At
> first I wanted to use it to perform my analyses and fill such database.
> Now I realize the problem is simpler and I am proposing a more generic
> system to perfor such analyses. The idea is to have something similar to
> Debile [4], performing analyses on fedora packages (C/C++ only at the
> first moment) but I want something a bit more extensible, which we could
> also point to git repositories or other sources.
>
> Later, we want to compare the reports from different package versions
> (maybe using Kamil's  codescan-diff [5]) to display only the warnings
> introduced in the latest package version (we believe this would help
> developers avoid looking into some false positives).
>
> At the moment, we are proposing the system architecture and I will
> probably start implementing something this week. Whenever I have some
> data to share, I would like to take on some dmalcolm ideas I read in the
> mailing lists and make it available in something like
> check.fedoraproject.org.
>
> Do you have any thoughts on it? Also, I am thinking in proposing such
> system to Fedora GSoC this year. Would any of you like to mentor me on
> that?  Otherwise, I would probably be able to mentor someone to work on
> it with me (if we get any students).
>
> [1] https://fedoraproject.org/wiki/StaticAnalysis
> [2] www.usp.br
> [3] https://samate.nist.gov
> [4] https://github.com/Debian/debile
> [5] https://github.com/kdudka/csdiff

[commops] GSoC 2017 org applications open ( sourcing interest and ideas)

[Brian Exelbierd]

On Wed, Feb 8, 2017, at 06:32 PM, Athos Ribeiro wrote:
> Hello,
>
> I do have a proposal for GSoC, should I just include it in the ideas
> page? It involves my masters degree research, which is in the static
> analysis field.

yes,

https://fedoraproject.org/wiki/Summer_coding_ideas_for_2017 yet.  Please
add it.
> I'd rather have someone from either the static analysis SIG or infra
> mentoring me on it, but I would not be opposed to mentor a student on it
> if I cannot find a mentor. I already sent an email to the guys in the
> Static Analysis SIG (https://fedoraproject.org/wiki/StaticAnalysis) this
> week.

If you are comfortable being the sole mentor, definitely get it added. 
If you need help, try to line that up first, but you may want go ahead
and add it today.  We can remove it before applications get started in
March if it isn't going to work out.

regards,

bex
> I attached the message I sent to the SIG.
> > For conducting my research, I need a database with static analysis
> > reports from different analyzers in different software versions.  I
> > ping'd Dave Malcolm in IRC a while ago about mock-with-analysis. At
> > first I wanted to use it to perform my analyses and fill such database.
> > Now I realize the problem is simpler and I am proposing a more generic
> > system to perfor such analyses. The idea is to have something similar to
> > Debile [4], performing analyses on fedora packages (C/C++ only at the
> > first moment) but I want something a bit more extensible, which we could
> > also point to git repositories or other sources.
> >
> > Later, we want to compare the reports from different package versions
> > (maybe using Kamil's  codescan-diff [5]) to display only the warnings
> > introduced in the latest package version (we believe this would help
> > developers avoid looking into some false positives).
> >
> > At the moment, we are proposing the system architecture and I will
> > probably start implementing something this week. Whenever I have some
> > data to share, I would like to take on some dmalcolm ideas I read in the
> > mailing lists and make it available in something like
> > check.fedoraproject.org.
> >
> > Do you have any thoughts on it? Also, I am thinking in proposing such
> > system to Fedora GSoC this year. Would any of you like to mentor me on
> > that?  Otherwise, I would probably be able to mentor someone to work on
> > it with me (if we get any students).
> >
> > [1] https://fedoraproject.org/wiki/StaticAnalysis
> > [2] www.usp.br
> > [3] https://samate.nist.gov
> > [4] https://github.com/Debian/debile
> > [5] https://github.com/kdudka/csdiff
>
> -- 
> Athos Ribeiro
>
> http://www.ime.usp.br/~athoscr
>
> -- 
> Athos Ribeiro
>
> http://www.ime.usp.br/~athoscr
> _______________________________________________
> summer-coding mailing list -- [e-mail]
> To unsubscribe send an email to
> [e-mail]