Hello Matthias, Matthias Paulmier <matthias.paulm...@etu.u-bordeaux.fr> writes:
> I put up the first draft for my proposal here : > <matthias.paulmier.emi.u-bordeaux.fr/proposal.pdf>. I think this is a good first draft. A few comments: - For the “Project” and “Plan” parts, feel free to expand on the functional and non-functional requirements, based on previous discussion (for example the fact that the AST will probably have a coarse grain) and from your personal intuition. It doesn't matter if your intuition doesn't match with what I have in mind, it will just be a good occasion to discuss the project in more details. - Regarding the example script deliverable, I think you can precise that a set of examples that can be manually tested will be provided. If it helps you and fit your workflow (for example if you want to do TDD or similar), you can add some automated unit tests however this is not a requirement. - For the documentation, this doesn't have a high priority. I will be happy with just some basic docstrings specifying the functional contract of subroutines. > The communication part still needs to be discussed. As for the plan tell me > what > you think. Regarding the communication. For the weekly status update and discussion, if that's OK with you I would rather have a VOIP one on one conversation (via Ring or Jitsi) when possible and use email as a fallback or complement. Regarding the instantaneous communication IRC is convenient for me. Thanks. -- Mathieu Lirzin GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
