I didn't received any answer to my post.
Sorry, I don't recall seeing the previous post.
Does this means this kind of problem is considered secondary for developpers ?
You can propose whatever changes you think will be beneficial.
However, if the developers feel that those changes will be detrimental to Mailman or to using Mailman on other platforms, I believe that they're highly unlikely to accept them.
If the changes are felt to be beneficial, then they are more likely to be accepted. If they are minor, they may be slipped in earlier during the development and maintenance process. If they are larger, then you are likely to have to wait longer, as more code restructuring is likely to be necessary to accommodate them.
In any event, you'll have to wait for Barry (or one of the other developers) to find the time necessary to incorporate them, and where you get in this process will depend on their personal priorities.
At this point, I would suggest getting into the code and start mucking about. Post your suggested changes and why you think they should be made, and let's discuss.
-- Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
