aero|oreaMail
So I received a message from Mark Cushman last night about my changes to AeroMail. He liked them but he didn't want to implement all of the MySQL features. He basically thought that LDAP is a more widely used solution for storing user address books and options. He basically summed things up by saying that the features that I've added to AeroMail are not part of the straight line path that he is taking from version 1.4 to version 2.0 of AeroMail.
I'm cool with that and he has every right as the author of the program to decide where it's going to go. I just don't want to do a code fork. He suggested that I change the name of my code base to something else so as not to confuse users with a name like aeromail-mysql or something like that. So in my first attempt at coming up with a name I tried OreaMail(orea being aero spelled backwards). I went ahead and changed some things in the tarball and released my modified aeromail to the aeromail mailing list as OreaMail 1.0. Before I fell asleep last night I thought of a better name. WindMail. Since Aero is like air I thought Wind would be a nice related name and also it's a pun on windmill. There could be a little logo with envelopes as the blades on a windmill. Ok.....
So I recieved a message from someone on the aeromail list today saying that the changes I made were great and that they were just what he was looking for. That got me a bit hyped up and now I think I might continue on with my fork of AeroMail. But I think what I will do is everytime I make a new release of WindMail, I will also submit the changes back to the aeromail list and likewise whenever a new version of AeroMail is released I will try to incorporate the changes back into WindMail. That way they evolve somewhat as sister programs.
11:54pm
Hmmm, obviously the advogato software doesn't do input checking very well. As I was able to make myself a doubter of project universe by telneting to port 80. Not that I shouldn't be a doubter, but I shouldn't be allowed to be one officially I guess.