Google Summer of Code

Dear All,

Has someone registered LLVM as an organization for Google Summer of Code 2015? I'm interested in mentoring a GSoC student this summer.

-- John T.

I believe Anton was going to do so.

John,

Yes, I'm taking care about application as usual.

John,

Yes, I'm taking care about application as usual.

Thanks, Anton!

-- John T.

John,

Yes, I'm taking care about application as usual.

I saw the the LLVM mentoring org was accepted. Congrats!
Anton, could you tell me what is the procedure of submitting a proposal for a project (I will be the mentor)?
Many thanks,
Vassil

Please provide a patch to Open Projects list.

Hi Anton,
   (CC-ing the people who might be interested to review)
   I am attaching the patch.
Many thanks,
Vassil

CopyPasteDetectorGSoC15.diff (3.99 KB)

+Easily, some of the code snippets end up being copied dozens of
+times, which leads to worse maintainability, understandability and logical
+design.

The project description stresses code maintainability and logical design more than bug finding due to omissions in copy and pasted code. Reading this made me think of a check that would suggest people to replace copy and pasted code with a function call or something like that… Examples do stress the specific bugs that could be found, which is what I had in mind:

  • Copy-paste infrastructure could be used to build other “goodies”. Some
    +examples and possible applications are:

Is this intentional? If not, maybe we could rephrase a bit with more emphasis on bug finding. I would also make it a requirement to use the infrastructure for bug detection.

Thanks for driving this!
Anna.

Should be better now. Well, partially yes, I wanted to have the project description as broad as possible so that interested students to specialized in a direction, in which they are most comfortable. Because IMO the project is bigger than 1 usual GSoC project. I rephrased it to make it more focused towards bugs. Could you elaborate on the “I would also make it a requirement to use the infrastructure for bug detection.”, please? BTW, please feel free to submit a patch to the patch (:)), if you think something else requires fixing or better wording. Sure, thank you for reviewing! Vassil

CopyPasteDetectorGSoC15_v2.diff (4.23 KB)

I would prefer not to have pure infrastructure, but rather develop infrastructure along with uses of it. Bug finding is one such use. That would allow to set clear goals for the students and allow for better qualification of the infrastructure.

(However, I see your point about making it open to students that are interested in using this infrastructure for other projects.)

I see your point and I agree. I really want the proposal up soon. Can we discuss that in IRC, I think it would be easier for me? My nickname is vvassilev. Many thanks, Vassil

I see your point and I agree. I really want the proposal up soon. Can we discuss that in IRC, I think it would be easier for me? My nickname is vvassilev.

I am not going to be online in the next couple of hours. I would just rewrite this a bit to make it clear that we expect some useful features being developed along with the copy and paste detection with bug finding as an example. Writing those features would be part of the project.

If a student is interested in a feature other than bug finding, I’d expect them to specify what that is when they apply. (As far as I recall, the students also write proposals. I am not sure what is the workflow when they reply to our proposal.)

I think the proposal is generally good. I’d just emphasize feature driven development in the goals.

Anna.

Maybe Anton knows better. AFAIK the organization proposals give the idea of what can be done, later the students and the mentors make a proposal and based on that a slot for the student is allocated and a student is picked up. Thanks, see the 3rd version attached. Vassil

CopyPasteDetectorGSoC15_v3.diff (4.56 KB)

Maybe Anton knows better. AFAIK the organization proposals give the idea of
what can be done, later the students and the mentors make a proposal and
based on that a slot for the student is allocated and a student is picked
up.

So far we never explicitly required students to always select a
project from the list. If he / she can propose something useful and
there is a mentor around - why not?