[GSOC] Proposal for "Modularize Automake to improve the test-suite performance"

[Matthias Paulmier]

Hello,

I am candidating for the project "Modularize Automake to improve the
test-suite performance"

As you may have noticed, this is my second proposal for the GSoC to the
Automake project. You may have also noticed that 2 other persons are
interested in this other project. This is why I have decided, after
speaking with Mathieu Lirzin, that it would be a wise idea to candidate
to other projects or project ideas. The goal of the summer of code is
not to have a race with other candidates. As Mathieu told me, there may
be multiple students working for Automake under his mentorship.

You will find my proposal for this subject here :
matthias.paulmier.emi.u-bordeaux.fr/proposal_am_2.pdf. Please give me
feedbacks on this proposal. I am conscious it is bit lackey as I have
thought more about the previous one (for example I don't know what to
add to the deliverables).

I have been advised to look at other projects but as I said, I didn't
find much interest in other projects either because of technical or
philosophical aspects. I will however take a second look at other
projects from GNU as there has been new idea submissions since I
candidated here and if I find interesting projects I will likely make a
proposal tonight (CET) or tomorrow and keep you informed.

Thanks.
--
Matthias Paulmier

[Mathieu Lirzin]

Hello,

Post by Matthias Paulmier
I am candidating for the project "Modularize Automake to improve the
test-suite performance"
As you may have noticed, this is my second proposal for the GSoC to the
Automake project. You may have also noticed that 2 other persons are
interested in this other project. This is why I have decided, after
speaking with Mathieu Lirzin, that it would be a wise idea to candidate
to other projects or project ideas. The goal of the summer of code is
not to have a race with other candidates. As Mathieu told me, there may
be multiple students working for Automake under his mentorship.

To be precise I will mentor at most 2 students. :-)

Post by Matthias Paulmier
matthias.paulmier.emi.u-bordeaux.fr/proposal_am_2.pdf. Please give me
feedbacks on this proposal. I am conscious it is bit lackey as I have
thought more about the previous one (for example I don't know what to
add to the deliverables).

This project is highly iterative, meaning that you will have to define
the modules you will be writing based on what you analyse while
refactoring. So for the deliverables a "set" of modules is fine.

The idea is that the modules should be written so that they can be
easily testable (without requiring convoluted mocks for
example). Ideally you can define the qualities (like low coupling) that
the written modules should have.

The most important part in this proposal should be the description of
the various testing strategies that you intend to use and the generic
software architectures that could help with the modularity goal. If you
are not familiar with either Testing or Architecture concepts for
example with terms like blackbox/whitebox testing, you should consider
studying those concepts in the community bounding phase.

Regarding the plan I think the beginning should contain at least the
following two things:

* A rewrite of the few existing unit tests with Test::More to get
familiar with the framework.

* An analysis phase with the production of a small report containing
some informal UML diagrams representing the current architecture of
'automake'.

Post by Matthias Paulmier
I have been advised to look at other projects but as I said, I didn't
find much interest in other projects either because of technical or
philosophical aspects. I will however take a second look at other
projects from GNU as there has been new idea submissions since I
candidated here and if I find interesting projects I will likely make a
proposal tonight (CET) or tomorrow and keep you informed.

IMHO with 2 proposals you should be fine in particular with this
"Modularize" project that doesn't get much traction. But feel free to
look around. :-)

Thanks.

[Matthias Paulmier]

Hello and sorry for the late response, I didn't expect to have so much
work to do for school this week end.

I have uploaded an updated version of the proposal for this subject. I tried
to take into consideration your suggestions.

Post by Mathieu Lirzin
The most important part in this proposal should be the description of
the various testing strategies that you intend to use and the generic
software architectures that could help with the modularity goal. If you
are not familiar with either Testing or Architecture concepts for
example with terms like blackbox/whitebox testing, you should consider
studying those concepts in the community bounding phase.

I am somewhat familiar with those concepts but will surely strengthen
this during the community bonding period.

Post by Mathieu Lirzin
IMHO with 2 proposals you should be fine in particular with this
"Modularize" project that doesn't get much traction. But feel free to
look around. :-)

I finally didn't apply to any other project.

Thanks.
--
Matthias Paulmier