Hi,
I had a quick talk with Andrea today (that was a random choice, he was
the first to ask for my status), and summarized a set of things to do
before we start with the coding. I would detail each item in a separate
mail, and hope for some discussion. :)
1. We need to decide on a revision control system
2. Assemble a reading list
Since you are all computer scientists with a bit of background, and
have not worked with wavepacket propagation, it would be a good idea
to spend some time on refreshing the math/physics background.
I would talk this over with Burkhard, which books would be a good
read for introduction and the numerical stuff, and what
knowledge or topics you should aim for as an orientation.
3. Add you to the project, so that you have permission to modify things.
4. Naming the project
5. Decide on a ticket system to keep track of what is being done, to do
etc.
6. Update the roadmap / tasks what to do
Since we are now 4 people, we are enough for two parallel
development tracks. The current, very primitive, roadmap does not
accomodate that.
7. Converge to a coherent objective (mostly I have to write the
motivation in a way that is, well, motivating, but if you have
input, that would be fine).
8. I had a bit more ideas regarding programming language. This I would
like to discuss.
If 8. is settled, a few more things have to be discussed:
9. We need to decide on a build system.
10. We need to come up with some coding conventions as far as it makes
sense now.
11. We need to figure out and play around a bit with prospective
libraries.
Ulf
|
